OEM / private label · Multi-factory sourcing · Export project coordination
sales@moxasourcing.comCall UsChat on WhatsApp

Verification Evidence: Requirements to Test Reports

NASA’s systems-engineering handbook distinguishes verification against specified requirements from validation against the intended use and environment.

Verification Evidence: Requirements to Test Reports: Requirement, Verification method, Recorded evidence, Supported conclusion
Original educational diagram by Moxa Sourcing.
Quick comparison
Evidence or termWhat it means here
AnalysisA supported calculation or model used to evaluate a requirement.
DemonstrationAn observed operation that shows a required capability.
Inspection or testA defined examination or measurement producing evidence for a requirement.

What does the evidence explain?

How are meeting a written requirement and meeting the intended need different?

NASA’s systems-engineering handbook distinguishes verification against specified requirements from validation against the intended use and environment. A product can conform to what was written while the written description fails to capture what the customer needs. Conversely, a promising demonstration of intended use does not close every dimensional, documentary or interface requirement. The two questions should remain visible when turning a sample approval into a production specification.

For a commercial sample file, this distinction can be applied by separating a requirement’s pass/fail evidence from the buyer’s decision that the selected configuration suits the intended project. This is an editorial adaptation of the engineering method, not a claim that an aerospace verification program is required for mugwort products. Clinical efficacy, human-use safety and destination-market authorization need their own applicable evidence and qualified decisions. A general sample-use observation cannot be promoted into any of those conclusions.

Why should design evidence stay separate from acceptance of produced units?

The NASA source distinguishes verification and qualification of a flight-unit design from acceptance activities on individual flight units. It also distinguishes certification as an evidence review by the appropriate certifying authority. These terms belong to the source’s aerospace context. Their useful general lesson is that evidence about a design, evidence about a manufactured item and an authority’s certification are different objects.

In a sourcing file, identify which object a document actually supports. A development test on one configuration does not show that every later lot matches that configuration. A lot inspection does not establish that the design has received a particular certification. NASA’s statements about performing certain design activities once must not be transferred into an exemption from repeated batch controls for a consumer product. The order still needs its own agreed acceptance arrangements, and any certification claim needs the exact issuing body, scope and applicable product evidence.

What must be available before a requirement is checked?

The source identifies four main inputs: the product to be checked, the verification plan, the specified requirements baseline and the enabling products needed to perform the work. Enabling products include fixtures, support equipment and representations of interfacing items. This separates the object being evaluated from the equipment or associated objects needed to evaluate it. The distinction is especially useful when a sample is only one part of an assembled configuration.

For the adapted specification record, identify the product version, the approved requirement set and the procedure version before collecting results. Also identify any fixture or mating component whose presence affects the check. If one of these inputs changes, the earlier result may no longer describe the later configuration. Preparing the file in advance prevents an attractive result from being assigned retrospectively to an unspecified version or to a requirement that was revised after the work.

What is a practical readiness check for verification work?

Verification preparation includes approved step-by-step procedures, appropriate facilities, tools, measuring devices, environmental conditions and available people. NASA describes readiness reviews whose formality is tailored to the project and life-cycle stage. The point is to establish that the planned work can produce meaningful evidence, not merely that a sample has arrived at a laboratory or inspection desk.

Where the task includes an operator or other user, the source also calls attention to how that person is represented: skills, training, physical characteristics, clothing and relevant equipment can affect the activity. For a commercial adaptation, describe the actual role and task instead of assuming any available person represents every intended user. This is not a proposed human-subject test or permission for unreviewed exposure. The approved technical and safety scope determines what work is appropriate; the readiness record states whether the resources for that scope are actually present.

What does verification by analysis contribute?

Analysis uses mathematical models or analytical techniques to evaluate the requirement from calculated information or evidence from lower-level products. NASA distinguishes the model, a mathematical representation, from simulation, which operates on that model. Analysis can be useful before a final product exists, but its result depends on the model, inputs and the relationship between modeled conditions and the requirement.

