Acq Notes

The Capability Production Document (CPD) captures the information necessary to support production, testing, and deployment of an affordable and supportable increment within an acquisition strategy. The CPD identifies, in threshold/objective format, the specific attributes that contribute most significantly to the desired full operational capability of a system. The CPD is prepared during the Engineering & […]

The Capability Development Tracking and Management Tool (CDTM) is a web-based tool used by authors and reviewers of capabilities documents; Initial Capabilities Document (ICD), Capability Development Document (CDD), System Requirements Document (SRD), and Capability Production Document (CPD). The software presents a series of “wizard” screens that guide the user through capability document creation, step-by-step. CDTM

The Capability Development Document (CDD) specifies the operational requirements for the system that will deliver the capability that meets the operational performance criteria specified in the Initial Capabilities Document (ICD). It outlines militarily useful increments of capability with its own set of attributes and development performance values (i.e., thresholds and objectives) in terms of Key

Requirements Development Process In Step 6 “Manage Requirements”, the requirements have been accepted and a baseline is established by the stakeholders. Any changes to the requirements are controlled using a Configuration Management (CM) process. Managing requirements is a continuous process and is conducted throughout a system’s life cycle and confirmed at each technical review. The

In Step 5, “Verify & Validate Requirements,” each requirement must be verified and validated to ensure that they are the correct requirement. This ensures that the requirements meet the overall objective of the system and all stakeholder needs. Verification and Validation should be done continuously throughout the development of requirements at every level and as

Requirements Development Steps Step 4 “Analyze, Refine & Decompose Requirements” examines each requirement to see if it meets the characteristics of a good requirement. Each requirement is then decomposed into a more refined set of requirements that are allocated to sub-systems and documented in the Weapons System Specification (WSS). Newly derived requirements are expected to

Requirements Development Process Step 3 “Check Completeness” is to check that a complete set of requirements have been developed and documented that defines all system functions that are needed to satisfy the stakeholder needs with their associated performance, environmental, and other non-functional requirements. Visit: Requirements Evaluation Requirements designers should go back to Stakeholders with the

Step 2 “Write & Document Requirements” officially documents the requirements. The requirements must be documented in order to establish a requirements baseline to start building a system and manage any changes. This step focuses on writing down the functional and performance level requirements into the appropriate requirements documents. Requirements can be developed using the Capability

  Requirements Development Steps Step 1 in the requirement development process is to Gather and Develop requirements data from key stakeholders, project objectives, and already developed requirements. A number of typical sources used to gather requirements data are: Concept of Operations (CONOPS) Defense Federal Acquisition Requirements Supplement (DFARS) Earn Value Management Requirements Federal Acquisition Requirements