5-3 Concept & Requirements Definition

Conduct HF Assessments to Support Refinement of Concepts. As indicated in crdguidelines.pdf (faa.gov): “The alternatives developed during the CRD phase will be high-level concepts, and thus referred to as preliminary alternative descriptions.”

These alternatives will developed into a Solution ConOps that:

• “Describes how users will employ the new capability and how it will achieve desired objectives for the proposed service need”
• “Defines the roles and responsibilities of key participants (e.g., controllers, maintenance technicians, pilots”
• “Explains operational issues that system engineers must understand when developing requirements”
• “Identifies procedural issues that may lead to operational change”
• “Incorporates and reflects key enterprise data and information needs”
• “Establishes a basis for identifying alternative solutions and estimating their likely costs and benefits” (crdguidelines.pdf (faa.gov)).
  

The guidelines emphasize the importance of “human factors engineering to ensure performance requirements and objectives are consistent with human capabilities and limitations”. As an example, “HF implications can include the appropriateness of automation or procedures from a HF perspective, in the context of other systems and tasks. Such analysis can be performed well before establishing details such as computer human interface (CHI) requirements later in the AMS lifecycle” (crdguidelines.pdf (faa.gov)).