Enterprise Architecture

Welcome to the This Session “TOGAF9: The Open Group Architecture Framework” : Welcome to the This Session “TOGAF9: The Open Group Architecture Framework” Syed Naqvi, PMP

Agenda : Agenda Introduction EA The Open Group TOGAF9 TOGAF9 Core Concepts TOGAF9 Concepts Framework TOGAF9 Framework TOGAF9 Management Framework Architecture Domain Stakeholders, View and View Points Deliverables, Artifacts and Building Blocks Enterprise Continuum Architecture Repository Architecture Content Model Establishing and Maintaining an Enterprise Architecture Capability ADM(Architecture development methods) TOGAF9 Document categorization Model ADM Guideline and Practices Using TOGAF9 with Other Frameworks

EA Definition by IT Gurus : EA Definition by IT Gurus What it is ? What the Scope is ? What the result is ? What the benefit is ? IEEE 1471 – 2000 The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution. Gartner Definition Enterprise architecture is the business of architecting the enterprise Gartner Has A EA practice which is more focus on Future and faster Time to Value TOGAF9 1. "A formal description of a system, or a detailed plan of the system at component level to guide its implementation. 2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time."

Enterprise Architecture : Enterprise Architecture Enterprise A group of Person and OU(Organizations units) working towards a common goal by optimized utilization of People, Process and Resource People: Vision, Mission, Strategy, Goals and Objective, Collaboration, Innovating thinking, Governance, partners, Customers Process: Implementation strategy via Cross Functional, End to End Business Processes , Business policies and rules Resource: Technology, Equipments, Materials, Products, Location Environment: Judicious integration and unification of People, Process and Resource creates an environment which is unique and provides competitive advantage to enterprise

Architecture Metamodel : Architecture Metamodel

Why EA ? : Why EA ? Alignment Alignment of Enterprise strategy with Resources (IT system, Materials, Facilities, Equipments ) Alignment lead to real business value delivery to the enterprise Agility Ability to responds to change in controlled manner with in business time Architecture enables traceability from business needs to business processes to application and data components to components containers/environment Enterprise Traceability is the key to Agility Simplification Simplification and visibility of enterprise strategy and IT system complexity Cost reduction Reduction in cost on medium and long term basis

Benefit of EA according to open group : Benefit of EA according to open group ‘‘An effective enterprise architecture is critical to business survival and success and is the indispensable means to achieving competitive advantage through IT.’’ A more efficient IT operation: Lower software development, support, and maintenance costs Increased portability of applications Improved interoperability and easier system and network management Improved ability to address critical enterprise-wide issues like security Easier upgrade and exchange of system components Better return on existing investment, reduced risk for future investment: Reduced complexity in IT infrastructure Maximum return on investment in existing IT infrastructure The flexibility to make, buy, or out-source IT solutions Reduced risk overall in new investment, and the costs of IT ownership 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. The ability to procure heterogeneous, multi-vendor open systems.

TOGAF9 Concepts : TOGAF9 Concepts Framework TOGAF9 Framework TOGAF9 Management Framework Architecture Domain Stakeholders, View and View Points Deliverables, Artifacts and Building Blocks Enterprise Continuum Architecture Repository Architecture Content Model Establishing and Maintaining an Enteprise Architecture Capability ADM(Architecture development methods) TOGAF9 Document categorization Model ADM Guideline and Practices Using TOGAF9 with Other Frameworks

What is a Architecture Framework ? : What is a Architecture Framework ? EA Architecture framework describes What to Do or what artifact to create How to create and use above artifact in most optimum manner TOGAF9 is also a framework Methods/Process for creating current, transition and target architecture states for enterprise A set of building blocks and Artifacts required for them How Building block can be used together to create a Solution A common set of vocabulary for better communication and understanding

