Introduction to Enterprise Architecture - PowerPoint Presentation

1. Introduction to Enterprise ArchitectureBy Smt. Gayatri PSenior Technical Director

2. Workshop schedulingSession 1: Introduction to Enterprise ArchitectureSession 2: Exploring various EA FrameworksSession 3: IndEA FrameworkSession 4: EA Case Study – Land Hub Andhra PradeshSession 4: EA Case Study – University EA FrameworkSession 5: Interactive session involving question and Answers about Enterprise Architecture and associated

3. Agenda: Session 1Understanding the nexus of Enterprise ArchitectureHistory & Evolution of Enterprise ArchitectureComponents of Enterprise ArchitectureLifecycle of Enterprise ArchitectureImplementation of EAEnterprise Architecture FrameworksZachman FrameworkToGAF IndEA

4. Evolution of Government ObservedIn the early days...Automation of manual taskse.g. Payroll, In-House DevelopmentThe next steps...Application packages (Siloed Apps)e.g. HR, Financial administrationRunning business needs applicationsto be integratedMoving from departmental stovepipes to citizen centric approach in service deliveryTransforming and integrating the back officeCollaborative working and information sharingProduct and service innovationCitizen engagement and inclusionNetworked form of organization model adding to the complexityEnhancing the economic infrastructure and government Performance4

5. Evolution of Government ObservedIn the early days...Now …..5

6. How are we going to survive this Jungle?Incompatibilities Data between applications User interfaces Terminologies Workflows Hardware and software platforms Business and IT !Problems Business KPIs are not aligned with Business Vision/ MissionOrganization structure, functions and technology do not align to meet the business goalsAccurate or complete operational data is unavailable when requiredApplications implemented do not integrate / communicate properlyBusiness processes are ad-hoc and manual and managing them is time consumingTechnology investments are ad-hoc and not cost effective.Decision making takes longer timeData is scattered across departments and information is redundant6

7. Enterprise ArchitectureAgilityCoherenceRobustnessAlignmentInteroperabilityScalabilityAbility to migrateTransformation7

8. 8Defining EnterpriseEnterprise is 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 frequently includes 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 EnterprisesSource:: TOGAF

9. Defining EnterpriseA collection of departments or organizations which may be geographically dispersedAn evolving and transforming business entity having a common ownershipAn enterprise has a shared vision and a common set of goalsIt exists to serve its stakeholders while maintaining its bottom lines It delivers stakeholder services using business processes and multiple IT systemsIt follows policies, guidelines, business rules and legislative requirements of operating geographies

10. 10Defining ArchitectureArchitecture 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 SystemsArchitectureA 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. 11Defining Enterprise Architecture

12. Definition Enterprise 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.12

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

14. 14What is Enterprise Architecture ?A bunch of hardware, software, and technical documents describing enterprise ITA 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.A one-time effort or a projectBusiness Strategy & IT Governance Enterprise ArchitectureWhat is Not Enterprise Architecture?A shared business and IT vision for the organization along with performance benchmarksAn interoperable and cost effective framework which could transcend, be referenced and used for inter-organization discovery and digital collaboration for effective service delivery to stakeholdersIt 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 etcWhat is Enterprise Architecture?

15. AgendaUnderstanding the nexus of Enterprise ArchitectureHistory & Evolution of Enterprise ArchitectureComponents of Enterprise ArchitectureLifecycle of Enterprise ArchitectureImplementation of EAEnterprise Architecture FrameworksZachman FrameworkToGAF IndEA

16. 16 Evolution of Enterprise Architecture

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

18. 18Evolution of Enterprise Architecture – PRISM EA Framework

19. 19ZachmanFramework

20. 20 Evolution of Enterprise Architecture from 90sYear 198719941995199620022003200620092017ActivityZachman’s Enterprise ArchitectureTAFIM releasedTOGAF 1.0 Enterprise Edition releasedClinger – Cohen Bill passedFEA replaces FEAFTOGAF 8.0 Enterprise Edition releasedFEA completed (~)TOGAF 9 releasedIndEA releasedThe 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 architectureGartner Methodology is based on the amalgamation of Gartner framework and Meta architecture development process. 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 improvementThe Zachman FrameworkThe Open Group Architectural FrameworkThe Gartner MethodologyThe Federal Enterprise ArchitectureSource: TOGAF and A comparison of top four EA methodologies, 2007 by MicrosoftThe development of the above frameworks has paved the way for multiple Nations (Korea, Singapore, UAE, UK and USA) and Industry (Microsoft and Oracle) to develop their own tailored enterprise architecture frameworks which are being consumed by enterprises.

