Defense Business Systems (DBS) Model
DBS Pathway (BCAC)
Capability Need ID Phase
Solution Analysis ATP
Solution Analysis Phase
Functional Requirements ATP
Functional Req and Acq Planning Phase
Acquisition, Testing, and Deployment Phase
Capability Support ATP
Capability Support Phase
Business System Solution Documentation
How to use this site
Each page in this pathway presents a wealth of curated knowledge from acquisition policies, guides, templates, training, reports, websites, case studies, and other resources. It also provides a framework for functional experts and practitioners across DoD to contribute to the collective knowledge base. This site aggregates official DoD policies, guides, references, and more.
DoD and Service policy is indicated by a BLUE vertical line.
Directly quoted material is preceeded with a link to the Reference Source.
Reference Source: DoDI 5000.75 Appendix 4D
- Functional requirements will be linked to inputs and outputs that define how the functional requirements support the business processes.
- Functional requirements will be linked to technical and lifecycle support requirements that constrain how the functional requirements support the business process.
Potential Business System Solution Selection
The program manager, with support from the functional lead and the appropriate cost agency, establishes criteria for evaluating potential business system solutions.
Evaluation criteria must include:
- Economic analysis (cost and benefit).
- Satisfaction of functional requirements and inputs and outputs.
- Satisfaction of technical requirements and lifecycle support requirements.
- Overall risk.
Other criteria may also include:
- Delivery schedule.
- Evaluation of trade space for functional requirements.
- Impacts to other programs.
Business System Design Specifications
Design specifications provide sufficient detail on the solution or service being acquired or developed to support delivery and verification of the business system.
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.
Design specifications must be prioritized to the extent practicable to allow for cost and schedule trades within scope.
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:
- 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.
- Technical requirements, e.g., infrastructure, open architecture, data standards, data management, hosting and security, and lifecycle support requirements (availability, scalability, maintainability, supportability, and interoperability).
- System and sub-system design, user interface design, logical and physical data models, business rules and related architectural products.
- Communication-oriented description of system interaction with other systems, e.g., interface control and interface design documents and related system architectural products.
- Traceability mappings from requirements through design to method of verification.