TOGAF9 Management Frameworks : TOGAF9 Management Frameworks TOGAF9 also include four interrelated management Framework Business Capability Management (Business Direction and Planning) that determines what business capabilities are required to deliver business value including the definition of return on investment and the requisite control/performance measures. Portfolio/Project Management Methods that determine how a company manages its change initiatives. Operations Management Methods that describe how a company runs its day-to-day operations, including IT. Solution Development Methods that formalize the way that business systems are delivered in accordance with the structures developed in the IT architecture Source: Open group TOGAF9 Standard

Architecture Domains : Architecture Domains Architecture Domains Business Architecture Data Architecture Application Architecture Technology Architecture 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 application systems 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.

Architecture States : Architecture States As is Architecture or Baseline or Operational Architecture Transitions architecture Target Architecture or Strategic Architecture As Is Architecture Transition Architecture Target Architecture ADM Guide Lines ADM Guide Lines ADM Guide Lines ADM Guide Lines ADM Guide Lines ADM Guide Lines

Approach to Architecture Definition : Approach to Architecture Definition Baseline First: In this style, an assessment of the baseline (i.e., current state) landscape is used to identify problem areas and improvement opportunities. This process is suitable when a target solution is not clearly understood and agreed upon Target First: In this style, the target solution is elaborated in detail and then mapped back to the baseline, in order to identify change activity. This process is suitable when a target state is agreed at a high level and where the enterprise wishes to avoid proliferating current business practice into the target model

Stakeholders, Viewpoints and Views : Stakeholders, Viewpoints and Views Stakeholders is a person or organization unit or a role who has an stake in the architecture of the enterprise Stakeholders has concerns and needs related to EA which is expressed in viewpoints Each Stakeholders looks EA from his point of view, normally expressed in viewpoints Enterprise Architecture captures stakeholder viewpoint in a view and a model with description During the EA process, it is important to identify stakeholders and views which need to be developed From the Enterprise perspective views may be classified on the basis of roles, Purpose and content into following categories Source: Open group Archimate standard

Deliverables, Artifacts and Building Blocks : Deliverables, Artifacts and Building Blocks A deliverable is a work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders An Artifact is a more granular architectural work product that describes an architecture from a specific viewpoint An architectural deliverable may contain many Artifacts and artifacts will form the content of the Architecture Repository. A building block represents a (potentially re-usable) component of business, IT, or architectural capability that can be combined with other building blocks to deliver architectures and solutions Building blocks are of two types : Architecture Building Blocks (ABBs) typically describe required capability and shape the specification of Solution Building Blocks (SBBs) For example, a customer services capability may be required within an enterprise, supported by many SBBs, such as processes, data, and application software.

Deliverables, Artifacts and Building Blocks : Deliverables, Artifacts and Building Blocks Source: Open group TOGAF9 Standard

Deliverables, Artifacts and Building Blocks : Deliverables, Artifacts and Building Blocks Source: Open group TOGAF9 Standard

Architecture Repository : Architecture Repository Architecture Repository is an enterprise wise repository where architecture and other software components assets are published Architecture Repository provides enterprise wise visibility for assets Assets can be discovered for reuse via search function in business terms An enterprise wise repository is becoming an integral part of software development environment for every large scale, multi-location development Source: Open group TOGAF9 Standard

Enterprise Wise Architecture Repository : Enterprise Wise Architecture Repository The major components within an Architecture Repository are as follows: The Architecture Metamodel describes the organizationally tailored application of an architecture framework, including a metamodel for architecture content. The Architecture Capability defines the parameters, structures, and processes that support governance of the Architecture Repository. The Architecture Landscape shows an architectural view of the building blocks that are in use within the organization today (e.g., a list of the live applications). The landscape is likely to exist at multiple levels of abstraction to suit different architecture objectives. The Standards Information Base (SIB) captures the standards with which new architectures must comply, which may include industry standards, selected products and ser vices from suppliers, or shared services already deployed within the organization. The Reference Library provides guidelines, templates, patter ns, and other forms of reference material that can be leveraged in order to accelerate the creation of new architectures for the enterprise. The Governance Log provides a record of governance activity across the enterprise.