21. AgendaUnderstanding the nexus of Enterprise ArchitectureHistory & Evolution of Enterprise ArchitectureComponents of Enterprise ArchitectureLifecycle of Enterprise ArchitectureImplementation of EAEnterprise Architecture FrameworksZachman FrameworkToGAF IndEA

22. Components of Enterprise Architecture22

23. AgendaUnderstanding the nexus of Enterprise ArchitectureHistory & Evolution of Enterprise ArchitectureComponents of Enterprise ArchitectureLifecycle of Enterprise ArchitectureImplementation of EAEnterprise Architecture FrameworksZachman FrameworkToGAF IndEA

24. 24Life Cycle of Enterprise Architecture

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

26. AgendaUnderstanding the nexus of Enterprise ArchitectureHistory & Evolution of Enterprise ArchitectureComponents of Enterprise ArchitectureLifecycle of Enterprise ArchitectureImplementation of EAEnterprise Architecture FrameworksZachman FrameworkToGAF IndEA

27. 27Ecosystem of Enterprise Architecture I

28. 28Ecosystem of Enterprise Architecture II

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

30. 30

31. 31Business LayerIllustrative

32. ImpactDescriptionClarity on long term goalsEA focusses on enterprises developing strategic capabilities. It provides a long-term view of the organization’s processes, systems and technologies. This roadmap and blueprint is enabled through strong Governance and Coordination teams which help the sub-enterprises to achieve the desired state.Strategic, responsive and optimized IT investmentsEA enables IT investments to be optimized, strategic, responsive, promote alignment, standardization and re-use of IT assets. This in turn mandates that IT looks at future requirements and capabilities and is designed to maximize reuse and reduce duplication.Agile EA is viewed as a key enabler by creating, communicating and improving the key requirements, principles and models that describe an enterprise’s future state and enable its evolution.Source:: Enterprise Architecture by Open Group and MIT white paper on Enterprise Architecture Landscape in Singapore Government Agencies published on February 2013EA implementation benefits32

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

34. Need for an Enterprise Architecture34

35. Roles and Responsibilities of an EA35

36. Roles and Responsibilities of an EA36

37. Risks associated with Enterprise Architecture37

38. Risks associated with Enterprise ArchitectureInability to rapidly respond to new requirementsLack of focus on enterprise requirementsLack of common direction and synergiesIncomplete visibility of the current and future visionInability to predict impacts of future changesIncreased gaps and architecture conflictsLack of commonality and consistency Rigidity, redundancy and lack of scalability and flexibility in the deployed solutionsLack of integration, compatibility and interoperability between applicationsPiece-meal and ad hoc software development driven by a tactical and reactive approach38

39. Challenges to EA implementationComponentDescriptionAwareness and understanding of EAMultiple definitions and EA frameworks are currently existing with their own definitions and frameworks. EA has evolved from IT hence there is a confusion on whether EA is to solve IT specific technical problems which enterprises face. Measuring tangible benefits out of EAUS Government Accountability Office (US GAO) identifies EA benefits under lower costs, enhanced productivity, improved management, and greater interoperability. Benefits of EA implementation will cut across ministries and departments which leads to difficulty in establishing the overall benefits. EA implementation and maturity requires significant time to realize improvements in overall enterprise architecture.Lack of EA sponsorshipEA implementation requires support of the senior leadership of an enterprise. Typically this would involve direct reporting to CEO (for private entities) and Cabinet Division / Prime Minister / President (for nations). Without the support from senior leadership, the mandate for reforms and transformations through EA is not implementable.SustainabilityStandards and policies associated with EA are linked to the underlying technology and platforms. With technology refresh, it is important to establish a habit for continuous review and improvement of the existing EA practices without which the entire process would fail in three years.39

40. Current Challenges in Enterprise Architecture40

41. AgendaUnderstanding the nexus of Enterprise ArchitectureHistory & Evolution of Enterprise ArchitectureComponents of Enterprise ArchitectureLifecycle of Enterprise ArchitectureImplementation of EAEnterprise Architecture FrameworksZachman FrameworkToGAF IndEA

42. Enterprise Architecture FrameworksIndEAGartnerFEA42

