DODI 5000.75 Appendix 4D Business Systems Solutions and Documentation
4D.1. FUNCTIONAL REQUIREMENTS.
a. Functional requirements will be linked to inputs and outputs that define how the functional requirements support the business processes.
b. Functional requirements will be linked to technical and lifecycle support requirements that constrain how the functional requirements support the business process.
4D.2. POTENTIAL BUSINESS SYSTEM SOLUTION SELECTION.
a. The program manager, with support from the functional lead and the appropriate cost agency, establishes criteria for evaluating potential business system solutions.
b. Evaluation criteria must include:
(1) Economic analysis (cost and benefit).
(2) Satisfaction of functional requirements and inputs and outputs.
(3) Satisfaction of technical requirements and lifecycle support requirements.
(4) Overall risk.
c. Other criteria may also include:
(1) Delivery schedule.
(2) Evaluation of trade space for functional requirements.
(3) Impacts to other programs.
4D.3. BUSINESS SYSTEM DESIGN SPECIFICATIONS.
a. Design specifications provide sufficient detail on the solution or service being acquired or developed to support delivery and verification of the business system.
b. Design specifications are not a specific document. Instead, they are the content needed by the program office to specify the design of the business system, as stored and used by the program in whatever applicable format or repository is needed.
c. Design specifications must be prioritized to the extent practicable to allow for cost and schedule trades within scope.
4D.4. CONTENT OF BUSINESS SYSTEM DESIGN SPECIFICATIONS.
Design specifications are based upon the high-level requirements established during functional requirement definition. This includes the functional requirements, along with associated inputs and outputs for the functional requirements, and associated technical and lifecycle support requirements. The detailed design includes:
a. Task-oriented description of end user interaction with the system, e.g., use cases, user stories, or functional requirements statements expressed as functions that “the system shall” perform.
b. Technical requirements, e.g., infrastructure, open architecture, data standards, data management, hosting and security, and lifecycle support requirements (availability, scalability, maintainability, supportability).
c. System and sub-system design, user interface design, logical and physical data models, business rules and related architectural products.
d. Communication-oriented description of system interaction with other systems, e.g., interface control and interface design documents and related system architectural products.
e. Traceability mappings from requirements through design to method of verification.