Considerations. Include software costs in the cost of the equipment. For
example, when a software development facility is created to support the
development of software, the effort associated with this element is considered
part of the CSCI it supports or, if more than one CSCI is involved, the
software effort should be included under integration, assembly, test, and
checkout. Software developed to reside on specific equipment must be
identified as a subset of that equipment.
Integration, assembly, test, and checkout
includes production acceptance testing (including first article test) of
Research and Development (R&D) and production units but excludes all
systems engineering/program management and system test and evaluation that are
associated with the overall system.
The appendices identify integration,
assembly, test, and checkout separately, except for Appendix A, Aircraft
Systems. To be consistent with the historical data sets that are
maintained on airframe, integration, assembly, test, and checkout are
considered a sub-element of the airframe and, therefore, are included in the
airframe WBS element.
This handbook does not identify Level 3
elements for the systems engineering or program management WBS elements.
This allows the program manager and contractor flexibility to identify efforts
that are important to the specific program. Systems engineering and
program management elements can be reported together or separately and their
levels will be specified by the requiring activity. For example, a need may
exist to uniquely track systems engineering from program management therefore
the WBS may require to separate these elements rather than combined as
currently defined. The definitions in Appendix I illustrate typical
systems engineering and program management efforts.
System test and evaluation should always
separately identify those tests performed in the development of a system
(e.g., development test and evaluation), and those tests performed by the
operational user (e.g., operational test and