Enterprise Integration and Architecture

The assignment delves into the concept of enterprise integration and its impact on development processes. It discusses the three primary layers of business architecture: business, application, and technology. Each layer is illustrated with diagrams and explained in detail, highlighting their roles and relationships within an integrated system. The document also touches upon cloud migration and its implications for enterprise architecture.

Running head: NETWORK ENTERPRISE ARCHITECTURE
Network Enterprise Architecture
Name of the Student:
Student ID:
Name of the University:
Author’s note:

1NETWORK ENTERPRISE ARCHITECTURE
Table of Contents
Task 1...............................................................................................................................................2
Relevant Frameworks Analysis...................................................................................................2
Task 2...............................................................................................................................................4
Identification of the Gap Analysis...............................................................................................4
Identification of Digital Capabilities...........................................................................................4
Task 3...............................................................................................................................................5
Motivational Model.....................................................................................................................5
Task 4...............................................................................................................................................5
Discussion of the core layers of business....................................................................................5
Business Layer.............................................................................................................................8
Application Layer........................................................................................................................8
Technology Layer........................................................................................................................9
References......................................................................................................................................10

2NETWORK ENTERPRISE ARCHITECTURE
Task 1
Relevant Frameworks Analysis
Framework Brief Description Pro Con Reference
TOGAF TOGAF architecture is
developed for forming the
improved approach for
design making, developing
plan, forming
implementation, and
governance for the
deployment of the effective
and improved operations. It
is a high level operational
approach for forming the
deployment of the heavy
modularization and
standardization. The four
levels of model application
are business, application,
data, and technology.
TOGAF provides the set of
tools for forming the range
of architectures.
It describes the method
helpful for building the
information system,
showing the fitting of
building blocks, containing
the set of tools, and
providing common
development
Define business
strategy for the
business governance
Provide blueprint for
individual system
development
Structuring the data
architecture in terms
of logical and
physical layer
Describes hardware
and software support
for the core
deployment
TOGAF recommendations
are inapplicable in most
cases
Requires some specified and
certified tools
Deployment of formal level
of qualifications
Weisman, R. (2012). An Overview of TOGAF® Version 9.1. [ebook] Ottawa, Ontario: The
Open Group 2011, pp.5-9. Available at:
http://www.opengroup.org/public/member/proceedings/q312/togaf_intro_weisman.pdf
[Accessed 16 Sep. 2017].
AGAF The Australian Government
Architecture framework
(AGAF) is implied for
forming the inter-related
reference model for
designing the facility for
cross agency analysis and
duplicate investment for
forming the analysis of the
gaps and opportunities. The
reference model would be
implied for forming the
analysis of the
Performance
reference model
would be formed for
integrating the
operations
Business reference
model would be used
for forming the
reference integration
Provides the
common language
for delivering the
product for
The Australian Government
Architecture framework had
been deployed by the
Australian government and it
is not implied for analysing
the development of the
operation and hence not
followed on global scale
Enterprisesolutions.vic.gov.au. (2017). Australian Government Architecture. [online] Available at:
http://www.enterprisesolutions.vic.gov.au/australian-government-architecture-aga/ [Accessed 16
Sep. 2017].

3NETWORK ENTERPRISE ARCHITECTURE
improvement facilities. The
deployment of the
Australian Government
Architecture framework
would comprise of forming
the reference models for
integrating the development
of the consistent and
improved
identification of the
cohesive deployment
and integration
Data reference model
would form the
integration of the
cohesive ICT
investment
development.
Zachman
Architecture
Zachman Architect is
deployed for developing
enterprise ontology for
structuring the enterprise
architecture for integrating
the formal structure of
viewing and defining the
enterprise development
Zachman Framework would
comprise of forming the
reference models for
integrating the development
of the consistent and
improved. It describes the
method helpful for building
the information system,
showing the fitting of
building blocks, containing
the set of tools, and
providing common
development
The ontology would
be developed for
forming the target
artefact for
realization of the
improvement
operations. The
ontology would be
helpful for the
scheming the
integration of the
data functionality
and owner
implication
Zachman framework is
implied for developing the
improvement of the synthetic
degeneration of the
improvement. The schema
would not be compatible
with the specific method of
integration and management.
The organization would be
formed for implementing the
design documentation for
integration of the artefacts
for implying the
development model.
Pubs.opengroup.org. (2017). ADM and the Zachman Framework. [online] Available at:
http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap39.html [Accessed 16 Sep. 2017].
Table 1: Analysis of Relevant Framework

