Example of Stan's WBS (with his personal notes) for a "traditional waterfall"

software development:

1. Requirements Definition (Phase 1)

1.1 Requirements
1.02 Define scope
1.3 Analyze existing system
1.3a Document system requirements
1.3b Validate against systems architecture
1.06 Management review / Phase 2 funding

2. Software Design (Phase 2)

2.1 Design the database //NOTE: Dave should take not more than 1 week for
this!
2.2 <The Stored Procedures should be created here>
2.3 Create a Data Abstraction Layer //Note: It will take me a couple of
days to do this. I will do this myself
2.4 Who will write the Functional Specifications document? //NOTE: Should
this be client-reviewed? I must ask the boss.

//NOTE to self: Project Management tasks need not be included in the schedule - as
I am working full time on this project

3. Programming and Unit Testing (Phase 3)

4.01 Decompose to units
4.01.01 Identify coding units //NOTE: This needs to be done by
Architects and development team BOTH
4.01.02 Identify coding unit input and output //NOTE: is this the
same as 4.01.01
4.01.03 Identify reusable units //NOTE: Who knows what units can
be reused?
4.01.04 Eliminate unit redundancies
4.02 Develop coding units
4.a Develop detailed unit logic
4.b Validate unit logic
4.c Code unit
4.d Develop unit test data
4.e Develop Windows DLLs
4.f Unit test coding
4.03 Update test/conversion API
4.03.01 Review test/conversion plans
4.03.02 Update test/conversion plans
4.04 Management review
4.04.01 Plan next phase
4.04.02 Reevaluate development costs
4.04.03 Reevaluate justification
4.04.04 Obtain user requirements consensus
4.04.05 Obtain technical consensus
4.05 //NOTE: this is a clever place-holder for anything I have missed

5 Installation (Phase 5)
5.01 Finalize conversion plan
5.01 Review interim conversion API
5.02 Develop conversion API
5.03 Develop conversion plan
5.04 Assign conversion responsibilities
5.02 Convert files/database
5.03 Install software
5.04 Run systems in parallel
 5.05 Turn off old system
5.06 Management review

Rules for your submission:

1. Understand that this assignment is for you to practice WBS reviews. Limit your
discussion only to the WBS and the data given above.
2. In this assignment, it DOES NOT matter if you don't understand the technical
specifics of the WBS. You should be looking for obvious problem signals.