You are on page 1of 8

J-STD-019-1995

Page 140

Contents

1. scop

1 .1 Identification

2. Referenced documents

3. Test preparations

3.x (project-unique identifier of a test)

3.x. 1 Hardware preparation

3.x.2 Software preparation

3.x.3 Other pretest preparations

4. Test descriptions

.x. y -2 Prerequisite conditions

ected test results


are Test Description (ST

1.1 Identification. This subciause s II contain a full identifi


software t o which this document applie including, as applicabl

alntenance; ~dentrfythe project sponsor, a


rganizations; identify current and planne
ocuments.

3 Document overview. This subclause s


is document and shall describe any security
its use.

2. Referenced documents. This clause shall list the number, title, revision,
of all documents referenced in this manual.
are Test Descripti

. Instructions for
J-STD-016-1995
Page 14

I are Test Descri tion (STD) -- (conrin

anner in which the input


1) Test the itemk) ith a minimum/reasonabie nu
2) Exercise the itemis) with a range of valid data t y
overload, saturation, and other "worst case" effe
3) Exercise the item(s) with invali
handling of irregular

Exoected test results. This subclause s


t h intermediate and final re

xy.5 Criteria for evaluatina results. This subclause shall identify t


ting the interrnediat I results of the test case. For e
information shall be

( a. The range or accuracy over which an output can vary an


Minimum number of combinations or alternatives of input utput conditions that
constitute an acceptable test result
ase addresses multiple
epk) address which re
J-STD-O 16- 19!?3
Page 14

Software Test Descripuon ( S 7 3 ) - (continued)

- Traceability from each system or software item requirement covered by this STD to
the test case(s) that address it. For software item testing, traceability from each
software item requirement in the software item's Sohware Requrrements
Specification (SRS) and associated Interface Requirements Specificarions (IRSs). For
system testing, traceability from each system requirement in the system's
System/Subsystem Specification (SSS) and associated IRSs. If a test case addresses
multiple requirements, the traceability shall indicate the particular test procedure
steps that address each require

6. Notes. This clause shall contain any general information that aids in understanding this
document (e-g., background information, glossary, rationaie). This clause shall inclu
alphabetical listing of all acronyms, abbreviations, and their meanings a s used in this
document and a list of any terms and definitions needed t o understand this document.

A. Annexes. Annexes may be used to provide information published separately for


zonvenlence in document maintenance (e.g., charts, classified data). As applicable, each
innex shall be referenced in the main body of the document where the data would normally
lave been provided. Annexes may be bound as separate documents for ease in handling.
4nnexes shall be lettered alphabetically (A, B, etc.).

You might also like