3.20 Evaluation. The process of determining whether an item or activity meets
3.21 Firmware. The combination of a hardware device and computer instructions
and/or computer data that reside as read-only software on the hardware
3.22 Hardware Configuration Item (HWCI). An aggregation of hardware that
satisfies an end use function and is designated for separate configuration
management by the acquirer.
3.23 Independent verification and validation (IV&V). Systematic
evaluation of software products and activities by an agency that is not
responsible for developing the product or performing the activity being
evaluated. IV&V is not within the scope of this standard.
3.24 Interface. In software development, a relationship among two or more
entities (such as CSCI-CSCI, CSCI-HWCI, CSCI-user, or software unit-software
unit) in which the entities share, provide, or exchange data. An interface is
not a CSCI, software unit, or other system component; it is a relationship among
3.25 Joint review. A process or meeting involving representatives of both the
acquirer and the developer, during which project status, software products,
and/or project issues are examined and discussed.
3.26 Non-deliverable software product. A software product that is not
required by the contract to be delivered to the acquirer or other designated
3.27 Process. An organized set of activities performed for a given purpose;
for example, the software development process.
3.28 Qualification testing. Testing performed to demonstrate to the acquirer
that a CSCI or a system meets its specified requirements.
3.29 Reengineering. The process of examining and altering an existing system
to reconstitute it in a new form. May include reverse engineering (analyzing a
system and producing a representation at a higher level of abstraction, such as
design from code), restructuring (transforming a system from one representation
to another at the same level of abstraction), redocumentation (analyzing a
system and producing user or support documentation), forward engineering (using
software products derived from an existing system, together with new
requirements, to produce a new system), retargeting (transforming a system to
install it on a different target system), and translation (transforming source
code from one language to another or from one version of a language to
3.30 Requirement. (1) A characteristic that a system or CSCI must possess in
order to be acceptable to the acquirer. (2) A mandatory statement in this
standard or another portion of the contract.
3.31 Reusable software product. A software product developed for one use but
having other uses, or one developed specifically to be usable on multiple
projects or in multiple roles on one project. Examples include, but are not
limited to, commercial off-the-shelf software products, acquirer-furnished
software products, software products in reuse libraries, and pre-existing
developer software products. Each use may include all or part of the software
product and may involve its modification. This term can be applied to any
software product (for example, requirements, architectures, etc.), not just to