Enterprise Architecture: Case Study, Problems, Solutions, Zachman Framework, Gartner, FEA, EA-Zachman, TOGAF, EA and SOA, ERD, Big Data, Cloud Computing

This article discusses the case study of J&J and the main problems faced by the company. It also provides possible solutions to solve these problems. The application of the Zachman Framework in J&J is explored, along with a comparison of frameworks such as Gartner, FEA, EA-Zachman, and TOGAF. The relationship between EA and SOA is discussed, and entity relationship diagrams for Milk Dairy and Quikfix Electronics are provided. The article also reviews the relationship between EA and big data, as well as EA and cloud computing.

Running head: ENTERPRISE ARCHITECTURE
Enterprise Architecture
Name of Student-
Name of University-
Author’s Note-

1ENTERPRISE ARCHITECTURE
Table of Contents
Case Study.......................................................................................................................................1
Main problems in J&J..................................................................................................................1
Possible solution to solve the problems.......................................................................................1
Application of Zachman Framework in J&J...............................................................................3
Framework for Enterprise Architecture...........................................................................................3
Processes proposed for EA..........................................................................................................3
Comparing frameworks of Gartner, FEA, EA-Zachman, and TOGAF......................................4
Relationship between EA and SOA.............................................................................................5
Entity Relationship Diagram...........................................................................................................6
Milk Dairy ERD..........................................................................................................................7
Quikfix Electronics ERD.............................................................................................................8
Journal Article Review....................................................................................................................8
EA an Big Data............................................................................................................................8
EA and Cloud Computing...........................................................................................................9
References......................................................................................................................................11

2ENTERPRISE ARCHITECTURE
Case Study
Main problems in J&J
The problem existing in J&J was that the company was following autonomous structure
for management. This autonomous structure enables the managers only to deal with the financial
results for independent companies that are operating in J&J. The main focus of the managers in
the company was to make all the operating units of the company to run efficiently. The
companies lacked in making customer retention. By the companies services, the life of the
customer were facing problem. The problems that the customers were facing was the customers
themselves had to deal with their own multiple invoices, multiple contracts, as well as sales calls.
The company has to change the operating system and implement IT support system in all the
operating system of the company. For changing the IT focus on the company to a customer
entailed technology should be the main focus of the company. The IT system of the company
was not aligned to the corporate strategy.
Possible solution to solve the problems
For mitigating the problems of not providing attention to customer retention in the
company, there are many strategies that can be implemented in the system to improve the
system. For implementing customer retention in the company helps to increase the customer
value as well as encourage the customer to purchase again and again from the company. This
customer retention also results in using mobile application for buying products from the
company. The possible solutions that J&J can implement in the system are stated below:
1. Implementing onboarding program: This is a customer function that shows the
customer about how to us a particular product. A representative of the company explains the

3ENTERPRISE ARCHITECTURE
usage of the product from where the customer might learn about how the use the product. This
can helps to save the time of the customer and understand how their goals can be achieved.
2. Implement customer feedback: The Company should implement customer feedback
regarding the product or the service they get from the company. This customer feedback helps to
improve the business and know about the feeling of the customer. The process of customer
feedback as well as sharing the information with the company should be present with the
company so that they can improve the business operation and satisfy the customers. The
feedback loop helps to collect, analyze as well as distribute the review the customer and
customer survey.
3. Establish proper communication with the customer: If feedback is received from the
customer, proper feedback result is to be communicated with the customer so that the people get
to know about the status of their feedback provided for the company. Communication helps to
manage all the customer engagements as well as helps to create opportunities so that the
company can get upsell as well as get cross-sell. Communication calendar is to be established in
the company which helps to track the communication of customer.
4. Should implement customer loyalty program: The Company should organize loyalty
program for the customers. The customers can be rewarded for their loyalty to the company. The
customer who have bought more products from the company should be rewarded with more
offers so that the customer might feel happy with the customer’s service.
Application of Zachman Framework in J&J
The blueprints of the processes are the fundamental process of documentation and are the
primary way to analyze as well as sustain the organizational change in the system (Whittle and

4ENTERPRISE ARCHITECTURE
Myrick 2016). The blueprints of the processes in an organization is made as per some specific
goals and includes perspective of modeler. The conflicting specifications mainly exists in same
process and the techniques that assists in modelling tasks. No agreement is done on modelling
criteria that are used by the stakeholders of the company. J&J faces the problem of having
blueprint of same process and there is no formal processes for sorting out the relevance (Safari,
Faraji and Majidian 2016). The processes included in the business most of the time crosses the
number of organizational units and includes stakeholders and includes quality, security,
information technology and auditing. The process of blueprints also includes the perspectives of
the stakeholders and the interests of the stakeholders. To handle all these issues Zachman
Framework can be used in the working process of the business of J&J.
Framework for Enterprise Architecture
Processes proposed for EA
The main processes that are included in the development process for EA helps in
explaining sequence of activities included for building the framework that is to be included in
EA. The processes included in the EA helps in developing content that are to be included in the
business process of the organization. The EA of an organization includes blueprints that targets
the state included to develop the processes iteratively. The model included in EA states project
that closes some amount that limits the present state of the working process of EA modelling.
This framework helps to support gap analysis in the working process and includes impact
analysis within the company. The EA development process mainly includes many different
architecture viewpoints integrated in meeting the business needs and including the IT needs that
are included in the organization (Rouhani et al. 2015). The process of EA helps in achieving an
overview that are mostly present in company. This might include to achieve an overview that are

