Test Equipment Black Box

This is an example traceability project for a piece of test equipment. It includes customer/user requirements and interface definitions, developed system requirements and a system interface control document, high-level design documentation, test objectives with associated test cases, and decomposed requirement specifications for PCB, software, and firmware items.

To create a project based on this template: select Projects => Create New Project => tick Based on Template, select "Test Equipment Black Box", select a location and project name, then click Create.

User Requirements Document

This document captures the customer / user needs.

User Interface Control Document

This document defines the customer-facing and user-facing interfaces, although in practice interface information can be incomplete, poorly defined, or buried in hard-to-obtain source documents provided by the customer.

System Requirements Document

This document states what the system is intended to do and primarily satisfies the user requirements, while also taking account of prior programme experience, future capability aspirations, and applicable business constraints or objectives.

System Interface Control Document

This is the external ICD for the system and can be shared with customers to define interface behaviour and boundaries without disclosing excessive intellectual property or detailed implementation design.

High Level Design Document

This document describes the top-level architecture, subsystem responsibilities, and key design decisions used to satisfy the system requirements and interface constraints.

FPGA1 Requirement Specification

This document decomposes relevant system behaviour into FPGA-specific requirements, including logic processing, timing, state control, and interface handling allocated to the programmable logic implementation.

PCB Requirement Specification

This document defines the hardware board-level requirements such as electrical interfaces, power constraints, physical connectivity, and environmental considerations allocated to the PCB design.

uProc1 Requirement Specification

This document captures processor/software-facing requirements allocated to the microprocessor subsystem, including control functions, data handling, sequencing, and diagnostic behaviour.

Internal Interface Control Document

This document defines internal subsystem-to-subsystem interfaces and apportions the external interfaces to individual subsystem boundaries, while treating the external ICD as the single source of truth for detailed interface definitions.

Test Objectives

This document defines what should be demonstrated for each requirement, setting out the intended verification intent, coverage goals, and pass criteria at an objective level.

Test Case 1 (Discretes)

This test case document details how selected discrete-signal objectives are verified, including setup, stimulus, expected results, and evidence capture steps.

Test Case 2 (Data Busses)

This test case document details how bus/data-interface objectives are verified, including data patterns, transaction sequencing, expected protocol behaviour, and acceptance evidence.