Case Study: Bj's Wholesale Enterprise Architecture

Pages: 6 (2261 words)  ·  Bibliography Sources: 6  ·  Level: Master's  ·  Topic: Business  ·  Buy This Paper


[. . .] Timing and frequency

Frequency content varies rapidly depending on the conceptualization of time. MDM version 11 represents an attempt to utilize FT for a short-time analysis window. The system is analyzed while stationary and reacts reasonably according the requirements of the time-invariance. MDM signals are based on identification of coding theorems, and this provides frequency information on process dynamics without disturbing various sections of the system. Efficiency on parallel computation is characterized provides execution on time consisting of processors. Numerical efficiency and uniformity load balances (Das, 2011, pp. 129). The ratio of the execution of total time includes data exchange, computations, and message reception. For this reason, MDM system is subject to the nature of hardware preferences maintained by BJ. However, parallelization of the algorithm will naturally vary broadly depending on the problem and algorithm type. High-end task will be scheduled to queuing mechanism. Load balance is considered a statistical and dynamic orientation.

Equipments applied

For MDM 11 to operate coherently, there are several prerequisites that should be applied in order to meet the goals. The most component is MDM Standard Edition Workbench, which is commonly known as formerly Master Data Service Workbench. Secondly, it is proper to run an InfoSphere MDM collaborative edition, which acts as a server. A collaborative server-scripting workbench seconds this like Infosphere MDM collaborative edition client. Thirdly, for version 11 to work, it is necessary to operate an MDM Domain Hub stand Alone and InfoSphere MDM Customs domain hub stand-alone workbench. Finally, the version requires and MDM references Data Management Hub (Alur, 2009).

The version can also operate on the following operating systems AIX, Linux, Windows, and Solaris. However, Linux provides a variety of options for the batch and online system applications. WebSphere Application servers, system Z, and Websphere application server. It is also possible to install oracle WebLogic servers. For network building, a series of devices are applied; these are -- Mainframe servers, Desktop P.Cs, Laptops, Tablets, Routers, Switches, Wireless dispensers and Smartphone devices (Das and Mishra, 2011, pp. 131-133).

The above preferences are based on the complexity of MDM system. Binding decisions depend on the dynamic deployment conditions; this operates local availability of user preferences, and of course, terminal / software characteristics and the service terminal provision time. This presents a middleware that supports the accessibility of users / terminals of information services and mobile agent based on expanding proxies and user/terminal roaming and references transparently. Moreover, availability of docking points ensures the devices enjoy an unlimited connectivity, and this presents challenging scenarios for the services and context mobility.

Preceding and succeeding systems

According to the 21 principles of enterprise architecture, each principle presents various considerations that should be instituted as a response to possible unplanned incidents. According to TOGAF, each principle has a name, descriptions, and implications. This report has identified a number of preceding and succeeding systems, which can be applied in the MGM system. The succeeding system includes Device management. This is the centralized management of the device users applying the device. Once the devices are secured and configured in secured central point, it is necessary to establish a control mechanism so that information can be easily accessed, modified, or deleted with ease. The system admin manages the docking devices directly thereby minimizing the vulnerability of the risk data (Lamolle, 2013, pp. 25).

The succeeding system fosters are bridging the old with the new. The BYOD approaches expand MDM functionality. Servers communicate better with simpler devices like mobile phones at these levels. Secondly, the application part where the user applies the MDM to communicate with the four main systems named briefly; Warehouse management, Payroll, Gas and Point of sales on GUI interfaces. At this succession stage, the system bridges new back to the old. This promotes a user-friendly application robustly which communicates to the old system comprised of servers.


Alur, N. (2009). Master data management rapid deployment package for MDM. United States?: IBM, International Technical Support Organization.

Das, T.K., & Mishra, M.R. (2011). A Study on Challenges and Opportunities in Master Data Management. International Journal of Database Management Systems, 3(2), 129-139.

Haug, A., & Arlbjorn, J.S. (2011). Barriers to master data quality. Journal of Enterprise Information Management, 24(3), 288-303.

Lamolle, M., Menet, L., & Duc, C.L. (2013). Incremental checking of Master Data Management model based on contextual graphs. Enterprise Information Systems, 4, 1-28.

Nedumov, Y.R., Turdakov, D.Y., Maiorov, V.D., & Ovchinnikov, P.E. (2013). Automation of data normalization for implementing master data management systems. Programming… [END OF PREVIEW]

Enterprise Architecture Term Paper

Architecture of the Mind Sight Essay

Architecture Is at a Curious Crossroads Essay

Architecture Modernism Dissertation

Architecture's Response to Nature Term Paper

View 1,000+ other related papers  >>

Cite This Case Study:

APA Format

Bj's Wholesale Enterprise Architecture.  (2014, May 31).  Retrieved August 17, 2019, from

MLA Format

"Bj's Wholesale Enterprise Architecture."  31 May 2014.  Web.  17 August 2019. <>.

Chicago Format

"Bj's Wholesale Enterprise Architecture."  May 31, 2014.  Accessed August 17, 2019.