5ENTERPRISE ARCHITECTURE
present in organization and should include organization for achieving concept of EA. The
concept of EA also helps to identify all the main points comprising of gaps as well as topics
which helps to initiate the plans for identifying the gaps for rectifying the redundancies within
the company.
Comparing frameworks of Gartner, FEA, EA-Zachman, and TOGAF
Gartner Framework: The Gartner framework in an organization creates EIM vision that
helps organization to specify its business vision. The vision of the organization includes business
vision that include EIM (Enterprise Information Management) to enable the vision. This should
clear the business vision and support the EIM vision (Plataniotis, Proper and Kinderen 2015).
The framework also includes strategy as well as roadmap that is needed for the organization and
states the current status of the organization. This also helps to create business case for improving
the business outcomes as well as attainment of the business.
FEA Framework: The FEA framework mainly describes tools for helping the
government planners for implementing all common approach (Plataniotis et al. 2015). This
includes OMB as well as federal agencies for describing as well as analyzing the investments.
The FEA framework is the core of CRM and consists of different reference models for
describing the sub-architecture domains included in the framework. The six sub-architectures are
strategy, security, business, infrastructure, data and applications.
EA-Zachman Framework: This framework mainly provides some specific means for
classifying the architecture of the organization. This includes a proactive tool that is mainly used
for modelling the existing function of the organization. This also includes elements as well as
processes and manages the business changes that are included in the organization (Niemi and
Pekkola 2017). This particular framework is mainly the feedback of the Zachman’s experience

6ENTERPRISE ARCHITECTURE
about stating how the change is being managed for the complex products including the buildings
and airplanes. The Zachman framework is actually a two dimensional framework including
classification scheme representing the descriptions included in enterprise stating the matrix
containing 36 cells that mainly focuses on the dimension as well as perspective of enterprise.
There are different rows in this framework that states different viewpoints included in system
developments.
TOGAF Framework: This is a proven framework that is used for improving the
business efficiency of an organization (Lapalme et al. 2016). A prominent as well as reliable
architecture is provided by TOGAF framework that enables to handle the methods, and
communication in the organization. The organization using the TOGAF standards mostly enjoy
industry credibility, career opportunities, as well as job effectiveness. This framework also
enables the practitioners to avoid proprietary methods, utilize all the resources, as well as realize
the ROI of the company. This architecture is based on the best practices that are available.
Relationship between EA and SOA
The EA architecture mainly deals with entire scope or the concerns that are included in
the business. The main goal of this framework is to align the strategies as well as problems that
are faced in the business (Lange, Mendling and Recker 2016). The goals of the framework
includes to align the strategies as well as using of all the resources that are viewed in long term
vision of the organization. The EA framework uses all the tools that are available for conducting
analysis for entire process of the business.
SOA states Service Oriented Architecture compared with EA are used in different ways.
The framework of SOA can be used for establishing the software protocols as well as enable the
communication, the related resources, as well as helps to maintain the IT infrastructure that area

7ENTERPRISE ARCHITECTURE
associated in the organization (Kistasamy, Merwe and Harpe 2010). This framework actually
spends lot of time arranging layout of cloud computing and also helps in putting standards for
ensuring components that are functional in the business process.
The relationship between the EA and SOA is that EA contemplates the simple design
from strength standpoint, functionality standpoint as well as placing the resources (Kasemsap
2018). The SOA ensures all such operations that includes some specific services and ensures all
the operations that are included in the system. SOA framework is used for making the IT
organization better while the EA framework is used for making proper business process as well
as include proper technological approach.
Entity Relationship Diagram
Milk Dairy ERD
Figure 1: ERD Diagram

8ENTERPRISE ARCHITECTURE
(Source: Created by Author)
Quikfix Electronics ERD
Figure 2: ERD Diagram
(Source: Created by Author)
Journal Article Review
EA an Big Data
Main cause behind project failure related to big data
Main cause for big data project failure is the organization are not able to arrange the huge
amount of data that are generated in the organizations (Hinkelmann et al. 2016). These

