| 1 |
Develop operational views
4Describes the to-be operational nodes and elements, assigned tasks and activities, and information flows required between nodes.
1. Develop Operational Information Exchange Matrix (OV-3). Expand and further define the needlines in the Component OV-2.
2. Develop Organizational Relationships Chart (OV-4). Decompose the nodes from the Component OV-2 as appropriate and assign organizational structure.
3. Develop Operational Activity Model (OV-5). Map business processes to the nodes that perform them.
4. Develop Operational Rules Model (OV-6's). Develop OV-6 products as appropriate, at a minimum documenting relevant business rules.
|
 DoD Architecture Framework (DoDAF)
BEA-Log Repository |
| 2 |
Initiate integrated dictionary
4Defines all terms used in the architecture products (AV-2).
1. Define architecture terms. Create repository with definitions of all terms used in the architecture. Development of this product is iterative as the architecture matures.
|
DoD Architecture Framework (DoDAF)
BEA-Log Repository |
| 3 |
Develop system views
4Describes the interoperability and functional support provided by existing information systems and the planned migration strategy over time.
1. Develop Systems Interface Description (SV-1). Describe existing system relationships
2. Develop Systems Functionality Description (SV-4). Document existing system capabilities.
3. Develop operational activity to Systems Function Traceability Matrix (SV-5). Map existing system capabilities to operational activities.
|
DoD Architecture Framework (DoDAF)
BEA-Log Repository |
| 4 |
Develop technical views
4Describes the desired and emerging technical standards that apply to information systems.
1. Develop TV-1. Describe adaptation of BEA-Log TV-1.
2. Develop TV-2. Describe adaptation of BEA-Log TV-2.
|
DoD Architecture Framework (DoDAF)
BEA-Log Repository |
| 5 |
Develop data views
4Describes the information required to support the business processes.
1. Develop OV-7. Describe the information entities within the scope of the enterprise and their relationships to each other.
2. Develop DV-1. Identify communities of interest (COIs) and the attendant business processes within the COIs that fall within the scope of the enterprise.
3. Develop DV-2a. Identify data assets and their interfaces based on the systems and their relationships to the COIs that fall within the scope of the enterprise.
4. Develop DV-2b. Identify the appropriate metadata for the data assets related to the COIs within the scope of the enterprise.
5. Develop DV-2c. Develop Common Information Models (CIMs) to support the processes in the COIs that fall within the scope of the enterprise.
6. Develop DV-3. Map shared data elements between the CIMs and the data assets that fall within the scope of the enterprise.
|
DoD Architecture Framework (DoDAF)
BEA-Log Repository |
| 6 |
Architecture evaluation
4Determines the Component architecture's level of compliance with the BEA-Log.
1. Ensure required information is available. See Section 4.1, BEA-Log Compliance Plan.
2. Work with LSM to schedule evaluation.
3. Produce briefing that supports the parameters of the review. See Section 4.2, BEA-Log Compliance Plan.
4. Forward architecture products/information to LSM. See Section 4.1, BEA-Log Compliance Plan.
5. Participate in review session.
6. Follow up on any action items.
7. Develop plan for obtaining compliance. If necessary, work with LSM to develop a plan for obtaining compliance with BEA-Log (see Section 4.4, BEA-Log Compliance Plan).
|
BEA-Log Repository |
Download Enterprise Integration Toolkit