ABSTRACT
Systems engineers expect to fulfi ll an end-user requirement with a solution that potentially includes hardware, software, facilities, and people. Th e requirements are gathered through interviews, documents, and materials collected from the user community, the acquisition community, and the regulatory community. Th e technical requirements are defi ned in a specifi cation that can be verifi ed externally. Th e acquisition requirements are defi ned in a Single Acquisition Management Plan (SAMP) or other acquisition planning document, along with a host of supporting documents that demonstrate the acquisition offi ce’s capability to develop a system solution. Th e regulatory requirements are documented as references in the technical and acquisition documents, for example, technical standards and the Federal Acquisition Regulations (FARs).
