Muutke küpsiste eelistusi

FEAC Certified Enterprise Architect CEA Study Guide [Raamat]

3.67/5 (9 hinnangut Goodreads-ist)
, ,
  • Formaat: Book, 832 pages, kõrgus x laius x paksus: 241x193x47 mm, kaal: 1562 g
  • Sari: Certification Press
  • Ilmumisaeg: 16-Aug-2011
  • Kirjastus: Osborne/McGraw-Hill
  • ISBN-10: 0071756132
  • ISBN-13: 9780071756136
Teised raamatud teemal:
FEAC Certified Enterprise Architect CEA Study GuideSuurem pilt
  • Formaat: Book, 832 pages, kõrgus x laius x paksus: 241x193x47 mm, kaal: 1562 g
  • Sari: Certification Press
  • Ilmumisaeg: 16-Aug-2011
  • Kirjastus: Osborne/McGraw-Hill
  • ISBN-10: 0071756132
  • ISBN-13: 9780071756136
Teised raamatud teemal:
Püsilink: https://www.kriso.ee/db/9780071756136.html
Märksõnad:
Publisher's Note: Products purchased from Third Party sellers are not guaranteed by the publisher for quality, authenticity, or access to any online entitlements included with the product. The best fully integrated study system availableFilled with practice questions, examples, and illustrations, FEAC Certified Enterprise Architect CEA Study Guide covers what you need to knowand shows you how to preparefor this challenging exam.





100% complete coverage of all official objectives for the FEAC CEA exam Modeling techniques for enterprise architecture implementations Enterprise architecture case study: Richard M. Nixon Airport Simulated exam questions that match the format, tone, topics, and difficulty of the real exam





Covers all the exam topics, including: Enterprise Architecute Concepts * Planning, Implementating, and Disseminating the EA * Maintaining, Governing, and Using the EA * All Viewpoint * Strategic/Capability Viewpoint * Porject Viewpoint * Operational Viewpoint * Systems Viewpoint * Services Viewpoint * Data and Information Viewpoint * Technology and Standards Viewpoint * EA in Government, Defense, and the Commercial Sector * EA Tools and Repositories

CD-ROM includes:





CEA-oriented practicums Practice exams for the FEAC FEAF and DoDAF programs and a list of study questions Major documentation for the FEAF and DoDAF programs E-book for studying on the go





Prakash Rao, MS, CEA, is chief architect at Metadata Management Corporation. He teaches Enterprise Architecture at the FEAC Institute.

Ann Reedy, Ph.D., worked on the development and editing of the early version of the DoD Architecture Framework at MITRE and teaches DoD Architecture Framework for the FEAC Institute.

