Preface |
|
xiii | |
Foreword |
|
xv | |
|
Chapter 1 TOGAF®: General Presentation |
|
|
1 | (24) |
|
|
1 | (4) |
|
1.1.1 Positioning and history |
|
|
1 | (1) |
|
1.1.2 "A" for Enterprise Architecture |
|
|
2 | (1) |
|
|
3 | (1) |
|
|
4 | (1) |
|
|
5 | (12) |
|
1.2.1 ADM and the TOGAF crop circle diagram |
|
|
5 | (1) |
|
1.2.2 Architecture transformation |
|
|
6 | (5) |
|
1.2.3 Architecture in TOGAF |
|
|
11 | (2) |
|
1.2.4 Goals, constraints, and requirements |
|
|
13 | (1) |
|
1.2.5 Stakeholders and the human factor |
|
|
13 | (3) |
|
1.2.6 Architecture strategy, governance, and principles |
|
|
16 | (1) |
|
|
17 | (1) |
|
|
18 | (6) |
|
1.4.1 Adapting the framework |
|
|
18 | (1) |
|
1.4.2 TOGAF: One framework among many? |
|
|
19 | (5) |
|
|
24 | (1) |
|
|
25 | (16) |
|
|
26 | (3) |
|
2.1.1 The breakdown into phases |
|
|
26 | (2) |
|
|
28 | (1) |
|
2.2 The phases of the ADM |
|
|
29 | (8) |
|
2.2.1 The preliminary phase |
|
|
29 | (1) |
|
|
29 | (1) |
|
2.2.3 Phases B, C, and D (Elaboration of Business, Information System, and Technology Architectures) |
|
|
30 | (2) |
|
2.2.4 Phases E and F (opportunities and solutions, migration planning) |
|
|
32 | (1) |
|
2.2.5 Phases G and H (implementation governance, architecture change management) |
|
|
33 | (1) |
|
2.2.6 Requirements management |
|
|
33 | (4) |
|
|
37 | (1) |
|
|
37 | (1) |
|
2.3.2 Priority to target architecture or baseline architecture |
|
|
37 | (1) |
|
2.4 ADM techniques and guidelines |
|
|
38 | (2) |
|
2.4.1 The different techniques |
|
|
39 | (1) |
|
2.4.2 Techniques in ADM phases |
|
|
39 | (1) |
|
|
40 | (1) |
|
Chapter 3 The Components of TOGAF Architecture |
|
|
41 | (16) |
|
3.1 Architecture components |
|
|
42 | (1) |
|
3.1.1 Artifacts, deliverables, and building blocks |
|
|
42 | (1) |
|
3.1.2 Using other content frameworks |
|
|
43 | (1) |
|
|
43 | (5) |
|
3.2.1 The "TOGAF core metamodel" |
|
|
43 | (2) |
|
3.2.2 Metamodel extensions |
|
|
45 | (2) |
|
3.2.3 Conceptual, logical, and physical |
|
|
47 | (1) |
|
3.2.4 Relationship to ADM phases |
|
|
47 | (1) |
|
|
48 | (3) |
|
3.3.1 Viewpoints and views |
|
|
49 | (1) |
|
3.3.2 Catalogs, matrices, and diagrams |
|
|
49 | (1) |
|
3.3.3 The catalog of TOGAF views |
|
|
50 | (1) |
|
3.3.4 Tools and languages |
|
|
50 | (1) |
|
|
51 | (1) |
|
3.4.1 The game of building |
|
|
51 | (1) |
|
3.4.2 Architecture building blocks and solution building blocks |
|
|
51 | (1) |
|
|
52 | (2) |
|
3.5.1 Description and use |
|
|
52 | (1) |
|
3.5.2 Deliverables and ADM phases |
|
|
52 | (2) |
|
|
54 | (3) |
|
Chapter 4 The Repository and Governance |
|
|
57 | (10) |
|
4.1 The architecture repository |
|
|
58 | (5) |
|
4.1.1 The repository and the ADM |
|
|
58 | (1) |
|
4.1.2 The structure of the repository |
|
|
58 | (1) |
|
|
59 | (1) |
|
4.1.4 Classification plan: Architecture continuum |
|
|
60 | (1) |
|
4.1.5 TOGAF reference models |
|
|
60 | (2) |
|
|
62 | (1) |
|
4.2 Architecture governance |
|
|
63 | (2) |
|
4.2.1 Architecture management |
|
|
63 | (1) |
|
4.2.2 The architecture board |
|
|
63 | (1) |
|
4.2.3 The architecture contract |
|
|
64 | (1) |
|
|
64 | (1) |
|
|
65 | (1) |
|
|
65 | (2) |
|
Chapter 5 Key Modeling Techniques |
|
|
67 | (26) |
|
5.1 Models: Benefits, uses, and characteristics |
|
|
68 | (4) |
|
|
68 | (1) |
|
5.1.2 Usefulness of a model |
|
|
69 | (1) |
|
5.1.3 Characteristics of models |
|
|
70 | (2) |
|
5.1.4 Limitations of models |
|
|
72 | (1) |
|
5.2 The concept of viewpoints |
|
|
72 | (5) |
|
5.2.1 The angle from which a problem is looked at |
|
|
72 | (1) |
|
5.2.2 View and viewpoint: Definition |
|
|
73 | (2) |
|
5.2.3 Usefulness of views |
|
|
75 | (1) |
|
|
76 | (1) |
|
5.3 Special role played by diagrams |
|
|
77 | (2) |
|
5.3.1 Models and diagrams |
|
|
77 | (1) |
|
5.3.2 Diagrams for communicating |
|
|
77 | (2) |
|
5.4 Consistency and traceability |
|
|
79 | (3) |
|
5.4.1 What is a "good" model? |
|
|
79 | (1) |
|
|
80 | (1) |
|
5.4.3 Using traceability in enterprise architecture |
|
|
81 | (1) |
|
5.5 Architecture repository |
|
|
82 | (1) |
|
5.6 Risks and main difficulties |
|
|
83 | (3) |
|
5.6.1 Limitations inherent to any model |
|
|
83 | (2) |
|
5.6.2 Usefulness and support: Major criteria |
|
|
85 | (1) |
|
5.6.3 "Bottom-up" or "top-down": Two limited techniques |
|
|
86 | (1) |
|
5.7 Repository governance |
|
|
86 | (3) |
|
|
89 | (2) |
|
5.8.1 Modeling tools: A necessary medium |
|
|
89 | (1) |
|
5.8.2 Tools available in the marketplace |
|
|
89 | (2) |
|
5.8.3 Summary of the appropriate use of modeling techniques |
|
|
91 | (1) |
|
|
91 | (2) |
|
Chapter 6 Introduction to TOGAF Models |
|
|
93 | (10) |
|
|
93 | (5) |
|
6.1.1 Using models to realize artifacts |
|
|
93 | (1) |
|
6.1.2 Preliminary phase: Determining useful artifacts in the context of the enterprise |
|
|
94 | (1) |
|
6.1.3 Structuring artifacts |
|
|
95 | (1) |
|
6.1.4 Organization of the model |
|
|
96 | (2) |
|
6.2 UML and BPMN for TOGAF modeling |
|
|
98 | (3) |
|
6.2.1 Choosing a representation mode for TOGAF models |
|
|
98 | (1) |
|
6.2.2 Modeling standards for TOGAF |
|
|
98 | (3) |
|
6.3 The "Discount Travel" enterprise |
|
|
101 | (1) |
|
|
102 | (1) |
|
Chapter 7 Models for Phase A: Vision |
|
|
103 | (32) |
|
|
103 | (2) |
|
7.1.1 Nature of phase A artifacts: Vision |
|
|
103 | (1) |
|
7.1.2 Essential concepts used in models |
|
|
104 | (1) |
|
|
105 | (1) |
|
7.3 Artifacts linked to goals |
|
|
106 | (8) |
|
|
106 | (4) |
|
7.3.2 The "Goal diagram" artifact |
|
|
110 | (2) |
|
7.3.3 The "Goal catalog" artifact |
|
|
112 | (2) |
|
7.4 Artifacts linked to requirements |
|
|
114 | (5) |
|
7.4.1 The "Requirements catalog" artifact |
|
|
114 | (4) |
|
7.4.2 The "Requirement diagram" artifact |
|
|
118 | (1) |
|
7.5 Artifacts linked to business processes |
|
|
119 | (8) |
|
7.5.1 Modeling business processes in phase A |
|
|
119 | (1) |
|
7.5.2 The "Event diagram" artifact |
|
|
120 | (7) |
|
7.6 The "Solution concept diagram" artifact |
|
|
127 | (4) |
|
7.6.1 Definition of the artifact |
|
|
127 | (3) |
|
7.6.2 Providing the envisaged solution with an orientation |
|
|
130 | (1) |
|
7.7 The "Value chain diagram" artifact |
|
|
131 | (2) |
|
7.7.1 Definition of the artifact |
|
|
131 | (2) |
|
7.7.2 Contribution of business functions to value |
|
|
133 | (1) |
|
|
133 | (2) |
|
Chapter 8 Models for Phase B: Business Architecture |
|
|
135 | (34) |
|
|
136 | (3) |
|
8.1.1 Nature of Phase B artifacts: Business architecture |
|
|
136 | (1) |
|
8.1.2 Essential concepts used in business architecture models |
|
|
136 | (3) |
|
8.2 The "business dictionary" artifact |
|
|
139 | (2) |
|
8.2.1 Description of the artifact |
|
|
139 | (1) |
|
8.2.2 Terminology: The cornerstone of business knowledge |
|
|
139 | (2) |
|
8.3 Artifacts linked to enterprise organization |
|
|
141 | (10) |
|
8.3.1 Concepts that support enterprise organization |
|
|
141 | (1) |
|
|
141 | (1) |
|
8.3.3 The "actor organization diagram" artifact |
|
|
142 | (3) |
|
8.3.4 The "organization decomposition diagram---flows" artifact |
|
|
145 | (1) |
|
8.3.5 The "organization decomposition diagram---role allocation" artifact |
|
|
146 | (2) |
|
8.3.6 The "location organization diagram" artifact |
|
|
148 | (1) |
|
8.3.7 The "location diagram" artifact |
|
|
149 | (2) |
|
8.4 Artifacts linked to enterprise functions and services |
|
|
151 | (4) |
|
8.4.1 The "functional decomposition diagram" artifact |
|
|
151 | (2) |
|
8.4.2 The "Goal/Objective/Service diagram" artifact |
|
|
153 | (2) |
|
8.5 Artifacts linked to business processes |
|
|
155 | (6) |
|
8.5.1 Key business processes of the enterprise |
|
|
155 | (1) |
|
8.5.2 The "process flow diagram" artifact |
|
|
155 | (2) |
|
8.5.3 The "business use case diagram" artifact |
|
|
157 | (2) |
|
8.5.4 The "service/information diagram" artifact |
|
|
159 | (1) |
|
8.5.5 The "business footprint diagram" artifact |
|
|
160 | (1) |
|
8.6 Artifacts linked to data |
|
|
161 | (6) |
|
8.6.1 The "conceptual data diagram" artifact |
|
|
161 | (5) |
|
8.6.2 The "product lifecycle diagram" artifact |
|
|
166 | (1) |
|
|
167 | (2) |
|
Chapter 9 Models for Phase C: Information System Architecture |
|
|
169 | (28) |
|
|
170 | (4) |
|
9.1.1 Nature of phase C artifacts: Information system architecture |
|
|
170 | (4) |
|
9.2 The "application communication diagram" artifact |
|
|
174 | (3) |
|
9.2.1 Description of the artifact |
|
|
174 | (2) |
|
9.2.2 Modeling application architecture |
|
|
176 | (1) |
|
9.3 The "application migration diagram" artifact |
|
|
177 | (2) |
|
9.3.1 Description of the artifact |
|
|
177 | (1) |
|
9.3.2 Building the migration strategy in accordance with the application evolution path |
|
|
178 | (1) |
|
9.4 The "application and user location diagram" artifact |
|
|
179 | (2) |
|
9.4.1 Description of the artifact |
|
|
179 | (1) |
|
9.4.2 Study of the geographical distribution of users and applications |
|
|
180 | (1) |
|
9.5 The "system use case diagram" artifact |
|
|
181 | (2) |
|
9.5.1 Description of the artifact |
|
|
181 | (1) |
|
9.5.2 Application use cases: Principles |
|
|
182 | (1) |
|
9.6 The "process system realization diagram" artifact |
|
|
183 | (3) |
|
9.6.1 Description of the artifact |
|
|
183 | (2) |
|
9.6.2 Strengthening application communication diagrams: Sequences and synchronizations |
|
|
185 | (1) |
|
9.7 The "enterprise manageability diagram" artifact |
|
|
186 | (2) |
|
|
188 | (7) |
|
9.8.1 The "logical data diagram" artifact |
|
|
188 | (1) |
|
9.8.2 The "data dissemination diagram" artifact |
|
|
188 | (3) |
|
9.8.3 The "data security diagram" artifact |
|
|
191 | (2) |
|
9.8.4 The "data migration diagram" artifact |
|
|
193 | (2) |
|
9.9 The "service data diagram" artifact |
|
|
195 | (1) |
|
9.10 Fundamental concepts |
|
|
196 | (1) |
|
Chapter 10 Models for Phase D: Technology Architecture |
|
|
197 | (10) |
|
|
197 | (2) |
|
10.1.1 Nature of phase D artifacts: Technology architecture |
|
|
197 | (1) |
|
10.1.2 Essential concepts used in technology architecture |
|
|
198 | (1) |
|
10.2 The "Environment and location diagram" artifact |
|
|
199 | (2) |
|
10.3 The "Processing diagram" artifact |
|
|
201 | (2) |
|
10.4 The "Network computing hardware diagram" artifact |
|
|
203 | (2) |
|
10.5 Fundamental concepts |
|
|
205 | (2) |
|
Chapter 11 Models for Phase E: Opportunities and Solutions |
|
|
207 | (6) |
|
|
207 | (1) |
|
11.2 The "Benefits diagram" artifact |
|
|
207 | (2) |
|
11.3 Project context diagrams |
|
|
209 | (4) |
|
Chapter 12 SOA, Processes, and Information |
|
|
213 | (24) |
|
12.1 Service-Oriented Architecture |
|
|
214 | (6) |
|
|
214 | (1) |
|
12.1.2 SOA: Not as simple as it seems |
|
|
215 | (1) |
|
12.1.3 Organizing components |
|
|
215 | (1) |
|
|
216 | (2) |
|
12.1.5 The BPM-SOA couple |
|
|
218 | (2) |
|
|
220 | (11) |
|
12.2.1 The central role of business processes |
|
|
220 | (1) |
|
12.2.2 What is a business process? |
|
|
221 | (1) |
|
12.2.3 Main characteristics of business processes |
|
|
221 | (2) |
|
|
223 | (3) |
|
12.2.5 Describing and modeling business processes |
|
|
226 | (3) |
|
12.2.6 Process governance |
|
|
229 | (1) |
|
12.2.7 BPM, BPMN, standards, and tools |
|
|
230 | (1) |
|
|
231 | (4) |
|
12.3.1 Different types of information in the enterprise |
|
|
232 | (1) |
|
12.3.2 Data exchange in the system |
|
|
233 | (1) |
|
12.3.3 Managing interoperability |
|
|
234 | (1) |
|
12.4 Fundamental concepts |
|
|
235 | (2) |
|
|
237 | (12) |
|
|
237 | (1) |
|
13.2 TOGAF within the AMUE |
|
|
238 | (4) |
|
|
238 | (1) |
|
13.2.2 Presentation of the AMUE |
|
|
238 | (1) |
|
13.2.3 The Government Architecture Reference Model (GARM) of the French state's IS |
|
|
239 | (1) |
|
13.2.4 The AMUE, establishments, and the GARM in the EA approach |
|
|
240 | (2) |
|
|
242 | (1) |
|
13.3 TOGAF within the EDF Group |
|
|
242 | (7) |
|
|
242 | (1) |
|
|
243 | (1) |
|
13.3.3 Choice of TOGAF and awareness campaign undertaken |
|
|
243 | (1) |
|
13.3.4 Enterprise architecture work applied to the emergence of Smart Grid applications |
|
|
243 | (4) |
|
|
247 | (2) |
|
|
249 | (10) |
|
14.1 The ArchiMate standard |
|
|
249 | (2) |
|
14.2 ArchiMate to EAP correspondence examples |
|
|
251 | (4) |
|
|
251 | (2) |
|
|
253 | (1) |
|
|
253 | (2) |
|
|
255 | (3) |
|
14.4 Fundamental concepts |
|
|
258 | (1) |
|
Chapter 15 The EAP Profile |
|
|
259 | (18) |
|
15.1 Mapping UML and BPMN to TOGAF |
|
|
259 | (2) |
|
15.1.1 How UML and BPMN are used to support TOGAF modeling |
|
|
259 | (1) |
|
15.1.2 Conventions for presenting EAP extensions |
|
|
260 | (1) |
|
15.2 Vision and requirements |
|
|
261 | (1) |
|
15.3 Global structure and architecture domains |
|
|
262 | (2) |
|
|
264 | (2) |
|
15.5 Business architecture |
|
|
266 | (4) |
|
15.6 Application architecture |
|
|
270 | (4) |
|
15.7 Technology architecture |
|
|
274 | (1) |
|
15.8 Fundamental concepts |
|
|
275 | (2) |
Glossary |
|
277 | (4) |
Bibliography |
|
281 | (2) |
Index |
|
283 | |