Enterprise Continuum : Enterprise Continuum The Enterprise Continuum is a view of the Architecture Repository that provides methods for classifying architecture and solution artifacts as they evolve from generic Foundation Architectures to Organization-Specific Architectures Source: Open group TOGAF9 Standard

Another view of Enterprise Continuum : Another view of Enterprise Continuum Source: Open group TOGAF9 Standard

Open group Reference Architecture – Boundaryless Information Flow : Open group Reference Architecture – Boundaryless Information Flow Source: Open group TOGAF9 Standard

Another view of Boundaryless Information flow : Another view of Boundaryless Information flow Source: Open group TOGAF9 Standard

TOGAF9 Reference Architecture : TOGAF9 Reference Architecture Source: Open group TOGAF9 Standard

TOGAF9 Content Model : TOGAF9 Content Model Source: Open group TOGAF9 Standard

TOGAF Content Extension Model : TOGAF Content Extension Model Source: Open group TOGAF9 Standard

Establishing and maintaining Enterprise Architecture Capability : Establishing and maintaining Enterprise Architecture Capability An Enterprise Architecture capability is set by defining an organization structures, roles, responsibilities, skills, and processes An Enterprise Architecture operational capability is set up by making delivery of Architecture capability as Business unit with profit and loss responsibility Source: Open group TOGAF9 Standard

ADM(Architecture Development methods) : ADM(Architecture Development methods) The TOGAF Architecture Development Method (ADM) provides a tested and repeatable process for developing architectures The ADM forms the core of TOGAF The result of contributions from many architecture practitioner. It is specifically designed to address enterprise’s business and IT needs by providing: A set of architecture views (business, data, application, technology) Guidelines on tools for architecture development A set of recommended deliverables Links to practical case studies A method for managing requirements ADM is an iterative and multiphase process ADM iteration may span Over the Whole process, With in a Phase, Between Phases For each iteration following should be consider Scope Focus Detail Schedule, Milestone Quality attributes ADM is a generic methodologies which need to be customized or extended in a given situation

ADM Phases : ADM Phases Source: Open group TOGAF9 Standard

ADM Structure for each Phase : ADM Structure for each Phase Objectives The Main objectives of the Phase Approach What approach should be taken or adopted towards work to be done in the specific phase Inputs Goal and Objectives, Stakeholders Need and Concerned Reference Materials, Requirements Document, Qualities of requirements, Guidelines Best practices, Principles Steps Select reference models, viewpoints, and tools Develop Baseline Architecture Description for the Domain Develop Target Architecture Description for the Domain Perform gap analysis for the Domain and Define roadmap components for the Domains Resolve impacts across the Architecture Landscape Conduct formal stakeholder review Finalize the Architecture Definition for The domain Create Architecture Definition Document for the domain Outputs Architecture Definition document, Other Deliverables Like Gap Analysis, Catalogues like Risk, Role, Business Objects, process, Function, Services, Events, Application, KPI’s and Measures

ADM Iterations : ADM Iterations Source: Open group TOGAF9 Standard

ADM Iterations : ADM Iterations Architecture Context iterations allow initial mobilization of architecture activity by establishing the architecture approach, principles, scope, and vision Architecture Definition iterations allow the creation of architecture content by cycling through Business, Information Systems, and Technology Architecture phases. These iterations also allow viability and feasibility tests to be carried out by looking at opportunities and migration planning Transition Planning iterations support the creation of for mal change roadmaps for a defined architecture Architecture Governance iterations support governance of change activity progressing towards a defined Target Architecture.

Adapting the ADM to Specific Situations/Contexts : Adapting the ADM to Specific Situations/Contexts ADM is generic development methodology which can and should be customized, tailored to specific situations and contexts Depending upon Breadth and Depth of Scope (Horizontal Scope) For Small Medium and Large Enterprise For Product Line Architecture For Co-locations or Multi-locations teams For Working with partners like Venders, Consultants etc.

