Book A.

Book B.
7150 Requirements Guidance

Book C.

References, & Terms

(NASA Only)

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Error formatting macro: alias: java.lang.NullPointerException
SWE-073 - Platform or Hi-Fidelity Simulations
Unknown macro: {div3}

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">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.





























Key:    A_SC = Class A Software, Safety Critical | A_NSC = Class A Software, Not Safety Critical | ... | - Applicable | - Not Applicable
X - Applicable with details, read above for more | P(C) - P(Center), follow center requirements or procedures

Unknown macro: {div3}

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.

Validation is performed to assure that the specified software systems fulfill their intended use when placed on the targeted platform in the target environment. The methods used to accomplish validation on the actual target platform or in a high fidelity simulator may include aspects that were applied to previous software work products (requirements, designs, prototypes, etc.). The use of these methods provides continuity of results through the assembling system.  The use of the high fidelity or targeted system allows the software developers to check systems level interfaces, memory performance and constraints, event timing, and other characteristics that can only be evaluated properly in the real system or near-system environment (see [SWE-055]). Validation activities include preparation, performance, analysis of results, and identification of corrective action. Validation at the systems level ensures that the correct product has been built.1

Unknown macro: {div3}

3. Guidance


Unknown macro: {div3}

4. Small Projects


Unknown macro: {div3}

5. Resources

  1. add
  2. add

5.1 Tools


Unknown macro: {div3}

6. Lessons Learned


  • No labels