Enterprise Architecture and Big Data

This article explores the relationship between Enterprise Architecture and Big Data, and discusses the main causes of failure in big data projects. It emphasizes the importance of clear business goals, proper planning, and effective implementation of changes. Desklib offers study material and solved assignments for Enterprise Architecture.

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

1ENTERPRISE ARCHITECTURE
Table of Contents
Portfolio 1.1:....................................................................................................................................2
Portfolio 1.2:....................................................................................................................................3
Portfolio 1.3:....................................................................................................................................5
Portfolio 1.4:....................................................................................................................................7
Week-3:........................................................................................................................................7
Week-4:........................................................................................................................................8
Week-7:......................................................................................................................................10
Portfolio 1.5:..................................................................................................................................12
Bibliography:.................................................................................................................................15

2ENTERPRISE ARCHITECTURE
Portfolio 1.1:
Main Problems: The main problem of the organization is that it has decentralized
structure that is not allowing to implement single point of contact. The managers of the
organization was accountable for running the business. This autonomous management structure
has provided profit to the organization, however, is now making the biggest issue in developing a
customer friendly approach. Another issue that organization is facing is proving high quality and
effective support to the consumers.
Aligning the IT with the freshly accepted corporate strategy is a problem for the
organization too. The organization is trying to provide training to the employees but it is not
resulting as effective as desired.
Solutions: The organization need to develop a manual for the system that can assist the
employee to interact with the system on their own. This is very vital for the employees because it
will boost their confidence and they will start to explore the system functionalities faster. J&J
needs a customer relationship management system that can facilitate the customer request
processing and customer response process. The organization can implement the CRM in the core
of the architecture so that newly proposed system can be user centric.
Zachman Framework: The Zachman Framework is considered to be one of the major
source of origin of enterprise architecture. This framework will allow J&J to examine, install and
customize newly proposed enterprise architecture frameworks, tools and methods. J&J can use
the Zachman Framework as a logical framework to classify and organize the expressive
showcasing of the enterprise. This enterprise representation will prove to be important for

3ENTERPRISE ARCHITECTURE
managing the proposed enterprise. J&J will use a grid view table or model to classify and
manage the description enterprise. In the grid model, there will be six different columns.
Figure 1: Example of Zachman Approach
(Source: Lapalme et al. 2016)
Portfolio 1.2:
Processes Proposed for Enterprise Architecture: The first process is business strategy
and IT strategy policies. These strategies makes sure that business requirements and priorities
can be aligned with architecture. The second process is enterprise architecture principles. These
principles provide high level direction for enabling the decision making. The second process
consist of architectural layer which has technical, application, business and information. These

4ENTERPRISE ARCHITECTURE
layers offer association among the technical architecture and business models. The next process
is transition plan which consist of target model, T1, T2 and current model. These transition plans
offer development roadmap. The next process is context diagram of high-level so that broader
picture can be presented. The subject area model is the next process and it allows association
among the projects and global context. The next process is the detailed models of the architecture
that entails the subject matter. The last process is technology standards and guidelines. This
process offers particular direction on developing the architectures.
Comparison between EA- Zachman, TOGAF, FEA, and Gartner: The Zachman
framework is considered to be logical structure that classifies and organizes the descriptive
illustration of an enterprise. It shows the architecture through a 6x6 matrix called grid model. US
DOD framework has been used for deriving the TOGAF framework. TOGAF enhances the
efficiency of business through offering a methodology. The The Open Group Architecture
Framework has architecture principles, architecture requirements, business architecture,
information system architecture, technology architecture and architecture realization. The
Federal Enterprise Architecture or FEA is referred to EA of federal government. The FEA offers
a basic technique regarding the integration of business, strategic and technology organization.
These integration is considered to be a part of the business performance and design.
Relation between EA and SOA: Both the enterprise architecture and Service oriented
architecture provides tangible factors of aligning the Information Technology with business.
SOA Concentrates on business process while EA concentrates on business architecture. In terms
of data architecture domain, the SOA works on data architecture and EA framework works on
information architecture. The SOA is limited to service modelling while the EA can work on
enterprise applications and application frameworks.

