Non-developmental software (NDS). Deliverable software
that is not developed under the contract but is provided by the contractor,
the Government, or a third party. NDS may be referred to as reusable software,
Government furnished software, or commercially available software, depending
on its source.
Product Baseline. See DOD-STD-480.
Release. A configuration management action whereby a
particular version of software is made available for a specific purpose (e.g.
released for test).
Reusable software. Software developed in response to the
requirements for one application that can be used, in whole or in part, to
satisfy the requirements of another application.
Software development file (SDF). A repository for a
collection of material pertinent to the development or support of software.
Contents typically include (either directly or by reference) design
considerations and constraints, design documentation and data, schedule and
status information, test requirements, test cases, test procedures, and test
Software development library (SDL). A controlled
collection of software, documentation, and associated tools and procedures
used to facilitate the orderly development and subsequent support of software.
The SDL includes the Developmental Configuration as part of its contents. A
software development library provides storage of and controlled access to
software and documentation in human-readable form, machine-readable form, or
both. The library may also contain management data pertinent to the software
Software engineering environment. The set of automated
tools, firmware devices, and hardware necessary to perform the software
engineering effort. The automated tools may include but are not limited to
compilers, assemblers, linkers, loaders, operating system, debuggers,
simulators, emulators, test tools, documentation tools, and data base
Software support. The sum of all activities that take
place to ensure that implemented and fielded software continues to fully
support the operational mission of the software.
Software test environment. A set of automated tools,
firmware devices, and hardware necessary to test software. The automated tools
may include but are not limited to test tools such as simulation software,
code analyzers, etc. and may also include those tools used in the software
System Specification. A system level requirements
specification. A system specification may be a System/Segment Specification
(SSS), Prime Item Development Specification (PIDS), or Critical Item
Development Specification (CIDS).
Validation. The process of evaluating software to
determine compliance with specified requirements.
Verification. The process of evaluating the products of a
given software development activity to determine correctness and consistency
with respect to the products and standards provided as input to that
Version. An identified and documented body of software.
Modifications to a version of software (resulting in a new version) require
configuration management actions by either the contractor, the contracting
agency, or both.
Definitions of acronyms used in this standard. See Appendix