Skip all navigation and jump to content Jump to site navigation Jump to section navigation.
NASA Logo + Visit NASA.gov
Assurance Process for Complex Electronics
Home Complex Electronics Background Complex Electronics Assurance Process TECHNIQUES CHECKLISTS Site Map
Life Cycle
PLANNING
V&V
REQUIREMENTS
PRELIMINARY DESIGN
DETAILED DESIGN
IMPLEMENTATION
testing
operationsoperations
SUPPORTING PROCESSES
PRINT THIS SECTION

Testing Phase

This Overview page for the Testing Phase contains the following sections:

Overview

While simulation is used extensively in complex electronic design, testing the actual chip can sometimes be an eye-opening experience. Simulation involves assumptions and compromises that may not match with the real world. Testing the programmed chip - either independently or integrated onto a circuit board - is a necessary step in verifying the design.

In-circuit verification tests the functionality and timing of the design on the actual chip. Ideally, special test software running on a host computer will interface with the device under test through available test ports, such as the JTAG port. This process is similar to in-circuit emulators that run embedded software on the target processor, and provide breakpoints and tracing into the actual software instructions.

The more common form of in-circuit tests is to manually run the complex electronics as part of a higher-level assembly to show that it meets all the specified requirements. This sub-system or system level test will show functionality at a black-box level, but will not provide a window into the internal functioning of the device.

If the complex electronic device is safety-critical, there will be a separate safety verification, usually at the system level.

Testing Process

The diagram below shows the implementation process for complex electronics. The Testing for Developers page describes the engineering process to create the design. The Assurance Process page describes the activities to assess and verify the design.

Entrance Criteria:

The following criteria should be met prior to beginning the testing process.

  • The complex electronic device is programmed or manufactured.
  • Test procedures are written, approved, and configuration controlled.
  • The design (at all levels) is configuration controlled.
  • Design documentation is of adequate quality and quantity to allow the test procedures to be reviewed.

Exit Criteria:

At the end of the testing phase, the following criteria should be met:

  • All requirements for the complex electronics are verified.

Roles and Responsibilities

The table below describes typical activities during the Testing Phase for both engineers and assurance personnel.

Testing Phase

Role

Typical Activities

Systems Engineer

Define system level tests. Ensure that all system requirements are verified.

Electronics Designer

Define board level tests. Ensure board functions properly in all anticipated nominal and fault conditions.

CE specialist (optional)

Define chip level tests. Ensure device functions properly in all anticipated nominal and fault conditions.

System Safety

Review and approve safety verifications. Witness safety tests. Assess changes for safety impacts.

CE/Quality Assurance

Review and approve device (and higher) test procedures. Witness some or all of the tests. Ensure problems are identified, reported, and properly fixed. Assess design changes for impacts.

Testing Site Map

The table below describes the information contained on the other pages in the Testing section.

Testing Site Map

Overview This page

Test Process for Developers

The process of testing complex electronics.

Assurance Process

Describes the assurance process for complex electronics testing.


FirstGov logo + NASA Privacy, Security, Notices NASA Curator: Richard Plastow
NASA Official: Cynthia Calhoun
Last Updated: 01/28/2008