5ENTERPRISE ARCHITECTURE
Portfolio 1.3:
Figure 2: The Entity Relationship Diagram of Milk dairy
(Source: Created by Author)

6ENTERPRISE ARCHITECTURE
Figure 3: The Entity Relationship Diagram of Quikfix Electronics
(Source: Created by Author)

7ENTERPRISE ARCHITECTURE
Portfolio 1.4:
Week-3:
Answer to Question 1: The main area of values generated by the EA are: business
processes, functions, services and information systems which includes strategic direction and
business goals (Lapalme et al. 2016).
Answer to Question 2: The main risks associated with it are: Lack of understanding of
enterprise, business performance metrics, increasing solution costs, lack of effective governance,
decreasing user acceptance, confusion among stakeholders and distracting critical staff.
Answer to Question 3: It helps in developing the strategic goals by: Reviewing initiatives
with high priority against the high capabilities and resources if affects. The EA can be used to
target certain state architectures that can be built to deliver details to each initiative. EA can be
used to get together information from different resources to differentiate overlapping and
singular ideas. EA also helps the PMO to make better decisions against funding and resources.
Answer to Question 4: The EA can help the business services by supporting enterprise
level business agility and visibility. It helps the enterprise by letting it see the organizational
structure, business processes, information assets and application infrastructure.
Answer to Question 5: The EA will help enterprises view their technology by allowing
information environment changes respond to the needs of the enterprise in a controlled and
timely manner.
Answer to Question 6: The two best way to manage the risks are: 1. Accepting the risk
by identifying it and getting it registered to deal with it later. This is risk acknowledgement. 2.

8ENTERPRISE ARCHITECTURE
The risk can also be avoided when the enterprise can estimate beforehand the huge impact of the
risk.
Answer to Question 7: It provide technology related standards to the different levels of
EA framework. It also provides decision making support at the executive, management and staff
levels of the company. The EA also helps in identifying the operational and strategic
requirements. In these ways it connects to technology, business and strategy (Whittle and Myrick
2016).
Answer to Question 8 a: In a large or medium sized enterprise like Microsoft by
avoiding over focus of architecture on the allowance of currently running processes.
Answer to Question 8 b: The confusion between different stakeholders towards the
benefits of EA in a company like Microsoft can result in failure of its implementation (Niemi and
Pekkola 2017). The best way to mitigate this risk is by informing the stakeholders about the
benefit of EA.
Answer to Question 8 c: EA can help here by increasing the enterprise’s Operational
efficiency, Opportunity creation, Process effectiveness and automation efficiency.
Week-4:
Answer to Question 1: An EA implementation methodology can be described as a group
of methods, postulates and rules to plan, structure and implement the process of creating an EA
(Rouhani et al. 2015).
Answer to Question 2: The EA framework within EA methodology helps in scoping the
documentation work involved and helps in specifying the classification structure and types for
arranging EA work products or outputs.

9ENTERPRISE ARCHITECTURE
Answer to Question 3: The phase I activities in EA methodology established the EA
program and helps in preparing stakeholder communication plans.
Answer to Question 4: The phase III is depended on phase II because the EA framework
developed in phase II is needed for the implementation of the EA modelling in phase III
(Hinkelmann et al. 2016).
Answer to Question 5: In phase II, the EA standard is selected and customized with the
help of select EA software tools but in phase IV the already created EA components are updated
and the EA compliance is integrated in decision making.
Answer to Question 6: Yes, the steps of EA methodology can be changed for different
enterprises in order to accommodate the needs of those enterprises.
Answer to Question 7: The top management is usually responsible for the execution of
EA program and EA methodology.
Answer to Question 8: The EA should be updated continuously in order to always
maintain a high level and detailed view of the EA activities and resources for current and future
needs.
Answer to Question 9a: The phases and steps of a EIAM in a company like Microsoft
are: Panning, As-Is, To-Be, Implementation and Governance.
Answer to Question 9b: The following objectives must be implemented to get EA
stakeholder support: communication and understanding, internal monitoring, governance,
conformance and integration, partnership and readiness of change.

