C2.2.1. The acquisition strategy shall
provide a summary description of the requirement the acquisition is intended
to satisfy. The summary shall highlight aspects of the requirement that are
driven by family-of-systems or mission area requirements for
interoperability, and that reflect dependency on planned capability being
achieved by other programs. The summary shall also state whether the
requirement is structured to achieve full capability in time-phased
increments or in a single step. For time-phased requirements, define the
block about to be undertaken, as well as subsequent blocks.
C2.2.2. Approved Source Documents. The
acquisition strategy shall identify approved source documents constituting
the authoritative definition of the requirement. Such documents include the
ORD, Capstone Requirements Document (CRD), and APB.
C2.2.3. Status of In-Process Source
Documents. The acquisition strategy shall describe the status of source
documents as of a specified date. Identify any significant aspects of the
requirement that are unsettled, and the impact this uncertainty has on the
acquisition strategy. The acquisition strategy shall be flexible enough to
accommodate the requirements decisions ultimately made, either through
providing alternative strategies when potential outcomes are limited and
known, or through providing for a strategy update.