Flow Description needlines between them Information Resource Flow Matrix Description of needlines in terms of information flows O U O U O U Operational Activity Hierarchy expressed in ECM terms (extended as necessary) X U U X U U U Activity or process models O U O U X U Operational (Business) Rule Matrix Summary matrix of business rules defined in operational views. O O O Service Component View (ESL and TSC) Description of the program’s services in ESC terms. Child diagrams must be provided for each ESC expressed in Technical Service Component (TSC) terms. X U U X U U X U Interaction Diagram Description of the main interactions between delivered services including data requirements. X U X U X U U Service Communication Requirements Description of the program’s communications X U X U Interaction Matrix Description of the data resource flows defined in Service Interactions X U X U X U 3.4.5 Deployment Sequence Description of the deployment patterns leveraged by the program (i.e., centralized, decentralized…) X U X U U X 3.4.6 Service Sequence Implementation sequence relationship between provisioned services X X U U Inventory View Mapping of provisioned services to ESC and TSCs X U X U
Cross Reference with DoD Architecture Framework (V2.02) Table . Artifacts mapped to DoDAF Models # Program Architecture Guide View Name View Description DoDAF 2.0 Model DoDAF 2.0 Model Name DoDAF Model Description 3.1.1 Overview and Summary Overview of architecture AV-1 Overview and Summary Information Describes a Project's Visions, Goals, Objectives, Plans, Activities, Events, Conditions, Measures, Effects (Outcomes), and other artifacts to be produced. 3.1.2 Integrated Dictionary Glossary or description of objects in architecture views AV-2 Integrated Dictionary An architectural data repository with definitions of all terms used throughout the architectural data and presentations. 3.2.1 Capability Taxonomy with JARM ECM Mapping Breakdown of capabilities within program scope in terms of JARM ECM that includes the enterprise guidance, policy, strategy it aligns to, and the capability description CV-2 Capability Taxonomy Captures capability taxonomies. The model presents a hierarchy of capabilities. These capabilities may be presented in context of a timeline - i.e., it can show the required capabilities for current and future capabilities. 3.2.2 Capability Description Overview of capability to be delivered (may be combined with Operational Concept Description) CV-1 Vision (may be combined with Addresses the enterprise concerns associated with the overall vision for transformational endeavors and thus define the strategic context for a group of capabilities.
3.2.3 Enterprise Guidance Matrix Rules and Constraints defined in Services Views (table listing applicable policies) Services Rules Model Used to describe service functionality. It identifies constraints that are imposed on systems functionality due to some aspect of system design or implementation. 3.3.1 Operational Concept Description Overview of operation concept being delivered OV-1 High Level Operational Concept Graphic The high-level graphical/textual description of the operational concept. 3.3.2 Information Resource Flow Description Description of Person Performers and Information needlines between them OV-2 Operational Resource Flow Description A description of the Resource Flows exchanged between operational activities. 3.3.3 Information Resource Flow Matrix Description of needlines in terms of information flows OV-3 Operational Resource Flow Matrix A description of the resources exchanged and the relevant attributes of the exchanges. 3.3.4 Operational Activity Hierarchy expressed in ESL terms OV-5a Operational Activity Decomposition Tree The capabilities and activities (operational activities) organized in a hierarchal structure. 3.3.5 Activity (Business Process) Diagram Activity or process models OV-5b Operational Activity Model The context of capabilities and activities (operational activities) and their relationships among activities, inputs, and outputs; Additional data can show cost, performers or other pertinent information. OV-6c Event-Trace Description Model used to describe activity (operational activity). It traces actions in a scenario or sequence of events.
3.4.5 Service Sequence Sequence relationship between provisioned Services SvcV-8 Services Evolution Description The planned incremental steps toward migrating a suite of services to a more efficient suite or toward evolving current services to a future implementation. 3.4.6 Deployment Sequence Alternative patterns for implementing technical services in different combinations, and their high level pros and cons. N/A N/A N/A 3.4.7 Inventory Mapping of provisioned services to ESC and TSCs SvcV-5 Operational Activity to Services Traceability Matrix A mapping of services back to operational activities. 3.5.1 Conceptual Data View Executive view of major data concepts DIV-1 Conceptual Data Model The required high-level data concepts and their relationships. 3.5.2 Logical Data View Logical view of detailed data concepts and relationships DIV-2 Logical Data Model The documentation of the data requirements and structural business process (activity) rules. 3.6.1 Relevant Standards Matrix Identification of functional relevant mandated standards (current and future) StdV-1 Standards Profile The listing of standards that apply to solution elements. StdV-2 Standards Forecast The description of emerging standards and potential impact on current solution elements, within a set of time frames.
Needlines Needlines depict what type of information is needed to support the activities between the Nodes. For example: The OV-2 depicts Operational Needlines that indicate a need to exchange resources. DoDAF 2.0 Viewpoints & Models Reference Architecture An architectural design pattern that indicates how an abstract set of mechanisms and relationships realizes a predetermined set of requirements. OASIS Reference Model for Service Oriented Architecture 1.0, 12 October 2006 Segment Architecture A results-based plan for a portion (or segment) of an enterprise aligning with the strategic and relevant program plans of the organization. Detailed results-oriented architecture (baseline and target) and a transition strategy for a portion or segment of the enterprise. Enterprise Architecture Segment Report v1.2, May 2009 OMB FEA Practice Guidance Shared Space Enterprise-shared space refers to a store of data that is accessible by all users within or across security domains in the GIG. A shared space provides virtual or physical access to any number of data assets (e.g., catalogs, web sites, registries, document storage, and databases). As described in this strategy, any user, system, or application that posts data uses shared space. CJCSI 6212.01E Solution Architecture An architecture for an individual IT system that is part of a segment. A solution architecture is reconciled to the segment architecture above it. OMB FEA Practice Guidance Stakeholder A person or organization that has a legitimate interest in a project or entity; anyone with an interest (or stake) in what the entity does. NIEM CONOPS Table 11 summarizes the acronyms used in this Program Architecture Guide. Table . Acronyms Name Definition ASEC Architecture Standards & Engineering Committee BPD Business Process Diagram CDR Critical Design Review CIO Chief Information Officer DODAF Department of Defense Architecture Framework DOTMLPF Doctrine, Organization, Training, Materiel, Leadership & Education, Personnel, and Facilities EA Enterprise Architecture