STD

This section shall be divided into the following paragraphs.

Converted from STD.html heading.

This paragraph shall contain a full identification of the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).

Converted from STD.html heading.

This paragraph shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and support agencies; identify current and planned operating sites; and list other relevant documents.

Converted from STD.html heading.

This paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.

Converted from STD.html heading.

This section shall list the number, title, revision, and date of all documents referenced in this document. This section shall also identify the source for all documents not available through normal Government stocking activities.

Converted from STD.html heading.

This section shall be divided into the following paragraphs. Safety precautions, marked by WARNING or CAUTION, and security and privacy considerations shall be included as applicable.

Converted from STD.html heading.

This paragraph shall identify a test by projectunique identifier, shall provide a brief description, and shall be divided into the following subparagraphs. When the information required duplicates information previously specified for another test, that information may be referenced rather than repeated.

Converted from STD.html heading.

This paragraph shall describe the procedures necessary to prepare the hardware for the test. Reference may be made to published operating manuals for these procedures. The following shall be provided, as applicable:The specific hardware to be used, identified by name and, if applicable, numberAny switch settings and cabling necessary to connect the hardwareOne or more diagrams to show hardware, interconnecting control, and data pathsStepbystep instructions for placing the hardware in a state ...

Converted from STD.html heading.

This paragraph shall describe the procedures necessary to prepare the item(s) under test and any related software, including data, for the test. Reference may be made to published software manuals for these procedures. The following information shall be provided, as applicable:The specific software to be used in the testThe storage medium of the item(s) under test (e.g., magnetic tape, diskette)The storage medium of any related software (e.g., simulators, test drivers, databases)Instructions ...

Converted from STD.html heading.

This paragraph shall describe any other pretest personnel actions, preparations, or procedures necessary to perform the test.

Converted from STD.html heading.

This section shall be divided into the following paragraphs. Safety precautions, marked by WARNING or CAUTION, and security and privacy considerations shall be included as applicable.

Converted from STD.html heading.

This paragraph shall identify a test by project unique identifier and shall be divided into the following subparagraphs. When the required information duplicates information previously provided, that information may be referenced rather than repeated.

Converted from STD.html heading.

This paragraph shall identify a test case by project unique identifier, state its purpose, and provide a brief description. The following subparagraphs shall provide a detailed description of the test case.

Converted from STD.html heading.

This paragraph shall identify the CSCI or system requirements addressed by the test case. (Alternatively, this information may be provided in 5.a.)

Converted from STD.html heading.

This paragraph shall identify any prerequisite conditions that must be established prior to performing the test case. The following considerations shall be discussed, as applicable:Hardware and software configurationFlags, initial breakpoints, pointers, control parameters, or initial data to be set/reset prior to test commencementPreset hardware conditions or electrical states necessary to run the test caseInitial conditions to be used in making timing measurementsConditioning of the simulate...

Converted from STD.html heading.

This paragraph shall describe the test inputs necessary for the test case. The following shall be provided, as applicable:Name, purpose, and description (e.g., range of values, accuracy) of each test inputSource of the test input and the method to be used for selecting the test inputWhether the test input is real or simulatedTime or event sequence of test inputThe manner in which the input data will be controlled to:Test the item(s) with a minimum/reasonable number of data types and valuesExe...

Converted from STD.html heading.

This paragraph shall identify all expected test results for the test case. Both intermediate and final test results shall be provided, as applicable.

Converted from STD.html heading.

This paragraph shall identify the criteria to be used for evaluating the intermediate and final results of the test case. For each test result, the following information shall be provided, as applicable:The range or accuracy over which an output can vary and still be acceptableMinimum number of combinations or alternatives of input and output conditions that constitute an acceptable test resultMaximum/minimum allowable test duration, in terms of time or number of eventsMaximum number of inter...

Converted from STD.html heading.

This paragraph shall define the test procedure for the test case. The test procedure shall be defined as a series of individually numbered steps listed sequentially in the order in which the steps are to be performed. For convenience in document maintenance, the test procedures may be included as an appendix and referenced in this paragraph. The appropriate level of detail in each test procedure depends on the type of software being tested. For some software, each keystroke may be a separate ...

Converted from STD.html heading.

This paragraph shall identify any assumptions made and constraints or limitations imposed in the description of the test case due to system or test conditions, such as limitations on timing, interfaces, equipment, personnel, and database/data files. If waivers or exceptions to specified limits and parameters are approved, they shall be identified and this paragraph shall address their effects and impacts upon the test case.

Converted from STD.html heading.

This paragraph shall contain:Traceability from each test case in this STD to the system or CSCI requirements it addresses. If a test case addresses multiple requirements, traceability from each set of test procedure steps to the requirement(s) addressed. (Alternatively, this traceability may be provided in 4.x.y.1.)Traceability from each system or CSCI requirement covered by this STD to the test case(s) that address it. For CSCI testing, traceability from each CSCI requirement in the CSCI's S...

Converted from STD.html heading.

This section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand this document.

Converted from STD.html heading.

Appendixes may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes may be bound as separate documents for ease in handling. Appendixes shall be lettered alphabetically (A, B, etc.).

Converted from STD.html heading.