Enterprise Architecture Analysis and Design

This assignment delves into Enterprise Architecture (EA) by applying industry standards like TOGAF and Archimate. It focuses on analyzing existing business processes and designing a target architecture to bridge the gap between current and desired state. The project uses visual diagrams, such as those provided in the Archimate tool, to communicate the findings and objectives effectively. Key aspects covered include Business Architecture design, gap analysis, stakeholder vision, baseline functions, and organizational structure.

Enterprise Architecture Applications
Word count- 1810(excluding references, table of contents, diagrams and executive summary)

Executive summary
ArchiMate is an open tool for graphical modelling of the enterprise architecture. The Enterprise
Architecture is give in three forms of layer they are business, application and system. In this
report the diagrams are done by using the ArchiMate tool gives a clear vision about the baseline
business architecture of the enterprise, baseline technology architecture, all business
applications, business functions, baseline business process, baseline information architecture,
application-alignment and co-ordination and the target architecture of the enterprise and analyses
of GAP.

Table of Contents
1. Introduction...........................................................................................................................2
2. Archimate diagrams from week 4 to week 11......................................................................2
3. Cost benefits analysis for the enterprise architecture.........................................................17
4. Conclusion..........................................................................................................................19
References..................................................................................................................................20

1. Introduction
Archimate is an independent and open tool for performing the graphical modelling of
enterprise architecture. With the assistance of TOGAF the notation of the Archimate is been
evolved. The Archimate diagrams is a view point that helps us to understand, communicate and
document the enterprise architecture. It gives a clear vision about the business domains. The
Archimate core defined by the TOGAF, the motivation of this project is to provide viewpoint for
the stakeholders, to view the target architecture, to analyses the goals of the business along with
the requirement and principles. The analysis of the GAP and the target architecture is will be
provided. This project provides a clear vision of the Business Architecture starting from week 4
to week 11, it also explains the application, business and system view of the enterprise
architecture. An architecture vision for the stakeholders concern will be provided and the
baseline business functions of the enterprise and the organization architecture will be provided.
2. Archimate diagrams from week 4 to week 11
A visual language that is used to capture the whole enterprise architecture is offered by the
Archimate tool. It includes processes, services, technical and data application of the organization
and the products and services. The Archimate tool is been used for the view point of the
stakeholders and to address the variety concern. The ArchiMate tool provides three layers
business, application and system/ technology. The services provided for the customers is been
given in the business layers, the application support that is provided to the organization is
provided in the application layer and the technical infrastructure is given in the technical layer
(Saha, 2012).
TOGAF is expanded as The Open Group Architecture Framework, that gives a clear
description about the supporting tools that is been used for developing the Enterprise
Architecture.
Commercial architectural assets involves
1. Business practices, business processes and business polices.

2. Information entities or concepts, relationship to the process of business.
3. Interfaces, relationship and the applications to the process of business.
4. Relationship and technologies to the applications.
The entire formal Enterprise architecture methods possess best practice which involves
1. establishment of target architecture
2. Establishment of baseline architecture
3. Gap analysis performance
4. Architectural roadmap development Migration plan development
Start with converting existing environment description into TOGAFA. It permits the team to
improve the architecture to get experience having the model and understanding their
components. Few adaptation might be needed to match the definition of the architecture methods
is explained in the process. Set down the key questions which is the significant part of the task. It
is used in the development process for measuring the new architecture effectiveness.

All relevant concepts of the Archimate and the Enterprise Architecture is been given in the
viewpoint of the ArchiMate. In the viewpoint of the stakeholders concern the organization
infrastructure, vision, mission and goals is provided in the diagram. The following diagram
provides the view point for the stakeholders concern.

Goals are defined as the target for achieving the desire system, they may be high levels of
objectives for the organization. To represent the goals of the Enterprise Architecture the goal
diagrams are used. The Enterprise goals is given as follows

The Baseline business architecture gives the overall business organization structure, a clear
description of the present organization structure is been given in this diagram (Resmini and
Rosati, 2011). The baseline business organization structure is given in the following diagram

The main functions that is been carried out in the organization is been given in the business
function diagram. It includes the business functions like customer relationship management, risk
management, financial auditing, marketing and service level management (Rosenfeld, Morville
and Arango, n.d.). The business functions in the enterprise architecture is given as follows

In Baseline Business process, the address of the level of detail depends on goal and scope of the
whole architecture effort. The process of new business needs to be defined. In Baseline Business
process, steps to be followed which is mentioned below.
 Development of baseline business architecture description
 Performance of gap analysis
 Choose viewpoints, tools and reference models
 Resolve the business architecture
In the business improvement process, the next step is the baseline setup. The team should collect
few performance measurements. Some of the performance measurements such as overtime,
quality, inventory dollars, productivity and throughput cycle time (Neufert et al., 2015).

Information system architecture includes the adoption of IT cost in the Enterprise
Architecture, the performance of the core business applications is been given in the diagram
(Hausman, 2011). The following diagram explains about the Information system architecture

The relationship between the different components in the organization is given in the
application co-operation diagram (Owen, 2012). The execution of the business process is given
in this diagram. The following diagram provides the Application Co-ordination view

The applications that is used in the organization that identifies the services that is required for
the business process and the process is provided in the application alignment diagram (Group
and Josey, 2010). The following diagram gives the Application alignment view
The conceptual business process and their major relationship is given with the logical data
objects by the ArchiMate tool The following diagram gives the Baseline Information system
architecture

The baseline technology architecture gives the organization an internal EA Baseline of
technology in the enterprise. It involves architectural assets from the entire architectural domain.
The software and the hardware components that supports the infrastructure of the enterprise is
given in the baseline technology architecture (REFRAMING INFORMATION
ARCHITECTURE, 2016).

The TOGAF phase C Information architecture has two parts that are data and application
architecture. The aim of the application architecture is to progress the target application
architecture (Perks and Beveridge, 2011). It supports the business architecture and the
architecture vision, during the process of addressing the request for architecture work and the
stakeholder fears. It is used to find out the roadmap components, that is depend on the GAP
between Baseline and target architecture.

The Goal refinement view enables the designer to change the level of refinement goals. The
high level refinement goals is modeled into the many concrete level refinement goals. The
concrete level refinement goals is changed to requirements. It defines the properties. The
properties are required to utilize a goals. The requirement get from the refinement of goals is
demonstrated by the help of Realization relationship. The Goal refinement diagram is given as

The target architecture is the desire architecture that is to be framed in the future. The
GAP analysis is nothing but a method of measuring the changes present in the performance of a
Business Information Systems. It is needed to regulate whether Business requirements stand
being encountered or not, If the requirement is not encountered what are steps needed to
safeguard the business. The GAP analysis is performed to achieve the Target Architecture. The
GAP analysis is performed by verifying the Architecture samples of an internal accuracy and
consistency, performing the Tradeoff analysis, checking the objectives, constraints and principles
of models, Measure the changes present at the viewpoint, testing the Architecture samples
(SIMON, 2016).

The target Architecture for the Enterprise is given as

The GAP Analysis is given in the following diagram
3. Cost benefits analysis for the enterprise architecture
EA is tightly tied by enhancing the exact medium finally to the execution which is
undertaking. So that the important stage is mainly to describe the boundary of attempt that is
being mentioned to. It is which might be whatever and is from change program to entire multi-
national scheme. The succeeding stage is to mainly characterize the grade and the nature of
different kind of medium period implementation change that is required. On the off chance that
implementation of the venture will then be adequate in average term and point is that in the
present there is no commercial or business case for the Enterprise Architecture (Reynolds, 2010).
EA is an administration rationality more than whatever else. On the off chance that senior
administration holds to a logic that arranging things is superior to responding to them, they will

see the advantages of EA. Since EA is the endeavor wide design, look for profits by
legitimization of assets, streamlined operation, and arrangement of assets to operation and key
arranging, speedier comprehension of the undertaking, normal vocabulary, acknowledgment of
vision and goals.
EA without anyone else's input is a logic, yet you can do a money saving advantage
investigation for EA with regards to EA particular activities. The money saving advantage would
be improved the situation things, for example, administrator costs for gatherings,
outline/demonstrating, and after that figured as an element of a money saving advantage
investigation on foundation extends that come to fruition because of the EA adopting a logical
strategy. You need to ingrain the rationality to begin with, at that point you can approach
fabricating the framework, else you get an indistinguishable wreckage from you had some time
recently. The imperative thing isn't to take a gander at EA as an undertaking, but instead a driver
of activities with regular interest over the association (WHELAN, 2016).
EA is a circuitous incentive similarly that a vital arranging bunch is and accordingly any ROI
or Cost/Benefit examination is greatly troublesome. Design helps in the change from
methodology to plan and goes about as confirmation of the nature of the procedure and adds to
enhanced nature of the arrangement - higher probability of accomplishment, bring down danger
of disappointment, prior conveyance of results. Factually, more than two third of business
procedures are not effectively executed. EA adds to expanding achievement rates.
EA as sort of forthright examination would not just let you measure the effect of EA, it
would likewise enable you to guide the program to drive greatest advantages the correct way. At
that point by considering a few suspicions from hazard/improve lessening into NPV/probabilities
approach, it ought to be conceivable to represent the expenses and advantages that may have
been achievable on past activities with various ways to deal with arranging. Applying the
knowledge picked up from this activity would then permit a sensible level of trust in the request
of size of advantages achievable by utilizing an EA approach on future suggestions.

4. Conclusion
A viewpoint for the stakeholders to view the target architecture and to analyses the goals of
the business along with the requirement and principles is been provided in the Archimate
diagrams by using the Archimate tool with the assistance of TOGAF. The analysis of the GAP
and the target architecture is been provided successfully. This project provides a clear vision
about the Business Architecture starting from week 4 to week 11, it also explains the application,
business and system view of the enterprise architecture. An architecture vision for the
stakeholders concern is provided and the baseline business functions of the enterprise and the
organization architecture is given.

References
Group, T. and Josey, A. (2010). TOGAF Version 9. Zaltbommel: Van Haren Pub.
Hausman, K. (2011). Sustainable enterprise architecture. Boca Raton, Fla.: CRC Press.
Neufert, E., Neufert, P., Kister, J., Sturge, D. and Brockhaus, M. (2015). Architects' data.
Chichester, West Sussex: Wiley-Blackwell.
Owen, S. (2012). Enterprise architecture. Delhi: White Word Publications.
Perks, C. and Beveridge, T. (2011). Guide to enterprise IT architecture. New York: Springer.
REFRAMING INFORMATION ARCHITECTURE. (2016). [Place of publication not
identified]: SPRINGER.
Resmini, A. and Rosati, L. (2011). Pervasive information architecture. Burlington, MA: Morgan
Kaufmann.
Reynolds, C. (2010). Introduction to business architecture. Boston, MA: Course Technology.
Rosenfeld, L., Morville, P. and Arango, J. (n.d.). Information architecture.
Saha, P. (2012). Enterprise architecture for connected e-government. Hershey, PA: Information
Science Reference.
SIMON, D. (2016). BUSINESS ARCHITECTURE MANAGEMENT. [Place of publication not
identified]: SPRINGER INTERNATIONAL PU.
WHELAN, J. (2016). BUSINESS ARCHITECTURE. [Place of publication not identified]:
ROUTLEDGE.