Beryl Bellman, Ph.D., is co-founder and academic director of the FEAC Institute and a tenured full professor of Communication Studies at California State University at Los Angeles. He has more than 25 years' consulting experience in the EA field.
Foreword xxix
Acknowledgments xxxiii
Preface xxxv
Introduction xxxix
Part I Foundation Concepts
1.1 Why EA and Why This Book
3(28)
Emergence of EA
5(7)
Early 1990s: Emergence of the CIO as an Executive Role and a Seat for IT at the Table
5(1)
1994: Federal IT Expenditure Was on the GAO's Radar
6(1)
1996: Clinger-Cohen Act: The ITMRA Compliance Threat
7(1)
What About the Nonfinancial Issues That Plagued the CIO?
8(1)
1999: Federal Enterprise Architecture Framework (FEAF)
8(1)
1999-2000: The Y2K Threat
9(1)
2001: The Disaster Recovery Threat
9(1)
Today: Current Enterprise Challenges
10(2)
The Case for Enterprise Architecture
12(1)
Communication
12(12)
Unifying Architecture Frameworks
13(1)
A Rich Set of Models
13(1)
Transformation
14(1)
Addressing a Family of Problems and Solutions Simultaneously
15(3)
Enterprise Architecture Certification
18(6)
The Relevance of This Text to Other EA Certifications
24(2)
Zachman Institute Certification
25(1)
The Open Group Certification
25(1)
Certification Process and Certificates
25(1)
FEAC Certification Process
26(1)
Learning Objectives for This Book
26(1)
Scope of the FEAC Certification Syllabus
27(1)
Formal Coursework
27(1)
Practicum Project
27(1)
Questions
28(2)
Reference List
30(1)
1.2 Enterprise Architecture Concepts
31(36)
Enterprise
32(1)
Segments
33(1)
Initiatives and Solutions
34(1)
Architecture
35(4)
Architectural Description
35(1)
Implicit and Explicit Architectural Descriptions
36(3)
Benefits of an Explicit Architecture
39(1)
Architecture Viewpoints
39(2)
Governance Viewpoint
40(1)
Project Viewpoint
40(1)
Capability Viewpoint
40(1)
Operational Viewpoint
40(1)
Architecture Models
41(1)
Enterprise Architecture
42(1)
Architecture Framework
43(3)
Benefits of Architecture Frameworks
45(1)
Example Architecture Frameworks
46(19)
Zachman Framework
46(2)
Federal Enterprise Architecture Framework (FEAF)
48(1)
Department of Defense Architecture Framework (DoDAF) Version 2.0
49(1)
The Open Group Architecture Framework (TOGAF)
50(2)
Other Frameworks
52(13)
Questions
65(1)
Reference List
65(2)
1.3 Enterprise Architecting
67(24)
Scope of the Enterprise Architecture
68(3)
Enterprise Level
69(1)
Segment Level
69(1)
Solution Level
70(1)
The Six Step Process
71(5)
Step 1 Determine the Intended Use of the Architecture
72(1)
Step 2 Determine the Scope of the Architecture
73(1)
Step 3 Determine the Data Needed to Support Architecture Development
74(1)
Step 4 Collect, Organize, Correlate, and Store Architecture Data
74(1)
Step 5 Conduct Analysis in Support of Architecture Objectives
74(1)
Step 6 Document Results in Accordance with Decision-Maker Needs
75(1)
Architecting the Business Domain
76(5)
Architecting the IT and Infrastructure Domain
81(6)
System Viewpoint
82(2)
Service Viewpoint
84(2)
Communications Infrastructure
86(1)
Questions
87(1)
Reference List
87(4)
Part II Architecture Development and Use
2.1 The Importance of Culture
91(32)
The Relevance of Culture to Enterprise Architecture
101(2)
Enacting Organizations
103(5)
Three Levels of Culture (Edgar Schein)
108(5)
Locating Culture as Business Rules
113(4)
The Emergence of Culture
117(1)
Perspectives on Culture
118(1)
Questions
119(1)
End Note
120(1)
Reference List
120(3)
2.2 Planning the EA
123(54)
Scoping the Architecture Work
125(35)
Purpose
125(6)
Scope
131(3)
Identifying Needed Data
134(3)
Determine What Models to Use: How to Organize and Correlate Data
137(13)
Planning Examples
150(9)
Success Factors in Scoping the Architecture Work
159(1)
Planning the Architecture Project
160(11)
The Project Plan
161(1)
What Is to Be Done
161(2)
Who Is Responsible
163(3)
How the Work Will Be Done: Managerial and Technical Approaches
166(2)
When Will the Work Be Done
168(3)
Summary of Project Planning
171(1)
Success Factors for Planning
171(1)
Summary of Six Step Process Advice
172(1)
Questions
173(2)
Reference List
175(2)
2.3 Implementing the Enterprise Architecture
177(26)
Statement of Work (SOW)
178(5)
Title
179(1)
Project Background
179(1)
Project Description and Scope
179(1)
Architecture Vision
179(1)
Management Approach
179(1)
Change Procedures
180(1)
Responsibilities and Deliverables
180(2)
Acceptance Criteria and Procedures
182(1)
High-Level Project Schedule
182(1)
Support/Automated Environment and Tools
183(1)
Work Breakdown Structure (WBS)
183(1)
Implementation Steps
183(13)
Architecture Development Methodology/Process
184(1)
EA LifEcycle
184(12)
Data Strategies
196(2)
Data Management Strategy
196(1)
Data Validation Strategy
197(1)
Data Dissemination Strategy
197(1)
Risk Management
198(3)
Risk Management Planning
200(1)
Risk Identification
200(1)
Risk Assessment
200(1)
Risk Quantification
200(1)
Risk Response Planning
201(1)
Risk Monitoring and Control
201(1)
Questions
201(1)
Reference List
202(1)
2.4 Disseminating the Enterprise Architecture
203(22)
Identifying the Audience for Architecture Dissemination
205(2)
Architecture Sponsors
205(1)
Architecture Team Members
206(1)
Architecture Stakeholders
206(1)
Executive Management
206(1)
Business Partners, Suppliers, Customers, and Agents
206(1)
Reusers
207(1)
Communities of Interest/Communities of Practice
207(1)
Fit-for-Purpose Displays
207(1)
Preparing for Dissemination
208(2)
Communicating the Contents of an Enterprise Architecture
210(2)
Dissemination to Another Receiving Enterprise Repository or Registry
210(1)
Dissemination Between Automated Computer Systems Applications
211(1)
Dissemination to People
212(1)
Architecture Presentation Techniques
212(6)
Choosing an Appropriate Presentation Technique
214(2)
Fit-for-Purpose View Display Formats
216(1)
Standardized View Display Formats
217(1)
Delivery of Dissemination
218(3)
Web Delivery
218(1)
Architecture Website/Web Portal
218(1)
Discovery Services
219(1)
Export/Import Files
220(1)
Repository Services
221(1)
Questions
221(2)
Reference List
223(2)
2.5 Maintaining the Enterprise Architecture
225(14)
Rate and Degree of Change of Architecture Elements
226(4)
Variation by Architecture Object Type
226(2)
Variation by Enterprise Nature
228(1)
Variations Introduced by Nonlinear Events
228(1)
A Change Response Model for Reference Models
228(2)
Who Is Responsible for Maintenance?
230(1)
Planning the Cost of Maintenance
230(1)
The Business Case for EA Maintenance
231(1)
Periodic Architecture Reassessment
231(5)
The Need for Periodic Reassessment
231(1)
Models Must Reflect Reality---Always
232(1)
Leverage Solution Architectures to Grow the EA
232(1)
Ensure That Business Direction and Processes Reflect Operations
233(1)
Ensure That the Current Architecture Reflects System Evolution
234(1)
Evaluate Legacy System Maintenance Requirements Against the Sequencing Plan
234(1)
Maintain the Sequencing Plan as an Integrated Program Plan
235(1)
Continue to Consider Proposals for EA Modifications
235(1)
TOGAF 9 ADM Phase H: Architecture Change Management
236(2)
Questions
238(1)
Reference List
238(1)
2.6 Governing the Enterprise Architecture
239(26)
Governance Framework
242(3)
Leadership
242(1)
Investment
243(1)
Organization
243(1)
Principles and Policies
244(1)
Processes
244(1)
Tools and Methods
245(1)
Measurements
245(1)
EA Maturity Assessment
245(1)
GAO EA Management Maturity Assessment Framework (EAMMF)
246(5)
The Five Stages of Maturity
247(2)
The Critical Attributes
249(2)
Other Maturity Assessment Models
251(5)
The Ross, Weill, and Robertson Model in Enterprise Architecture as Strategy
251(2)
OMB EA Assessment Framework
253(1)
Gartner EA Maturity Assessment Framework
254(2)
Security and Access and Privacy Issues
256(1)
EA Standards Compliance
257(1)
Architecture Governance in TOGAF (TOGAF 9)
258(4)
Organizational Structure for Architecture Governance
259(1)
Key Architecture Governance Processes
259(3)
Questions
262(1)
Reference List
262(3)
2.7 Using the EA
265(30)
Dimensions of Enterprise Transformation
266(3)
Zachman Framework Dimensions of Change
266(1)
DoD Dimensions of Enterprise Change
267(1)
Changes to Multiple Dimensions
268(1)
Using EA in Capital Planning and Investment Control (CPIC)
269(11)
EA in the Investment Management Process
270(6)
EA in Investment Management Maturity
276(4)
Using EA in Reorganization
280(2)
"Pure" Reorganization
280(1)
Organizational Transformation in Conjunction with Other Transformations
281(1)
Transition Planning
282(4)
Security
286(3)
Questions
289(1)
Reference List
290(5)
Part III Viewpoints and Models
3.1 Introduction to Viewpoints and Models
295(38)
Models
296(2)
Examples of Models
297(1)
Models Versus Pictures
298(2)
Viewpoints and Interests
300(3)
IEEE 1471 Definitions of Viewpoints and Views (IEEE 1471)
301(1)
TOGAF Definitions of Viewpoints and Views (TOGAF 9-2009)
302(1)
DoDAF 2 Definition of Viewpoints and Views
303(1)
Integrated Architecture Development
303(1)
Federated Architecture
304(1)
Frameworks and Viewpoints
305(7)
Zachman Framework
306(1)
DoD Architecture Framework
307(2)
Federal Enterprise Architecture Framework (FEAF)
309(1)
Federal Enterprise Architecture (FEA)
309(1)
The Open Group Architecture Framework (TOGAF)
310(1)
Office of Management and Budget
311(1)
Methodologies
312(3)
Integrated Definition Language (IDEF)
313(1)
Unified Modeling Language (UML)
313(1)
Universal Profile for DoDAF and MoDAF
313(1)
Activity-Based Methodology (ABM)
314(1)
Architecture Development Method (ADM)
314(1)
DoDAF Six Step Architecting Process
314(1)
Business Process Modeling Notation (BPMN)
315(1)
Model Representations
315(13)
DoDAF Viewpoints and Model Types
316(1)
Core Model Set
316(9)
Supporting Model Set
325(3)
Overarching Context of the Example Models
328(1)
Modeling Section Summary
329(1)
Questions
329(2)
Reference List
331(2)
3.2 All Viewpoint
333(46)
Architecture Overview and Summary
334(4)
AV-1 Architecture Overview and Summary
338(3)
Richard M. Nixon Airport Enterprise Architecture (RMN-EA) Architecture Overview and Summary (AV-1)
341(34)
Executive Summary
341(1)
Architecture Identification
342(1)
Architecture Purpose
342(6)
Stakeholders
348(1)
Geographical Considerations
349(1)
Information and Technology Infrastructure
350(2)
Management and Governance
352(3)
The Way Forward
355(5)
Questions Architecture Will Answer
360(1)
Proposed Analysis That Architecture Will Support
360(1)
Nature of Decision Support Required
361(1)
Nature of Solution to Be Provided
361(1)
Architecture Development
361(1)
Development Conventions, Methodologies, Standards, and Practices
362(1)
Architecture Key Drivers and Goals
362(1)
Architecture Scope
363(4)
Assumptions and Constraints
367(1)
Architecture-Specific Stakeholders
368(3)
Mapping of Models to EA Goals and Drivers
371(1)
Enterprise Architecture Development Approach
371(1)
Development Methods and Techniques
371(2)
Tools, Repository, Security, and Data Management
373(1)
Related Architecture Developments and Dependencies
374(1)
Architecture Release Schedule
374(1)
Findings and Recommendations
375(1)
Appendices
375(1)
AV-2 Integrated Data Dictionary
375(2)
Questions
377(1)
Reference List
378(1)
3.3 Strategic/Capability Viewpoint
379(28)
Government Performance Results Act (GPRA)
380(7)
Balanced Scorecard
382(2)
Joint Capabilities Integration and Development System (JCIDS)
384(2)
TOGAF 9 Support for Capability and Strategy
386(1)
Capability Viewpoint Integrated Models
387(2)
CV-1 Vision
389(2)
Example 1 RMN Enterprise CV4
389(2)
CV-2 Capability Taxonomy
391(3)
Example 1 RMN Terminal Operations CV-2
391(1)
Example 2 Passenger Processing CV-2
391(1)
Example 3 Passenger Identification CV-2
392(2)
CV-3 Capability Phasing
394(1)
CV-3 Example
394(1)
CV-4 Capability Dependencies
395(2)
CV-4 Example
396(1)
CV-5 Capability to Organizational Development Mapping
397(2)
Example
398(1)
CV-6 Capability to Operational Activities Mapping
399(2)
Example: Passenger Identification CV-6
400(1)
CV-7 Capability to Services Mapping
401(2)
Example: Passenger Identification CV-7
402(1)
Questions
403(2)
Reference List
405(2)
3.4 Project Viewpoint
407(14)
Project Viewpoint Integrated Models
410(1)
PV-1 Project Portfolio Relationships
411(3)
Example: Passenger Identification PV-1
412(2)
PV-2 Project Timelines
414(2)
Example: Passenger Identification PV-2
414(2)
PV-3 Project to Capability Mapping
416(2)
Example: Passenger Identification CV-3 Project to Capability Mapping
417(1)
Questions
418(1)
Reference List
418(3)
3.5 Operational Viewpoint
421(28)
Aspects of the Operational Viewpoint
422(3)
Concept of Operations
423(1)
Process or Activity Aspect
423(1)
Resource and Information Flows
423(1)
Organizational Relationships
424(1)
Operational Behaviors
424(1)
TOGAF 9 Support for the Operational Viewpoint
425(1)
Operational Viewpoint Integrated Models
426(2)
OV-1 High-Level Operational Concept Graphic
428(1)
Example: Passenger Identification OV-1
428(1)
OV-2 Operational Resource Flow Description
429(2)
Example: Passenger Identification OV-2
430(1)
OV-3 Operational Resource Flow Matrix
431(2)
Example: Passenger Identification OV-3
432(1)
OV-4 Organizational Relationships Chart
433(3)
Example 1 RMN Terminal Operations Division Organization Relationships Chart
434(1)
Example 2 Passenger Identification OV-4
434(2)
OV-5a and OV-5b Operational Activity Decomposition/Model
436(4)
Example 1 Functional Decomposition of Richard M. Nixon Airport's Enterprise Business Functions
436(2)
Example 2 Passenger Identification OV-5a
438(1)
Example 3 Passenger Identification OV-5b
439(1)
OV-6a Operational Rules Model
440(2)
Example: Passenger Identification Rules Model OV-6a (Fragment)
441(1)
OV-6b State Transition Description
442(2)
Example: Passenger Identification OV-6b
443(1)
OV-6c Event-Trace Description
444(2)
Example: Passenger Identification OV-6c
444(2)
Questions
446(2)
Reference List
448(1)
3.6 Systems Viewpoint
449(32)
Aspects of the Systems Viewpoint
451(2)
System Resource Flows/Information Exchanges
451(1)
Systems Functionality
451(1)
Systems Connectivity
452(1)
Systems Traceability to Operational Usefulness
452(1)
Systems Performance Specification
452(1)
Systems Evolution
453(1)
Systems Operating Platforms
453(1)
Systems Behavioral Models
453(1)
Systems Viewpoint Integrated Models
453(2)
SV-1 Systems Interface Description
455(2)
Example: Passenger Identification SV-1
456(1)
SV-2 Systems Resource Flow Description
457(1)
Example: Passenger Identification SV-2
457(1)
SV-3 System-to-System Matrix
458(2)
Example: Passenger Identification SV-3
459(1)
SV-4 Systems Functionality Description
460(3)
Example: Passenger Identification SV-4
461(2)
SV-5a and b Operational Activity to Systems-to-System Functions Traceability Matrix
463(3)
Example: Passenger Identification SV-5a
463(1)
Example: Passenger Identification SV-5b
464(2)
SV-6 Systems Resource Flow Matrix
466(1)
Example: Passenger Identification SV-6
466(1)
SV-7 Systems Measures Matrix
467(4)
Example: Passenger Identification SV-7
468(3)
SV-8 Systems Evolution Description
471(2)
Example: Passenger Identification SV-8
471(2)
SV-9 Systems Technology and Skills Forecast
473(2)
Example: Passenger Identification SV-9
473(2)
SV-10a Systems Rules Model
475(1)
SV- 10b Systems State Transition Model
476(1)
SV-10c Systems Event-Trace Description
477(1)
Questions
478(1)
Reference List
479(2)
3.7 Services Viewpoint
481(30)
The Service-Oriented Framework
483(4)
Service Resource Flows and Information Exchanges
484(1)
Services Functionality
485(1)
Services Connectivity
485(1)
Services Traceability to Operational Usefulness
486(1)
Services Performance Specification
486(1)
Services Evolution
486(1)
Services Operating Platforms
486(1)
Services Behavioral Models
487(1)
Services Viewpoint Integrated Models
487(2)
SvcV-1 Services Context Description
489(2)
Example: Passenger Identification SvcV-1
489(2)
SvcV-2 Services Resource Flow Description
491(1)
Example: Passenger Identification SvcV-2
491(1)
SvcV-3 a, b Systems-Service and Services-Service Matrices
492(3)
Example: Passenger Identification SvcV-3
493(2)
SvcV-4 Services Functionality Description
495(2)
Example: Passenger Identification SvcV-4 (Functional Decomposition)
495(2)
SvcV-5 Operational Activity to Services Traceability Matrix
497(3)
Example: Passenger Identification SvcV-5
497(3)
SvcV-6 Services Resource Flow Matrix
500(2)
Example: Passenger Identification SvcV-6
500(2)
SvcV-7 Services Measures Matrix
502(1)
Example: Passenger Identification SvcV-7
502(1)
SvcV-8 Services Evolution Description
503(1)
Example: Passenger Identification SvcV-8
503(1)
SvcV-9 Services Technology and Skills Forecast
503(2)
SvcV-10a Services Rules Model
505(1)
Example: Passenger Identification SvcV-10a
505(1)
SvcV-10b Services State Transition Description
506(1)
Example: Passenger Identification SvcV-10b
507(1)
SvcV-10c Services Event-Trace Description
507(1)
Questions
508(1)
Reference List
509(2)
3.8 Data and Information Viewpoint
511(20)
What Is the Difference Between Data and Information?
512(1)
Ontology
513(2)
Taxonomy
515(1)
Controlled Vocabularies
515(1)
FEA Data Reference Model
516(1)
Data Context
516(1)
Data Description
517(1)
Data Sharing
517(1)
DIV-1 Conceptual Data Model (Semantic Data Model)
517(1)
DIV-2 Logical Data Model (Key-Based/Fully Attributed Logical Data Model)
518(1)
DIV-3 Physical Schema
519(1)
Relationships Between the Data and Information Viewpoint Integrated Models
519(2)
DIV-1 Conceptual Data Model
521(2)
Example: Passenger Identification DIV-1
522(1)
DIV-2 Logical Data Model
523(1)
Example: Passenger Identification DIV-2
523(1)
DIV-3 Physical Data Model
524(4)
Example: Passenger Identification Model DIV-3
525(3)
Questions
528(1)
Reference List
529(2)
3.9 Technology and Standards Viewpoint
531(12)
Standards Viewpoint Integrated Models
533(1)
StdV-1 Standards Profile
534(4)
Example: Passenger Identification StdV-1
535(3)
StdV-2 Standards Forecast
538(1)
Example: Passenger Identification StdV-2
538(1)
Questions
539(1)
Reference List
540(3)
Part IV EA Examples
4.1 EA in Government
543(26)
Clinger-Cohen Act of 1996
544(1)
The Government Performance and Results Act (GRPA)
545(1)
Federal Enterprise Architecture Framework (FEAF)
545(3)
The Influence of the Zachman Framework
545(1)
The Influence of NIST
546(2)
Treasury Enterprise Architecture Framework (TEAF)
548(2)
The Federal Enterprise Architecting Process
550(15)
The OMB FEA Reference Models
551(7)
The Federal Segment Architecture Methodology (FSAM)
558(4)
Rapid Segment Architecture Methodology (RSAM)
562(2)
The Future of EA in Government
564(1)
EA Assessment Tools
565(2)
EAMMF
565(1)
EAAF
566(1)
Questions
567(1)
Reference List
568(1)
4.2 Enterprise Architecting in Defense
569(34)
The DoD Enterprise
570(10)
Enterprise Challenges
570(3)
Enterprise Initiatives
573(4)
DoD Architecting Levels
577(2)
DoD Architecture Framework
579(1)
DoD Business Processes Supported by the DoDAF
580(9)
JCIDS and Capability-Based Assessment (JCIDS/CBA)
581(1)
Planning, Programming, Budgeting, and Execution (PPBE)
582(3)
Defense Acquisition System (DAS)
585(1)
Systems Engineering Process (SE)
586(1)
Portfolio Management (PfM)
587(2)
DoD Enterprise Architecture Examples
589(11)
DoDEA
589(2)
Department of the Air Force EA
591(1)
Navy EA
592(2)
Army EA
594(3)
DoD Information Enterprise Architecture
597(1)
DoD Business Enterprise Architecture
598(2)
Questions
600(1)
Reference List
601(2)
4.3 Enterprise Architecture and the Commercial Sector
603(36)
TOGAF 9.0 in Relation to the Views and Models of This Guide
604(12)
The Architecture Development Methodology
616(16)
Phase A Architecture Vision
620(1)
Phase B The Business Architecture
621(1)
Phase C Information Systems Architecture
622(3)
Phase D Technology Architecture
625(2)
Phase E Opportunities and Solutions
627(1)
Phase F Migration Planning
628(1)
Phase G Implementation Governance
629(1)
Phase H Architecture Change Management
630(1)
Requirements Management
630(2)
TOGAF Iteration
632(1)
Integrated Architecture
633(1)
TOGAF Artifacts
633(1)
Questions
634(1)
Reference List
635(4)
Part V Resources
5.1 EA Tools and Repositories
639(40)
Select Your Framework
640(1)
Select Your Modeling Techniques and Methodologies
641(5)
Select Your Modeling Standards
646(1)
Integrated Definition Language 0 (Activity Modeling)
646(1)
Unified Modeling Language (UML)
646(1)
Business Process Modeling Notation (BPMN)
647(1)
Business Process Execution Language (BPEL)
647(1)
Select Your Architecture Data Exchange Standards
647(1)
Define or Select Your Modeling Lifecycle Processes
648(1)
How Do Tools Assist in EA Development?
648(2)
Methodology-Independent Tools
650(1)
Methodology-Specific Tools
651(1)
Process Support Tools
651(1)
Integrated Model Development
651(1)
Support for Fit-for-Purpose Views
652(1)
Configuration Management and Model Releases
653(1)
Tool-Based Document Generation
654(1)
Tool-Generated Model Dissemination
654(1)
Tool-Selection Criteria
655(6)
Technical Criteria
655(2)
Business Criteria
657(1)
Integration Criteria
658(1)
Functionality Criteria
658(3)
What Is an EA Repository?
661(13)
Repository Metamodel
662(1)
Benefits of the Repository Metamodel
662(3)
How Does a Repository Integrate Models?
665(1)
DoDAF Core Architecture Data Model (CADM)
666(1)
DoDAF DM2 Repository Metamodel
667(3)
TOGAF 9 Repository Metamodel
670(4)
How Do EA Tools Work with a Repository?
674(2)
Interface Standards
675(1)
Metamodel Unification
675(1)
Framework-Provided Semantics
676(1)
Repository Selection Criteria
676(1)
Questions
677(1)
Reference List
678(1)
5.2 A Case Study: Richard ML Nixon International Airport, CA
679(18)
Selecting the Scope of the Enterprise
682(1)
Strategic Thrust
683(1)
Planning for the Future
683(1)
Passenger Processing Capabilities
684(2)
Cargo Processing Capabilities
686(1)
Revenue Generation Capabilities
687(1)
Stakeholders
688(1)
Geographical Considerations
689(1)
Information and Technology Infrastructure
690(2)
Management and Governance
692(1)
FEAC's 50,000 View of the Role of the Enterprise Architecture
693(4)
Glossary 697(52)
Index 749
Prakash Rao, CEA, is Vice President and Chief Architect with Metadata Management Corporation Ltd., and a faculty member with the FEAC Institute where he teaches enterprise architecture and the DoD Architecture Framework. He is co-chair of the Association of Open Group Enterprise Architects, Washington Metropolitan Area Chapter.



Beryl Bellman, Ph.D, is co-founder and Academic Director of the FEAC Institute and is a tenured Professor of Communication Studies at California State University at Los Angeles. He has consulted in enterprise architecture in the public sector and for the U.S. Departments of Defense, Agriculture, Forest Service, Energy, and Justice/INS, and the Executive Office of the President.



Ann Reedy is a Ph.D. in Computer Science with extensive experience in academia and in the contractor community. After working with analyst support systems and software development environments, she worked on the C4ISR Architecture Framework, the precursor to the DoD Architecture Framework (DoDAF). She has supported the adaptation of the DoD Architecture Framework for various federal organizations and agencies as well as supporting startup enterprise architecture developments based on the DoD Architecture Framework. She currently teaches for the Federated Enterprise Architecture Certification (FEAC) Institute and continues to work part-time for the MITRE Corporation.