Enterprise Architecture Report: Cloud Computing, Big Data

This report delves into the realm of Enterprise Architecture (EA), examining its application in various contexts, including cloud computing and big data. It begins with a case study of Johnson & Johnson, identifying the challenges of a decentralized EA and proposing a centralized approach. The report then explores different EA frameworks, such as the Zachman framework, FEA, Gartner's EA Framework, and TOGAF, comparing their methodologies and applications. Furthermore, it addresses the integration of cloud computing and big data with EA, offering security recommendations for cloud environments and discussing the importance of EA in managing and analyzing big data. The report also includes ERD diagrams for a Quikfix repair shop and a milk dairy, illustrating data modeling principles. Finally, it examines the relationship between EA and SOA, highlighting their roles in aligning business strategies with IT solutions. The report also provides the importance of encryption to the storage of data within the cloud environment.

Running head: ENTERPRISE ARCHITECTURE
ENTERPRISE ARCHITECTURE
Name of student
Name of university
Author’s note:

1
ENTERPRISE ARCHITECTURE
Table of Contents
Johnson and Johnson case study....................................................................................2
Comparison of the framework of EA.............................................................................3
ERD diagram..................................................................................................................6
EA and cloud computing................................................................................................7
EA and big data..............................................................................................................8
References....................................................................................................................11

2
ENTERPRISE ARCHITECTURE
Johnson and Johnson case study
With the analysis of the case study of the Johnson and Johnson, it could be observed
that the major issue with the company is decentralised enterprise architecture. It mainly
prevented this company from making any kind of appropriate utilisation of IT resources from
various divisions of company. The centralised enterprise architecture is the solution that
could be proposed to the company. The centralised architecture mainly indicates that
significantly simplified availability of the sole or even several entities, which possess the
main control over the overall network. The introduction of the one-hop connectivity would be
done in this centralised approach but multihop network would be used in the situation of any
embedded systems working in short range. With the regards of security within the
organisation, any single centralised entity mainly needs the effective monitoring or
guaranteeing significant safety of entire network.
This specific network could be implemented in the organisation for allowing the
significantly efficient communication between various sectors of this company. With the
implementation of centralised architecture in the organisation, the prospect of any centralised
computing can be significantly achieved. This particular architecture could be utilised
effectively by Johnson and Johnson for providing the employees with all the required IT
resources. The centralised computing can be referred as the type of the computing
architecture where the majority of the processing or even the computing could be executed on
the single server. Centralised computing significantly permits the deployment of complete
computing resoures of company from any central server. This particular centralised system
significantly uses the architecture of Server/client where the connection of one or more client
computers are done to the central server. This particular type of network could be considered

3
ENTERPRISE ARCHITECTURE
as the most popular type of network that could be utilised by the organisation where any
clients sends request to company server and the server sends an appropriate response.
It could be observed in the presently developing world that the introduction of the
discipline Enterprise architecture has led to the structuring of several businesses as well as the
alignment with all IT systems of companies (Adhani, Abdillah and Widayati 2015). The
Zachaman framework is mainly referred as enterprise ontology and it could be described as
the most basic structure for enterprise architecture that provides all the required methods for
observing information systems as well as company from different viewpoints. After the
analysis of the companies from various viewpoints the main techniques of associated are
displayed that provides the idea about the connection among several components of
organisation (Ostadzadeh, Shams and Badie 2015). The main difficulties in the J&J
organisation are the management of the IT resources as well as the major alterations within
the market. The most important sector of this difficulty could be referred to the lack of the
adequate internal understanding of all the complex infrastructure along with the various
modules in various fields of the organisations where the legacy information about the
business has been prevented from accessing as it is maintained in the minds of specific
individuals or specific business units. The application of the framework is specifically correct
for the company, J&J as there has been the realisation of the need of significant integration of
business functions and the IT systems. This particular integration is intended to be achieved
with the implementation of several mutual standards. Presently, there has been the realisation
that the company requires to realign all the IT system with significantly advanced corporate
strategy.

