A practical guide to enterprise architecture

1、ea management guideoutline collection(last updated on 12/10/2005)list of outlines and definitionsthe practical guide to enterprise architecture2enterprise architecture planning: developing a blueprint for data, applications, and technology3building enterprise information architecture: reengineering

2、information systems3lightweight enterprise architectures3enterprise business architecture: the formal link between strategy and results3sung kun kim:3our definition about ea3ea-based irm (information resource management) guide4william sweet7outline7russell boyd8enterprise architecture management gui

3、de (eamg)8what is enterprise architecture.8what is ea management.8enterprise architecture management elements8john wu9what is ea ?9outline10hong s kim111. what is enterprise architecture ?112. what is enterprise architecture management ?123. the outline you recommend and the information about its so

4、urce.12ben bove13enterprise architecture book of knowledge13haiping luo14part i: definitions14part ii: ea management guides outline16mitre18guide to the (evolving) enterprise architecture body of knowledge18what is ea20ea knowledge areas20scott bernard21what is ea21an introduction to enterprise arch

5、itecture21feac institute: federal enterprise architecture certification program21feac dodaf course23klaus d. niemann25what is enterprise architecture25what is enterprise architecture management25outline26= the practical guide to enterprise architectureby james mcgovern, scott w. ambler, michael e. s

6、tevens, james linn, elias k. jo, vikas sharan comprehensive explanation of enterprise architecture concepts and methods extend the rational unified process to include enterprise architecture unified view of the various architectural disciplines to create strategic blueprints perspectives on enterpri

7、se development and technologyindispensable technical, process, and business insight from leading enterprise architectsmany organizations today face the challenge of designing, building, and maintaining large-scale distributed enterprise systems that are able to adapt to changing business needs. many

8、 repeat the mistakes of others, resulting in cost overruns, blown deadlines, and lost opportunity. todays business climate places additional burden on it to deliver. ever-adapting business drivers can diverge from the capabilities of the enterprise it systems today, especially if the systems are com

9、plex, fragile, and intolerant of change. enterprise architecture can help future-proof it investments made today.a practical guide to enterprise architecture helps readers create adaptive architecture strategies for successfully implementing enterprise architectures. this classic handbook goes beyon

10、d theory and presents strategies that are based on experiences within organizations across multiple industry verticals. behind each opinion, technique, and principle is a wealth of knowledge provided by some of the best-known industry thought leaders today.this books authors have architected industr

11、ial-strength software and infrastructure for many of the worlds leading firms-in financial services, telecommunications, media, and e-business. they present practical guidance, candid assessments of existing practice, and detailed examples from their own experience. coverage includes: strategies for

12、 enterprise architecture-which ones work and why proven product line practices for streamlining the design of enterprise software understanding how to translate key business drivers into enterprise architecture output agile architectural and modeling techniques-presented by their creator, scott ambl

13、er architecting presentation tiers, user experience, and usability methods to create a reusable base of core assets overcoming the challenges of transitioning to agile methods identifying architecture enabling human resource practiceswhether youre a working architect or plan to become one, a practic

14、al guide to enterprise architecture will be your timely, trusted advisor-today and for years to come.= enterprise architecture planning: developing a blueprint for data, applications, and technologyby steven h. spewaktable of contents= building enterprise information architecture: reengineering info

15、rmation systemsby melissa cooktable of contents = lightweight enterprise architecturesby fenix theuerkorntable of contents = enterprise business architecture: the formal link between strategy and resultsby ralph whittle =sung kun kim:our definition about ea is the explicit description and documentat

16、ion of the current and desired relationships among business and management process and information technology.however, we dont use the term ea management.instead, we use the term ea-based irm which is defined as theprocess of managing information resources through defining andutilizing the relations

17、hip among business and management process andinformation technology in an effort to accomplish agency missions.we think that the ea-based irm consists of the following stages:1) irm planning2) organizing3) architecture construction4) utilization of architecture5) maintenance of architecture6) evalua

18、tion of irm efforts.ea-based irm (information resource management) guideobjectives :this guide was written by koreas ministry of government administration & home affairs(mogaha http:/www.mogaha.go.kr/), koreas e-government leading ministry, and was distributed to all government ministries and agenci

19、es in an effort to promote an introduction of ea approach in their it management practices.language:koreandate: 2005, augustproject leader:sung kim(professor of chung-ang university & advisor of presidential advisory committee of korea e-government)key terms:information resource management: the proc

20、ess of managing information resources to accomplish agency missions.ministry: a government department.government-wide: throughout all ministries.contents:part i : a synopsis of ea-based irm guide chapter 1: an introduction of ea-based irm guide 1.1 objectives of ea-based irm guide1.1.1 it management

