Enterprise Architecture

1. Enterprise Architecture

2. What is an Enterprise An “enterprise” is any collection of organizations that has a common set of goals. For example, an enterprise could be a government agency, a whole corporation, a division of a corporation, a single department, or a chain of geographically distant organizations linked together by common ownership. The term "enterprise" in the context of "enterprise architecture" can be used to denote: an entire enterprise An enterprise architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization. a specific domain within the enterprise. In both cases, the architecture crosses multiple systems, and multiple functional groups within the enterprise.

3. Architecture Types

4. Why do I need an enterprise architecture? The purpose of enterprise architecture is to optimize processes (both manual and automated) into an integrated environmentthat is responsive to change and supportive of the delivery of the business strategy. An enterprise architecture provides effective management and exploitation of information through IT This is by developing the IT system in response to the constantly changing needs of the business environment. A good enterprise architecture enables you to achieve the right balance between IT efficiency and business innovation.

5. Why do I need an enterprise architecture? A more efficient business operation; Lower business operation costs More flexible workforce

6. Why do I need an enterprise architecture? • A more efficient IT operation; • Lower software development, support, and maintenance costs • Increased portability of applications • Improved ability to address critical enterprise-wide issues like security • Easier upgrade and exchange of system components

7. Why do I need an enterprise architecture? Better return on existing investment, reduced risk for future investment; Reduced complexity in the business and IT Maximum return on investment in existing business and IT infrastructure Reduced risk overall in new investments and their cost of ownership

8. Why do I need an enterprise architecture? • Faster, simpler, and cheaper procurement; • Buying decisions are simpler, because the information governing procurement is readily available in a coherent plan • The procurement process is faster - maximizing procurement speed and flexibility without sacrificing architectural coherence

9. What specifically would prompt me to develop an enterprise architecture? An enterprise architecture is developed for: preparation for business transformation needs or preparation for radical infrastructure changes.

10. Often key people identify areas of change (required in order for new business goals to be met). Such people are commonly referred to as the "stakeholders". The role of the architect is to address stakeholders concerns by: Identifying and refining the requirements that the stakeholders have Developing views of the architecture that show how the concerns and requirements are going to be addressed Showing the trade-offs that are going to be made in reconciling the potentially conflicting concerns of different stakeholders What specifically would prompt me to develop an enterprise architecture?

11. What is an Architecture Framework? An architecture framework is a conceptual architecture used to develop, implement, and sustain an enterprise architecture. It should describe a method for designing a target state of the enterprise in terms of a set of building blocks, and for showing how the building blocks fit together. It should include a list of recommended standards and compliant products that can be used to implement the building blocks.

12. The Value of a Framework? Provides a practical starting point for an architecture project : Avoids the initial panic when the scale of the task becomes apparent Systematic - “codified common sense” Captures what others have found to work in real life Contains a Baseline set of resources of reuse

13. What is TOGAF? TOGAF (The Open Group Architecture Framework) is a framework with a detailed method and a set of supporting tools for developing an enterprise architecture. TOGAF provides the methods and tools for assisting in the acceptance, production, use, and maintenance of an enterprise architecture. TOGAF is based on an iterative process model supported by best practices and a re-usable set of existing architecture assets.

14. What Kind of Architecture Does TOGAF Deal With?

15. What Kind of Architecture Does TOGAF Deal With? The Business Architecture defines the business strategy, governance, organization, and key business processes. The Data Architecture describes the structure of an organization's logical and physical data assets and data management resources. The Application Architecture provides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes of the organization. The Technology Architecture describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, standards, etc.

16. TOGAF Components

17. Architecture Development Method (ADM) The TOGAF Architecture Development Method (ADM) provides a tested and repeatable process for developing architectures. The ADM includes establishing an architecture framework, developing architecture content, transitioning, and governing the realization of architectures. All of these activities are carried out within an iterative cycle of continuous architecture definition and realization that allows organizations to transform their enterprises in a controlled manner in response to business goals and opportunities