The resulting record should therefore identify the analysis and assumptions rather than present its output as a directly measured product result. An inherited design or similar product can contribute evidence only through an explained comparison. The word “similar” alone does not establish equivalence. If a supplier supplies a calculation instead of a requested test report, preserve that evidence type and determine whether the agreed requirement permits that method. Calling both files “verified” would conceal an important difference in how the conclusion was obtained.

How does a demonstration differ from a detailed test?

NASA describes demonstration as showing that use of the product achieves an individual specified requirement, generally without the detailed data collection associated with testing. A demonstration may use a physical model or mock-up. Its evidence is therefore connected to what was actually shown and to the article used, rather than to every performance characteristic of a future production version.

For a sample file, a video showing assembly or operation can document a demonstrated action if its identity and conditions are clear. It does not automatically supply a measured duration, force, temperature profile or statistical variability. If the requirement calls for detailed data, the reviewer needs the corresponding test method and results. Keeping demonstration separate from test helps the buyer avoid treating an attractive demonstration as a complete performance report. No particular supplier video or product demonstration is claimed to have met a requirement through this explanation.

Which requirements can visual or documentary inspection address?

Inspection in the NASA method is visual examination of a realized product, and can also include drawings, documents or other records. It is useful for visible design features or identification. The method must match the requirement: observing that an item bears an identifier is different from demonstrating a hidden material property or performance over time.

A photograph or document check should state what was inspected and what the observation supports. Seeing printed wording does not establish that the wording is legally acceptable in a destination market. Seeing a dimension on a drawing does not establish that a production unit was measured to that value. These distinctions keep inspection evidence connected to its actual object. They also help separate a review of the proposed specification from inspection of the product manufactured under it.

What makes a test result more than a general product observation?

Testing obtains detailed data under controlled conditions to verify performance directly or support further analysis. NASA notes that the tested article may be a prototype or another developmental form, as well as a final product. The article’s status therefore belongs with the result. A result from a prototype is not automatically a result from the final manufactured configuration.

The record needs the requirement being tested, controlled conditions, method, article identity and collected data. Instruments and support equipment must be appropriate for the planned procedure. A statement that an item “worked well” does not supply these elements. The source also recognizes testing as resource-intensive, so the verification method should be chosen deliberately rather than applying the same laboratory exercise to every requirement. This does not prescribe a new product test; it identifies the information needed to understand an existing or agreed test result.

How does a verification matrix connect a requirement to its evidence?

NASA’s Appendix D recommends identifying each mandatory requirement uniquely and identifying the document from which it comes. The source uses “shall” to distinguish these requirements. It allows separate matrices for different source documents. The central idea is traceability: a reviewer should be able to locate the requirement being checked rather than infer it from a general test title.

An adapted commercial record can connect the requirement identifier and source version to the chosen method, result reference, outcome and any unresolved discrepancy. Those fields synthesize the matrix principle with the verification-report guidance in section 5.3; they are not a transcription of NASA’s image-only example table. A row marked complete needs supporting evidence for that exact requirement and product version. A blank template describes how work could be recorded; it is not proof that work occurred. The matrix also makes missing evidence visible without converting an unresolved requirement into a passing result.

Why might component evidence be insufficient for an assembled product?

NASA describes verification at component, assembly and higher system levels. Some characteristics must be checked at a low level because they become inaccessible after assembly. Other requirements concern the integrated configuration and cannot be closed merely because each component passed its own separate check. The verification plan allocates the requirement to the level where meaningful evidence can be obtained.

Applied to a commercial specification, distinguish evidence for a component from evidence for the complete configuration in which it is used. Interface compatibility is a separate question from a component’s identity. The source’s end-to-end method emphasizes interactions among items and external interfaces. This does not mean importing spacecraft tests into a sourcing order. It means stating whether a requirement concerns an individual item, the assembled combination or a complete use sequence, then choosing evidence that actually covers that level.

Does an unexpected verification result always mean the product is defective?

