Enterprise ArchitectureStrategy driven Enterprise ArchitectureAdrian CampbellSlide 2Enterprise ArchitectureWhat is Enterprise Architecture? Slide 3IT responding to Business needsTraditionally, ITs response to business requirements has been to give each user what they wanted, if possible when they wanted it. Applications were built according to the specifications of a particular constituency of users without much thought for the impact on the rest of the enterprise. And as long as the business operated as a collection of discrete business processes, that was okay. Unfortunately, this approach spawned a collection of discrete applications, with discrete and individual data formats. When the business needed to integrate those silo applications to support changing business processes or to integrate application and off the shelf products, chaos ensued.Slide 4IT response to ChaosThe response of IT was to become more precise, creating technology standards that appeared arbitrary to the business, requiring elaborate time consuming development processes and detailed documentation for new systems and changes to existing systems. While IT believed that they were imposing a formal discipline on a chaotic system, the business could only see that these stringent requirements stifled innovation and made it difficult for the business to be agile in response to sometimes rapidly changing market requirements.Slide 5Business response to ITFaced with seemingly arbitrary standards, it was not uncommon for the business to go its own way and develop applications in isolation from ITThis led to further chaos and complexities within the enterprise that interfered with the ability of the business to get services from the IT organisation. Slide 6Business StrategyWhat is the Business Strategy?What is the target operating model ?How do you link the Business Strategy to IT execution?New technologies such as SOA are not enoughBusiness agility and flexibility are importantIncreasing costs need to be controlledSilo Applications need to be consolidationSlide 7TrendsThe current trend in organisations is a renewed focus on business process management (BPM).This is now allowing business users to make immediate changes to their business process models (BPMN), combined with the technology to implement these changes in near real time, to a process orchestration and execution environment (BPEL). This trend drives better business and IT alignment and the ability to trace the business strategy straight through to the business execution.Slide 8Business TrendsImproving business processesControlling increasing operating costsSupporting competitive advantageImproving profitsSlide 9Strategic PrioritiesDelivery projects that enable business growthLinking Business and IT strategies and plansBuilding business skills in the IT organisationBuilding IT skills in the businessDemonstrating the business value of ITMeasuring service levels and performanceSlide 10Technology InvestmentsBusiness Intelligence applicationsSecurity ArchitectureMobile workforce applicationsCollaboration technologiesCustomer sales and self service applicationsSlide 11Strategy & EA Leading organizations use a business strategy driven architecture approach that focuses on translating the key components of the business strategy into a future state vision and an architecture road map they can implement. Enterprise architecture is integrated with other strategic planning disciplines, such as programme/project and application portfolio and managementThe Enterprise Architecture ensures that the long-term vision of the business is preserved as the enterprise builds new business capabilities and improves on old ones.Slide 12Current to TargetEnterprise Architecture is an iterative process that produces four major deliverables:A future-state Enterprise Architecture reference model that realises the business strategy Current-state Enterprise Architecture model (just enough)A gap analysis that identifies the shortfalls of the current state in terms of its ability to support the strategies of the enterpriseAn Architecture Roadmap that defines the initiatives required to migrate from the current state into the future stateSlide 13Enterprise Architecture as StrategyAn Enterprise Architecture driven out of the business strategy provides the enterprise with the highest degree of alignment between the business and IT.The concept of Enterprise Architecture has expanded well beyond the traditional notion of technology architecture. It is now the architecture of the whole enterprise. Slide 14Definition of Enterprise ArchitectureA definition of Enterprise Architecture is addressed in 2 constituent parts enterprise and architecture. The Open Group defines enterprise as follows:An enterprise is any collection of organisations that has a common set of goals and/or a single bottom line. In that sense, an enterprise can be a government agency, a whole corporation, a division of a corporation, a single department, or a chain of geographically distant organisations linked together by common ownership. Gartner define architecture as follows;lThe grand design or overall concept employed in creating a system, as in the architecture of a city or a customer information system; also an abstraction or design of a system, its structure, components and how they interrelate lA family of guidelines (concepts, policies, principles, rules, patterns, interfaces and standards) to use when building a new IT capability. Slide 15Purpose of Enterprise ArchitectureEnterprise Architecture is designed to ensures alignment between the business and IT strategies, operating model, guiding principles, and the software development projects and service delivery. By taking a global, enterprise-wide, perspective across all the business services, business processes, information, applications and technology, Enterprise Architecture ensures the enterprise goals and objectives are addressed in a holistic way across all the application development projects and their deployment into production.Slide 16EA ProcessSlide 17Gartner EA ProcessSlide 18Architecture DomainsArchitecture DomainsStrategy, Vision & PrinciplesBusiness ServicesBusiness Process ArchitectureOrganisation ArchitectureInformation ArchitectureApplication ArchitectureTechnology ArchitecturePerformanceThese architecture domains are interdependent and are developed simultaneously to ensure that the architecture reflects the optimal alignment of IT and the execution environment in support of the business strategy and target operating model.Slide 19Archimate FrameworkSlide 20Strategy, Vision & PrinciplesConcerns the motivation behind the Enterprise Architecture answering the Why questions. Addresses these in terms of the Business and IT Strategies, Target Operating Model, Vision, Principles, Goals and Objectives. Slide 21Business ServicesConcerns the Products and Services that are offered and sold to customers and partners.Addresses these in terms of Business Services, Contracts and Value provided. Slide 22Process ArchitectureConcerns the transformations that are performed in the Enterprise answering the How questions.Addresses these in terms of the Business Processes, Activities, Workflows (Value Streams), Scenarios and Business Events.Slide 23Organisation ArchitectureConcerns the people perspective in the Enterprise answering the Who question.Addresses these in terms of the Locations, Business Actors (people and organisation units), Business Roles and Business Functions (responsibilities), from both an internal (staff, partners) and external (customers, agents) perspective.Slide 24Information ArchitectureInformation Architecture includes the knowledge, information and data that flows through the business processes and the data that is accessed and stored by applications.Answers the What question in the Enterprise Architecture. The What refers to the things or assets which the enterprise needs to know about, use or create. Slide 25Application ArchitectureAddresses the When question in the enterprise, in terms of interaction and dialogue.Answering the How question in terms of the calculations and algorithms needed to implement the transformations in the enterprise.Slide 26Technology ArchitectureTechnology Architecture defines the technologies and infrastructure that support the applicationsAddresses the Where questions in the enterprise in terms of nodes, networks, devices, system software, communication infrastructure and persistent data storage.Slide 27PerformanceWhereas the Strategy, Vision & Principles provides the future direction for the Enterprise, the Performance Architecture is concerned with whether the goals and objectives have been achieved. These are addressed in terms of status, business results, performance metrics and measurements.Slide 28Traceability ViewSlide 29Levels of ConcernSlide 30TraceabilitySlide 31Cube ViewSlide 32The Enterprise Architecture isAn analysis tool to provide abstraction and modelling capabilities at all levels and perspective of the enterprise architectureA planning tool to translate strategic thinking into architecture roadmap of future development and integrationAn analysis tool to clearly plot the key relationships and dependencies between the business services, business processes, applications and technologyA decision-making tool to provide a framework for evaluating-, selecting and justifying strategic development options and architecture decisionsA design tool to provide the required support, in the form of industry best practice design approaches, patterns, guidelines, and reference models A change management tool to provide a framework for synchronising and coordinating development activities across multiple development projects and initiativesA governance tool to provide a sole architecture design authority and a master repository for the target enterprise architecture, and a single architectural blueprint of principles, standards, patterns, policies, guidelines, reference models, reusable assets and templatesAn alignment tool to provide an essential bridge between business strategy and IT delivery, and to furnish business managers with a non-technical over view of the enterprise architecture and how it supports the operating modelSlide 33Benefits of Enterprise ArchitectureEnterprise Architecture will deliver significant improvements in the following areas:The ability to rapidly adjust and adapt to new business circumstancesThe efficient and strategic use of applications & technology across the merged legal entities, and realisation of the Target Enterprise ArchitectureThe management of information/data and knowledge as a corporate assetThe alignment between IT and business for planning and execution purposesThe transparency, impartiality, quality and objectivity of architecture decision making The management of change based on a clear understanding of its impactThe optimisation, cost effectiveness, efficiency of the IT solutionsThe reduction of application complexity, and increased reuse of existing IT assetsThe reporting of performance results, and auditing of changesSlide 34Risks of no Enterprise ArchitectureFailure to implement an Enterprise Architecture will present the following risks:Inability to rapidly respond to challenges driven by business changesLack of focus on enterprise requirementsLack of common direction and synergiesIncomplete visibility of the current and future target enterprise architecture visionInability to predict impacts of future changesIncreased gaps and architecture conflictsLack of commonality and consistency due to the absence of standardsDilution and dissipation of critical information and knowledge of the deployed solutionsRigidity, redundancy and lack of scalability and flexibility in the deployed solutionsLack of integration, compatibility and interoperability between applicationsComplex, fragile and costly interfaces between incongruent applicationsDecision-making gridlock Piece-meal and ad hoc software development driven by a tactical and reactive approachSlide 35The ArchiMate project2 years, July 2002 - December 2004approx. 35 man-years, 4 million euro Consortium of companies and knowledge institutes, directed by the Telematica InstituutABN AMRO, Dutch Tax Administration, ABP Pension Fund, OrdinaUniversity of Nijmegen, University of Leiden,Center for Mathematics & Computer ScienceSlide 36Results in PracticeApplications at numerous organisationsvarious cases at e.g. ABN AMRO, ABP, Dutch Tax Administration, and approximately 25 other companiesImplementation by tool vendorsBiZZdesign Architect, Troux Metis (certified)IDS Scheer (ARIS), Adaptive (currently implementing)Casewise, ASG (considering implementation)EducationArchiMate basic trainingVarious universities and polytechnics use itSlide 37Goal: support for architectssupport for architects is insufficientOverview and dependenciesPowerPoint, Word and Excel are the most important toolsCommunication over architectures with others is difficult“fuzzy pictures”-imageHidden knowledge in architecturesPowerPoint is not suitable for analysisSlide 38ArchiMate GoalsTo describe architectures and their relationsCommunicate architectures with all stakeholders Judge the impact of changesRealize architecture by relating to existing standards, techniques and toolsSlide 39AnalysisArchiMate FocusIntegrationVisualizationSlide 40ArchiMate ForumOpen cooperation between ArchiMate stakeholdersLong term objective: An independent standard for describing Enterprise ArchitecturesRequired: Creating critical massContributing to international standardsSupporting organizations in applying ArchiMateTo this end, the Forum:actively brings in members to increase critical massfacilitates working groups for knowledge exchangesupports members in applying ArchiMateSlide 41Members ArchiMate ForumBiZZdesign ArchitectTool for Enterprise ArchitectureSlide 43BiZZdesign ArchitectTool to model, visualize, analyze and communicate enterprise architecturesBased on meta model of open standard ArchiMateBased on IEEE1471-definition: stakeholders, viewpoints and viewsCovers all EA-domains and relations: business goals and principles, business services, products, processes, business functions, business objects, application services, applications, application data, interfaces, infrastructure services, software, hardware,Supports many architecture frameworks, like IAF, Zachman, DYA, Tapscott, Nolan-Norton, TOGAFSlide 44Concepts Archimate / ArchitectBusinessApplicationTechnologyInformationBehaviourStructureGoals, principles, guidelinesGoals, principles, guidelinesGoals, principles, guidelinesGoals, principles, guidelinesSlide 45Main functionality Architect - 1Modeling business and IT-architectureBased on ArchiMateExtensible meta model, especially properties of objectsImport/export of already existing architecture overviews (harvesting)Tables to and from e.g. Word and ExcelProcess models to and from BiZZdesigner (process tool)Other imports and exports on the basis of XMI (in preparation)Generating views from a modelBased on viewpoint definitionsResulting in graphical schemes, lists, matrices, landscape mapsBoth total views as well as selectionsSlide 46Main functionality Architect - 2Visualization of propertiesColor view, label view, tool tip viewImpact-of-change analysesGraphical or in tablesDocumenting, reporting, and publishing architecturesAdding documentation and hyperlinks to all objectsPublication to Word or HTML (intranet), readable with Office toolsTeam support via repositoryLocking (check in and checkout) en version managementRole based authorizationSeveral repository solutions allowing growth (shared file, Oracle or SQL Server, Adaptive)Slide 47ModellingSlide 48ExamplesSlide 49Impact analysisSlide 50PrinciplesSlide 51Relation principles and modelsSlide 52Landscape mapsSlide 53Multi user supportSlide 54AuthorisationRole basedAny level of granularityEnterprise ArchitectureAdrian CampbellIngenia.Bizadrianingenia.biz+44 (0) 777 555 6878