Skip to content

Latest commit

 

History

History
67 lines (39 loc) · 8.49 KB

ref-arch-business.md

File metadata and controls

67 lines (39 loc) · 8.49 KB
Raw
published permalink layout filename title
true
/ref-arch-business/
default
ref-arch-business.md
Business/Mission Domain Section Reference Architecture Template

The reference architecture (RA) templates are designed to aid the development of reference architecture artifacts to support interoperability. To learn more about the purpose, structure, method, and how to use these templates, visit the main Reference Architecture Template page.

Alignment with Project Interoperability Tools and Resources: Operational Capabilities, Exchange Patterns.

Overview: Describe the lines of business and organizations and the operational concept to be achieved. Provide the overall vision in a strategic context for the capabilities and a high level scope. Provide a hierarchy of capabilities along with description of the capabilities. Show the planned achievement of the capabilities by time frames and what constrains/policies are being applied.

Objectives of the Architecture: Describe how the architecture supports the operational enterprise data and makes it discoverable and searchable, i.e., registry or service inventory. For example: The Identity and Access Management initiative provides enterprise information through the use of a global registry to support naming standards and federated access to support other mission capabilities.

Business Models, Diagrams, and Flows:

  • Describe the operational concept to be achieved by the architecture and provide the overall vision in a strategic context for the capabilities. (B1)

  • Describe the flow of resources/data exchanged from a business perspective between operational activities. (B6)

  • General overview of architecture (description and graphics). (B2)

  • Policy and Governance considerations: Provide policies, governance information, or applicable laws that will affect the implementation of the architecture. (B5)

  • Architecture Environment considerations: Describe any federation, cloud, mobile considerations in the implementation of the architecture. (B5)

  • Define the intended interoperability outcomes for each of the business functions within the architecture. (B4)

Business Processes:

  • Establish specific exchange patterns for the architecture. (B6)

  • Document internal and external information flows. (B6)

  • Establish the authoritative sources of information/data along with agreements. (B7)

  • Document any dependencies on other work not included in the reference.

  • List assumptions used in development of the reference architecture.

Business/Mission Exchange Processes:

  • Provide the exchange specification as they relate to the services which would include applicable technical standards from accepted standards bodies (e.g., ISO, IEEE, and NIST). (B9)

  • Build use cases for each type of data exchange.

  • Information/Data sharing access agreements established and exposed to users. (B8)

Other Business/Mission Domain Considerations:

  • Consult security officer to capture applicable security rules/requirements. The results should be captured as annotations with the applicable artifacts

  • Consult privacy officer to capture privacy rules/laws Applicable rules and laws should be noted on artifacts in order to capture them as requirements in the implementation lifecycle

  • Consult the modernization plan to ensure alignment Modernization plan considerations should be captured on existing artifacts as discovered or as part of "to-be" artifacts

Key Focus Area: Business - Capture business requirements, preferably using standards and guidance from organizations to develop diagrams, models and layers of abstractions to depict business analysis completed, business processes and organizational and business service relationships using standard methods (e.g., Business Process Model Notation (BPMN), IDEF0, Unified Modeling Language (UML), etc.). Services should be standardized both within and between agencies whenever possible to enhance interoperability. Standards Development Organizations should be primary source, i.e., IEEE, OMG, OASIS, NIST, and ISO, to enable the use of architecture and business models and analysis with regard to comparison or alternatives.

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
• (B2) Provide the overall vision in a strategic context for the capabilities and a high-level scope
• (B3) Provide a hierarchy of capabilities along with a description of the capabilities
• (B4) Show the planned achievement of the capabilities by time frames and what constrains/policies are being applied | • Business Operating Plan
• Business Service Catalog
• Concept Overview Diagram
• Strategic Plan | • CV-1: Vision
• CV-2: Capability Taxonomy
• CV-3 Capability Phasing or PV‑2 Project Timelines (for Portfolio Management)
• OV-1: High-level Operational Concept Graphic | • Business Process Models
• Capabilities
• Provisioning Model | • Operational Concept Description
• Capability Description
• Capability Taxonomy
• Enterprise Guidance Matrix | • Phase A: Architecture Vision, Scope, Stakeholder Management, Communications Plan
• 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 |
• (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
• (B6) Describe the information exchanges and their attributes
• (B7) Document the data requirements and the structural business process rules | Business Process Diagram Logical Data Model | • DIV-2: Logical Data Model
• OV-2: Operational Resource Flow Description
• OV-3: Operational Resource Flow Matrix
• OV-5b: Operational Activity Model | • Enterprise Integration Patterns | • Activity Business Process Diagram
• Operational Concept Description
• Logical Data Model
• Information Resource Flow Description
• 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
• OV-3: Operational Resource Flow Matrix
• OV-6a: Operational Rules Model | • Information Model
• Message Exchange Patterns | • Information Resource Flow Description
• Operational Rules Matrix
• 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 |