18. Architecture Development Method (ADM)—Basic Principles • An iterative method, over the whole process, between phases and within phases. • Each Iteration= new decisions. • Decision based on: • Resource availability • Value accruing to the enterprise

19. Architecture Development Method (ADM)— Basic Principles • Every phase is validated against and validates the current requirements of business.

20. Preliminary Phase • Describes the preparation and initiation activities required to create an Architecture Capability. • Understand business environment • High level management commitment. • Agreement on scope • Establish principles • Establish governance structure

21. Phase A Architecture Vision • Describes the initial phase of an architecture activities. • Set scopes , constraints and expectations • Identifies stakeholders, • Creates the Architecture Vision • Obtaining approval to proceed with the architecture development.

22. Phase BBusiness Architecture • The fundamental Organization of a business, embodied in • Its business processes and people, • Their relationships • To each other and the environment, • And the principles governing its design and evolution • Shows how the organization meets its business goals

23. Phase BBusiness Architecture - Contents • Organization structure • Business goals and objectives • Business functions • Business services • Business processes • Business roles • Correlation of organization and functions

24. Phase C Information System Architectures • The fundamental organization of an IT system, embodied in • The major types of information and applications that process them • Relationships to each other and the environment, and the principles governing its design and evolution • Shows how the IT systems meet the business goals of the enterprise

25. Phase C Data or Applications first? • It is usually necessary to address both • Not always the case, depending on project scope and constraints • May be developed in either order, or in parallel • Theory suggests Data Architecture comes first • Practical considerations may mean that starting with Application Architecture may be more efficient • There will be need to be some iteration to ensure consistency

26. Phase D Technology Architecture • The fundamental organization of an IT system embodied in • Its hardware, software and communications technology • Their relationships to each other and the environment, • And the principles governing its design and evolution

27. Phase E Opportunities and Solutions • Perform Initial implementation planning • Identify the major implementation projects • Determine if an incremental approach is required, if so define Transition Architectures • Decide on the approach • Assess priorities • Identify dependencies

28. Phase F Migration Planning • For work packages and projects indentified in phase E perform • Cost/benefit analysis • Risk assessment • Finalize a detailed implementation and Migration Plan

29. Phase G Implementation Governace • Provide architectural oversight for the implementation. • Defines architecture constraints on implementation projects • Govern and manage an Architecture contract • Monitors implementation work for conformance • Produce a Business Value Realization

30. Phase H Architecture Change Managment • Provide continual monitoring and a change management process • Ensures that changes to the architecture are managed in a cohesive and architected way • Establishes and supports the Enterprise Architecture to provide flexibility to evolve rapidly in response to changes in the technology or business environment

31. Architecture output Architects executing the ADM will produce a number of outputs as a result of their efforts, such as process flows, architectural requirements, project plans, project compliance assessments, etc. The Architecture Framework uses three categories to describe the type of architectural work product: deliverables, artifactsand building blocks.

32. Deliverables, Artifacts, and Building Blocks • Deliverable • Formal products • Contractually specified • Outputs from a project • Can contain many artifacts • Building Blocks • Components that can be combined with other building blocks to deliver architectures and solutions. • Artifacts • Describes an architecture from a specific point of view • Classified as • Catalogs (list of things) • Matrices showing relationships between things) or • Diagrams (pictures of things)

33. Relationship between Deliverables, Artifacts, and Building Blocks

34. Ex: Catalog

35. Ex: Stakeholder Map Matrix

36. Ex: Business footprint Diagram

37. Building Blocks A package of functionality defined to meet business needs across an organization may be assembled from or subassembly of other building blocks Its reusable and replaceable Building blocks can be defined at various levels of detail Grouping at the functional such as customer database ( Architecture Building Block) Real products or specific custom ( Solution Building Block)

38. Building Blocks • Building blocks can relate to "architectures" or "solutions". • Architecture Building Blocks (ABBs) • Define what functionality will be implemented • Capture business and technical requirements • Technology-aware • Shape the specification of Solution Building Blocks (SBBs). • Solution Building Blocks (SBBs) • Define what product or component will implement the functionality • Define the implementation • Fulfil business requirement • Product or vendor-aware