Atjaunināt sīkdatņu piekrišanu

E-grāmata: Certified Enterprise Architect All-in-One Exam Guide

4.43/5 (9 ratings by Goodreads)
, ,
  • Formāts: 640 pages
  • Izdošanas datums: 12-Oct-2018
  • Izdevniecība: McGraw-Hill Education
  • Valoda: eng
  • ISBN-13: 9781260121490
Citas grāmatas par šo tēmu:
  • Formāts - PDF+DRM
  • Cena: 76,64 €*
  • * ši ir gala cena, t.i., netiek piemērotas nekādas papildus atlaides
  • Ielikt grozā
  • Pievienot vēlmju sarakstam
  • Šī e-grāmata paredzēta tikai personīgai lietošanai. E-grāmatas nav iespējams atgriezt un nauda par iegādātajām e-grāmatām netiek atmaksāta.
Certified Enterprise Architect All-in-One Exam GuidePalielināt
  • Formāts: 640 pages
  • Izdošanas datums: 12-Oct-2018
  • Izdevniecība: McGraw-Hill Education
  • Valoda: eng
  • ISBN-13: 9781260121490
Citas grāmatas par šo tēmu:

DRM restrictions

  • Kopēšana (kopēt/ievietot):

    nav atļauts

  • Drukāšana:

    nav atļauts

  • Lietošana:

    Digitālo tiesību pārvaldība (Digital Rights Management (DRM))
    Izdevējs ir piegādājis šo grāmatu šifrētā veidā, kas nozīmē, ka jums ir jāinstalē bezmaksas programmatūra, lai to atbloķētu un lasītu. Lai lasītu šo e-grāmatu, jums ir jāizveido Adobe ID. Vairāk informācijas šeit. E-grāmatu var lasīt un lejupielādēt līdz 6 ierīcēm (vienam lietotājam ar vienu un to pašu Adobe ID).

    Nepieciešamā programmatūra
    Lai lasītu šo e-grāmatu mobilajā ierīcē (tālrunī vai planšetdatorā), jums būs jāinstalē šī bezmaksas lietotne: PocketBook Reader (iOS / Android)

    Lai lejupielādētu un lasītu šo e-grāmatu datorā vai Mac datorā, jums ir nepieciešamid Adobe Digital Editions (šī ir bezmaksas lietotne, kas īpaši izstrādāta e-grāmatām. Tā nav tas pats, kas Adobe Reader, kas, iespējams, jau ir jūsu datorā.)

    Jūs nevarat lasīt šo e-grāmatu, izmantojot Amazon Kindle.

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.


This effective study guide offers comprehensive coverage of topics comprising the enterprise architecture body of knowledge. 

This unique resource provides detailed coverage and lays out actionable methodologies and best practices to create and maintain successful EA models, artifacts and building blocks. It helps prepare readers to take any of the various EA certification exams and academic courses in enterprise architecture.

This highly effective self-study guide offers comprehensive coverage of all topics in the enterprise architecture body of knowledge. Written by a team of experienced academics, practitioners, and professionals, the book takes a holistic look at the practice of enterprise architecture. You will get actionable methodologies and best practices and learn how to develop, deploy, and maintain successful enterprise architecture models, artifacts, and building blocks. Designed to help you prepare for certification, the Certified Enterprise Architect All-in-One Exam Guide also serves as an essential on-the-job reference.

Coverage includes:
•Enterprise architecture foundation concepts
•Planning the enterprise architecture
•Enterprise architecture development, governance, and maintenance
•Defense frameworks
•Viewpoints and views
•The Zachman Framework
•The Open Group Architecture Framework (TOGAF)
•The Common Approach to Federal Enterprise Architecture
•FEAF2
•Comparison of frameworks
•Case Study integrated throughout the text
•And much more