An unexpected result can arise from the product or from the verification procedure, equipment, conduct or conditions. NASA calls for stopping the affected verification activity when a discrepancy appears, documenting it and analyzing the events leading to it. The first task is to determine what the discrepancy represents. Repeating the work without preserving the original result can destroy the evidence needed to answer that question.

The adapted record should distinguish an actual product nonconformance from a problem in how the check was performed. If the procedure or environment was wrong, record the correction and the basis for repeating the activity. If the product does not meet its requirement, record the affected configuration and its disposition. A successful repeat after correcting the measuring setup is different from a successful repeat after modifying the product. Both may be legitimate, but they should not be merged into a single unexplained “pass” that hides what changed.

Why review the data before dismantling the verification setup?

NASA recommends analyzing the collected results for integrity, correctness, consistency and validity, if possible while the test or analysis configuration is still intact. The practical reason is that a missing measurement or a procedural correction may require another run. Once the configuration has been dismantled, reconstructing the relevant conditions can become more difficult.

This review is more specific than checking whether a report file opens. It asks whether the required results were actually collected and whether anomalies have been resolved or reported. For the adapted sample record, keep the original data, setup identity and review decision connected. If a later correction changes the interpretation, the revised report should retain the explanation. The aim is a defensible connection between the evidence and requirement, rather than a polished report that no longer allows the original activity to be understood.

Which versions belong in a verification report?

The source explicitly calls for the versions of the specified requirements, the product verified, and the tools, data and equipment standards used. It also retains the results for each verification, pass/fail declarations and discrepancies. These fields make the report reproducible as a record of a particular activity. They prevent a result for an earlier product or requirement from being silently reassigned to a later version.

The report also captures decisions, assumptions, rationale and corrective actions. A requirement reference should lead to its evidence, and the evidence should identify the requirement it supports. This two-way connection is useful when one result addresses several requirements or one requirement needs several methods. If a file is renamed for a new order, its contents do not thereby become evidence for that order’s actual configuration. The product and requirement versions, not the filename alone, define the result’s scope.

When does a corrected product need renewed verification?

The handbook recognizes that resolving nonconformance can require redesign, a changed product, a corrected procedure or a changed environment. Where mitigation changes the product, verification may need to be planned and performed again. Where the problem was not in the product, the appropriate facility, procedure or supporting equipment correction and renewed verification are recorded instead. These paths preserve the reason the original activity did not close the requirement.

NASA’s stated completion criteria include documented objective evidence of meeting the requirements or an authorized waiver, together with closure of discrepancy and nonconformance reports. In a commercial adaptation, an exception must have the authority and scope agreed for the order; a reviewer cannot erase an unmet safety or legal requirement by renaming it a waiver. A report marked finished is an administrative state. Closure of the requirement still depends on the relevant evidence and a recorded, authorized decision.

FAQ

How are meeting a written requirement and meeting the intended need different?

NASA’s systems-engineering handbook distinguishes verification against specified requirements from validation against the intended use and environment. A product can conform to what was written while the written description fails to capture what the customer needs. Conversely, a promising demonstration of intended use does not close every dimensional, documentary or interface requirement. The two questions should remain visible when turning a sample approval into a production specification.

When does a corrected product need renewed verification?

The handbook recognizes that resolving nonconformance can require redesign, a changed product, a corrected procedure or a changed environment. Where mitigation changes the product, verification may need to be planned and performed again. Where the problem was not in the product, the appropriate facility, procedure or supporting equipment correction and renewed verification are recorded instead. These paths preserve the reason the original activity did not close the requirement.

Sources and scope

Sources: NASA Systems Engineering Handbook section 5.3 and Appendix D, edited as general requirement-and-evidence methods for a commercial specification. Aerospace design and certification rules are context, not obligations or approvals for mugwort products. No NASA endorsement, current test, regulatory clearance or completed customer project is claimed. Source figures and the image-only matrix table are not reproduced. NASA product verification NASA requirements verification matrix

Chat on WhatsApp+852 5725 4301