10ENTERPRISE ARCHITECTURE
Answer to Question 9c: The enterprise architecture updating schedule depends on the
needs of the business or organization it is implemented in.
Week-7:
Answer to Question 1: The current views of enterprise architecture elements has the
purpose of validating the business resources along with Information Technology resources for
supporting the strategic objective achievement. This assist the organization in making decisions
and conducting plans. This EA element present ‘As-Is’ enterprise view. The current elements
reveals the link, performance gaps and dependencies among the present capacity and business
requirements.
Answer to Question 2: The artifacts can be considered as the tangible forms that store or
describe the enterprise architecture at every level of the structure. The artifacts are consisted of
reports, charts, videos, spreadsheets, diagrams and many more. Regarding the current view, the
present architecture can be referred to the set of enterprise architecture artifacts which record the
present enterprise architecture components into a document. This documentation is done
throughout the enterprise for establishing an ‘As-Is’ enterprise view.
Answer to Question 3: The examples are future view artifact and current view artifact.
Answer to Question 4: IDEF-0 modelling is referred to as the function modelling
technique that can describe functions regarding manufacturing. The IDEF-0 provides a
modelling platform for evaluating, reengineering, development and integration of software
engineering, information system and business processes. The IDEF-0 will allow the organization
to execute strategic planning at the Products & Services level of the EA3 Cube Framework.

11ENTERPRISE ARCHITECTURE
Answer to Question 5: Unified Modelling Language or UML is referred to general
purpose standardized modeling language that represents visual object-oriented models of
software intensive applications. On the other hand, the ERD or entity relationship diagram is the
data model that represent every element of a database. The DFD shows how the data model will
distribute data among various external entities.
Answer to Question 6: The artifacts of EA in Applications & Services level are
capabilities, competitive advantages and business goals.
Answer to Question 7: Vendor-supplied documentation is important because it can serve
as the service level agreement.
Answer to Question 8: System Interface Diagram, System Data Flow Diagram System
Interface Matrix, databases, applications, network connectivity diagram, network inventory,
network center diagram and platforms are desired at the Network & Infrastructure level of the
EA3 Cube Framework.
Answer to Question 9: The Walmart in Australia uses EA3 Cube Framework. Strategic
goal of Walmart is to remain as the industry leader. The organization take initiatives to expand
business to various countries. The outcome of the framework is most retail stores in the country.
Current LOBs of Walmart is selling products through retail stores, being competitive in the
market and efficiently managing the huge amount of human resources. The business service is
product sell, after sale service, logistics and more.

12ENTERPRISE ARCHITECTURE
Currently the organization uses cloud database and applications for sharing data between
headquarter, retails stores, warehouse and logistics. Currently the organization has one data
center for storing all the data and a server to process all the user requests.
Portfolio 1.5:
EA and Big Data
There are five main causes for the failure of big data projects.
The first cause: Most big data projects fail due to the lack of clear business goals or
understanding of the requirements. It may also fail if the crucial requirements are missing. The
second cause: The second major cause is poor planning and failure to estimate the project scope.