21、 problems and their causes1.1.2 why we need ea-based irm guide? 1.2 organization of ea-based irm guide 1.3 where and how we can use ea-based irm guide?part ii : an understanding of irm and ea chapter 2: introduction to irm 2.1 it management problems faced by public sectors and new approaches to them

22、 2.1.1 characteristics of public sectors it projects2.1.2 sources and causes of public sectors it management problems2.1.3 united states effort to overcome these problems 2.2 concept and characteristics of information resource management(irm)2.2.1 concept of irm2.2.2 characteristics of irm chapter 3

23、: introduction to enterprise architecture 3.1 what ea is and how it relates to irm?3.1.1 definition of enterprise architecture3.1.2 the relationship of ea with irm 3.2 evolution of ea3.2.1 how ea has evolved in us?3.2.2 how ea has evolved in korea? 3.3 contents and representation of architecture inf

24、ormation3.3.1 architecture framework3.3.2 architecture-related reference model3.3.3 how architecture information can be represented? 3.4 an understanding of architecture construction process3.4.1 eap3.4.2 pgfea3.4.3 togaf3.4.4 dodaf 3.5 ea management tools3.5.1 what ea management tools are?3.5.2 fun

25、ctions of ea management tools3.5.3 classification of ea management tools3.5.4 benefits of ea management tools3.5.5 evaluation & selection criteria of ea management tools3.5.6 roles & responsibilities with respect to usage of ea management tools3.5.7 an understanding of ea management system chapter 4

26、: an analysis of irm practices by korea public sector 4.1 irm practices4.1.1 how we view irm practices?4.1.2 types of it management decision-making 4.2 problems of irm practices4.2.1 problems in planning & organizing stage4.2.2 problems in acquisition & construction stage4.2.3 problems in operating

27、& supporting stage4.2.4 problems in evaluation & monitoring stagepart iii : guide to ea-based irm (ministry-level) chapter 5: general guide to ea-based irm 5.1 overview of ea-based irm5.1.1 definition of ea-based irm5.1.2 why ea is needed for effective irm? 5.2 ea-based irm process5.2.1 irm planning

28、5.2.2 organizing5.2.3 architecture construction5.2.4 utilization of architecture5.2.5 maintenance of architecture5.2.6 evaluation of irm efforts 5.3 principles of ea-based irm 5.4 organizational structures for effective ea-based irm5.4.1 roles & responsibilities needed in ea-based irm5.4.2 organizat

29、ion chart of ea-based irm chapter 6: guide of ea construction 6.1 overview of ea construction guide6.1.1 objectives of ea construction guide6.1.2 contents & organization of ea construction guide 6.2 architecture information6.2.1 business architecture information6.2.2 data architecture information6.2

30、.3 application architecture information6.2.4 technical architecture information6.2.5 investment architecture information chapter 7: guide of ea utilization 7.1 overview of ea utilization guide7.1.1 objectives of ea utilization guide7.1.2 organizational structures for ea utilization7.1.3 ea utilizati

31、on process 7.2 architecture utilization in planning & organizing stage7.2.1 information strategy planning7.2.2 it budgeting 7.2.3 identification & proposing of new it projects7.2.4 determination of future it directions7.3 architecture utilization in acquisition & construction stage7.3.1 determinatio

32、n of acquisition approaches7.3.2 management of system development project7.3.3 acquisition & maintenance of applications7.3.4 acquisition & maintenance of infrastructures7.4 architecture utilization in operating & supporting stage7.4.1 it asset management7.4.2 information systems operation7.4.3 it s

33、ecurity7.4.4 joint usage of it resources7.5 architecture utilization in evaluation & monitoring stage7.5.1 performance evaluation7.5.2 evaluation of internal controlpart iv : future direction for government-wide ea-based irm chapter 8: government-wide ea-based irm 8.1 sources & causes of government-

34、wide ea-based irm practices 8.2 needs & objectives of government-wide ea-based irm 8.3 future works & strategies for government-wide ea-based irm8.3.1 future works for government-wide ea-based irm8.3.2 future strategies for government-wide ea-based irm = william sweetoutlinei. what is enterprise arc

35、hitecture ii. what is enterprise architecture management iii. enterprise architecture managementb.ea program managementb.1identify executive sponsorshipb.2align with it governance practicesb.2a) portfolio managemnetb.3identify program managerb.4identify program management staffb.5implement risk mana

