Describes business and technical requirements needs at a more granular level by putting mid-level detail around previously defined high level flows and process. This enables Software Vendors to have a better understanding of such requirements. Begins to engage buyer resources at the subject matter expert (SME) level.
| Step | Tools | |
|---|---|---|
| 1 | Gather and Review Available Information
4 Secure and review applicable information available and/or from previous tasks (Define Problem/Challenge and Define High Level Business Case), |
|
| 2 | Identify Leads and Establish Team
4 Determine lead for documenting mid-level requirements, and identify business process leads and technical leads involved and impacted by the problem and business case. |
|
| 3 | Conduct Requirements Interviews
4 Determine requirements via interviews with process owners, key users and technical leads to define the mid-level requirements and update architecture products (OV-2, OV-4, OV-5, DV-1, DV-2). |
|
| 4 | Confirm Flows and Define Requirements
4 Schedule, execute and document integrated process discussions with process owners, key users and technical leads to review/confirm high level process flow and map to business drivers, goals of business case. Update/develop the following architecture products: AV-1, AV-2, OV-2, OV-3, OV-4, OV-5, OV-6, OV-7, DV-1, DV-2, SV-6, SV-9, SV-10, and SV-11/DV-3 |
|
| 5 | Review Systems and Architectural Framework and Guidelines
4 Review existing DoD logistics system information/interfaces to understand the system interfaces that have been registered (through May 2002), the architectural framework that exists, and the guidelines for consistent development processes. |
|
| 6 | Review Existing System Support for the Future Logistics Enterprise
4 Review existing DoD logistics systems architecture information/interfaces developed in a rendering tool. (Review BEA-Log SV-1, Systems Interface Description, SV-3, System to System Matrix, SV-4, Systems Functional Description, and SV-5, Operational Activity to Systems Function Traceability Matrix) |
|
| 7 | Solicit External Feedback
4 Provide mid-level requirements document for external commentary and review. |
|
| 8 | Incorporate Feedback
4 Incorporate feedback from external sources to finalize Requirements Documentation. |
|
| 9 | Sponsor Signoff
4 Present documented process flows and requirements to top management, process and technical owners for approval and signoff. |
Download Enterprise Integration Toolkit
DoDAF and Data Views
Sample MS Access logistics systems database 
Logistics Architecture Framework Reference 
Architectural Guidelines for Business Intelligence, Data Warehousing, and DataMarts Reference