Foreword xxv
Preface xxxi
Acknowledgments xxxv
Introduction xxxvii
Part I Foundation Concepts
Chapter 1 Enterprise Architecture Concepts
3(22)
High-Level Concepts
3(7)
Enterprise
3(2)
Architecture
5(2)
Enterprise Architecture
7(3)
Architecture Frameworks
10(10)
Levels of Enterprise
11(3)
Viewpoints
14(2)
Views
16(2)
Repositories and Metamodels
18(1)
Methodologies and Process
19(1)
Summary
20(1)
Questions
20(1)
References
21(4)
Chapter 2 The Importance of Culture, Climate, and Tribes in the Context of Enterprise Architecture
25(30)
Introduction to Culture
25(2)
Origins of Culture Study
26(1)
Organizational Climate and Organizational Culture
26(1)
Corporate Tribes
26(1)
Understanding Culture: Language Perspective
27(7)
Classifying Cultures
29(5)
How Culture Affects the Enterprise Architecture
34(2)
Social Networks
36(3)
Schein's Three Levels of Culture
39(5)
Clinical Cultural Analysis Example: DEC
40(2)
Clinical Cultural Analysis Example: Novartis
42(2)
Representing Culture as Business Rules
44(3)
Culture as a Emergent Phenomenon
47(2)
Culture from Multiple Perspectives
49(1)
Summary
49(1)
Questions
50(1)
References
50(5)
Part II Architecture Development and Use
Chapter 3 Introduction to the Case Study
55(16)
RMN Airport Today
55(1)
Background
55(1)
Opportunities and Aspirations
56(1)
Challenges
57(9)
Regulations
58(1)
Stakeholders
59(1)
Larger Management Staff
60(1)
More Functions, Facilities, and Capabilities
60(5)
Continuous Interactions with Communities of Interest
65(1)
Cultural Issues
66(1)
Plans
66(2)
Summary
68(1)
References
68(3)
Chapter 4 Basic Concepts for Defense Frameworks
71(30)
Levels of Enterprise
72(4)
Enterprise Level
73(2)
Segment Level
75(1)
Solution Level
75(1)
DoDAF Viewpoints
76(3)
All Viewpoint
77(1)
Capability Viewpoint
77(1)
Data and Information Viewpoint
77(1)
Operational Viewpoint
77(1)
Project Viewpoint
78(1)
Services Viewpoint
78(1)
Standards Viewpoint
78(1)
Systems Viewpoint
78(1)
Viewpoint Relationships
78(1)
DoDAF Views
79(6)
Integration of Views
84(1)
Repository and Metamodel
85(10)
Elements of the Business Domain
85(4)
Elements of the IT and Infrastructure Domain
89(5)
Ontology
94(1)
Process: The Six-Step Process
95(4)
Step 1: Determine the Intended Use of the Architecture
96(1)
Step 2: Determine the Scope of the Architecture
96(1)
Step 3: Determine the Data Needed to Support Architecture Development
97(1)
Step 4: Collect, Organize, Correlate, and Store Architecture Data
97(1)
Step 5: Conduct Analyses in Support of Architecture Objectives
97(1)
Step 6: Document Results in Accordance with Decision-Maker Needs
98(1)
Summary
99(1)
Questions
99(1)
References
100(1)
Chapter 5 Planning the Enterprise Architecture
101(34)
Scoping the Architecture Work
102(28)
Purpose
103(6)
Scope
109(3)
Identifying Needed Data Types
112(2)
Determine What Views to Use: How to Organize and Correlate Data
114(8)
Planning Examples
122(8)
Success Factors in Scoping the Architecture Work
130(1)
Summary
130(1)
Questions
131(2)
References
133(2)
Chapter 6 Developing the Architecture
135(26)
Overview of the Project Plan
135(9)
The Project Plan
136(8)
Summary of Project Planning
144(1)
Details of Project Planning
144(14)
Statement of Work
145(3)
Project Implementation Details
148(10)
Success Factors for Planning
158(1)
Summary
159(1)
Questions
159(1)
References
160(1)
Chapter 7 Disseminating the Enterprise Architecture
161(18)
Preparing for Dissemination
161(1)
Marketing and Communications Plan
162(2)
Identifying the Audience for Architecture Dissemination
164(2)
Architecture Sponsors
164(1)
Architecture Team Members
164(1)
Architecture Stakeholders
164(1)
Executive Management
164(1)
Business Partners, Suppliers, Customers, Agents
165(1)
Reusers
165(1)
Communities of Interest/Communities of Practice
165(1)
Architecture Presentation Techniques
166(5)
Choosing an Appropriate Presentation Technique
166(3)
Fit-for-Purpose View Display Formats
169(1)
Standardized View Display Formats
170(1)
Audience Presentation Tips
170(1)
Delivery of Dissemination
171(4)
Web Delivery
172(1)
Architecture Web Site/Web Portal
172(1)
Dissemination to Computerized Systems
173(2)
Summary
175(1)
Questions
175(2)
References
177(2)
Chapter 8 Maintaining the Enterprise Architecture
179(14)
Rate and Degree of Change of Architecture Elements
179(4)
Variation by Architecture Object Type
179(2)
Variation by Enterprise Nature
181(1)
Variations Introduced by Nonlinear Events
181(1)
A Change Response Model for Reference Models
182(1)
Who Is Responsible for Maintenance?
183(1)
Planning the Cost of Maintenance
184(1)
The Business Case for EA Maintenance
184(1)
Periodic Architecture Reassessment
184(5)
The Need for Periodic Reassessment
184(1)
Models Must Reflect Reality-Always
185(1)
Leverage Solution Architectures to Grow the EA
185(1)
Ensure that Business Direction and Processes Reflect Operations
186(1)
Ensure that Current Architecture Reflects System Evolution
187(1)
Evaluate Legacy System Maintenance Requirements Against the Sequencing Plan
187(1)
Maintain the Sequencing Plan as an Integrated Program Plan
187(1)
Continue to Consider Proposals for EA Modifications
188(1)
TOGAF 9.2 ADM Phase H: Architecture Change Management
189(1)
Summary
190(1)
Questions
191(1)
References
191(2)
Chapter 9 Governing the Enterprise Architecture
193(14)
Governance Framework
194(4)
Leadership
195(1)
Investment
195(1)
Organization
196(1)
Principles and Policies
196(1)
Processes
197(1)
Tools and Methods
197(1)
Measurements
198(1)
Security, Access, and Privacy Issues
198(1)
EA Standards Compliance
199(1)
FA Maturity Assessment
200(1)
Architecture Governance in TOGAF (TOGAF 9.2)
201(3)
Organizational Structure for Architecture Governance
202(1)
Key Architecture Governance Processes
203(1)
Summary
204(1)
Questions
204(1)
References
205(2)
Chapter 10 Using the Enterprise Architecture
207(20)
Some Classes of Enterprise Problems
208(6)
Aligning Technology Infrastructure with Operating Models
208(1)
Aligning Business Model with Data and Information
209(1)
Modernizing Technology
209(1)
Modernizing Process
210(1)
Capital Planning and Investment Control (CPIC)
210(1)
Establishing Credible Business Case Analysis for Capital Investments
211(1)
Changing Enterprise Topology
211(1)
"Dissolving" Innovation into the Enterprise
212(1)
Planning for Enterprise Security
212(1)
Reorganizing or Reallocating Responsibilities
213(1)
Managing Information Asset Inventory
213(1)
Summary of Problem Classes
213(1)
DoDAF Viewpoints and Uses
214(7)
Use of the Capability Viewpoint
214(1)
Use of the Project Viewpoint
215(1)
Use of the Operational Viewpoint
216(1)
Use of the Services Viewpoint
217(1)
Use of the Systems Viewpoint
218(1)
Use of the Data and Information Viewpoint
219(1)
Use of the Standards Viewpoint
220(1)
Use of the All Viewpoint
221(1)
Summary
221(1)
Questions
222(1)
References
222(5)
Part III Viewpoints and Views
Chapter 11 Introduction to Viewpoints and Views
227(8)
Views, Models, Pictures, and Artifacts
227(1)
Tailoring of Views
228(1)
Review of DoDAF Viewpoints and Views
228(1)
Organization of the Viewpoint
Chapters
229(1)
View Information at a Glance
229(1)
View Integration
230(1)
Review of Ontology Entities
230(3)
Case Study Example Context
233(1)
Summary
233(1)
References
233(2)
Chapter 12 All Viewpoint
235(14)
Introduction to the Views in the All Viewpoint
235(4)
AV-1: Overview and Summary Information
236(1)
AV-2: Integrated Dictionary
237(1)
Alternative Views
238(1)
AV-1: Overview and Summary Information
239(6)
Example: Richard M Nixon Airport Enterprise Architecture (RMN-EA) Overview and Summary Information
241(4)
AV-2: Integrated Dictionary
245(1)
Example: Integrated Dictionary Sample Entries
245(1)
Summary
246(1)
Questions
247(1)
References
248(1)
Chapter 13 Capability Viewpoint
249(20)
Federal Government Planning Requirements
249(1)
DoD Planning Requirements
250(1)
Views in the Capability Viewpoint
251(1)
Capability Viewpoint Element Overview
252(1)
CV-1: Vision
253(2)
Example: RMN Airport Enterprise CV-1
254(1)
CV-2: Capability Taxonomy
255(2)
Example: Handle Domestic Commuter Flights CV-2
256(1)
CV-3: Capability Phasing
257(1)
Example: RMN Airport Transformation Phase 1 CV-3
257(1)
CV-4: Capability Dependencies
258(2)
Example: RMN Airport Capability Dependencies CV-4
259(1)
CV-5: Capability to Organizational Development Mapping
260(1)
Example: Organizational Use of Capabilities During RMN Airport Phase 1 Transformation CV-5
260(1)
CV-6: Capability to Operational Activities Mapping
261(2)
Example: Domestic Passenger Identification CV-6
262(1)
CV-7: Capability to Services Mapping
263(1)
Example: Domestic Passenger Identification CV-7
263(1)
Alternatives
264(2)
TOGAF 9.2 Support for Capability and Strategy
264(1)
FEAF2 Support for Strategic/Capability Viewpoint
265(1)
Balanced Score Card
266(1)
Summary
266(1)
Questions
267(1)
References
268(1)
Chapter 14 Project Viewpoint
269(10)
Views in the Project Viewpoint
270(1)
PV-1: Project Portfolio Relationships
271(3)
Example: RMN Passenger Management PV-1
272(2)
PV-2: Project Timelines
274(1)
Example: Passenger Management PV-2
275(1)
PV-3: Project to Capability Mapping
275(2)
Example: Domestic Passenger Identification PV-3
276(1)
Summary
277(1)
Questions
277(1)
References
277(2)
Chapter 15 Operational Viewpoint
279(32)
Architecting Concerns for the Operational Viewpoint
280(2)
Operational Viewpoint Integrated Models
282(1)
Operational Focus
283(2)
Operational Activity
283(1)
Operational Event
284(1)
Operational Location
284(1)
Performer
284(1)
Views in the Operational Viewpoint
285(19)
OV-1: High-Level Operational Concept Graphic
287(1)
OV-2: Operational Resource Flow Description
288(2)
OV-3: Operational Resource Flow Matrix
290(2)
OV-4: Organizational Relationships Chart
292(2)
OV-5a: Operational Activity Decomposition Tree
294(1)
OV-5b: Operational Activity Model
294(4)
OV-6a: Operational Rules Model
298(2)
OV-6b: State Transition Description
300(2)
OV-6c: Event-Trace Description
302(2)
TOGAF Support for the Operational Viewpoint
304(2)
FEAF2 Support for Operational Viewpoint
306(1)
Summary
307(1)
Questions
307(1)
References
308(3)
Chapter 16 Systems Viewpoint
311(34)
Purposes of the Systems Viewpoint Views
312(3)
System Resource Flows/Information Exchanges
312(1)
Systems Functionality
312(1)
Systems Need for Connectivity
313(1)
Systems Traceability to Operational Usefulness
313(1)
Systems Performance Specification
314(1)
Systems Evolution
314(1)
Systems Operating Platforms
314(1)
Systems Behavioral Models
315(1)
Systems Viewpoint Integrated Views
315(2)
SV-1: Systems Interface Description
317(1)
Example: Passenger Identification SV-1
317(1)
SV-2: Systems Resource Flow Description
318(2)
Example: Passenger Identification SV-2
319(1)
SV-3: Systems-Systems Matrix
320(3)
Example: Passenger Identification SV-3
321(2)
SV-4: Systems Functionality Description
323(1)
Example: Passenger Identification SV-4
323(1)
SV-5a: Operational Activity to Systems Function Traceability Matrix
324(1)
SV-5b: Operational Activity to Systems Traceability Matrix
325(3)
Example: Passenger Identification SV-5a
326(1)
Example: Passenger Identification SV-5b
327(1)
SV-6: Systems Resource Flow Matrix
328(1)
Example: Passenger Identification SV-6
328(1)
SV-7: Systems Measures Matrix
329(2)
Example: Passenger Identification SV-7
330(1)
SV-8: Systems Evolution Description
331(2)
Example: Passenger Identification SV-8
332(1)
SV-9: Systems Technology and Skills Forecast
333(2)
Example: Passenger Identification SV-9
334(1)
SV-10a: Systems Rules Model
335(1)
SV-10b: Systems State Transition Model
336(1)
SV-10c: Systems Event-Trace Description
337(1)
TOGAF Information Systems Architecture
338(3)
FEAF2 Applications Subarchitecture Domain
341(1)
Summary
342(1)
Questions
343(1)
References
344(1)
Chapter 17 Services Viewpoint
345(36)
Conventional Information Technology Services
345(2)
Business Services
345(1)
Software as a Service (SaaS)
346(1)
Platform as a Service (PaaS)
347(1)
Infrastructure as a Service (IaaS)
347(1)
Architecting a DoDAF Solution Through Service Components
347(3)
Services Viewpoint Views
350(20)
SvcV-1: Services Context Description
352(1)
SvcV-2: Services Resource Flow Description
353(2)
SvcV-3a: Systems-Services Matrix
SvcV-3b: Services-Services Matrix
355(2)
SvcV-4: Services Functionality Description
357(1)
SvcV-5: Operational Activity to Services Traceability Matrix
358(1)
SvcV-6: Services Resource Flow Matrix
359(3)
SvcV-7: Services Measures Matrix
362(2)
SvcV-8: Services Evolution Description
364(1)
SvcV-9: Services Technology and Skills Forecast
365(1)
SvcV-10a: Services Rules Model
366(1)
SvcV-10b: Services State Transition Description
367(2)
SvcV-10c: Services Event-Trace Description
369(1)
DoD View of Services (DoD Information Enterprise Architecture)
370(1)
TOGAF View of Services
370(3)
TOGAF Service Artifacts
370(2)
TOGAF Technical Reference Model
372(1)
FEAF2 and Federal View of Services
373(4)
Service-Oriented Framework
373(2)
FEAF2 Service Artifacts
375(1)
FEAF2 Business Reference Model
376(1)
Summary
377(1)
Questions
377(1)
References
378(3)
Chapter 18 Data and Information Viewpoint
381(26)
Representing Data
381(7)
Data at Rest and Data in Motion
382(1)
Historical Time Varying Data
383(1)
Structured Data vs. Unstructured Data
383(1)
Data vs. Information
383(5)
Data and Information Viewpoint Views
388(3)
DIV-1: Conceptual Data Model
388(1)
DIV-2: Logical Data Model
389(1)
DIV-3: Physical Data Model
389(1)
Relationships Among the Data and Information Viewpoint Integrated Views
390(1)
DIV-1: Conceptual Data Model
391(2)
Example: Passenger Identification DIV-1
392(1)
DIV-2: Logical Data Model
393(2)
Example: Passenger Identification DIV-2
394(1)
DIV-3: Physical Data Model
395(2)
Example: Passenger Identification DIV-3
396(1)
FEAF2 Data Subarchitecture Domain Artifacts
397(1)
FEAF2 Data Reference Model (DRM)
398(3)
Data Context
399(1)
Data Description
399(1)
Data Sharing
400(1)
TOGAF Data Architecture Artifacts
401(1)
Summary
402(1)
Questions
403(1)
References
404(3)
Chapter 19 Standards Viewpoint
407(14)
Views of the Standards Viewpoint
409(2)
Standards Profile View
409(1)
Standards Forecast View
410(1)
Standards Viewpoint Integrated Views
410(1)
StdV-1: Standards Profile
411(2)
Example: Passenger Identification StdV-1
412(1)
StdV-2: Standards Forecast
413(1)
Example: Passenger Identification StdV-2
414(1)
Alternatives
414(3)
TOGAF Technology Architecture
414(1)
FEAF2 Approach to Standards
415(2)
Summary
417(1)
Questions
418(1)
References
419(2)
Chapter 20 Extension Viewpoints
421(12)
The Need for Extension Viewpoints
421(2)
TOGAF Extension Example
422(1)
DoDAF Extensions
422(1)
Extending a Standard Framework
423(1)
Ontology Extensions
424(5)
IDEAS Foundation Ontology
425(1)
DoDAF Metamodel (DM2)
426(1)
UML Foundation Ontology
427(2)
Summary
429(1)
Questions
429(1)
References
430(3)
Part IV Comparative Frameworks
Chapter 21 The Zachman Framework
433(12)
The Zachman Framework as an Ontology
433(4)
Reification
436(1)
The Perspectives
437(1)
The Interrogative Columns
438(1)
Classification Schema
439(1)
Primitives and Composites
439(3)
Rules for the Use of the Zachman Framework Ontology
442(1)
Summary
443(1)
Questions
443(1)
References
444(1)
Chapter 22 TOGAF: The Open Group Architecture Framework
445(18)
TOGAF Documentation
446(2)
The ADM
448(4)
The Preliminary Phase
448(1)
Phase A: Architecture Vision
448(1)
Phase B: Business Architecture
448(1)
Phase C: Information Systems Architecture, and Phase D: Technology Architecture
449(1)
Phase E: Opportunities and Solutions
450(1)
Phase F: Migration Planning
450(1)
Phase G: Implementation Governance
450(1)
Phase H: Architecture Change Management
451(1)
Requirements Management
451(1)
Architecture Content Framework
452(1)
The Enterprise Continuum
453(2)
TOGAF Reference Models
455(2)
ADM Guidelines and Techniques
457(3)
Architecture Capability Framework
460(1)
Summary
461(1)
Questions
461(1)
References
462(1)
Chapter 23 Common Approach and FEAF2
463(28)
Background
464(1)
Levels of Scope (Levels of Enterprise)
465(3)
Subarchitecture Domains (Viewpoints)
468(4)
Subarchitecture Domain Artifacts (Views)
468(4)
Reference Models
472(9)
Performance Reference Model (PRM)
473(5)
Enterprise Roadmap
478(3)
Repositories and Metamodels
481(1)
Methodology/Process
481(2)
Overview of the Common Approach
483(4)
Primary Outcomes
483(1)
Basic Elements of FEA
484(2)
The FEAF2 Framework
486(1)
Summary
487(1)
Questions
487(1)
References
488(3)
Chapter 24 Summary Comparison of Frameworks
491(18)
DoD Architecture Framework
491(2)
Federal Enterprise Architecture Framework
493(1)
The Open Group Architecture Framework
494(1)
Zachman Framework
495(1)
Normalizing Comparison Criteria
496(10)
Summary
506(1)
Questions
506(1)
References
506(3)
Glossary 509(62)
Index 571
Biežāk uzdotie jautājumi par e-grāmatām Biežāk uzdotie jautājumi par e-grāmatām
Permanent link: https://www.kriso.lv/db/97812601214902e.html
Keywords: