Skip to content

Commit

Permalink
Update ref-arch-data.md
Browse files Browse the repository at this point in the history
Added hyperlinks to FEAF, DoDAF, and TOGAF. Also cleaned up residual brackets around DoDAF artifacts.
  • Loading branch information
dsofranac committed Aug 20, 2014
1 parent 29fd281 commit 24783aa
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions ref-arch-data.md
Expand Up @@ -70,10 +70,10 @@ Other Data Domain Considerations:

## Architecture Framework Alignment Grid

| **ISE Interoperability Framework: Minimum Requirements for Interoperability** | **ISE Interoperability Framework: Artifact Description** | **FEAF** | **DoDAF/UAF** | **GRA Service Specification Package v 1.0.0** | **IC-related (based on ICEA PAG)** | **TOGAF** |
| Mechanism for identifying and categorizing candidate assets for sharing | (D1) Provide the high-level data concepts and their relationships | • Knowledge Management Plan <br/> • Data Asset Catalog <br/> • Provider-to-Consumer Matrix |[DIV-1: Conceptual Data Model] | • Domain Vocabulary |&nbsp;Conceptual Data Model | • Phase C: Information Systems Architecture – Data <br/> • Application Principals, Data Principals |
| Framework for capturing data elements and the relationship between them (semantics) | (D2) Document the data requirements and their relationships, as well as the structural business process rules and metadata where necessary | • Logical Data Model |[DIV-2: Logical Data Model] | • Message Definitions Mechanism | • Logical Data Model | • Architecture Definitions Document |
| Approach for documenting exchange patterns | (D3) Show the repeatable set of tasks that help accomplish the commonly occurring need for exchange of data/information between exchanging partners, as well as the data relationships and how the data relates to the business activities and their rules/policies | • Business Process Diagram <br/> • Logical Data Model <br/> • Data Flow Diagram |[OV-5b: Operational Activity Model] <br/> • [DIV-1: Conceptual Data Model] <br/> • [DIV-2: Logical Data Model] <br/> • [OV-3: Operational Resource Flow Matrix] <br/> • [OV-2: Operational Resource Flow Description] | • Message Exchange Patterns | • Activity Diagram <br/> • Conceptual Data Model <br/> • Logical Data Model <br/> •&nbsp;Information Resource Flow Description <br/> •&nbsp;Information Resource Flow Matrix | • Activity Model <br/> • Baseline and Target Data Descriptions <br/> • Information Exchange Matrix |
| Principles and roles and responsibilities for data managements and stewardship | (D4) Show organizational relationships with respect to the data and its lifecycle | • Knowledge Management Plan |[OV-4: Organizational Relationships Chart] (along with narrative) | |&nbsp;Operational Concept Description | • Data Management, Data Migration, and Data Governance |
| Technical standards to design and implement information sharing capabilities in ISE systems | (D5) Provide any necessary or relevant data standards to be considered for interoperability | • Technical Standards Profile |[StdV-1 Standards Profile] | | • Relevant Mandated Standards | |
| **ISE Interoperability Framework: Minimum Requirements for Interoperability** | **ISE Interoperability Framework: Artifact Description** | [**FEAF**](http://www.whitehouse.gov/sites/default/files/omb/assets/egov_docs/common_approach_to-federal_ea.pdf) | [**DoDAF**/**UAF**](http://dodcio.defense.gov/dodaf20.aspx) | **GRA Service Specification Package v 1.0.0** | **IC-related (based on ICEA PAG)** | [**TOGAF**](http://pubs.opengroup.org/architecture/togaf9-doc/arch/) |
| Mechanism for identifying and categorizing candidate assets for sharing | (D1) Provide the high-level data concepts and their relationships | • Knowledge Management Plan <br/> • Data Asset Catalog <br/> • Provider-to-Consumer Matrix | • DIV-1: Conceptual Data Model | • Domain Vocabulary |&nbsp;Conceptual Data Model | • Phase C: Information Systems Architecture – Data <br/> • Application Principals, Data Principals |
| Framework for capturing data elements and the relationship between them (semantics) | (D2) Document the data requirements and their relationships, as well as the structural business process rules and metadata where necessary | • Logical Data Model | • DIV-2: Logical Data Model | • Message Definitions Mechanism | • Logical Data Model | • Architecture Definitions Document |
| Approach for documenting exchange patterns | (D3) Show the repeatable set of tasks that help accomplish the commonly occurring need for exchange of data/information between exchanging partners, as well as the data relationships and how the data relates to the business activities and their rules/policies | • Business Process Diagram <br/> • Logical Data Model <br/> • Data Flow Diagram | • OV-5b: Operational Activity Model <br/> • DIV-1: Conceptual Data Model <br/> • DIV-2: Logical Data Model <br/> • OV-3: Operational Resource Flow Matrix <br/> • OV-2: Operational Resource Flow Description | • Message Exchange Patterns | • Activity Diagram <br/> • Conceptual Data Model <br/> • Logical Data Model <br/> •&nbsp;Information Resource Flow Description <br/> •&nbsp;Information Resource Flow Matrix | • Activity Model <br/> • Baseline and Target Data Descriptions <br/> • Information Exchange Matrix |
| Principles and roles and responsibilities for data managements and stewardship | (D4) Show organizational relationships with respect to the data and its lifecycle | • Knowledge Management Plan | • OV-4: Organizational Relationships Chart (along with narrative) | |&nbsp;Operational Concept Description | • Data Management, Data Migration, and Data Governance |
| Technical standards to design and implement information sharing capabilities in ISE systems | (D5) Provide any necessary or relevant data standards to be considered for interoperability | • Technical Standards Profile | • StdV-1 Standards Profile | | • Relevant Mandated Standards | |

0 comments on commit 24783aa

Please sign in to comment.