Book A.

Book B.
7150 Requirements Guidance

Book C.

References, & Terms

(NASA Only)

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin



1. Requirements

3.4.9 The project shall ensure that the software system is validated on the targeted platform or high-fidelity simulation.

1.1 Notes

Typically, a high-fidelity simulation has the exact processor, processor performance, timing, memory size, and interfaces as the flight unit.

1.2 Applicability Across Classes

Class G is labeled with "P (Center)." This means that an approved Center-defined process that meets a non-empty subset of the full requirement can be used to achieve this requirement.





2. Rationale

Validation is a process of evaluating work products to ensure that the right behaviors have been built into the work products. The right behaviors adequately describe what the system is supposed to do and what the system is supposed to do under adverse conditions. They may also describe what the system is not supposed to do.



3. Guidance

The basic validation process is shown below with the steps addressed by this requirement highlighted:

Image Removed


Validation activities are not be confused with verification activities as each has a specific goal. Validation is designed to confirm the right product is being produced while verification is conducted to confirm the product being produced meets the specified requirements correctly.

Validation, as used in this requirement, addresses the following:

  • Confirmation of the correctness, completeness, clarity, and consistency of the requirements with stakeholders.
  • Confirmation that implied or inherent requirements (e.g., system must do X before Y) are correctly implemented.

See SWE-055 for additional information on requirements validation during the concept, design, coding, and initial testing phases of the software development life cycle.

Once the software work products have been integrated into a software system, validation activities are concentrated on systems-level effects, interactions, interfaces, and the overall behavior of the system (i.e., whether the system is providing for and meeting the needs of the customer). This level of validation can be accomplished in either an actual operational environment with the use of the targeted platform, or if this combination is not viable, on a high-fidelity simulator. Recall from the note associated with this requirement that a high-fidelity simulation typically has the exact processor, processor performance, timing, memory size, and interfaces as the flight unit. 

The following scenarios provide additional considerations for selection of the most appropriate validation approach at the systems level:


  • Running the software in an actual operational environment.
  • Using this technique to confirm that implied, derived, and inherent requirements such as "the software will run" are properly fulfilled in the target environment.
  • Using this technique to view a system or subsystem as a collected implementation of the requirements and confirm that the software product fulfills its intended purpose, not just individual requirements, but as a collected set of requirements, addressing needs, expected behavior, and functionality.



See Lessons Learned for other considerations related to simulated environment validation.


  • Validate portability by running appropriate software and system tests on all the required platforms.

Also, consider user-created operational scenarios, when appropriate. They can be a valuable tool in either simulated or operational environments.
Additional guidance related to platform or hi-fidelity simulations may be found in the following related requirements in this Handbook:




Validation Planning




Validation Results


4. Small Projects

The small project does not normally involve highly complex platforms, so it is generally easier and cheaper to validate software systems on the targeted platform. However, the environment for space systems will typically need to be simulated during validation for projects regardless of size. When using simulated platforms, small projects are advised to look for existing tools rather than creating their own.



5. Resources





6. Lessons Learned

 The NASA Lessons Learned database contains the following lessons learned related to simulations: