18.104.22.168 Software Operating on Specific Equipment.
Multi-function software will be identified as a subset of the equipment WBS
element, which either includes the software in the element specification or
exercises the most critical performance constraint. In cases where a
conflict exists between selecting either the element specification or that
which exercises the most critical performance constraint, selecting the
specification relationship will take precedence. For example, an
aircraft's electronic equipment typically has software included in each of
the subsystem elements. Software that resides and interfaces with more
than one piece of equipment (i.e., applications software, and overall system
software which facilitates the O&M of the computer systems and
associated programs) will be called out at the appropriate work breakdown
For example, elements of software development often are high technical
risk and high cost. Since all critical system software should be
identified, it may be appropriate to collect lower level information. In
such cases, the following structure and definitions could be used:
|Build 1...n (Specify names)
||CSCI 1...n (Specify names)|
||CSCI to CSCI Integration and|
|Integration, Assembly, Test and
All integral software should be summarized in a Program or Contract WBS
in conjunction with the hardware it supports. This allows for
effective performance measurement and management control. When needed, a
contractor's management systems can use an identifier for each software
element to produce summaries for software management purposes.
22.214.171.124 Separately Contracted or Stand-Alone Software.
Separately contracted or stand-alone software will include the data,
services, and facilities required to develop and produce that software
product. Where software is considered stand alone, the Government should use
the same product-oriented WBS format. Figure 3-6 provides an example
of a WBS for a standalone software system.