Introduction to Enterprise Architecture

1. Introduction to Enterprise Architecture By Smt. Gayatri P Senior Technical Director

2. Workshop scheduling • Session 1: Introduction to Enterprise Architecture • Session 2: Exploring various EA Frameworks • Session 3: IndEA Framework • Session 4: EA Case Study – Land Hub Andhra Pradesh • Session 4: EA Case Study – University EA Framework • Session 5: Interactive session involving question and Answers about Enterprise Architecture and associated

3. Agenda: Session 1 • Understanding the nexus of Enterprise Architecture • History & Evolution of Enterprise Architecture • Components of Enterprise Architecture • Lifecycle of Enterprise Architecture • Implementation of EA • Enterprise Architecture Frameworks • Zachman Framework • ToGAF • IndEA

4. Evolution of Government Observed In the early days... The next steps... Running business needs applications to be integrated • Moving from departmental stovepipes to citizen centric approach in service delivery • Transforming and integrating the back office • Collaborative working and information sharing • Product and service innovation • Citizen engagement and inclusion • Networked form of organization model adding to the complexity • Enhancing the economic infrastructure and government Performance Automation of manual tasks e.g. Payroll, In-House Development Application packages (Siloed Apps) e.g. HR, Financial administration

5. Evolution of Government Observed In the early days... Now …..

6. How are we going to survive this Jungle? • Problems • Business KPIs are not aligned with Business Vision/ Mission • Organization structure, functions and technology do not align to meet the business goals • Accurate or complete operational data is unavailable when required • Applications implemented do not integrate / communicate properly • Business processes are ad-hoc and manual and managing them is time consuming • Technology investments are ad-hoc and not cost effective. • Decision making takes longer time • Data is scattered across departments and information is redundant • Incompatibilities • Data between applications • User interfaces • Terminologies • Workflows • Hardware and software • platforms • Business and IT !

7. Enterprise Architecture Transformation Alignment Coherence Agility Interoperability Robustness Scalability Ability to migrate

8. Defining Enterprise Enterpriseis a collection of organizations that has a common set of goals. An enterprise could be a Government agency, a corporation a single department or a chain of geographically distant organizations linked by a common ownership. An extended enterprise frequentlyincludes partners, suppliers, and customers. If the goal is to integrate an extended enterprise, then the enterprise comprises the partners, suppliers, and customers, as well as internal business units. A Government consists of multiple ministries, departments and agencies. All government organizations, are unified under the common goal to achieve Digital India vision. Hence, a Government may be considered as an “Enterprise of Enterprise”. Enterprises Enterprise of Enterprises Source:: TOGAF

9. Defining Enterprise • An enterprise has a shared vision and a common set of goals • An evolving and transforming business entity having a common ownership • A collection of departments or organizations which may be geographically dispersed • It exists to serve its stakeholders while maintaining its bottom lines • It delivers stakeholder services using business processes and multiple IT systems • It follows policies, guidelines, business rules and legislative requirements of operating geographies

10. Defining Architecture Architecture in context of Enterprise Architecture is fundamental organization of system, embodied in its components, their relationship to each other and the environment and the principles governing its design and evolution - ISO/IEC 42010:2007, Systems and Software Engineering – Recommended Practice for Architectural Description of Software-Intensive Systems Architecture A formal description of a system, or a detailed plan of the system at a component level to guide its implementation. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.

11. Defining Enterprise Architecture

12. DefinitionEnterprise Architecture (EA) • An enterprise architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization. • The intent of an enterprise architecture is to determine how an organization can most effectively achieve its current and perceived future objectives.

13. Architecture transformation • Which routes to follow? • How to organize oneself? • How to communicate? • • What are the main risks and how can they be reduced?

14. What is Enterprise Architecture ? What is Not Enterprise Architecture? What is Enterprise Architecture? A bunch of hardware, software, and technical documents describing enterprise IT • A shared business and IT vision for the organization along with performance benchmarks • An interoperable and cost effective framework which could transcend, be referenced and used for inter-organization discovery and digital collaboration for effective service delivery to stakeholders • It ensures economies of scale by reusing Business and Application Services, by the use of consistent vocabulary in Business, Data, Application and Technology layers by specifying the interoperability requirements in terms of open standards and open data formats • It ensures “Single Source of Truth” thereby avoiding multiple data entry, data duplicity etc A one-time effort or a project Enterprise Architecture • Business Strategy & • IT Governance • A set of artefacts, or documents generated by architects that describes current state and future state architecture or documents generated as part of an EA framework.

15. Agenda • Understanding the nexus of Enterprise Architecture • History & Evolution of Enterprise Architecture • Components of Enterprise Architecture • Lifecycle of Enterprise Architecture • Implementation of EA • Enterprise Architecture Frameworks • Zachman Framework • ToGAF • IndEA

16. Evolution of Enterprise Architecture

17. Evolution of Enterprise Architecture – Genesis: Business Systems Planning methodology

18. Evolution of Enterprise Architecture – PRISM EA Framework

19. Zachman Framework

