Page History
...
| Div | ||
|---|---|---|
| ||
1. PurposeTopic 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. |
...
| id | tabs-2 |
|---|
2. Definition
...
| id | tabs-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.
...
- SW Management (incl budget, schedule, contractor mgmt, risk, CM, training, IV&V coord, lesson learned, etc)
- SW Requirements Management
- SW Testbed Management
- CSCI Development
- CSCI Test
- CSC Test
- Sustaining Engineering
- 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 | ||
|---|---|---|
| ||
4. Common IssuesThere are several work activities that are often forgotten in developing the WBS:
|
| Div | ||
|---|---|---|
| ||
5. Resources
5.1 Tools
|
