Company: | Joyes Inc. |
Manager: | Nathan Joyes |
Start: | January 15, 2007 |
Finish: | May 3, 2007 |
Report Date: | March 18, 2007 |
WBS | Name | Start | Finish | Work | Priority | Complete | Cost | Notes |
---|---|---|---|---|---|---|---|---|
1 | Phase I | Jan 15 | Jan 15 | |||||
2 | Define the Application Objectives and Scope | Jan 15 | Jan 16 | 4d | ||||
2.1 | Project Charter | Jan 15 | Jan 16 | 2d | 100% | |||
2.2 | Project Plan | Jan 15 | Jan 16 | 2d | 100% | |||
3 | Detailed System Investigation | Jan 17 | Jan 17 | 1d | ||||
3.1 | Summarize 'Client' Interviews | Jan 17 | Jan 17 | 1d | 100% | Since there is no real client, this task details the creation of a document that fully describes what the 'client' was looking for, as well as other details required to complete the project. | ||
4 | Modeling and Analysis | Jan 18 | Feb 2 | 21d | ||||
4.1 | Use Case Diagram | Jan 18 | Jan 19 | 2d | 100% | |||
4.2 | Use Case Description | Jan 18 | Jan 26 | 7d | 100% | |||
4.3 | Class Diagram | Jan 29 | Jan 30 | 2d | 100% | This is the analysis level class diagram | ||
4.4 | State Chart Diagrams | Jan 29 | Feb 2 | 5d | 100% | |||
4.5 | Sequence Diagrams | Jan 29 | Feb 2 | 5d | 100% | |||
5 | System/Subsystem Design | Feb 5 | Feb 9 | 10d | ||||
5.1 | Package Diagram | Feb 5 | Feb 6 | 2d | 100% | |||
5.2 | Class Diagram | Feb 5 | Feb 7 | 3d | 100% | This is the design level class diagram | ||
5.3 | Network Model | Feb 5 | Feb 9 | 5d | 100% | |||
6 | Database Design | Feb 5 | Feb 9 | 10d | ||||
6.1 | Database ERD | Feb 5 | Feb 9 | 5d | 100% | |||
6.2 | Data Dictionary | Feb 5 | Feb 9 | 5d | 100% | |||
7 | Screen/Report Design | Feb 5 | Feb 9 | 10d | ||||
7.1 | User Interface Layout | Feb 5 | Feb 9 | 5d | 100% | |||
7.2 | Navigation Diagram | Feb 5 | Feb 9 | 5d | 100% | |||
8 | Phase II | Feb 9 | Feb 9 | |||||
9 | Prepare Detailed Design Plan | Feb 12 | Feb 22 | 20d | ||||
9.1 | Project Plan | Feb 12 | Feb 13 | 2d | 100% | Review the project plan now that the project is well underway. | ||
9.2 | Screen Prototypes | Feb 12 | Feb 22 | 9d | 100% | |||
9.3 | Report Design | Feb 12 | Feb 22 | 9d | 100% | |||
10 | Present Project Plan to Faculty Advisor | Feb 23 | Feb 23 | 1d | ||||
10.1 | Formal Presentation | Feb 23 | Feb 23 | 1d | 100% | |||
11 | Present Project Plan to Client | Feb 26 | Feb 26 | 1d | ||||
11.1 | Client Revisions | Feb 26 | Feb 26 | 1d | 100% | Since there is no 'Client' this task is for review of the product to make sure it matches the initial 'Client' interviews. | ||
12 | Phase III | Feb 26 | Feb 26 | |||||
13 | Code Programs and Test | Feb 27 | Apr 5 | 40d | ||||
13.1 | Project Plan | Feb 27 | Feb 28 | 2d | 100% | Again further review of the project plan is necessary at the start of this phase. | ||
13.2 | Unit Test Plans | Feb 27 | Mar 5 | 5d | 100% | |||
13.3 | Module Test Plans | Feb 27 | Mar 5 | 5d | 100% | |||
13.4 | Code Programs | Mar 6 | Mar 30 | 19d | 40% | |||
13.5 | Unit Test Plan Results | Mar 6 | Mar 12 | 5d | 10% | |||
13.6 | Individually Test Modules | Apr 2 | Apr 5 | 4d | 0% | |||
14 | Phase IV | Apr 5 | Apr 5 | |||||
15 | Assemble Modules to Make the System | Apr 6 | Apr 18 | 21d 5h | ||||
15.1 | Integration Tests and Results | Apr 6 | Apr 12 | 5d | 0% | |||
15.2 | Help/Tutorial | Apr 6 | Apr 12 | 4d 5h | 0% | |||
15.3 | Deployment Guides | Apr 12 | Apr 18 | 12d | ||||
15.3.1 | System Administrator | Apr 12 | Apr 18 | 4d | 0% | |||
15.3.2 | User | Apr 12 | Apr 18 | 4d | 0% | |||
15.3.3 | Standalone Installation | Apr 12 | Apr 18 | 4d | 0% | |||
16 | Phase V | Apr 18 | Apr 18 | |||||
17 | Public Demonstration and Marking | Apr 18 | May 3 | 8d | ||||
17.1 | System Documentation | Apr 18 | Apr 24 | 4d | 0% | |||
17.2 | User Manuals | Apr 18 | Apr 19 | 1d | 0% | |||
17.3 | ID Sheet and Installation CD | Apr 18 | Apr 19 | 1d | 0% | |||
17.4 | Final Testing by Advisor | Apr 25 | Apr 25 | 1d | 0% | |||
17.5 | Tech@Work Day | May 3 | May 3 | 1d | 0% |
Name | Short name | Type | Group | Cost |
---|