4NETWORK ENTERPRISE ARCHITECTURE
Task 2
Identification of the Gap Analysis
Figure 1: Gap Analysis diagram
(Source: Created by the author)
Identification of Digital Capabilities

5NETWORK ENTERPRISE ARCHITECTURE
Figure 2: Digital Capabilities diagram
(Source: Created by the author)
Task 3
Motivational Model
Figure 3: Motivational Model diagram

6NETWORK ENTERPRISE ARCHITECTURE
(Source: Created by the author)
Task 4
Discussion of the core layers of business
Core
Architectur
e
Service
Description
Function
Description
Process
Description
Component
Description
Node
Description
Any other
Applicabl
e
Business Internet
banking is
the primary
service
description
factor for
the business
layer and it
would
involve the
developmen
t of the
banking
analysis for
the
completion
of the
business
activity
Customer
Integration is
done for
forming the
integration
of the data of
customers
and the
analysis of
the
improvement
facilities.
CRM
process is
developed
for implying
the effective
and
improved
description
of the project
operations
and its
synthetic
development
.
SOA is
formed for
integrating
the
development
of the
solutions for
Oracle and
SAP
integration
and it would
involve the
development
of the
banking
analysis for
the
completion
of the
Oracle
system is
formed for
implying
effective
database
structure for
the
deployment
of the
operations.
Banking
Data

7NETWORK ENTERPRISE ARCHITECTURE
business
activity
Application Data
Managemen
t is the
primary
service
description
factor for
the
application
layer and it
would
involve the
developmen
t of the
banking
analysis for
the
completion
of the
application
activity
Database
Management
would be
done for
using the
application
for
managing
the data in
the
organization
that is
formed for
tormenting
the
development
of the
process of
integration
and
development
.
Integration
of database
is done for
forming the
analysis of
the
structured
database by
integrating
the Oracle
and SAP
SAP
Interface is
used for
accessing the
database and
selection of
the improved
data structure
SAP
application
is formed for
tormenting
the
development
of the
process of
integration
and
development
.
Computer
devices
Database
Structure
Technology Cloud
Migration is
Cloud
Hosting is
Export to
cloud is done
Azure Cloud
is formed for
Azure
HDInsights
Cloud data

8NETWORK ENTERPRISE ARCHITECTURE
the primary
service
description
factor for
the
technology
layer and it
would
involve the
developmen
t of the
banking
analysis for
the
completion
of the
technology
activity
deployed for
developing
the
technology
of the
immigrate
analysis of
the project
integration
management
and it would
be developed
for
evaluating
the cloud
migration.
for ensuring
that the
cloud
network is
being
developed
for forming
the sufficient
management
of the
operations.
ensuring the
development
of the cloud
mitigation
would be
developed
for
implementin
g the
development
of the
operations.
is formed for
hosting the
cloud in the
Azure
platform for
ensuring that
the cloud
network is
being
developed
for forming
the sufficient
management
of the
operations.
Table 2: Discussion of the core layers of business
Business Layer

9NETWORK ENTERPRISE ARCHITECTURE
Figure 4: Business Layer diagram
(Source: Created by the author)
Application Layer
Figure 5: Application Layer diagram
(Source: Created by the author)
Technology Layer

10NETWORK ENTERPRISE ARCHITECTURE
Figure 6: Technology Layer diagram
(Source: Created by the author)

11NETWORK ENTERPRISE ARCHITECTURE
References
Da Xu, L., 2014. Enterprise integration and information architecture. CRC Press.
Enterprisesolutions.vic.gov.au. (2017). Australian Government Architecture. [online] Available
at: http://www.enterprisesolutions.vic.gov.au/australian-government-architecture-aga/ [Accessed
16 Sep. 2017].
Hansen, P. and Hacks, S., 2017. Continuous Delivery for Enterprise Architecture
Maintenance. Full-scale Software Engineering/The Art of Software Testing, p.56.
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.
Pubs.opengroup.org. (2017). ADM and the Zachman Framework. [online] Available at:
http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap39.html [Accessed 16 Sep. 2017].
Simon, D., Fischbach, K. and Schoder, D., 2014. Enterprise architecture management and its role
in corporate strategic management. Information Systems and e-Business Management, 12(1),
pp.5-42.
Weisman, R. (2012). An Overview of TOGAF® Version 9.1. [ebook] Ottawa, Ontario: The Open
Group 2011, pp.5-9. Available at:
http://www.opengroup.org/public/member/proceedings/q312/togaf_intro_weisman.pdf
[Accessed 16 Sep. 2017].