20. Evolution of Enterprise Architecture from 90s The development of the above frameworks has paved the way for multiple Nations (Korea, Singapore, UAE, UKand USA) and Industry (Microsoft and Oracle) to develop their own tailored enterprise architecture frameworks which are being consumed by enterprises. The Federal Enterprise Architecture The Gartner Methodology The Zachman Framework The Open Group Architectural Framework A federal enterprise architecture (FEA) provides a common approach for the integration of strategic, business and technology management as part of organization design and performance improvement Gartner Methodology is based on the amalgamation of Gartner framework and Meta architecture development process. The Zachman Framework is an Enterprise Ontology which provides a formal and structured way of viewing and defining an enterprise. The Open Group Architecture Framework (TOGAF) is a framework for enterprise architecture which provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture Source: TOGAF and A comparison of top four EA methodologies, 2007 by Microsoft

21. Agenda • Understanding the nexus of Enterprise Architecture • History & Evolution of Enterprise Architecture • Components of Enterprise Architecture • Lifecycle of Enterprise Architecture • Implementation of EA • Enterprise Architecture Frameworks • Zachman Framework • ToGAF • IndEA

22. Components of Enterprise Architecture

23. Agenda • Understanding the nexus of Enterprise Architecture • History & Evolution of Enterprise Architecture • Components of Enterprise Architecture • Lifecycle of Enterprise Architecture • Implementation of EA • Enterprise Architecture Frameworks • Zachman Framework • ToGAF • IndEA

24. Life Cycle of Enterprise Architecture

25. Life Cycle of Enterprise Architecture – Illustration of a government project

26. Agenda • Understanding the nexus of Enterprise Architecture • History & Evolution of Enterprise Architecture • Components of Enterprise Architecture • Lifecycle of Enterprise Architecture • Implementation of EA • Enterprise Architecture Frameworks • Zachman Framework • ToGAF • IndEA

27. Ecosystem of Enterprise Architecture I

28. Ecosystem of Enterprise Architecture II

29. Enterprise Architecture helps to align the vision of the project to the implementability

31. Business Layer Illustrative

32. EA implementation benefits Source:: Enterprise Architecture by Open Group and MIT white paper on Enterprise Architecture Landscape in Singapore Government Agencies published on February 2013

33. Increasing the need for Enterprise Architecture and the roles and responsibilities of an Enterprise Architect

34. Need for an Enterprise Architecture

35. Roles and Responsibilities of an EA

36. Roles and Responsibilities of an EA

37. Risks associated with Enterprise Architecture

38. Risks associated with Enterprise Architecture • Inability to rapidly respond to new requirements • Lack of focus on enterprise requirements • Lack of common direction and synergies • Incomplete visibility of the current and future vision • Inability to predict impacts of future changes • Increased gaps and architecture conflicts • Lack of commonality and consistency • Rigidity, redundancy and lack of scalability and flexibility in the deployed solutions • Lack of integration, compatibility and interoperability between applications • Piece-meal and ad hoc software development driven by a tactical and reactive approach

39. Challenges to EA implementation

40. Current Challenges in Enterprise Architecture

41. Agenda • Understanding the nexus of Enterprise Architecture • History & Evolution of Enterprise Architecture • Components of Enterprise Architecture • Lifecycle of Enterprise Architecture • Implementation of EA • Enterprise Architecture Frameworks • Zachman Framework • ToGAF • IndEA

42. Enterprise Architecture Frameworks Gartner IndEA FEA

43. Countries who have adopted EA

44. Popular EA Frameworks

45. TOGAF Enterprise Architecture Frameworks Gartner FEA Zachman EA Frameworks Focus areas of the four Enterprise Architecture Frameworks: • TOGAF – Process Centric • FEA – Implementation Centric • Zachman – Taxonomy/Framework Centric • Gartner – Practice/outcome Centric Each of the frameworks follow different philosophies as presented in the above table. It is up to the implementing agency to choose bits and pieces from each of the methodologies, modify and merge them as per their unique set of requirements. Source:: TOGAF and Gartner Report September 2014

46. Methods for implementing Enterprise Architecture In an EA project, Enterprise Architect must select a framework and an implementation methodology. There are multiple frameworks available, it is important to select one and model it to the organization’s requirements Covered in this session

47. Zachman Framework

48. Zachman Framework Overview The Zachman Framework™ is a schema - the intersection between two historical classifications that have been in use for literally thousands of years. The first is the fundamentals of communication found in the primitive interrogatives: What, How, When, Who, Where, and Why. It is the integration of answers to these questions that enables the comprehensive, composite description of complex ideas. The second is derived from the transformation of an abstract idea into an instantiation that was initially postulated by ancient Greek philosophers and is labeled in the Zachman Framework™: Identification, Definition, Representation, Specification, Configuration and Instantiation The Zachman Framework™ typically is depicted as a bounded 6 x 6 “matrix” with the Communication Interrogatives as Columns and the levels of abstractions Transformations as Rows. The Framework classifications are represented by the Cells, that is, the intersection between the Interrogatives and the Transformations. This matrix would necessarily constitute the total set of descriptive representations that are relevant for describing something... anything: in particular an enterprise Source:https://www.zachman.com/about-the-zachman-framework

49. View Points

50. The Zachman Framework Matrix Planner's ViewContextual Owner’'s ViewConceptual Designer’'s ViewLogical Builder'’s Viewphysical Integrator's View User's View. Identification, Definition, Representation, Specification, Configuration Instantiation Why When Who What Where How Source:https://www.zachman.com/about-the-zachman-framework