Enterprise Architecture: Johnson & Johnson Case Study Report

This report delves into the realm of Enterprise Architecture (EA), commencing with an introduction to the subject and a detailed case study of Johnson & Johnson, analyzing the company's transformation into a customer-centric system and the problems encountered during implementation. It proposes solutions and examines the Zachman Framework's applicability. The report then explores various EA frameworks, including TOGAF, FEA, and Gartner, comparing their methodologies and processes. It also constructs Entity-Relationship Diagrams (ERDs) for a milk dairy and Quikfix Electronics to illustrate data requirements. Furthermore, the report reviews journal articles on the impact of Big Data and Cloud Computing on EA, discussing the challenges and benefits of their integration. The report concludes with a summary of findings, emphasizing the successful analysis of EA applications and frameworks.

Running head: ENTERPRISE ARCHITECTURE
Enterprise Architecture
Name of the Student
Name of the University
Author Note

1ENTERPRISE ARCHITECTURE
Table of Contents
Introduction................................................................................................................................2
Case Study..................................................................................................................................2
Problem in the implementation..............................................................................................2
Solution for the framework....................................................................................................2
Zachman Framework.............................................................................................................3
Enterprise Architecture Framework...........................................................................................3
Entity Relationship Diagram......................................................................................................5
Milk Dairy..............................................................................................................................6
Quikfix...................................................................................................................................7
Journal articles review................................................................................................................8
Big Data and Enterprise Architecture....................................................................................8
Cloud Computing and Enterprise Architecture......................................................................9
Conclusion..................................................................................................................................9
References................................................................................................................................11

2ENTERPRISE ARCHITECTURE
Introduction
Enterprise architecture deals with the structural and organizational approach to
viewing a business organization. This report intends to discuss about the provided case study
in terms of an Enterprise system (Iacob et al. 2014). The report also discussed about the
transformation of the system into a customer-centric, big data and cloud computing
implementation in Enterprise system, comparison of different methods and framework of EA
analysis, ERD development, the relationship between EA and SOA (Service Oriented
Architecture) with the analysis of proposed processes from the University of Newcastle.
Case Study
Johnson & Johnson is a large healthcare pharmaceutical company, which is also
dealing in medical devices for the firms. The case study shows the process of transforming an
Enterprise System into a more customer-centric system.
The problem in the implementation
The company has multiple operating companies for the overall process. The customers of the
company have to deal with the interactions more than once and at numerous places for their
invoices. Previously the company's primary aim was to focus on the business rather than the
customers' comfort. Now the company has decided to be more towards the customer-centric
approaches (Srisamran and Ractham 2014). The main problem occurred in this change that
the company now have to collaborate their infrastructure as the Information Technology that
deals with a corporate strategy. It means every involved person have to aware of the IT in
terms of the corporate and operating level.

3ENTERPRISE ARCHITECTURE
Solution for the framework
To successfully apply this change, some policies of the company has to be changed in
terms of IT. The structure of the management is built in a way that it only manages the
revenues and the services. To become a customer centric company, some corporate strategies
will require to adapt to the employees and the company. For making this adaptation easier,
the company has introduced some training programs for the employees. Also, the Funding for
the company was first decided according to the operating companies. However, now they
think that establishing new infrastructure and all these new training programs will require a
funding method that will be based on a corporate strategy.
Zachman Framework
Zachman framework is one of the available models for analysing the Enterprise
Architecture for developing a business organization that has a variety of complex
information. The Enterprise Architecture aligns the business structure and the information
technology together with achieving the aim of the company (Korpela et al. 2013). It provides
a different perspective of analysing the information technology system. In the mentioned case
study, the Zachman fits as it requires the classification of their functions, operating
companies and invoices for their customer. In term of business, there is no change in the aim
and goals of the company. However, the new infrastructure is going to be implemented with
the existing one, and the Zachman framework is best for analysing a system where the current
system is kept for further development.
Enterprise Architecture Framework
Proposed Method
The proposed processes for the Enterprise Architecture were mainly related to the
policies of Business and its strategies. It ensures that the architecture is aligning with the

4ENTERPRISE ARCHITECTURE
business requirements and needs. The linkage of the two different architecture of IT and
business is also shown in the case study. Transition maps are provided in the architecture
layer to create a roadmap. The designing is consist of various processes that include the high
level context diagram, subject area model and detailed models of subject matter description.
Enterprise Architecture Frameworks
As it is known, the Zachman framework helps is analysing the Enterprise Architecture
and by providing a structural and organizational view. It is best for developing a taxonomy
based Architecture in a system. It establishes a link between the enterprise system and
information technology where the main focuses of the framework are data, network, time,
people, function and motivation (Korpela et al. 2013). Also, with these foci points, there are
six players in perspective that are enterprise, designer, subcontractor, builder, owner and
planner.
In the present time, TOGAF (The Open Group Architectural Framework) is the widely used
frameworks in any business organization. It has the very powerful standard tools and
software for best practice of Enterprise System Project managements (Desfray and Raymond
2014). It provides the planning, designing, implementation and managing phases for the
development.
On another hand, FEA (Federal Enterprise Architecture) is a US-based, federal
government Enterprise Architecture Framework. It is the newest type of framework which
deals with the modelling, partitioning and perspective evaluation to build a stable architecture
(Al-Nasrawi and Ibrahim 2013).
Gartner framework does not confirm any structural classification. However, it has an
advantage over the moving parameters and objects, keeping the aim of the organization in the

5ENTERPRISE ARCHITECTURE
concept. Business focus, practice guidance, and value management analysis is done
effectively in this Framework (Rouhani et al. 2013). Gartner framework is not the same as
the remaining three frameworks.
Relationship between EA and SOA
Service-Oriented Architecture (SOA) and Enterprise Architecture both are the integral
strategic to stabilise the organisation in the way of alignment and discipline between business
and Information Technology. However, it has been seen that very few organisations have
combined benefit of this two architecture (Kistasamy, Van Der Merwe and De La Harpe
2010). However, both the frameworks have similar architectural domains, and the aim is to
align the IT and business. Also, both use the business objective based input and require
similar planning and strategies. The things between camps of these two EA and SOA has
become more complex in terms of prioritizing of the importunate of alignment and discipline.
In terms of SOA practitioners, it is not identified tat how one can keep the existing EA while
performing the SOA framework. On the one hand, SOA provides Customer-oriented IT. On
another hand, there is an argument over the co-existence of EA in SOA.
Entity Relationship Diagram
Entity-relationship Diagram is the basically structural view of the entities, attributes and
relationship between them. It shows the logical and conceptual schema of the database
(Lagerström et al. 2013). An ERD in designing phase can help in defining the requirements
in an Enterprise system development.

6ENTERPRISE ARCHITECTURE
Milk Dairy
Figure 1: Milk Dairy ERD
Source: Created by author

7ENTERPRISE ARCHITECTURE
Quikfix
Figure 2: Quikfix ERD
Source: Created by author

8ENTERPRISE ARCHITECTURE
Journal articles review
Big Data and Enterprise Architecture
Today's organizations have become very complex in terms of the generation of the
data and a variety of data. The complexity of the data also depends on the source of the data
like from the customers, suppliers etc. and usually resides on the different sections of the
organization. This complexity makes the data hard to retrieve and analyse properly (Kaisler
et al. 2013). The main challenges for these organisation in working with big data is to
discover an effective way of accessing the data in time. The implementation is supposed to
help the existing IT structure and enterprise services. However, the problem domain is more
technical in big data implementation rather than managing the implementation in the business
organization. Study shows that 55% of the company that implemented big data in their
infrastructure has failed for multiple reasons. The reasons in the big data projects can be due
to the unclear aim of the company in the earlier phases of the development (Cameron 2014).
The use of the new integration is definitely analysed and defined in the planning phase. The
poor planning can lead any project to the failures. Apart from the failures, it can divert the
project's outcome in different opposite directions or just produce inaccurate outcomes. As
discussed, the big data resides in the different section of the company or organization; it is
also hard to access those data in the first place. The timing and completeness of the data also
affect the outcomes in the data analysing phase. Even the lack of communication between the
management and employees or other stakeholders can fail the whole project. The stakeholder
communication can disrupt as the big data is a totally new technology in terms of data
management systems. Hence it's also possible that they behave reluctantly towards the idea of
the implementation. Also, one reason for the failure can be that a big data management is
totally technical functions while the business system has nothing to do with it.