36、gementb.6implement change managementb.7implement communications managementb.8implement architectural review boardb.9 plan the ea lifecyclec.ea lifecycle managementc.1choose an architectural framework(the framework is an existing template and process)c.2develop the as-is architectural blueprint(the b

37、lueprint is the completed framework templates)c.3develop the to-be architectural blueprint(align business mission with technology platform)c.4develop the architectural transition plan(transition from as-is to to-be)c.5develop the enterprise architecture standards(standards to be enforced and enforce

38、ment process)c.6periodic refresh of architecture blueprints and standardsiv. glossary of definitions and acronyms (if any) = russell boydenterprise architecture management guide (eamg)draft outline by russell boyd, november 30, 2005what is enterprise architecture. enterprise architecture is a strate

39、gic information asset base, which defines the mission, the information necessary to perform the mission, and the transitional processes for implementing new technologies in response to the changing mission needs. an enterprise architecture includes a baseline architecture, target architecture, and a

40、 sequencing plan. (a practical guide to federal enterprise architecture, cio council, version 1.0, february 2001)what is ea management.enterprise architecture management (eam) addresses at a holistic way the elements of strategy, frameworks, the overall ea process, methods and techniques, standards

41、and tools to enable the coordination and delivery of the various elements that makeup the enterprise architecture within the organization to maximize business benefits. enterprise architecture management elementsea assessmentea strategy and planningea project management and process ea development ea

42、 maintenanceea governance organization and staffea in investment management cpic portfolio managementea performance measurement & communication1. glossary elements in this context are all elements that enclose the areas of people, processes, business and technology. examples are: strategies, busines

43、s drivers, principles, stakeholders, budgets, domains, functions, processes, services, and communication.= john wuwhat is ea ? ea was initiated to overcome the challenge automation island and stove pipe systems. it pursue the commonality from different system to share resources and provide interoper

44、ability. it is a different paradigm from application development, business process reengineering and strategic planning. application development is a paradigm to develop application systems to automate business processes and manage information. bpr is the effort by taking advantage of technology evo

45、lution to optimize business processes, it pursue the uniqueness to win the competitive edge. strategic planning establishes the vision and direction by the decision makers. the following figure illustrate the relation between ea , application development , bpr and strategic planning. ea address the

46、commonality to share resources, bpr pursue uniqueness to win the competitive edge, application system support the strategic planning by leveraging on the common resource to enable agile application development to automate the optimized business processes. enterprise architecture is initiated in the

47、information age, it means to develop automation with enterprise consideration rather then by each individual system. taking the term of enterprise architecture out of the context from information age, it has been interpreted as “architecting the enterprise”. under this concept, ea has become the umb

48、rella term for strategic planning, business process reengineering, application development and automation design. ea has become a concept rather than a discipline. “architecture the enterprise” has been a concept before information age from the early days when emperor nero attempted to transform the

49、 city of rome, and in the 20th century , the socialism country architect the planned economy , in the late 20th century, the effort of enterprise engineering. all of this concept has come and go similar to rubik cube .ea is here to stay. it is not the best interest of ea to become the next wave of “

50、 “architecting the enterprise”. ea is an emerging paradigm in the evolution of information age rather than a redundant paradigm of strategic planning, application development and business process reengineering. outline1 why ea ? 1.1 comprehend the big picture 1.2 tracking current environment 1.3 est

51、ablish target architecture 1.4 plan for transition 1.5 support investment management 1.6 support project management 1.7 support procurement management 1.8 support sdlc management 1.9 support security management 1.10 support portfolio management2. what is ea 2.1 the ea paradigm2.2the ea context2.3the

52、 ea myth 3. governance and compliance processes management 3.1 governance structure 3.2 stakeholders 3.3 ea standards change management 3.4 sdlc processes 3.5 cpic process. 3.6 procurement processes 3.7 security certification processes 2.8 the governance framework4.0 business architecture 4.1 archit

53、ecture overview 4.2 mission 4.2 functions4.3 information 4.4 organizations 4.5 locations 4.8 mission workload 5. current environment 5.1 application system inventory 5.2 infrastructure system inventory6. target architecture 6.1 reference models for engineering of reuse6.1.1 brm 6.1.2 prm 6.1.3 srm 6

54、.1.4 drm 6.1. 5 trm 6.2 solution architectures for engineering of sharing 6.2.1 application architecture 6.2.2 data architecture 6.2.3 technology architecture 6.3 target architecture framework 6.4 transition plan 7 portfolio management 7.1 report cards 7.2 earn value management 7 .3 maturity 8. communication 8.1 architecture drawings8.2.ea portal8.3.ea liaison= hong s kim1. what is enterprise architecture ?my definition of ea:enterprises essential framework