Strategy driven Enterprise Architecture_第1頁
Strategy driven Enterprise Architecture_第2頁
Strategy driven Enterprise Architecture_第3頁
Strategy driven Enterprise Architecture_第4頁
Strategy driven Enterprise Architecture_第5頁
已閱讀5頁,還剩50頁未讀, 繼續(xù)免費閱讀

下載本文檔

版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進行舉報或認(rèn)領(lǐng)

文檔簡介

1、Enterprise ArchitectureStrategy driven Enterprise ArchitectureAdrian CampbellEnterprise ArchitectureWhat is Enterprise Architecture? IT responding to Business needsTraditionally, ITs response to business requirements has been to give each user what they wanted, if possible when they wanted it. Appli

2、cations 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 colle

3、ction 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.IT response to ChaosThe response of IT was to become mo

4、re 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, t

5、he 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.Business response to ITFaced with seemingly arbitrary standards, it was not uncommon for the business to go

6、 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. Business StrategyWhat is the Business Strategy?What is the target operating model ?How

7、 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 consolidationTrendsThe current trend in organisations is a renewed focus on business process

8、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 ali

9、gnment and the ability to trace the business strategy straight through to the business execution.Business TrendsImproving business processesControlling increasing operating costsSupporting competitive advantageImproving profitsStrategic PrioritiesDelivery projects that enable business growthLinking

10、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 performanceTechnology InvestmentsBusiness Intelligence applicationsSecurity ArchitectureMobile workforce application

11、sCollaboration technologiesCustomer sales and self service applicationsStrategy & 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 imp

12、lement. 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

13、 improves on old ones.Current 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 identif

14、ies 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 stateEnterprise Architecture as StrategyAn Enterprise Architecture driven out of

15、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. Definition of Enterpri

16、se 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 enterpri

17、se 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;The grand design or overall concept employed in creating a system, as i

18、n 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 A family of guidelines (concepts, policies, principles, rules, patterns, interfaces and standards) to use when building a new IT capability. Pu

19、rpose 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 s

20、ervices, 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.EA ProcessGartner EA ProcessArchitecture Dom

21、ainsArchitecture DomainsStrategy, Vision & PrinciplesBusiness ServicesBusiness Process ArchitectureOrganisation ArchitectureInformation ArchitectureApplication ArchitectureTechnology ArchitecturePerformanceThese architecture domains are interdependent and are developed simultaneously to ensure that

22、the architecture reflects the optimal alignment of IT and the execution environment in support of the business strategy and target operating model.Archimate FrameworkStrategy, Vision & PrinciplesConcerns the motivation behind the Enterprise Architecture answering the Why questions. Addresses these i

23、n terms of the Business and IT Strategies, Target Operating Model, Vision, Principles, Goals and Objectives. Business 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. Process Ar

24、chitectureConcerns 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.Organisation ArchitectureConcerns the people perspective in the Enterprise

25、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.Information ArchitectureInformation Ar

26、chitecture 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 o

27、r create. Application 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.Technology ArchitectureTechnology Architecture define

28、s 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.PerformanceWhereas the Strategy, Vision & Principles provides the future

29、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.Traceability ViewLevels of ConcernTraceabilityCube ViewThe Enterprise Archi

30、tecture 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 relationshi

31、ps 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

32、 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 desi

33、gn 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

34、 delivery, and to furnish business managers with a non-technical over view of the enterprise architecture and how it supports the operating modelBenefits of Enterprise ArchitectureEnterprise Architecture will deliver significant improvements in the following areas:The ability to rapidly adjust and a

35、dapt 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 plannin

36、g 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 increa

37、sed reuse of existing IT assetsThe reporting of performance results, and auditing of changesRisks 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 enterp

38、rise 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 standardsDiluti

39、on 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 incongrue

40、nt applicationsDecision-making gridlock Piece-meal and ad hoc software development driven by a tactical and reactive approachThe ArchiMate project2 years, July 2002 - December 2004approx. 35 man-years, 4 million euro Consortium of companies and knowledge institutes, directed by the Telematica Instit

41、uutABN AMRO, Dutch Tax Administration, ABP Pension Fund, OrdinaUniversity of Nijmegen, University of Leiden,Center for Mathematics & Computer ScienceResults in PracticeApplications at numerous organisationsvarious cases at e.g. ABN AMRO, ABP, Dutch Tax Administration, and approximately 25 other comp

42、aniesImplementation by tool vendorsBiZZdesign Architect, Troux Metis (certified)IDS Scheer (ARIS), Adaptive (currently implementing)Casewise, ASG (considering implementation)EducationArchiMate basic trainingVarious universities and polytechnics use itGoal: support for architectssupport for architect

43、s 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 analysisArchiMate GoalsTo describe architectures and their r

44、elationsCommunicate architectures with all stakeholders Judge the impact of changesRealize architecture by relating to existing standards, techniques and toolsAnalysisArchiMate FocusIntegrationVisualizationArchiMate ForumOpen cooperation between ArchiMate stakeholdersLong term objective: An independ

45、ent 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 exchangesupport

46、s members in applying ArchiMateMembers ArchiMate ForumBiZZdesign ArchitectTool for Enterprise ArchitectureBiZZdesign 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, inte

溫馨提示

  • 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 人人文庫網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負(fù)責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時也不承擔(dān)用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。

評論

0/150

提交評論