9ENTERPRISE ARCHITECTURE
Support of Enterprise Architecture
In terms of support of big data in enterprise architecture, the implementation part of
the big data is needed to be handled very carefully. The training programs can help the
development by a good practice (Wang, Kung and Byrd 2018). It requires the capturing and
understanding the requirements for EA to support the existing system by careful planning,
training and testing before the launch of the product.
Cloud Computing and Enterprise Architecture
The recommendations in Application security and encryption: The recommendations I
this implementation of cloud computing deals with the applications, strategy and data
perspective. They have become safe after the encryption of the data and information (Aureli,
Pierfranceschi and Wache 2012). To avail the security measurements, one company should
define these business rules for encryption.
a. It is compulsory to encrypt each credential id application has Credential Credential.
b. If application usesFile File then it is mandatory that each File hasEncryptionStorage
Encryption Method.
c. If application usesFile File then it is mandatory that each File hasEncryptionUsage
Encryption Method.
Conclusion
The provided case studies helped a lot to analyse the Enterprise system and its various
frameworks. This report discussed about the problem statement and its solution for the
Johnson & Johnson Company to change their infrastructure as more centric towards the
customer. Their system is also successfully evaluated with the Zachman framework. Later the
comparison between different framework has been introduced and the relationship between
the Enterprise Architecture and Service-Oriented Architecture. The Entity-Relationship

10ENTERPRISE ARCHITECTURE
diagrams for Milk Dairy system and Quikfix Electronics are also developed to understand the
data requirement for the enterprise syetem better. Later the failure of big data
implementations and cloud computing security in EA also discussed. Hence it can be said
that the objectives of the report have been successfully achieved by the full analysis of the
Enterprise System Application.

11ENTERPRISE ARCHITECTURE
References
Cameron, B.H., 2014. The Need for Enterprise Architecture for Enterprise-Wide Big
Data. I/S: A Journal of Law and Policy for the Information Society 10, p.827.
Kistasamy, C., Van Der Merwe, A. and De La Harpe, A., 2010, October. The relationship
between service oriented architecture and enterprise architecture. In 2010 14th IEEE
International Enterprise Distributed Object Computing Conference Workshops (pp. 129-
137). IEEE.
Iacob, M.E., Meertens, L.O., Jonkers, H., Quartel, D.A., Nieuwenhuis, L.J. and Van
Sinderen, M.J., 2014. From enterprise architecture to business models and back. Software &
Systems Modeling, 13(3), pp.1059-1083.
Srisamran, P. and Ractham, V.V., 2014. Customer-centric knowledge creation for customer
relationship management. Journal of Applied Business Research, 30(2), p.397.
Korpela, K., Kuusiholma, U., Taipale, O. and Hallikas, J., 2013, January. A framework for
exploring digital business ecosystems. In 2013 46th Hawaii International Conference on
System Sciences (pp. 3838-3847). IEEE.
Desfray, P. and Raymond, G., 2014. Modeling enterprise architecture with TOGAF: A
practical guide using UML and BPMN. Morgan Kaufmann.
Rouhani, B.D., Mahrin, M.N., Nikpay, F. and Nikfard, P., 2013, September. A comparison
enterprise architecture implementation methodologies. In 2013 International Conference on
Informatics and Creative Multimedia (pp. 1-6). IEEE.
Wang, Y., Kung, L. and Byrd, T.A., 2018. Big data analytics: Understanding its capabilities
and potential benefits for healthcare organizations. Technological Forecasting and Social
Change, 126, pp.3-13.

12ENTERPRISE ARCHITECTURE
Kaisler, S., Armour, F., Espinosa, J.A. and Money, W., 2013, January. Big data: Issues and
challenges moving forward. In 2013 46th Hawaii International Conference on System
Sciences (pp. 995-1004). IEEE.
Lagerström, R., Baldwin, C., MacCormack, A. and Dreyfus, D., 2013, November.
Visualizing and measuring enterprise architecture: an exploratory biopharma case. In IFIP
Working Conference on The Practice of Enterprise Modeling (pp. 9-23). Springer, Berlin,
Heidelberg.
Aureli, L., Pierfranceschi, A. and Wache, H., 2012, June. Enterprise architectures for cloud
computing. In 2012 IEEE Fifth International Conference on Cloud Computing (pp. 979-980).
IEEE.
Al-Nasrawi, S. and Ibrahim, M., 2013, June. An enterprise architecture mapping approach for
realizing e-government. In 2013 Third International Conference on Communications and
Information Technology (ICCIT) (pp. 17-21). IEEE.