bannera

Book A.
Introduction

Book B.
7150 Requirements Guidance

Book C.
Topics

Tools,
References, & Terms

SPAN
(NASA Only)

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Tabsetup
1. Purpose
1. Purpose
12. Definition
23. The Basic WBS
34. Common Issues
45. Resources1. Purpose
Div
idtabs-1

1. Purpose

Topic 7.5 provides guidance on the development of a work breakdown structure (WBS) for software on projects. The WBS provides a common planning framework to use in estimating the scope of a project.

Div
idtabs-2

2. Definition

Per the NASA Systems Engineering Handbook

sweref
273
273
(Section 6.1.2.1), a work breakdown structure is a hierarchical breakdown of the work necessary to complete a project. The WBS can be product- or process-oriented. A product-oriented WBS has work activities grouped by the product or service they support. A process-oriented WBS includes in the appropriate WBS element the work activities associated with the processes being used.
sweref
389
389
The WBS provides the framework to plan, organize, and control a project.
sweref
388
388

Excellent information on the development and usage of the WBS can be found in NASA/SP-2010-3404, NASA Work Breakdown Structure (WBS) Handbook.

sweref
390
390
Additionally, both the NASA Systems Engineering Handbook
sweref
273
273
and the "CMMI for Development, Guidelines for Process Integration and Product Improvement"
sweref
388
388
provide further guidance on the development of WBS structures containing software. The NASA Software Engineering curriculum, especially
Term
SWE 301
SWE 301
sweref
389
389
, addresses the use of the WBS for software on projects. These resources are cited in the
Tablink
5
1Resources tab of this topic
5
.

Div
idtabs-3

3. The Basic WBS

A project's software may be a stand-alone system or exist as part of a larger system or project. For example, for a space flight project, software may be shown under the Avionics subsystem. For both types, the WBS developer needs to be aware of the responsibilities required of his or her project.

As another example consider the following list-oriented approach to a WBS. Again, the use of NASA/SP-2010-3404, NASA Work Breakdown Structure (WBS) Handbook,

sweref
390
390
will help in the development of the lower levels of the WBS elements.

  1. SW Management (incl budget, schedule, contractor mgmt, risk, CM, training, IV&V coord, lesson learned, etc)
  2. SW Requirements Management
  3. SW Testbed Management
  4. CSCI Development
  5. CSCI Test
  6. CSC Test
  7. Sustaining Engineering
  8. Security (physical and IT)

The project's software may also be developed in the context of a product-driven structure. Lower level development of the WBS will include the approach to software development for the individual component or system to be produced in the sub-element. The following figure suggests several approaches for this type of WBS.

The WBS is updated iteratively over the project life cycle . The initial WBS is used for early estimating of cost and schedule. The detailed WBS helps organize and control the work done by populating the project's cost plans and schedule.

A companion WBS dictionary, which is also developed, fully describes the work being done including the title and objective of the element, expected products/services from each element, and the dependencies between elements.

The Software Development Plan (SWE-102) is a place to record the WBS of the life cycle processes and activities.

Div
idtabs-4

4. Common Issues

There are several work activities that are often forgotten in developing the WBS:

  • Process planning and monitoring activities
  • Requirement engineering activities
  • Formal review activities
  • Development activities
  • Stakeholder activities
  • Training activities
  • Planning, documenting, and tracking of commitments from other organizations
Div
idtabs-5

5. Resources

refstable-topic

5.1 Tools

toolstable-topic