4
ENTERPRISE ARCHITECTURE
Comparison of the framework of EA
Business architecture, the application architecture, information architecture as well as
technology architecture are some of the processes that has been proposed for EA. The
Zachman framework mainly includes the enterprise ontology and it could be referred as the
basic structure for enterprise architecture, which offers the most efficient procedure for the
observation of information systems within any company from several viewpoints and then
provides the main procedures of relation among several components of the organisation
(Bernal et al. 2016). The elements of systems development are distinctly identified with this
particular approach. Instead of the representation of all processes as any sequence of steps,
the emphasis has been put on the several players. It has helped in offering majority of the
organisations with efficient mechanism of assessment of comprehensiveness of the
development process models of software, in the terms of the information necessities of the
organisation. It could be analysed that common structure of Zachman framework mainly
includes the two dimensional classification methods for the descriptive representations of the
enterprises that has been mainly structured as any matrix, which comprises the 36 cells. Each
single of the cells significantly emphasising on sole perspective or dimension of the
enterprise. The columns within this particular framework mainly denotes the several
viewpoints of all stakeholders, which are involved within any organisation whereas the rows
mainly presents the distinct viewpoints that are included within process of the system
development.
Federated Enterprise Architecture or the FEA is mainly referred to the configuration
within any enterprise architecture, which allows the efficient interoperability and the effective
sharing of information with the decentrally semi-autonomous structured business lines,
applications and the systems of information technology (Antunes et al. 2015). The major
advantages of being extensively autonomous of any kind of global authority are likely to

5
ENTERPRISE ARCHITECTURE
compensate the main problems that are instigated by any kind of misinterpretations and the
incompatibilities (Demchenko et al. 2014).
Enterprise Architecture Framework of Gartner significantly emphasises on the fact
that any EA is related to integration of the three key constituents, namely the business
owners, the information experts and the implementers of technology. According to Gartner,
the EA project is required to be started after executing the efficient understanding of direction
of enterprise on business and simply not with analysis of present position of company.
The TOGAF architecture could be defined as architectural framework that is the
abbreviation of The Open Group Architectural Framework (Svee and Zdravkovic 2015). It
has been reflected as the significant tool that helps with the development of vast range of the
various IT architectures. Mostly, this particular framework mainly allows the evaluation, the
designing and then implementing the most appropriate architecture for any organisation. The
most crucial aspect of the TOGAF is that, this particular architecture is significantly
dependable, proven procedure for the development of any IT architecture that assists with
meeting each requirement of any business (Tao et al. 2017). TOGAF could be defined as the
enterprise architecture, which significantly offers the extensive level framework for
performing software development within the organisations. It assists with simplified
organisation of all the processes included in the development using the systematic approach.
This particular framework mainly intends to reduce the errors, effectively manage all the
timelines, efficiently handle the budget as well as helps in arranging all the prospects of the
IT resources in business units (Delima, Santoso and Purwadi 2016). This alignment helps
with generating significantly high results.
EA as well as the SOA are currently reflected as significant strategic disciplines
which provides any organisation with the tangible procedures of arranging the business with

6
ENTERPRISE ARCHITECTURE
IT, however due to misunderstanding of any relationship between these specific disciplines.
All the required answers are provided by the EA where the organisation vast processes, the
steps of arranging processes with the strategies as well as the procedures using which any
process is associated with performance measures are included. Significantly customer
responsive IT solutions are provided by the SOA along with the interfunctional
synchronisation of the information flows with the strong platform, which could be later
utilised by that business for establishment of applications.
ERD diagram
Figure 1: ERD diagram of Quikfix repair shop
Source: (Created by author)

7
ENTERPRISE ARCHITECTURE
Figure 2: ERD diagram of milk dairy
Source: (Created by author)
EA and cloud computing
The major suggestions regarding application security and encryption could be
categorised as:
 It is significantly vital to properly use the methods of encryption for executing
proper security to the storage of the data within the cloud environment. Similarly,
the protection to data is provided with use of the encryption procedures during
usage of the services within the cloud environment as well as within any external
system.
 It is required to properly manage the application credentials and the credentials are
required to be significantly secured and protected.

8
ENTERPRISE ARCHITECTURE
 The keys that have been utilised for executing the encryption of the data is
required to be protected efficiently during the tasks of transmitting, storing or
even the backup of the data (Web.fhnw.ch. 2019).
 It is required that the selected encryption system should conform to all the existing
standards of the government and the rules of industry
 It is easily possible that in any scenario of IaaS, the files in the virtual machine as
well as the temporary data needs significant encryption
 Constantly check whether encryption has been done on the data during the
transmission within the network of cloud provider. There is significant level of
security present in the cloud provider network and it is greater than the internet
but it could be easily shared among several customers.
EA and big data
In the present times, the enterprise architecture is referred as conceptual model that
primarily provides the general idea regarding the operation and structure of organisations.
The methods using which any organisation could accomplish all the future and present
objectives are mainly provided by the enterprise architecture. Machine generated data as well
as the human generated data are mainly included in the technology of big data. Primary
examples of machine generated data could be categorised as the call details records, the log
of any equipment, data generated from manufacturing sensors and data produced from
vehicle tracking systems while the human produced involves the data of customer feedback
streams, data of platforms of social media, images, call logs from CRM, video files, and data
gained from direct conversations with any supplier, customer or employees. With the
significant increase of quantity of the data that is presently being produced, one of the main
challenges for any enterprise is analysed as designing any appropriate system that could help
in efficient handling of data as well as the analysis of big data. The data that is generated

9
ENTERPRISE ARCHITECTURE
from the analysis of data could be then used by the decision makers for making the informed
decisions. Although big data is being considered as the significant asset in the present times,
it has been observed from the statistics that 61% of all the projects of big data could not
efficiently finished and many additional projects extensively fails due to objectives
(Kb.osu.edu, 2019). Many companies blindly create sophisticated databases and then start
collecting data on the basis of significantly unclear plan. The gathering of data is done
without the appropriate knowledge regarding the main requirement from the big data
technology and without the knowledge of this important field, the projects fails. In the present
business markets, main reason for the failure of projects of big data is mainly unsuccessful
due to the sitaution of not possessing the required business goal within the early stages of
projects. The initiation of various big data projects is done before properly defining all the
requirements of the organisation from the project and without properly defining the business
driver (Kb.osu.edu, 2019). The main reasons for the failure of projects of big data integration
in the organisations could be categorised as the failure of defining any clear and adequate
scope, lack of efficient collaboration within various stakeholders of organisation, lack of the
enterprise wide data access along with the issues of change management and the extensive
focus on big data technology instead of the business requirements.
The current gap in adequate implementation of the strategic planning which have been
cited by the researchers could be easily filled with the application of the practices of
enterprise architecture as enterprise architecture mainly intends to execute the analysis,
planning, developing and then implementing projects within the enterprise. Considering that
there are several benefits gained by the organisation from the implementation of projects of
big data could be easily alleviated. Assuming the absence of a appropriate business goal as
the primary cause of failure of projects of big data, the portfolio management is utilised by
the enterprise architecture that helps with the effective prioritising of the projects and the

10
ENTERPRISE ARCHITECTURE
efficiently allocating resources that are required by the processes. Besides this, efficient
governance of all IT projects that involves enterprise architecture, big data projects could
help in assuring the effective arrangement of the project with business strategy of the
organisation.

11
ENTERPRISE ARCHITECTURE
References
Adhani, M., Abdillah, L.A. and Widayati, Q., 2015, August. Analisa dan perancangan sistem
informasi penerimaan siswa baru dan pembayaran SPP menggunakan Zachman Framework.
In Seminar Nasional Informatika 2015 (SNIf2015). Universitas Potensi Utama.
Antunes, G., Barateiro, J., Caetano, A. and Borbinha, J., 2015. Analysis of federated
enterprise architecture models.
Bernal, W.N., Caballero, G.C., Sánchez, J.O. and Paéz-Logreira, H., 2016, May. Enterprise
architecture framework oriented to cloud computing services. In 2016 6th International
Conference on Computers Communications and Control (ICCCC) (pp. 64-69). IEEE.
Delima, R., Santoso, H.B. and Purwadi, J., 2016, October. Architecture Vision for Indonesian
Integrated Agriculture Information Systems Using TOGAF Framework. In 2016
International Conference on Informatics and Computing (ICIC) (pp. 66-71). IEEE.
Demchenko, Y., Ngo, C., de Laat, C. and Lee, C., 2014, March. Federated access control in
heterogeneous intercloud environment: Basic models and architecture patterns. In 2014 IEEE
International Conference on Cloud Engineering (pp. 439-445). IEEE.
Kb.osu.edu. (2019). [online] Available at:
https://kb.osu.edu/bitstream/handle/1811/75415/ISJLP_V10N3_827.pdf?sequence=1
[Accessed 10 Sep. 2019].
Ostadzadeh, S.S., Shams, F. and Badie, K., 2015. An architectural model framework to
improve digital ecosystems interoperability. In New trends in networking, computing, e-
learning, systems sciences, and engineering (pp. 513-520). Springer, Cham.

12
ENTERPRISE ARCHITECTURE
Svee, E.O. and Zdravkovic, J., 2015, June. Extending enterprise architectures to capture
consumer values: the case of TOGAF. In International Conference on Advanced Information
Systems Engineering (pp. 221-232). Springer, Cham.
Tao, Z.G., Luo, Y.F., Chen, C.X., Wang, M.Z. and Ni, F., 2017. Enterprise application
architecture development based on DoDAF and TOGAF. Enterprise Information
Systems, 11(5), pp.627-651.
Web.fhnw.ch. (2019). [online] Available at:
http://web.fhnw.ch/personenseiten/holger.wache/Papers/aureli-etal-12.pdf [Accessed 10 Sep.
2019].