43. Countries who have adopted EA  Document NameAustralian Government Architecture Reference ModelsNSW Government Enterprise Architecture StrategyAdministration on the NetThe ABC guide of eGovernment in Austria FedICT e-govBhutan e-Government Master PlanGovernment of Canada Enterprise ArchitectureWhite Paper on Enterprise Architecture Working GroupStandards and Architectures for eGovernment ApplicationsGovernment Enterprise ArchitectureOman eGovernment Architecture Framework (OeGAF) - A Quick GlanceAndhra Pradesh State Enterprise Architecture (e-Pragati)Sr. No. ParametersAustraliaNew South Wales (Southeastern Australian state)AustriaBelgiumBhutanCanadaDenmarkGermanyNew ZealandOmanIndia1 Architecture TypeFederatedFederatedFederatedFederatedNAFederatedFederatedNA FederatedNA Federated2 MethodologyFEATOGAFSOA ParadigmSOA ParadigmTOGAFTOGAFZachmanRM-ODP TOGAFTOGAF3Architecture Ref ModelsVision/MissionYYYNAYYYYYYY4Performance Ref ModelYNNANANNANANAYNY5Business Ref ModelYYNANAYYNAYYYY6Service Ref ModelYNNANANNANAYNNY7Data Ref ModelYYNANAYYNAYYYY8Application Ref ModelNYNANAYYNAYYYY9Technology Ref ModelYYNANAYYNAYYYY10Security Ref ModelNNNANANNANAYYNY11Governance Ref ModelNYNANAYYNANANANAY43

44. Popular EA Frameworks

45. EA FrameworksEnterprise Architecture FrameworksFEAGartnerZachmanTOGAFFocus areas of the four Enterprise Architecture Frameworks:TOGAF – Process CentricFEA – Implementation CentricZachman – Taxonomy/Framework CentricGartner – Practice/outcome CentricEach 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 201445

46. 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 Methods for implementing Enterprise Architecture Covered in this session46

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 InstantiationSource:https://www.zachman.com/about-the-zachman-frameworkThe 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 enterprise48

49. View Points49

50. Source:https://www.zachman.com/about-the-zachman-frameworkWhatHowWhereWhoWhenWhyPlanner's ViewContextualOwner’'s ViewConceptualDesigner’'s ViewLogicalBuilder'’s ViewphysicalIntegrator's ViewUser's View.Identification, Definition, Representation, Specification, Configuration InstantiationThe Zachman Framework Matrix50

51. Source:https://www.zachman.com/about-the-zachman-frameworkZachman Framework Rules51

52. Source:https://www.zachman.com/about-the-zachman-frameworkThe Zachman Framework™ is a metamodel and unlike a methodology, does not imply anything about:Whether you do Architecture or whether you simply build implementations that is, whether you build Primitive Models, the ontological, single-variable intersections between the Interrogatives and the Transformations or whether you simply build ad hoc, multi-variable, composite models made up of components of several Primitive ModelsHow you do Architecture: top-down, bottom-up, left to right, right to left, where to start, etc., etcThe long-term/short-term trade-off relative to instantiating the expression of the components of the object that is, what is formalized in the short-term for implementation purposes versus what is engineered for long-term reuseHow much flexibility you want for producing composite models (Enterprise implementations) from your Enterprise Architecture (primitive models), that is, how constrained (little flexibility) or unconstrained (much flexibility) you make the horizontal, integrative relationships between the Cell components across the Rows and the vertical, transformational relationships of the Cell components down the Columns.Although these are significant, identifiable, methodological choices, they are not prescriptions of the Framework structureThe Zachman Framework52

53. TOGAF Framework

54. TOGAF- The Open Group Architecture Framework The Open Group Architecture Framework (TOGAF) is a framework for enterprise architecture which provides an approach for planning, designing, implementing, and governing an enterprise information technology architectureSource:: TOGAF 9.1Overview54

55. 9 ComponentsTOGAF- The Open Group Architecture Framework 55

56. Architecture Development Method (ADM)TOGAF- The Open Group Architecture Framework The TOGAF Architecture Development Method (ADM) provides a tested and iterative process for developing EA. It comprises instituting an architectural framework, transitioning, developing architecture contents, and governing the comprehension of architectures.56

57. TOGAF-The Open Group Architecture Framework TOGAF Architecture Domains Architecture DomainsDescription Business Architecture Business Strategy, Governance, Organization and key Business Process Data Architecture Structure of Organization’s logical and physical data assets and data management resourcesApplication Architecture A blueprint of individual application systems to be deployed, their interactions, and their relationships to the core business processes of the organization Technology Architecture Software and Hardware capabilities that are required to support the deployment of business, data and application services. This includes IT infrastructure, middle ware, networks, communications, processing and standards Source:: TOGAF 9.157

58. 4 Iteration cycles, based on a grouping of phases:TOGAF- The Open Group Architecture Framework (Architecture Capability )(Architecture development)(Transition planning)Architecture governance58

59. Enterprise ContinuumTOGAF- The Open Group Architecture Framework 59

60. Architecture Content FrameworkTOGAF- The Open Group Architecture Framework 60

61. Enterprise Repository Eight Reference Models of IndEATOGAF- The Open Group Architecture Framework 61

