PREPARE HUMAN FACTORS FOR MISSION ANALYSIS AND REQUIREMENTS

Purpose

The purpose of this section is to provide basic guidelines for the development of human factors requirements. Human factors (HF) requirements are often poorly stated in the flow of documents related to system acquisitions.  Human factors input to documentation during and subsequent to a Mission Analysis (MA) must provide essential elements of information upon which to build good requirements; prepare cost, benefit, and risk analyses; conduct studies and analyses, and develop plans, specifications, and statements of work.

Human factors requirements are intended to ensure that equipment operated or maintained by the FAA is easy to operate, maintain, and train.  The FAA Human Factors Design Standard (HFDS) provides detailed guidelines and conventions to achieve a human-centered, error resistant, error tolerant, operationally effective, operationally suitable, and usable system.  Human factors requirements must address:

Human-system interfaces that impact on user performance efficiency and effectiveness

System architecture design that impacts on human-system interfaces

Human-systems considerations that impact human resources and systems outside the boundary of the system being acquired.

Timing

Timing  HF input to the Mission Analysis is reflected in the Mission Need Statement (MNS) which defines a mission capability shortfall or technological opportunity the FAA should address and includes consideration of major human resource and human-system performance issues.

The MNS is prepared in the Mission Analysis phase.  Joint Resources Council (JRC) approval of the MNS initiates entry into the Investment Analysis phase.  The MNS is revalidated at the Investment Decision. Incorporation of major human resource and performance considerations provides a basis for addressing constraints related to the human component of the required capability.

HF considerations are incorporated into Mission Analysis products to identify capability shortfalls or opportunities for enhancement of human-system performance.  HF requirements are developed during the Integrated Requirements Team (IRT) activities and incorporated into the initial Requirements Documents (iRDs) and final Requirements Documents (fRDs).

Requirements are developed early in the investment analysis process by the sponsoring organization.  Capability shortfalls or technological opportunities identified in the MNS are translated into essential top level operational and functional requirements.  An initial Requirements Document (iRD) is prepared and updated during the Investment Analysis phase.  Requirements evolve into greater specificity throughout the process to support detailed market, investment, and affordability analyses.

The iRD establishes the baseline criteria for selecting candidate solutions, conducting market analyses, analyzing alternatives, and performing affordability assessments to provide the best overall approach for satisfying the mission need.

Throughout the alternatives and affordability assessment phases of the investment analysis process, requirements are evaluated against cost, benefit, schedule, and performance considerations.  Requirements that are descriptive enough of what is being asked of industry to satisfy (via a contract or other government vehicle) will be provided to the IA Team to conduct the market analysis.

Human factors inputs to the Requirements Document identify requirements for human performance factors that may impact system design.  Broad cognitive, physical, and sensory requirements for the operator, maintainer, and support personnel that contribute to or constrain total system performance are established.  Any safety, health hazards, or critical errors that reduce job performance or system effectiveness are defined.  The staffing and training concepts and constraints are also described.

"How To" -
General Guidelines

Human factors practitioners have found utility in general and specific guidelines for supporting mission needs and requirements development activities.

Human factors practitioners are expected to participate in IRT activities to provide essential expert input for the development of requirements documents.  These guidelines are general in nature and apply without regard to specific AMS policy/processes that may require tailoring of human factors requirements.  Consideration should be given to the following.

Human factors requirements developed early in a program will likely need greater specificity later in the program.  However, even requirements in the FRD may not sufficiently define the specific measures, performance values, thresholds, or data collection requirements that will be needed to verify the requirement during test and evaluation.

Some requirements may evolve to near specification-like details especially for critical issues.  They may be complemented by SOW-type requirements for conducting activities (analyses/studies) to define the specification-like details or government requirements for the same.

There is a direct and devolving relationship between the Critical Operational Issues (COIs), requirements, Specs/SOW, and test and evaluation plans. Quality in one determines the quality of the next.

Specific Guidelines

Human factors practitioners have found utility in general and specific guidelines for supporting mission needs and requirements development activities.

Human factors practitioners are expected to participate in IRT activities to provide essential expert input for the development of requirements documents.  These guidelines are general in nature and apply without regard to specific AMS policy/processes that may require tailoring of human factors requirements.  Consideration should be given to the following.

Human factors requirements developed early in a program will likely need greater specificity later in the program.  However, even requirements in the FRD may not sufficiently define the specific measures, performance values, thresholds, or data collection requirements that will be needed to verify the requirement during test and evaluation.

Some requirements may evolve to near specification-like details especially for critical issues.  They may be complemented by SOW-type requirements for conducting activities (analyses/studies) to define the specification-like details or government requirements for the same.

There is a direct and devolving relationship between the Critical Operational Issues (COIs), requirements, Specs/SOW, and test and evaluation plans. Quality in one determines the quality of the next.

Steps











Related Documents

Step 1 Human-System Performance Analysis

Step 2 Integrate HF Principles into System Context

Step 3 Prepare and Formalize HF-Requirements for AMS Requirements Document

Checklist