13ENTERPRISE ARCHITECTURE
This can lead to failure of both big and small projects. The third cause: The challenges big data
experts face while trying to retrieve the internal data of a company is another cause for the
failure. Lack of cooperation between stakeholders may also lead to failure. The fourth cause:
The success of a big data project depends on the new changes being implemented in the project.
Failure to accept or implement changes may lead to the project failure. The fifth cause: Too
much focus on technology rather than business goals may lead to the project getting stuck in the
technology trap resulting in the projects failure (Cameron 2014).
Enterprise architecture can act as a bridge between execution and planning of the strategy. It can
be used to conduct planning, design, implementation and analysis of the company. The enterprise
architecture gives the user insights and holistic information to improve efficiency, effectiveness
and agility. It also focuses on the transformation of a business from the current state to a better
future state. It also helps in implementing the business strategy to products, processes and new
services (Cameron 2014).
EA and cloud computing
The main recommendations concerning the encryption and application security are:
The following recommendations are valid for all enterprises that are thinking of a
possible switch to a cloud based environment. According to the paper, the first recommendation
the author suggests that the application credentials should be managed properly. It is of
paramount importance to keep the credentials protected and secured. The second
recommendation states that the data in a cloud environment must be secured properly using
proper encryption. This encryption should be used to protect the data both inside the cloud
system and outside the system. The third recommendation states that the encryption that is

14ENTERPRISE ARCHITECTURE
chosen for encrypting the application credentials must also comply with the current existing
industry and government standards. The fourth recommendation states that the encryption keys
that are used to encrypt the data must also be protected while storing or moving them (Aureli,
Pierfranceschi and Wache 2012). The keys can be stored in emergency backups to protect them.
The fifth recommendation stated that it is also very important to check if the data is protected or
kept encrypted while it is being moved or accessed inside the cloud provider’s network. It is
usually seen that the cloud networks are generally more secure than the internet, but as the data is
being shared between multiple users it is always recommended to encrypt it. The sixth
recommendation stated that it is possible that while working in an IaaS scenario, there may arise
a need to encrypt even the virtual machine files and the temporary data to make the system more
secure and safe. If failed to implement the above mentioned cases, a possible data theft of private
information might occur.

15ENTERPRISE ARCHITECTURE
Bibliography:
Ahadi, A., Behbood, V., Vihavainen, A., Prior, J. and Lister, R., 2016, February. Students'
Syntactic Mistakes in Writing Seven Different Types of SQL Queries and its Application to
Predicting Students' Success. In Proceedings of the 47th ACM Technical Symposium on
Computing Science Education (pp. 401-406). ACM.
Ahadi, A., Prior, J., Behbood, V. and Lister, R., 2015, June. A quantitative study of the relative
difficulty for novices of writing seven different types of SQL queries. In Proceedings of the
2015 ACM Conference on Innovation and Technology in Computer Science Education (pp. 201-
206). ACM.
Al-Masree, H.K., 2015. Extracting Entity Relationship Diagram (ERD) from relational database
schema. International Journal of Database Theory and Application, 8(3), pp.15-26.
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.
Dick, J., Hull, E. and Jackson, K., 2017. Requirements engineering. Springer.
Evans, R., Richard, G. and Rogers, A., 2016. GSU Event Portal.
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.

16ENTERPRISE ARCHITECTURE
Kadam, K.S. and Onkar, V.C., 2015. A review paper on student information supervision system.
International Journal of Research In Science & Engineering, 1, pp.66-72.
Khan, F., Jan, S.R., Tahir, M., Khan, S. and Ullah, F., 2016. Survey: Dealing Non-Functional
Requirements at Architecture Level. VFAST Transactions on Software Engineering, 9(2), pp.7-
13.
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.
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.
Long, J.E., 2018. Relationships between common graphical representations used in system
engineering. INSIGHT, 21(1), pp.8-11.
Niemi, E. and Pekkola, S., 2017. Using enterprise architecture artefacts in an organisation.
Enterprise Information Systems, 11(3), pp.313-338.
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 Research
Challenges in Information Science (RCIS), 2015 IEEE 9th International Conference on (pp. 518-
519). IEEE.

17ENTERPRISE ARCHITECTURE
Putra, D.A., Jasmi, K.A., Basiron, B., Huda, M., Maseleno, A., Shankar, K. and Aminudin, N.,
2018. Tactical Steps for E-Government Development. International Journal of Pure and Applied
Mathematics, 119(15), pp.2251-2258.
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.
Whittle, R. and Myrick, C.B., 2016. Enterprise business architecture: The formal link between
strategy and results. CRC Press.