62. ADM Guidelines and TechniquesGuidelines for Adapting the ADM ProcessWays to apply iteration to the ADM,Applying the ADM at different levels of the enterprise,Security considerations for the different phases andSupporting SOATechniques for Architecture DevelopmentArchitecture Principles,Stakeholder Management,Architecture Patterns,Business Scenarios,Gap Analysis,Migration Planning TechniquesInteroperability Requirements,Business Transformation Readiness Assessment,Risk Management,Capability-Based PlanningTOGAF- The Open Group Architecture Framework 62

63. TOGAF-The Open Group Architecture Framework TOGAF Capability Framework Source:: TOGAF 9.163

64. Source:: TOGAFTOGAF-The Open Group Architecture Framework 64

65. IndEA Framework

66. India Enterprise Architecture (IndEA)IndEA is a framework for developing a holistic architecture treating the Government as a single enterprise or more realistically, as an Enterprise of Enterprises, which are functionally inter-relatedIndEA is a structured combination of several Reference Models that, together, enable a boundary-less flow of information across the length and breadth of the government and facilitate the delivery of integrated services to the stakeholders It is an authoritative reference providing an integrated, consistent and cohesive view of strategic goals, business services and enabling technologies across the entire organization66

67. IndEAWhole of Government WoG Level67

68. IndEAAgency Level68

69. IndEASolution Level69

70. IndEA vis-à-vis State Enterprise Architecture in the National Context70

71. Comparison of a few EA frameworks

72. Comparison of the frameworksSr #CriteriaDescription of CriteriaPreferred Framework1Taxonomy CompletenessHow well you can use the methodology to classify the various architectural artifacts?Zachman2Process CompletenessHow fully the methodology guides you through a step-by-step process for creating an enterprise architecture?TOGAF3Reference-model GuidanceHow useful the methodology is in helping you build a relevant set of reference models.?FEA, TOGAF4Practice GuidanceHow much the methodology helps you assimilate the mind-set of enterprise architecture into your organization and develop a culture in which it is valued and used?Gartner5Maturity ModelHow much guidance the methodology gives you in assessing the effectiveness and maturity of different organizations within your enterprise in using enterprise architecture?FEA6Business FocusWhether the methodology will focus on using technology to drive business value, in which business value is specifically defined as either reduced expenses and/or increased income?Gartner7Governance GuidanceHow much help the methodology will be in understanding and creating an effective governance model for enterprise architecture?FEA, Gartner8Partitioning GuidanceHow well the methodology will guide you into effective autonomous partitions of the enterprise, which is an important approach to managing complexity?FEA9Prescriptive CatalogHow well the methodology guides you in setting up a catalogue of architectural assets that can be reused in future activities?FEA10Vendor NeutralityHow likely you are to get locked-in to a specific consulting organization by adopting this methodology?TOGAF11Information AvailabilityAmount and quality of free or inexpensive information about this methodology.TOGAF12Time to ValueLength of time you will likely be using this methodology before you start using it to build solutions that deliver high business value.GartnerSource:: A comparison of top four EA methodologies, 2007 by Microsoft72

73. Comparison between EAIMMajor Aspects of EAIM ( Enterprise Architecture Implementation Methodologies ) Concepts : EA concepts are important for Enterprises 1.Alignment between Business and IT 2.Importance of Repository3.Association & Communication among artefacts4. EAIM Strategy5. Governance Modeling :EA concepts provide basis for EAIM. Modeling of different perspectives of enterprise are significant part of modelling 1.Easy to Use2.Easy to learn 3.Traceability4.Consistency5.Different Views 6.Complexity Process :The activities and steps that guide Enterprise Architects in EA implementation 1.Requirement2.Step by Step3.Detailed Design 4.Implementation 5.Guidelines6.Maintenance73

74. Comparison between EAIMConcept TOGAFDODAFGartnerFEAAlignment between Business and IT MMMLAssociation & Communication among artefactsHMMMGovernance HMMLImportance of RepositoryMMMMEAIM StrategyHHMHModelingTOGAFDODAFGartnerFEAEasy to UseLMMMEasy to learn LMMMTraceabilityHLLMConsistencyHLLMDifferent Views MMLMComplexity LLLLLegendLlow consideration or high level descriptionMMedium consideration or little descriptionHhigh consideration or detailed and clear description74

75. Comparison between EAIMProcess :TOGAFDODAFGartnerFEA1.RequirementHLLL2.Step by StepMMMM3.Detailed Design MMMM4.Implementation MMMM5.GuidelinesHMLH6.MaintenanceMLLMLegendLlow consideration or high level descriptionMMedium consideration or little descriptionHhigh consideration or detailed and clear description75

76. Thank you