Scoping The Architecture Works : Scoping The Architecture Works It is Important to define architecture scope keeping following in mind The objectives and stakeholder concerns to be addressed within the architecture The availability of people, finance, and other resources Four dimension for Defining the Scope of Architecture Enterprise Breadth or Horizontal focus Architecture Footprint Enterprise Domains Vertical Scope or level of details Time Horizon

An Example Target First Approach : An Example Target First Approach Source: Open group TOGAF9 Standard

ADM Guidelines and technique : ADM Guidelines and technique ADM Guidelines Applying Iteration to the ADM Applying the ADM at Different Enterprise Levels Security Architecture and the ADM Using TOGAF to Define & Govern SOAs Architecture Techniques Architecture Principles Stakeholder Management Architecture Patterns Business Scenarios SMART Gap Analysis Migration Planning Techniques Interoperability Requirements Business Transformation Readiness Assessment Risk Management Capability-Based Planning

Architecture done as per TOGAF9 : Architecture done as per TOGAF9 Source: Open group Archimate Standard

Using TOGAF9 with other Architecture Framework : Using TOGAF9 with other Architecture Framework RUP or Rational unified process is a popular framework for software development which is practically used in many enterprises The Zachman Framework for Enterprise Architectures—Although self-described as a framework, is actually more accurately defined as a taxonomy The Open Group Architectural Framework (TOGAF)—Earlier version of TOGAF were focused on methodology, TOGAF9 also include content framework The Federal Enterprise Architecture—Can be viewed as either an implemented enterprise architecture or a model specially for Government agencies The Gartner Methodology—Can be best described as an enterprise architectural practice and is more business and future centric.

TOAGAF9 and RUP : TOAGAF9 and RUP

Using Zackman Framework and TOGAF9 : Using Zackman Framework and TOGAF9 Zackman Framework: The [Enterprise Architecture] Framework as it applies to Enterprises is simply a logical structure for classifying and organizing the descriptive representations of an Enterprise that are significant to the management of the Enterprise, as well as to the development of the Enterprise's systems

Using Zackman Framework and TOGAF9 : Basic of Zachman Framework The first point of Zachman taxonomy is that every architectural artifact should live in one and only one cell. There should be no ambiguity about in which cell a particular artifact lives The second point of the Zachman taxonomy is that an architecture can be considered a complete architecture only when every cell in that architecture is complete. A cell is complete when it contains sufficient artifacts to fully define the system for one specific player looking at one specific descriptive focus. Third point of Zachman taxonomy is that when each cell in a row is fully populated with appropriate artifacts, It fully describe the system from the perspective of a single player Fourth point of Zachman taxonomy is that when every cell (All 36 cells) is populated with appropriate artifacts, there is a sufficient amount of detail to fully describe the system from the perspective of every player (what we might today call a stakeholder) In practice it will be very rare when all 36 cells will be populated The fifth point is that there should be traceability between artifacts across columns from top to bottom . This is the key to traceability Major advantages of Zachman Framework: Ensure that every stakeholder's perspective has been considered from his point of view Improve the artifacts themselves by sharpening each of their focus points to one particular concern for one particular audience Ensure that all business requirements can be traced down to some technical implementation Using Zackman and TOAGF9 together Zackman framework can be used along with TOAGF9 ADM Zackman can be used to identify appropriate artifacts while ADM and ADM guideline and practices can be used to develop the artifacts It is obvious that Zackman and TOGAF9 are complementary in many respects Using Zackman Framework and TOGAF9

Federal Enterprise Architecture(FEA) : Federal Enterprise Architecture(FEA) FEA provides a reference model for US Federal government . This reference model can be used as basis for Architecting a multi-department or Agencies scenarios FEA Reference model can be further refined and customized to specific scenario, with ADM process, practices and guidelines

Gartner Architecture Framework & TOGA9 : Gartner Architecture Framework & TOGA9 Gartner framework is an Agile Architecture proven and repeatable future centric practices which can be used to deliver value in less value TOGAF9 is a matured, widely accepted process centric standard Gartner Architecture Framework can be combine with TOGAF9 ADM to get benefits of Agility and discipline together

Thank You : Thank You Syed Naqvi, PMP