Enterprise Integration Toolkit

• LOG OUT

• Road Map Overview

• Initiation
• Acquisition
  • Software
  • Systems Integration
• Implementation
• Post Go-Live
• Change Management
  • By Phase
  • By Role

Previous | Next

Initiation | Document High Level Requirements

Puts preliminary description of business needs into writing; Identifies wider, potential project team members; Builds business process flows; enabling assessment of technology fit & impact; Creates draft functional and technical requirements

Long descriptions: Show all | Hide all

| | Steps

	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 high-level requirements, and identify business process and technical leads involved and impacted by the problem and business case.
3	Develop draft requirements and supporting products 4 Develop Operational Activity Model (OV-5), Operational Activity to System Function Traceability Matrix (SV-5), and Systems Evolution Description (SV-8) to support the business change reflected in the high-level business case.	BEA-Log Repository DoD Architecture Framework (DoDAF)
4	Conduct requirements interviews 4 Schedule, execute and document interviews with process owners, key users and technical leads to define the mid-level requirements.	Requirements Document
5	Update process flows in OV-5 4 Refine high-level process flows as a result of interviews.	BEA-Log Repository DoD Architecture Framework (DoDAF)
6	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.	Architectural Guidelines for Business Intelligence, Data Warehousing and Data Marts BEA-Log Repository Logistics Enterprise Framework
7	Define Testing Requirements 4 Develop testing requirements to conform to Clinger-Cohen Act.	Clinger-Cohen Checklist
8	Determine Technical Compliance Requirements 4 Ensure that the program to be acquired is consistent with the Global Information Grid policies and architecture, to include relevant standards	BEA-Log Repository
9	Develop Information Assurance Strategy and Get Approval 4 Develop an information assurance strategy that is consistent with DOD policies, standards and architecture, to include relevant standards	Information Assurance: Acquisition Strategy Considerations