9ENTERPRISE ARCHITECTURE
organization deals with large amount of data and are not capable of handling those huge data by
implementing small big data projects. The companies needs to implement complex projects that
are capable of organizing and handle large data sets in an organization.
Another main reason for project failure states that the EA that are implemented in the
organization do not have objective as well as goals so that they can handle the large amount of
data in the organization (Giachetti 2016). The businesses do not includes alignment for the
business included in the working process of the organization. The organizations also lacks in
data access for which the project fails.
EA used for big data project implementation
The framework of EA includes gap analysis that comes between the future state as well
as current state of the project. The framework of EA helps to reduce the gap in the project and
helps to complete the project on time (Chorafas 2016). The mission included in the company is
wide and includes strategic goal in the business and includes many products and the services
included in the organization (Cameron 2014). EA is used for implementation of big data is
because the system is mainly holistic that describes set that are related with the enterprise all
over the time. The purpose included to develop as well as describe the architecture of
organization are included in the system. With the EA architecture, the organization might include
different frameworks as well as strategies that can be used in the organization for many different
reason.
EA and Cloud Computing
Recommendations for application security and encryption

10ENTERPRISE ARCHITECTURE
1. This should include assessing of secure installation as well as helps to maintain
encryption control for the company or the organization.
2. There should be performance as well as security monitoring for all the elements that
are to be used for encrypting the control process in the system.
3. It should be able to access the main management processes.
4. The information security should also include reviews as well as helps in approving the
encryption requests that are to be included in the system.
5. This process also ensures performance as well as monitoring of security from all the
perspectives included in encrypting the control processes.
6. This information security ensures secured application as well as helps to maintain
equipment that supports encryption control.

11ENTERPRISE ARCHITECTURE
References
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.
Cameron, B.H., 2014. The Need for Enterprise Architecture for Enterprise-Wide Big
Data. ISJLP, 10, p.827.
Chorafas, D.N., 2016. Enterprise architecture and new generation information systems. CRC
Press.
Giachetti, R.E., 2016. Design of enterprise systems: Theory, architecture, and methods. CRC
Press.
Hinkelmann, K., Gerber, A., Karagiannis, D., Thoenssen, B., Van der Merwe, A. and Woitsch,
R., 2016. A new paradigm for the continuous alignment of business and IT: Combining
enterprise architecture modelling and enterprise ontology. Computers in Industry, 79, pp.77-86.
Kasemsap, K., 2018. The role of information system within enterprise architecture and their
impact on business performance. In Global Business Expansion: Concepts, Methodologies,
Tools, and Applications (pp. 1078-1102). IGI Global.
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.

12ENTERPRISE ARCHITECTURE
Lange, M., Mendling, J. and Recker, J., 2016. An empirical analysis of the factors and measures
of Enterprise Architecture Management success. European Journal of Information
Systems, 25(5), pp.411-431.
Lapalme, J., Gerber, A., Van der Merwe, A., Zachman, J., De Vries, M. and Hinkelmann, K.,
2016. Exploring the future of enterprise architecture: A Zachman perspective. Computers in
Industry, 79, pp.103-113.
Niemi, E. and Pekkola, S., 2017. Using enterprise architecture artefacts in an
organisation. Enterprise Information Systems, 11(3), pp.313-338.
Plataniotis, G., De Kinderen, S., Ma, Q. and Proper, E., 2015, July. A conceptual model for
compliance checking support of enterprise architecture decisions. In 2015 IEEE 17th Conference
on Business Informatics (Vol. 1, pp. 191-198). IEEE.
Plataniotis, G., Ma, Q., Proper, E. and de Kinderen, S., 2015, May. Traceability and modeling of
requirements in enterprise architecture from a design rationale perspective. In 2015 IEEE 9th
International Conference on Research Challenges in Information Science (RCIS) (pp. 518-519).
IEEE.
Rouhani, B.D., Mahrin, M.N.R., Nikpay, F., Ahmad, R.B. and Nikfard, P., 2015. A systematic
literature review on Enterprise Architecture Implementation Methodologies. Information and
Software Technology, 62, pp.1-20.
Safari, H., Faraji, Z. and Majidian, S., 2016. Identifying and evaluating enterprise architecture
risks using FMEA and fuzzy VIKOR. Journal of Intelligent Manufacturing, 27(2), pp.475-486.

13ENTERPRISE ARCHITECTURE
Whittle, R. and Myrick, C.B., 2016. Enterprise business architecture: The formal link between
strategy and results. CRC Press.
Zimmermann, A., Schmidt, R., Sandkuhl, K., Wißotzki, M., Jugel, D. and Möhring, M., 2015,
September. Digital enterprise architecture-transformation for the internet of things. In 2015 IEEE
19th International Enterprise Distributed Object Computing Workshop (pp. 130-138). IEEE.