Skip to content

Commit

Permalink
Merge pull request #31 from dsofranac/patch-16
Browse files Browse the repository at this point in the history
Update ref-arch-business.md
  • Loading branch information
allalala committed Aug 20, 2014
2 parents 276f6a2 + 599aaf4 commit 411875e
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions ref-arch-business.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,8 +60,8 @@ Other Business/Mission 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** |
| Alignment of ISE participant architecture capabilities to ISE relevant interoperability and information sharing policies and guidance | • (B1) Describe the operational concept to be achieved <br/> • (B2) Provide the overall vision in a strategic context for the capabilities and a high-level scope <br/> • (B3) Provide a hierarchy of capabilities along with a description of the capabilities <br/> • (B4) Show the planned achievement of the capabilities by time frames and what constrains/policies are being applied | • Business Operating Plan <br/> • Business Service Catalog <br/> • Concept Overview Diagram <br/> • Strategic Plan | • [CV-1: Vision] <br/> • [CV-2: Capability Taxonomy] <br/> • [CV-3 Capability Phasing] or [PV‑2 Project Timelines] (for Portfolio Management) <br/> • [OV-1: High-level Operational Concept Graphic] | • Business Process Models <br/> • Capabilities <br/> •&nbsp;Provisioning Model | •&nbsp;Operational Concept Description <br/> • Capability Description <br/> • Capability Taxonomy <br/> • Enterprise Guidance Matrix | • Phase A: Architecture Vision, Scope, Stakeholder Management, Communications Plan <br/> • Phase B: Business Architecture, Baseline Descriptions, Business Models, Information Exchange Matrix, Business Node Activities |
| Standards and approaches for capturing business requirements and modeling business processes and information flows | <br/> • (B5) Capture business requirements, preferably using standards from organizations (NIST, IEEE, ISO, etc.) that enable enterprise architecture models and analysis with regard to likewise comparisons between lines of business and organizations <br/> • (B6) Describe the information exchanges and their attributes <br/> • (B7) Document the data requirements and the structural business process rules | Business Process Diagram Logical Data Model | • [DIV-2: Logical Data Model] <br/> • [OV-2: Operational Resource Flow Description] <br/> • [OV-3: Operational Resource Flow Matrix] <br/> • [OV-5b: Operational Activity Model] | • Enterprise Integration Patterns | • Activity Business Process Diagram <br/> •&nbsp;Operational Concept Description <br/> • Logical Data Model <br/> •&nbsp;Information Resource Flow Description <br/> •&nbsp;Information Resource Flow Matrix | • Business Process Models, Node Connectivity Diagrams, Information Exchange Matrix |
| Considerations for Information Sharing Agreements (ISAs) | (B8) Document the relevant ISAs and how these affect the exchange of information between users | Business Process Diagram |[OV-2: Operational Resource Flow Description] <br/> • [OV-3: Operational Resource Flow Matrix] <br/> • [OV-6a: Operational Rules Model] | • Information Model <br/> • Message Exchange Patterns |&nbsp;Information Resource Flow Description <br/> •&nbsp;Operational Rules Matrix <br/> • Enterprise Guidance Matrix | • Activity Models, Service Levels, Boundaries and Contracts |
| Exchange Specifications and their relation to technical standards and services within a specific mission context. | (B9) Provide the exchange specifications as they relate to the services, to include applicable technical standards from accepted standards bodies (ISO, IEEE, NIST, NIEM) | Technical Standards Profile |[StdV-1 Standards Profile] | • Service Interaction Profiles | • Relevant Mandated Standards | • Architecture Definitions, Architecture Requirement Specifications |
| **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/) |
| Alignment of ISE participant architecture capabilities to ISE relevant interoperability and information sharing policies and guidance | • (B1) Describe the operational concept to be achieved <br/> • (B2) Provide the overall vision in a strategic context for the capabilities and a high-level scope <br/> • (B3) Provide a hierarchy of capabilities along with a description of the capabilities <br/> • (B4) Show the planned achievement of the capabilities by time frames and what constrains/policies are being applied | • Business Operating Plan <br/> • Business Service Catalog <br/> • Concept Overview Diagram <br/> • Strategic Plan | • CV-1: Vision <br/> • CV-2: Capability Taxonomy <br/> • CV-3 Capability Phasing or PV‑2 Project Timelines (for Portfolio Management) <br/> • OV-1: High-level Operational Concept Graphic | • Business Process Models <br/> • Capabilities <br/> •&nbsp;Provisioning Model | •&nbsp;Operational Concept Description <br/> • Capability Description <br/> • Capability Taxonomy <br/> • Enterprise Guidance Matrix | • Phase A: Architecture Vision, Scope, Stakeholder Management, Communications Plan <br/> • Phase B: Business Architecture, Baseline Descriptions, Business Models, Information Exchange Matrix, Business Node Activities |
| Standards and approaches for capturing business requirements and modeling business processes and information flows | <br/> • (B5) Capture business requirements, preferably using standards from organizations (NIST, IEEE, ISO, etc.) that enable enterprise architecture models and analysis with regard to likewise comparisons between lines of business and organizations <br/> • (B6) Describe the information exchanges and their attributes <br/> • (B7) Document the data requirements and the structural business process rules | Business Process Diagram Logical Data Model | • [DIV-2: Logical Data Model] <br/> • OV-2: Operational Resource Flow Description <br/> • OV-3: Operational Resource Flow Matrix <br/> • OV-5b: Operational Activity Model | • Enterprise Integration Patterns | • Activity Business Process Diagram <br/> •&nbsp;Operational Concept Description <br/> • Logical Data Model <br/> •&nbsp;Information Resource Flow Description <br/> •&nbsp;Information Resource Flow Matrix | • Business Process Models, Node Connectivity Diagrams, Information Exchange Matrix |
| Considerations for Information Sharing Agreements (ISAs) | (B8) Document the relevant ISAs and how these affect the exchange of information between users | Business Process Diagram | • OV-2: Operational Resource Flow Description <br/> • OV-3: Operational Resource Flow Matrix <br/> • OV-6a: Operational Rules Model | • Information Model <br/> • Message Exchange Patterns |&nbsp;Information Resource Flow Description <br/> •&nbsp;Operational Rules Matrix <br/> • Enterprise Guidance Matrix | • Activity Models, Service Levels, Boundaries and Contracts |
| Exchange Specifications and their relation to technical standards and services within a specific mission context. | (B9) Provide the exchange specifications as they relate to the services, to include applicable technical standards from accepted standards bodies (ISO, IEEE, NIST, NIEM) | Technical Standards Profile | • StdV-1 Standards Profile | • Service Interaction Profiles | • Relevant Mandated Standards | • Architecture Definitions, Architecture Requirement Specifications |

0 comments on commit 411875e

Please sign in to comment.