System Integration and Architecture 1 part1

1. ENTERPRISE ARCHITECTURE &
INTEGRATION

3. What is Enterprise Architecture?
A method for managing your business or enterprise:
• A decision making tool
• A change management tool
• The knowledgebase of your business or enterprise

4. What is EA ?
• The primary reason for developing an enterprise architecture (EA)
programmed is to have a clear picture of your organization and
learn how it works from the business to IT and how business
visions and strategy can be met.
• EA enables you to align organizational structures, processes,
applications and technology to help business services get delivered
at less cost, higher quality and higher speed.
• An enterprise architecture programmed helps steer your business
in the right direction, prepare to deal with disruptive business and
IT change, and invest in the right projects.

5. “Enterprise architecture consists of the vision, principles and
standards that guide the purchase and deployment of
technology within an enterprise”
Forrester, Gene Leganza.

6. Scope of Enterprise Architecture?
• The scope of enterprise architecture includes the enterprise’s
• People,
• Processes,
• Information Technology,
• their relationships to each other,
• And the external environment

7. Who is Enterprise Architect?
Enterprise architects are the people who:
• create the solutions to address the business challenges
• and support the enterprise in implementing those solutions.

9. Scope of enterprise architecture
 Current perspectives, or beliefs, with regards to the meaning of
the enterprise architecture, typically fall towards one or a hybrid
of three schools of thought:
 Enterprise IT design – According to this school, the purpose
of enterprise architecture is the greater alignment between IT and
business concerns.
 The main purpose of enterprise architecture is to guide the
process of planning and design the Information System
capabilities of an enterprise, in order to meet desired
organizational objectives.

10.  Enterprise integrating – According to this school, the purpose of
EA is to achieve greater coherency between the various concerns
of an enterprise (HR, IT, Operations, etc.) including the linking
between strategy formulation and execution.
 Enterprise ecological adaptation – According to this school, the
purpose of enterprise architecture is to foster and maintain the
learning capabilities of enterprises so that they may be
sustainable. Consequently, a great deal of emphasis is put on
improving the capabilities of the enterprise to improve itself, to
innovate.

11. Benefits of enterprise architecture
 The benefits of enterprise architecture are achieved through its
direct and indirect contributions to organizational goals, in the
following areas:
 Organizational design - Enterprise architecture provides
support in the areas related to design and re-design of the
organizational structures during general organizational change.
 Project portfolio management - Enterprise architecture
supports investment decision-making and work prioritization.

12.  Project management - Enterprise architecture enhances the
collaboration and communication between project stakeholders.
 Requirements Engineering - Enterprise architecture increases the
speed of requirement elicitation and the accuracy of requirement
definitions, through publishing of the enterprise architecture
documentation.
 IT management and decision making - Enterprise architecture is
found to help enforce discipline and standardization of IT planning
activities and to contribute to reduction in time for technology-related
decision making.
 IT value - Enterprise architecture helps reduce the systems
implementation and operational costs, and minimize duplication of
IT infrastructure services across business units.

13. • IT complexity - Enterprise architecture contributes to reduction
in IT complexity, association of data and applications, and to
better interoperability of the systems.
• IT risk management - Enterprise architecture contributes to
reduction of business risk from system failures and security
breaches. Enterprise architecture helps reduce risks of project
delivery.

14. Enterprise Architect
 Enterprise architects are practitioners of enterprise
architecture;
 Enterprise architects work with stakeholders, both leadership
and subject matter experts,
 to build a holistic view of the organization's strategy,
processes, information, and information technology assets.
 The role of the enterprise architect is to take his knowledge and
ensure that the business and IT are in alignment.

15. Enterprise Architect
 The enterprise architect links the business mission, strategy, and
processes of an organization to its IT strategy,
 that show how the current and future needs of an organization will be met
in an efficient, sustainable and adaptable manner.

16. Integrated Enterprise Information Systems?
• Enterprise
• A business, an industrious effort, especially one directed toward
making money
• Information System
• An Information System (IS) is a system composed of people
and computers that processes or interprets information.
Integrated
• Joined together, united,
made into a whole
by having brought
all parts together

17. Enterprise Engineering (EE)
• EE is defined as the body of knowledge, principles, and practices
to design all or a part of an enterprise.
• An enterprise is a complex system that comprises
interdependencies, resources of people, information and
technology that must interact with each other and their
environment in support of a common mission.
• EE is a sub discipline of industrial engineering/System
engineering.

18. Zachman Framework

19. The Evolution of Enterprise Architecture
• Enterprise architecture was developed by John Zachman while
with IBM in the1980s, after observing the building and airplane
construction industries and the IT industry.
• He saw similarities between the construction of buildings,
airplanes, and the information systems used by an enterprise.
• These industries manage the design, construction, and
maintenance of complex products by considering the needs of
different people.

20. The Evolution of Enterprise Architecture
• The owner in the building industry, who uses architect’s drawings to
decide that the building addresses specific requirements.
• For airplane manufacture, the owner uses the high-level work
breakdown structure of the plane to determine requirements.
• For information systems, the owner uses a model of the business to
determine the enterprise needs.

21. The Evolution of Enterprise Architecture
• The designer, however, needs a different set of
diagrams:
• architect’s plans for the building,
• sets of engineering design diagrams for the plane,
• or information system models for the enterprise.

22. The Evolution of Enterprise Architecture
• The builder relies on still different types of diagrams:
• contractor’s plans for construction of the building,
• a manufacturing engineering design for plane construction,
• or technology models for information systems.

23. The Evolution of Enterprise Architecture

24. The Evolution of Enterprise Architecture
• What is needed is important to know. This is represented in
Figure 2 by material, such as bills of materials for buildings and
planes, and data models for information systems.
• How these are used is indicated by functions, such as functional
specifications for buildings and planes, and functional models for
information systems.
• Where is also important, as indicated by location—in drawings for
building and plane construction and in network models for
information systems

26. The Evolution of Enterprise Architecture
• There are a further three columns— Who, When, and Why —in
the complete Zachman framework for enterprise architecture