DoD Architecture Framework Version 1.5 - Chief Information Officer

Table 1-3: New Products for v1.5
New Product
SV-4a
Systems Functionality
Description
SV-4b
Services Functionality
Description
SV-5a
Operational Activity
to Systems Function
Traceability Matrix
SV-5b
Operational Activity
to Systems
Traceability Matrix
SV-5c
Operational Activity
to Service
Traceability Matrix
Description and Reason for Addition
Description: The SV-4a documents system functional hierarchies and system
functions, and the system data flows between them.
Reason: This product applies the original v1.0 definition. The net-centric concepts
have been applied to a new product to prevent overloading the original description.
Description: The SV-4b documents service functionality that is exposed to the Net-
Centric Environment, their respective grouping into service families, and their
service specifications.
Reason: This product was developed to capture the services functionality of an
architecture.
Description: The SV-5a depicts the mapping of operational activities to system
functions and thus identifies the transformation of an operational need into a
purposeful action performed by a system.
Reason: This product applies the original v1.0 definition. The different matrices
have been broken out to provide clarity.
Description: The SV-5b extends the SV-5a and depicts the mapping of capabilities
to operational activities, operational activities to system functions, system functions
to systems, and thus relates the capabilities to the systems that support them.
Reason: This product applies the original v1.0 definition. The different matrices
have been broken out to provide clarity.
Description: The SV-5c depicts the traceability and mapping of services to
operational activities to assist in understanding which services support operational
activities.
Reason: This product applies the net-centric concepts. The different matrices have
been broken out to provide clarity.
1.2.2 Integrated Architectures and Federated Architectures
As architecture becomes a key means to enabling better decision making throughout the
Department’s enterprise, the various ways in which architectures are combined, collectively
utilized, managed, and governed are pivotal to fulfilling the many needs of architecture
stakeholders. See Figure 1-1.
1-4