WORK BREAKDOWN CHART    

Note: Some of these are group activities and some are individual activities. Determining which is which is an important management activity.
Note: This list contains product related activities only.  There are many process related activites (e.g. customize project plan, write training plan, complete status reports) that are not listed, but need to be planned for.
Note: The number in parenthesis before each item is a WAG of total team man-hours required.

  1. (4) Study Project Description from customer.
  2. (1) Interview sponsor about requirements.
  3. (1) Select/Agree CASE tool for team.  (EasyCASE or ASCENTor ?)
  4. (15) Learn to use team CASE tool.
  5. (1) Perform UI Task Analysis.
  6. (2) Develop UI semantics (general tasks and sequencing).
  7. (1) Choose interaction style and physical devices.
  8. (5) Design draft screen layouts and user interaction syntax.
  9. (10) Construct Prototype according to class guidelines.
  10. (1) Assess prototype
  11. (2) Revise prototype
  12. (1) External evaluation of prototype (Demo with Customer).
  13. (4) Revise prototype using customer feedback
  14. (15) Continue refining prototype obtaining customer feedback until satisfied.
  15. (1) Class Demo of user interface prototype.
  16. (1) Create the Context Diagram
  17. (2) Write Preliminary DFD. Make a copy for each team member.
  18. (2) Write Data Dictionary   
  19. (2) Write Data Model
  20. (15) Write Levelled DFD (include assumptions and questions for sponsor).   
  21. (15) Write draft of Mini-Specs  (aka Activity Specifications)
  22. (5) Write Event Model (State Transition Diagram)
  23. (1) Assess Levelled DFD and Mini-Specs
  24. (1) Meet with sponsor to answer analysis questions.
  25. (10) Revise Levelled DFD  
  26. (5) Revise Mini-specs
  27. (5) Write SRS Intro and Non-functional requirements
  28. (1) Assess and Revise Intro and Non-functional requirements.
  29. (2) Write Engineering Analysis.
  30. (5) Assemble SRS Document using class document format.
  31. (5) Assess SRS using QA criteria and refine.
  32. (1) Schedule Formal Technical Review. (QA)
  33. (1) Distribute SRS to Reviewers. (QA)
  34. (1) FORMAL TECHNICAL REVIEW: SRS
  35. (10) Participate as reviewers for another team.
  36. (10) Revise SRS according to Review Issues 
  37. (1) Write review summary report. (QA)
  38. (1) Obtain Customer sign off on SRS (and user interface prototype). (QA)
  39. (1) Determine Feasibility Prototype requirements (negotiate with instructor).
  40. (25) Build Feasibility Prototype.
  41. (1) Demo Feasibility Prototype to management
  42. (1) Obtain management signoff on Feasibility Prototype.
  43. (15) Transform DFD into rough cut structure chart
  44. (1) Assess rough cut structure chart
  45. (15) Revise structure chart to include control modules, etc.
  46. (1) Evaluate the structure chart according to design guidelines
  47. (15) Revise structure chart adding module parameters.
  48. (5) Package low level modules into classes as appropriate.
  49. (1) Divide structure chart, assign modules to team members.
  50. (15) Write Module Headers (or Class Skeletons) for each module in structure chart as javadoc comments.
  51. (1) Update Data Dictionary with any new items from Design.
  52. (2) Write Design Overview.
  53. (5) Assemble High Level Design Document.
  54. (2) Evaluate Design using QA criteria and refine.
  55. (2) Assess design for consistency with DFD and Data Dictionary.
  56. (1) Schedule Formal Technical Review.
  57. (1) Distribute Design to Reviewers. (QA)
  58. (1) FORMAL TECHNICAL REVIEW: High Level Design
  59. (5) Revise High Level Design according to Review Issues
  60. (1) Write review summary report (QA)
  61. (1) Revise Data Dictionary with actual source code names 
  62. (5) Code and Compile (do not execute) Module Headers (and class skeletons) source code with empty method bodies.  (Record defect data for SQA metrics)
  63. (20) Write preliminary Detailed Design, selecting or constructing the best algorithm for each module. 
  64. (15) Write algorithms as pseudocode in method bodies.
  65. (5) Evaluate Detailed Design using Design Walkthrough.
  66. (5) Revise Detailed Design according to Walkthrough Issues
  67. (2) Write Staged Delivery Plan. Negotiate stages and schedule with instructor.
  68. (5) Implement Stage 1 (negotiate with instructor).  (Record LOC and defect data for QA metrics).
  69. (1) Demo Stage 1 to customer.
  70. (10) Assemble all project deliverables and reports according to Project Submission Guidelines

Total team hours: 346

Document History

Date Author Changes
1/3/04 JD Initial Release