INDEX
Please note that index links point to page beginnings from the print edition. Locations are approximate in e-readers, and you may need to page down one or more times after clicking a link to get to the indexed material.
References to figures are in italics.
A
accepted releases, 161
ACF. See TOGAF ACF
Ackoff, Russ, 34–35
acquisition programs, 269
Acrobat PDF files, 175
action assertion rules, 300, 335
actor/role matrix, 305
ADM. See TOGAF ADM
agency head, 479
agents, 165
airlines, 60
Airport Master Plan (AMP), 66–68
airports, 9–10
All Viewpoint, 77, 221, 228, 235–246 See also specific views
application and user location diagram, 339
application communication diagram (A-2), 339, 341, 375
application data exchange matrix (A-4), 341, 375
application interaction matrix, 339
application interface diagram (A-1), 341, 375
application interface matrix (A-3), 341, 375
application inventory (A-9), 342
application inventory (A-10), 375
application migration diagram, 340, 372
application performance matrix (A-6), 341, 375
application portfolio catalog, 338, 371
application reference model (ARM), 476–477
application service matrix (A-5), 341, 375
application use case diagram, 340
application/data matrix, 337, 401
application/function matrix, 339
application/organization matrix, 338, 371
applications artifacts, 470–471
Applications subarchitecture domain, 340–342
Application/Technology Matrix, 415
application maintenance procedure (A-8), 342
Architect Perspective, 438
architect reviewers, 140
architecture
as-is and to-be, 8
defined, 5
federated architectures, 14
reference architectures, 10
solution architecture, 13
stakeholders, 14–15
Architecture Capability Framework, 447
architecture change management, 189–190
Architecture Content Framework (ACF). See TOGAF ACF
Architecture Content Metamodel, 453
Architecture Definition Document, 452
architecture descriptions, 5, 6
architecture development
integration of tools, 155–158
lessons learned, 152–153
methodology/process, 148–149
processes and tools, 153–154
Architecture Development Method (ADM). See TOGAF ADM
architecture frameworks, 10–11
comparison of, 496–505
extending a standard framework, 423–424
methodologies and process, 19–20
repositories, 18
viewpoints, 14–15
views, 16–18 See also defense architecture frameworks
architecture planning. See planning
Architecture Program Maturity Assessment (APMA), 201
architecture scope, 465–468
architecture sponsors, 164
architecture stakeholders, 164
architecture team members, 164
Architecture Vision, 238
artifacts, 16–17
applications, 470–471
data, 469–470
data architecture, 401–402
data subarchitecture domain, 397–398
FEAF2 service artifacts, 375
infrastructure, 471
security, 471–472
strategy, 468–469
to support a strategic viewpoint, 265
to support technology architecture, 414–415
TOGAF service artifacts, 370–372
as-is architecture, 8
Asset Inventory (I-11), 416
Australian Defense Architecture Framework. See DAF
Authoritative Reference, 484
AV-1: Overview and Summary Information, 221, 236–237, 239–241
case study example, 241–244
AV-2: Integrated Dictionary, 84, 85, 221, 237–238, 245
case study example, 245–246
B
Bachman, Charles, 433
balanced score card (BSC), 266
Bellman, Beryl, 46
binary files, 175
Bricklin, Dan, 31
BSC. See balanced score card (BSC)
business architect, 480
business case/alternatives analysis (B-6), 306
business cases
establishing credible business case analysis for capital investments, 211
for maintenance, 184
business control, 204
business domain, 85–89
business footprint diagram, 305, 371
business interaction matrix, 304
Business Management Perspective, 437
aligning with data and information, 209
business operating plan (B-2), 306
business process diagram (B-1), 306
Business Process Execution Language (BPEL), 198
Business Process Modeling Notation (BPMN), 44, 170, 198
business reference model (BRM), 182, 376, 475
business review board/committee (BRB/BRC), 161, 188–189
business rules, representing culture as, 44–47, 48
business service catalog (B-3), 306, 375
business service/function catalog, 304, 370
business service/information diagram, 305, 371
business services, 345–346, 370
business use-case diagram, 305, 371
butterfly effect, 35
C
Cable Plant Diagram (I-5), 416
Canon Business Machines, 31
capability configuration, 87, 251, 269, 270
Capability Viewpoint, 77, 79, 214–215, 228, 249
balanced score card (BSC), 266
DoD planning requirements, 250–251
element overview, 252–253
federal government planning requirements, 249–250
TOGAF 9.2 support for, 264–265
views, 251–252, 253–264 See also specific views
capital planner, 481
capital planning and investment control (CPIC), 184, 210–211
case study of RMN Airport, 55–56
Airport Master Plan (AMP), 66–68
airside functions and facilities, 61–62
AV-1: Overview and Summary Information, 241–244
AV-2: Integrated Dictionary, 245–246
business domain, 86–87
cargo processing, 64
challenges, 57–58
cultural issues, 66
CV-1: Vision, 254–255
CV-2: Capability Taxonomy, 256
CV-3: Capability Phasing, 257–258
CV-4: Capability Dependencies, 259
CV-5: Capability to Organizational Development Mapping, 260–261
CV-6: Capability to Operational Activities Mapping, 262
CV-7: Capability to Services Mapping, 263–264
DIV-1: Conceptual Data Model, 392–393
DIV-2: Logical Data Model, 394–395
DIV-3: Physical Data Model, 396–397
information technology, 64–65
interacting with communities of interest, 65–66
IT and infrastructure domain, 91
landside functions and facilities, 60–61
management staff, 60
opportunities and aspirations, 56–57
OV-1: High-Level Operational Concept Graphic, 287–288
OV-2: Operational Resource Flow Description, 289–290
OV-3: Operational Resource Flow Matrix, 291–292
OV-4: Organization Relationships Chart, 293–294
OV-5a: Operational Activity Decomposition Tree, 295–298
OV-5b: Operational Activity Model, 297–298
OV-6a: Operational Rules Model, 299–300
OV-6b: State Transition Description, 301
OV-6c: Event-Trace Description, 302–304
passenger processing, 62–63, 75
PV-1: Project Portfolio Relationships, 272–273
PV-2: Project Timelines, 274–275
PV-3: Project to Capability Mapping, 275–276
regulations, 58–59
StdV-1: Standards Profile, 412–413
StdV-2: Standards Forecast, 414
SV-1: Systems Interface Description, 317–318
SV-2: Systems Resource Flow Description, 319–320
SV-3: Systems-Systems Matrix, 321–322
SV-4: Systems Functionality Description, 323–324
SV-5a: Operational Activity to Systems Function Traceability Matrix, 326
SV-5b: Operational Activity to Systems Traceability Matrix, 327
SV-6: Systems Resource Flow Matrix, 328–329
SV-7: Systems Measures Matrix, 330–331
SV-8: Systems Evolution Description, 332–333
SV-9: Systems Technology and Skills Forecast, 334
SvcV-1: Services Context Description, 352–353
SvcV-10a: Services Rules Model, 366–367
SvcV-10b: Services State Transition Description, 368–369
SvcV-2: Services Resource Flow Description, 354
SvcV-3a: Systems-Services Matrix, 355–356
SvcV-3b: Services-Services Matrix, 356
SvcV-4: Services Functionality Description, 357–358
SvcV-5: Operational Activity to Services Traceability Matrix, 359, 360–361
SvcV-6: Services Resource Flow Matrix, 362, 363
SvcV-7: Services Measures Matrix, 364
SvcV-8: Services Evolution Description, 364–365
views, 233
change management. See architecture change management
change of architecture elements
by architecture object type, 179–181
by enterprise nature, 181
introduced by nonlinear events, 181
change response models, 182–183
Chen, Peter, 433
chief information officer (CIO), 7, 138, 479
chief technology officer (CTO), 138
CIO. See chief information officer (CIO)
Clinger-Cohen Act of 1996, 464–465
Command Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance. See C4ISR
Common Approach, 463–464
audits, 486
Collaborative Planning Methodology (CPM), 481–482
enterprise roadmap, 478–481
governance, 484
levels of scope, 465–468
method, 485
overview, 483–486
principles, 484
reporting, 486
repositories and metamodels, 481
standards, 485
subarchitecture domains (viewpoints), 468–472
tools, 485
use, 485–486
“The Common Approach to Federal Enterprise Architecture.” See Common Approach
Common Data Interchange Format (CDIF), 174
Communications Engineering Diagram, 415
communications infrastructure, 93–94
communities of interest, 165
communities of practice, 165
compliance, 203
composite views, 169
composites, 439
concept of operations (CONOPS), 279
conceptual data diagram, 402
conceptual models
technology and infrastructure model, 207, 208
configuration control board (CCB), 140, 161–162
configuration management, 138, 154, 161–162
connectedness, 36
“Consolidated FEA Reference Model Document,” 182
contract/measure catalog, 304
contractors, 60
controlled vocabularies, 387
Corghil, Cort, xxxi–xxxiii
corporate tribes, 26–27 See also tribes
Cross, Rob, 37
culture
as business rules, 44–47
classifying, 29–34
DEC, 40–42
as an emergent phenomenon, 47–48
how it affects enterprise architecture, 34–35
language perspective, 27–29
from multiple perspectives, 49
Novartis, 42–44
organizational culture, 26
origins of culture study, 26
overview, 25
RMN Airport (case study), 66
Shchein’s three levels of, 39–44
and social networks, 38–39
customers, 165
customized response networks, 37
Customs and Border Protection (CBP), 60
CV-1: Vision, 214, 215, 251, 252, 253–254
case study example, 254–255
CV-2: Capability Taxonomy, 214, 251, 255–256, 304
case study example, 256
CV-3: Capability Phasing, 215, 251, 257–258
CV-4: Capability Dependencies, 215, 252, 258–259
CV-5: Capability to Organizational Development Mapping, 215, 252, 260–261, 304
CV-6: Capability to Operational Activities Mapping, 214–215, 252, 261–262
CV-7: Capability to Services Mapping, 215, 217, 252, 263–264, 348
CXOs, 480
D
DAF, 72
dashboards, 169
data
historical time varying data, 383
vs. information, 383–385
representing, 381–382
at rest and in motion, 382
structured vs. unstructured, 383
Data and Information Viewpoint, 77, 79, 219–220, 229, 381, 382, 384
views, 388–391 See also specific views
data architect, 480
data artifacts, 469–470
Data Center/Server Room Diagram (I-8), 416
data context, 399
data description, 399–400
Data Dictionary (D-9), 398
data dissemination diagram, 338, 402
data element naming, 387–388
data entity/business function matrix, 401
data entity/data component catalog, 401
Data Flow Diagram (D-4), 397
data life cycle diagram, 402
data migration diagram, 402
data models, 88
Data Quality Plan (D-3), 397
data reference model (DRM), 182, 398–401, 475–476
data security diagram, 402
data sharing, 400–401
data subarchitecture domain, artifacts, 397–398
data warehousing, 383
Data.gov, 400
clinical cultural analysis example, 40–42
DEC Is Dead, Long Live DEC (Schein), 39
decomposition, 12–13
diagram, 45
Defense Acquisition System (DAS), 491
defense architecture frameworks, 71–72
Defense Architecture Registry System (DARS), 174
Defense Information Technology Standards Repository (DISR), 410, 494
delimited data files, 174
Department of Agriculture, Agriculture Public Health Inspection Service (APHIS), 60
Department of Defense Architecture Framework (DoDAF). See DoDAF
Department of Defense, Intelligence, Surveillance, and Reconnaissance (ISR), 71–72
Department of Homeland Security (DHS), regulations, 59
Department of National Defense/Canadian Armed Forces Architecture Framework. See DNDAF
development specialists, 139
dictionary, 18
Digital Equipment Corporation. See DEC
discovery services, 173
dispensation, 203
dissemination of enterprise architecture
to computerized systems, 173–175
delivery methods, 172–175
identifying the audience for, 164–165
marketing and communications plans, 162–163
preparing for, 161–162
presentation techniques, 166–171
presentation tips, 170–171
DIV-1: Conceptual Data Model, 220, 232, 388–389, 391–393, 401
DIV-2: Logical Data Model, 220, 389, 393–395, 401, 402
DIV-3: Physical Data Model, 220, 389, 395–397
DM2. See DoDAF Metamodel (DM2)
DNDAF, 72
DoD Architecture Framework Version 2.0, 6
DoD Core Data Center, reference architecture, 74
DoD Defense Discovery Metadata Specification (DDMS), 173
DoD Information Enterprise Architecture (DoD IEA), 370
DoD Information Technology Portfolio Repository (DITPR), 494
DoD Joint Information Enterprise, reference architecture, 74
DoD planning requirements, 250–251
core processes, 491–493
extension viewpoints, 422–423
reference models, 74
repository, 85
service components, 347–350
v2.02, 400
viewpoints, 76–79, 214–221, 228–229
DoDAF Metamodel (DM2), 85
business domain, 85–89
communications infrastructure, 93–94
IT and infrastructure domain, 89–94
domain of discourse, 385
Douglas, Mary, 31–33
draft views, 161
driver/goal/objective catalog, 304
Drug Enforcement Agency (DEA), 60
duality of structure, 36
Dublin Core, 400
E
EA executive steering committee (EAESC), 138, 161–162, 188–189
emergence, 10
end-user representatives, 481
Engineer Perspective, 438
enterprise
defined, 3–4
emergence, 10
extended, 11
levels of, 11–14
partitioning, 11–14
segments, 12–13
transformation, 8–10
enterprise architect, 480
enterprise architecture, 7–8
architecture web site/web portal, 172–173
audience for dissemination, 164–165
discovery services, 173
at federal level, 464–465
how culture affects, 34–35
levels of, 72–76
marketing and communications plans, 162–163
preparing for dissemination, 161–162
presentation techniques, 166–171
presentation tips, 170–171
problem classes, 208–213
repository services, 173
web delivery, 172
Enterprise Architecture as Strategy (Ross et al.), 200
enterprise continuum, 447, 453–455
Enterprise Level architectures, 72, 73–74, 85–87
business domain, 86–87
planning example, 122–123
in RMN Airport case study, 96
enterprise manageability diagram, 340, 372
“Enterprise Performance Life Cycle Framework,” 108
Enterprise Perspective, 438
enterprise resource planning (ERP), 9
Enterprise Security Architecture: A Business-Driven Approach (Sherwood), 213
enterprise service bus diagram (A-8), 375
Enterprise Transition Roadmap, 8
environment management, 204
Environments and Locations Diagram, 415
event diagram, 306
Event Sequence Diagram (D-8), 398
executive management, 164–165
Executive Perspective, 437
Expeditionary Combat Support System (ECSS), 9, 27
export files, 174–175
extended enterprise, 11
Extensible Markup Language (XML) files, 175
extension viewpoints, 421–429
F
facilities, 180
Facility Blueprints (I-12), 416
Family of Systems (FoS), 72, 76, 311
FEAF. See Federal Enterprise Architecture Framework (FEAF)
FEAF2. See Federal Enterprise Architecture Framework Version 2 (FEAF2)
Federal Aviation Administration (FAA), 56
regulations, 58–59
Federal Enterprise Architecture (FEA), 465
basic elements, 484–486
performance reference model (PRM), 113
Federal Enterprise Architecture Framework (FEAF), 7, 465
reference models, 182–183
Federal Enterprise Architecture Framework Version 2 (FEAF2), 463, 486
Applications subarchitecture domain, 340–342
business reference model (BRM), 376
Collaborative Planning Methodology (CPM), 494
consolidated reference model, 472
data reference model (DRM), 398–401
data subarchitecture domain artifacts, 397–398
infrastructure reference model, 416–417
infrastructure subarchitecture domain, 415–416
overview, 493–494
service artifacts, 375
service-oriented framework, 373–374
support for capability and strategy, 265–266
support for the Operational Viewpoint, 306
“Federal Enterprise Architecture Reference Model Maintenance Process,” 182
federated architectures, 14, 73
Fit-for-Purpose views, 122, 169, 228
fixed base operators (FBOs), 60
formal configuration management, 161–162
formal models, 17
FoS. See Family of Systems (FoS)
foundation ontology, 385–386
Frankston, Bob, 31
functional decomposition diagram, 305
functional experts, 481
Functional Integration, 484
functions, 370
fusion views, 169
G
GAO. See Government Accountability Office (GAO)
GAO EA Management Maturity Assessment Framework (EAMMF) version 1.1, 200
Garfinkel, Harold, 34
Gartner EA Maturity Assessment Framework, 201
Gladwell, Malcom, 27
Global Earth Observation System of Systems (GEOSS), 76
goal/objective/service diagram, 305, 371
goals, 86
governance
business control, 204
Common Approach, 484
compliance, 203
considerations for all governance strategies, 193–194
dispensation, 203
environment management, 204
framework, 194–198
investment, 195–196
leadership, 195
maturity assessment, 200–201
measurements, 198
monitoring and reporting, 203
organizational structure, 196, 202–203
policy management and take-on, 203
principles and policies, 196–197
security, access and privacy issues, 198–199
standards compliance, 199
in TOGAF 9.2, 201–204
tools and methods, 197–198
Government Accountability Office (GAO), 7, 8, 27
Government Performance and Results Modernization Act of 2010 (GPRA), 475
graph theory, 36–37
graphics, 169
grid, 31–34
ground, 32 See also grid
group, 31–34
H
Health and Human Services (HHS), segments, 75
hidden order, 35
high long term (LTO), 31
Hofstede, Geert, 27, 28, 30–31
Holland, John, 35
Hosting Concept of Operations (I-2), 415
Hymes, Dell, 28–29
I
IBM Systems Journal, 433
ICAM Definition for Functional Modeling (IDEF0), 18, 170
ICOMS, 44
IDEAS, 386
foundation ontology, 425–426
Immigration and Customs Enforcement (ICE), 60
import files, 174–175
information assets, managing information asset inventory, 213
information exchange matrix, 339, 372
Information Sharing Environment Building Blocks, 401
information system services, 370
Information Systems architecture, 337–340
Information Technology Management Reforms Act (ITMRA), 464–465
infrastructure architect, 480
infrastructure artifacts, 471
Infrastructure as a Service (IaaS), 347
infrastructure reference model (IRM), 477
initiatives, 13
innovation, dissolving into the enterprise, 212
inputs, 473
Integrated Definition for Functional Modeling 0 (IDEF0), 44, 198
integrated product teams (IPTs), 139
integrated views, 315–316, 390–391
of tools, 155–158
Integration Definition for Information Modeling (IDEF1X), 399
International Defence Enterprise Architecture Specification. See IDEAS
investment, 195–196
ISO/IEC 11179, 400
ISR (Intelligence, Surveillance, and Reconnaissance) community, 71–72
IT and infrastructure domain, 89–94
J
Jackendoff, Ray, 28
Joint Capabilities Integration and Development System (JCIDS), 250, 423, 491
Joint Capability Areas (JCAs), 75, 494
Joint Common System Function List, 494
Joint Requirements Oversight Council (JROC), 107
Joint Technical Architecture (JTA), 445
K
Kaplan, Robert, 266
Knowledge Management Plan (D-2), 397
Kunda, Gideon, 26
L
language, and culture, 27–29
Language, Consciousness, Culture (Jackendoff), 28
lattice organizations, 33
leadership, 195
level of effort (LOE), 142
estimating issues, 143–144
life cycle issues, 149–152
line of business managers, 481
lines of business (LOBs), 75
Linked Open Data, 400
location catalog, 304
logical data diagram, 402
Logical Data Model (D-1), 397
Lorenz, Edward, 35
Lynch, Michael, 26
M
macro-phenomena, 48
maintenance
business case for, 184
evaluating against the sequencing plan, 187
leveraging solution architectures, 185–186
need for periodic reassessment, 184–185
planning cost of, 184
reflecting operations, 186–187
reflecting reality, 185
reflecting system evolution, 187
responsibility for, 183–184
of the sequencing plan as an integrated program plan, 187
marketing and communications plans, 162–163
Masculinity (MAS) ranking, 30
maturity assessment, 200–201
measurements, 198
messes, 34–35
Common Approach, 481
DoDAF, 85
micro-rules, 48
Microsoft Office files, 175
micro-specifications, 48
Ministry of Defense (United Kingdom) Architecture Framework (MODAF). See MODAF
mission, 180
models, 17
modernizing process, 210
modernizing technology, 209–210
modifying the enterprise architecture, 188–189
modular response networks, 37, 38
monitoring, 203
N
N2 model or node connectivity diagram, 339
NAF, 72
NASCIO, 7
NATCA. See National Air Traffic Control Association (NATCA)
National Air Traffic Control Association (NATCA), 27
National Information Exchange Model (NIEM), 400
Natural Symbols (Douglas), 31
Network Diagram (I-1), 415
Networked Computing/Hardware Diagram, 415
nodes, 36
North Atlantic Treaty Organization (NATO) Architecture Framework. See NAF
Norton, David, 266
Novartis, clinical cultural analysis example, 42–44
O
Object Library (D-10), 398
Office of Inspector General, 8
Office of Management and Budget (OMB), 7, 96, 113
life cycle issues, 149–152
Olsen, Ken, 40–42
OMB. See Office of Management and Budget (OMB)
OMB Enterprise Architecture Assessment Framework (EAAF) version 3.1, 200
ONA. See Organizational Network Analysis (ONA)
ontology, 19, 94–95, 230–232, 385–386
extensions, 424–429
foundation ontology, 385–386
Zachman Framework as an ontology, 433–437, 442–443
aligning technology infrastructure with, 208
operational nodes, 36
Operational Viewpoint, 77–78, 79, 216–217, 228
architecting concerns, 280–282
FEAF2 support for, 306
integrated models, 282–283
operational activity, 283–284
operational event, 284
operational location, 284
overview, 279–280
performers, 284
TOGAF support for, 304–306
views, 285–286 See also specific views
Operations (OPS), 492
ordered anarchies, 26
organization chart (B-4), 306
organization decomposition diagram, 305
organization/actor catalog, 304
organizational climate, 26
organizational culture, 26
Organizational Network Analysis (ONA), 37
organizational structure, 196, 202–203
reorganizing or reallocating responsibilities, 213
outcomes, 473
Common Approach, 483–484
outputs, 473
OV-1: High-Level Operational Concept Graphic, 216, 280, 285, 287–288
OV-2: Operational Resource Flow Description, 84, 216, 281, 285, 288–290, 348
OV-3: Operational Resource Flow Matrix, 84, 216, 281, 285, 290–292, 401
OV-4: Organization Relationships Chart, 280, 285, 292–294
OV-5a: Operational Activity Decomposition Tree, 216, 280, 286, 294–298
OV-5b: Operational Activity Model, 84, 216, 281, 282, 286, 294–298
OV-6a: Operational Rules Model, 216, 217, 281, 282, 286, 298–300, 402
OV-6b: State Transition Description, 281, 282, 286, 300–301
OV-6c: Event-Trace Description, 84, 216, 217, 281, 286, 302–304
P
partitions, 11–14
PDI. See Power Distance Index (PDI)
performance measures, 86, 88, 113
Performance Measures Scorecard (S-5), 265
performance reference model (PRM), 113, 265–266, 473–475
personas, 32–33
Physical Data Model (D-5), 397
planning
Enterprise Level architecture planning example, 122–123
identifying needed data types, 112–113
identifying stakeholders and their issues, 106–109
identifying the scope and deliverables, 102–103
integration of legacy systems, 105
mission interoperability, 105
overview, 101–102
purpose, 103–109
scope, 109–112
Segment Level architecture planning example, 124–127
Solution Level architecture planning example, 127–130
success factors for, 158
success factors in scoping architecture work, 130
tradeoffs, 105–106
transformation, 104
views, 114–122 See also project plan
Planning, Programming, Budgeting, and Execution (PPBE), 492
Platform as a Service (PaaS), 347
Platform Decomposition Diagram, 415
Point of Presence Diagram (I-10), 416
policies, 196–197
policy management and take-on, 203
Portfolio Management (PfM), 492
Power Distance Index (PDI), 30–31
Practical Guide to Federal Enterprise Architecture, 95
“Practical Guide to Federal Enterprise Architecture,” 183
presentation techniques, 166–171
primitives, 439–440
principles, 196–197
Common Approach, 484
Principles Catalog, 238
process flow diagram, 306
process of structuration, 36
process/application realization diagram, 340, 372
key architecture governance processes, 203–204
modernizing, 210
process/event/control/product catalog, 304
Processing Diagram, 415
product life cycle diagram, 305
profiles, 85
UML, 427–428
program managers, 481
programs, 269
project plan
how work will be done, 140–142
overview, 135–136
statement of work (SOW), 135, 136, 137, 145–148
summary, 144
what is to be done, 136–138
when will the work be done, 142–144
who is responsible, 138–140
Project Viewpoint, 78, 79, 215–216, 228, 269–270
views, 270–276 See also specific views
purpose, 103–109
PV-1: Project Portfolio Relationships, 215, 270, 271–272
case study example, 272–273
PV-2: Project Timelines, 215, 270, 274–275
PV-3: Project to Capability Mapping, 215, 216, 270, 275–276
R
Rack Elevation Diagrams (I-7), 416
rationality, types of, 33
rearchitecting. See architecture change management
reassessment, 184–189
reference architectures, 10
DoD Core Data Center, 74
DoD Joint Information Enterprise, 74
solutions, 76
Unified Capabilities, 74
U.S. Army Identity and Access Management (IdAM), 74
U.S. Army Network Security Enterprise, 74
reference models, 17, 169, 472–473
application reference model (ARM), 476–477
business reference model (BRM), 182, 475
change response models for, 182–183
data reference model (DRM), 182, 475–476
DoDAF, 74
infrastructure reference model (IRM), 477
performance reference model (PRM), 265–266, 473–475
security reference model (SRM), 478
TOGAF, 455–457
reliever airport, 56
reporting, 203
repositories, 18
Common Approach, 481
DoDAF, 85
repository manager, 481
repository services, 173
Resource Optimization, 484
resources, 88
responsibilities, reallocating, 213
return on investment (ROI), 113
reusers, 165
RMN Airport (case study), 55–56
Airport Master Plan (AMP), 66–68
airside functions and facilities, 61–62
AV-1: Overview and Summary Information, 241–244
AV-2: Integrated Dictionary, 245–246
business domain, 86–87
cargo processing, 64
challenges, 57–58
CV-1: Vision, 254–255
CV-2: Capability Taxonomy, 256
CV-3: Capability Phasing, 257–258
CV-4: Capability Dependencies, 259
CV-5: Capability to Organizational Development Mapping, 260–261
CV-6: Capability to Operational Activities Mapping, 262
CV-7: Capability to Services Mapping, 263–264
DIV-1: Conceptual Data Model, 392–393
DIV-2: Logical Data Model, 394–395
DIV-3: Physical Data Model, 396–397
information technology, 64–65
interacting with communities of interest, 65–66
IT and infrastructure domain, 91
landside functions and facilities, 60–61
management staff, 60
opportunities and aspirations, 56–57
OV-1: High-Level Operational Concept Graphic, 287–288
OV-2: Operational Resource Flow Description, 289–290
OV-3: Operational Resource Flow Matrix, 291–292
OV-4: Organization Relationships Chart, 293–294
OV-5a: Operational Activity Decomposition Tree, 295–298
OV-5b: Operational Activity Model, 297–298
OV-6a: Operational Rules Model, 299–300
OV-6b: State Transition Description, 301
OV-6c: Event-Trace Description, 302–304
passenger processing, 62–63, 75
PV-1: Project Portfolio Relationships, 272–273
PV-2: Project Timelines, 274–275
PV-3: Project to Capability Mapping, 275–276
regulations, 58–59
Six-Step Process, 96–99
StdV-1: Standards Profile, 412–413
StdV-2: Standards Forecast, 414
SV-1: Systems Interface Description, 317–318
SV-2: Systems Resource Flow Description, 319–320
SV-3: Systems-Systems Matrix, 321–322
SV-4: Systems Functionality Description, 323–324
SV-5a: Operational Activity to Systems Function Traceability Matrix, 326
SV-5b: Operational Activity to Systems Traceability Matrix, 327
SV-6: Systems Resource Flow Matrix, 328–329
SV-7: Systems Measures Matrix, 330–331
SV-8: Systems Evolution Description, 332–333
SV-9: Systems Technology and Skills Forecast, 334
SvcV-1: Services Context Description, 352–353
SvcV-2: Services Resource Flow Description, 354
SvcV-3a: Systems-Services Matrix, 355–356
SvcV-3b: Services-Services Matrix, 356
SvcV-4: Services Functionality Description, 357–358
SvcV-5: Operational Activity to Services Traceability Matrix, 359, 360–361
SvcV-6: Services Resource Flow Matrix, 362, 363
SvcV-7: Services Measures Matrix, 364
SvcV-8: Services Evolution Description, 364–365
SvcV-10a: Services Rules Model, 366–367
SvcV-10b: Services State Transition Description, 368–369
views, 233
role catalog, 304
role/application matrix, 339, 371
Ross/Weill/Robertson maturity model, 200
routine response networks, 37, 38
S
SABSA, 213
scenario behavior, 89
scheduling milestones, 142–143
The School of Management and Strategic Studies (SMSS), 45
security, 198–199
planning for enterprise security, 212–213
security architect, 480
security artifacts, 471–472
security reference model (SRM), 478
Segment Level architectures, 72, 75
core views, 116–118
planning example, 124–127
segments, 12–13
Health and Human Services (HHS), 75
semiformal views, 16
service composition, 347
Service Delivery, 483
service scenarios, 93
service-oriented architecture (SOA), 346, 374
service-oriented enterprise (SOE), 373
service-oriented infrastructure (SOI), 374
services reference model (SRM), 182–183
Services Viewpoint, 78, 79, 92–93, 217–218, 229
business services, 345–346
Infrastructure as a Service (IaaS), 347
Platform as a Service (PaaS), 347
Software as a Service (SaaS), 346–347
views, 350–351 See also specific views
Six-Step Process, 95–99
planning, 101–102 See also AV-1: Overview and Summary Information
social network theory, 36
social networks, 36–39
Software as a Service (SaaS), 346–347
software distribution diagram, 340
software engineering diagram, 340, 372
Software License Inventory (A-10), 342
solution architect, 480
solution architecture, 13
leveraging to grow the enterprise architecture, 185–186
Solution Level architectures, 72, 75–76
business domain, 87–89
core views, 118
IT and infrastructure domain, 91
planning example, 127–130
supporting views by category, 120–121
SoS. See System of Systems (SoS)
specialized aviation service operators (SASOs), 60
sponsors, 164
stable views, 161
stacks, 415
Stakeholder Map Matrix, 238
stakeholder matrix, 108–109
stakeholders, 14–15, 164, 479–481
identifying stakeholders and their issues, 106–109
management, 148
RMN Airport (case study), 59–60
standard interface, 93
standard model layouts, 170
standardized architecture data exchange specification, 175
standardized views, 170
standards compliance, 199
Standards Viewpoint, 78, 220–221, 229, 407–409
FEAF2 infrastructure reference model, 416–417
FEAF2 infrastructure subarchitecture domain, 415–416
integrated views, 410
TOGAF technology architecture, 414–415
views, 409–414 See also specific views
state behavior, 89
State Transition Diagram (D-7), 398
Statement of Architecture Work, 239
statement of work (SOW), 135, 136, 137, 145–148
StdV-1: Standards Profile, 221, 409–410, 411–412
case study example, 412–413
StdV-2: Standards Forecast, 221, 409, 410, 413
case study example, 414
stigmergy, 47–48
strange attractors, 35
Strategic Plan (S-2), 265
strategic planner, 480
Strategic Viewpoint, 249 See also Capability Viewpoint
strategy, 86
strategy artifacts, 468–469
Strengths, Weaknesses, Opportunities, and Threat Analysis (S-4), 265
structure assertion rules, 300, 335
structured documents, 16
subarchitecture domain artifacts (views), 468–472
subarchitecture domains (viewpoints), 468–472
suppliers, 165
SV-1: Systems Interface Description, 218, 219, 312, 317–318
SV-2: Systems Resource Flow Description, 218, 219, 313, 318–320
SV-3: Systems-Systems Matrix, 218, 312, 320–322
SV-4: Systems Functionality Description, 218, 219, 312–313, 323–324, 401
SV-5a: Operational Activity to Systems Function Traceability Matrix, 219, 314, 325–327
SV-5b: Operational Activity to Systems Traceability Matrix, 84, 219, 325–327
SV-6: Systems Resource Flow Matrix, 218, 219, 312, 328–329
SV-7: Systems Measures Matrix, 218, 219, 314, 329–331
SV-8: Systems Evolution Description, 218, 219, 314, 331–333
SV-9: Systems Technology and Skills Forecast, 218, 219, 221, 314–315, 333–334, 410
SV-10a: Systems Rules Model, 218, 315, 335, 402
SV-10b: Systems State Transition Description, 315, 336
SV-10c: Systems Event-Trace Description, 218, 315, 336–337
SvcV-1: Services Context Description, 217, 348–349, 352–353
SvcV-2: Services Resource Flow Description, 218, 349, 353–354
SvcV-3a: Systems-Services Matrix, 217, 355–356
SvcV-3b: Services-Services Matrix, 217, 349, 355–356
SvcV-4: Services Functionality Description, 217, 348, 357–358, 402
SvcV-5: Operational Activity to Services Traceability Matrix, 217, 349, 358–359
SvcV-6: Services Resource Flow Matrix, 217, 349, 359–362
SvcV-7: Services Measures Matrix, 349, 362–364
SvcV-8: Services Evolution Description, 217, 349, 364–365
SvcV-9: Services Technology and Skills Forecast, 349, 365–366, 410
SvcV-10a: Services Rules Model, 349, 366–367
SvcV-10b: Services State Transition Description, 349, 367–369
SvcV-10c: Services Event-Trace Description, 217, 349, 369
syntaxes, 16
System of Systems (SoS), 72, 76, 311
system/application evolution diagram (A-7), 341, 375
systems, 180
systems architect, 480
Systems Engineering (SE), 491
systems nodes, 36
Systems Viewpoint, 78, 79, 90–92, 218–219, 229
integrated views, 315–316
overview, 311–312
summary, 342
system resource flows/information exchanges, 312
systems behavioral models, 315
systems evolution, 314
systems functionality, 312–313
systems need for connectivity, 313
systems operating platforms, 314–315
systems performance specification, 314
systems traceability to operational usefulness, 313–314
T
taxonomy, 386–387
team members, 164
technical nodes, 36
technical reference model (TRM), 372–373, 409, 455–457
technical review board/committee (TRB/TRC), 161–162, 188–189
Technical Standards Profile (I-3), 415
Technician Perspective, 438
technology and infrastructure model, 207, 208
Technology Forecast (I-4), 416
technology modernization, 209–210
Technology Portfolio Catalog, 414
Technology Standards Catalog, 414
The Open Group Architecture Framework. See TOGAF
The Tipping Point (Gladwell), 27
to-be architecture, 8
TOGAF
data architecture artifacts, 401–402
documentation, 446–448
enterprise continuum, 447, 453–455
extension viewpoints, 422
governance, 201–204
Information Systems architecture, 337–340
reference models, 455–457
support for capability and strategy, 264–265
support for the Operational Viewpoint, 304–306
technical reference model (TRM), 372–373
technology architecture, 414–415
view of services, 370–373
TOGAF 9.2, 400
TOGAF 9.2 Standard, Version 9.2: A Pocket Guide, 445
TOGAF ACF, 447, 452–453, 460–461
architecture partitioning, 459
guidelines and techniques, 457–460
Phase A: Architecture Vision, 448–449
Phase B: Business Architecture, 449–450
Phase C: Information Systems Architecture, 449–450
Phase D: Technology Architecture, 449–450
Phase E: Opportunities and Solutions, 450
Phase F: Migration Planning, 450
Phase G: Implementation Governance, 450–451
Phase H: Architecture Change Management, 189–190, 451
Preliminary phase, 448
Requirements Management, 451
tool experts, 481
tool integration, 155–158
tools, 197–198
topologies, changing enterprise topology, 211–212
Transportation Security Agency (TSA). See TSA
tribes
corporate tribes, 26–27
without rulers, 26 See also culture
TSA, 60
regulations, 59
U
UAF. See Unified Architecture Framework (UAF)
UAFP. See Unified Architecture Framework Profile (UAFP)
uncertainty avoidance (UAI), 31
Unified Architecture Framework Profile (UAFP), 94–95
Unified Architecture Framework (UAF), 94–95, 428–429
Unified Capabilities, reference architecture, 74
Unified Modeling Language (UML), 85, 400
foundation ontology, 427–429
profiles, 427–428
Unified Profile for DoDAF and MODAF (UPDM), 85, 94–95, 428
unions, 60
United Architecture Framework/Profile (UAF/P), 174
Universal Description, Discovery, and Integration (UDDI), 173
UPDM. See Unified Profile for DoDAF and MODAF (UPDM)
U.S. Army Identity and Access Management (IdAM), reference architecture, 74
U.S. Army Network Security Enterprise, reference architecture, 74
use-case narrative and diagram (B-5), 306
V
viewpoints, 14–15
DoDAF, 76–79, 214–221, 228–229
extension viewpoints, 421–429
selecting, 115–116 See also subarchitecture domains (viewpoints)
DoDAF, 79–84
Fit-for-Purpose views, 122, 169, 228
integration of, 84, 230, 315–316
planning what views to use, 114–122
selecting, 116–122
tailoring, 228 See also specific views; subarchitecture domain artifacts (views)
VisiCalc, 31
vision, 238
vision statements, 86
vocabularies, 387
W
weather, 35
Web Ontology Language (OWL), 385
Web Services Description Language (WSDL), 348
Weber, Max, 33
well-formed views, 16
Western Behavioral Sciences Institute (WBSI), 44–46
Wireless Connectivity Diagram (I-6), 416
Wiring Closet Diagram (I-9), 416
work breakdown structure (WBS), 136–137
X
XML files, 175
Z
Zachman, John A., xxv–xxx, 5, 433
Zachman Framework, 71, 167, 168
classification schema, 439
development of, 433
as an ontology, 433–437, 442–443
overview, 495–496
primitives and composites, 439–442
stakeholders, 107