Description
Using the data spreadsheet provided below to achieve the following:
1. Feed the information provided in this handout in MS Project to create the Project Plan
and the Network Diagram
2. Create a WBS with the required phases and activities to complete this project
3. Assign the Resources to the Tasks making any assumptions you consider appropriate
(Your assumptions should be based on Software Engineering Assumptions).
4. What is the earliest finish date for this project if it is scheduled to start on 2/22/21?
5. If you are not allowed to use more than 20% of the resources available at any point of
time for this project, what is the earliest finish date for this project if it is scheduled
to start on 2/22/21?
6. Submit your MS Project File and a PDF document with your answers to Question #4 and
Question #5 above.
Resources Available
Important Note: ONLY assign the needed resources to the tasks; for example a
project manager needs one manager of the available managers, however, you could use
more than one requirement engineer to work on writing the requirements.
Category Initials
Project Manager PM2, PM3
Requirement Engineers RE7, RE8, RE9, RE10, RE13, RE14, RE15
System Engineers SE7, SE8, SE9, SE11, SE12, SE13, SE14, SE15, SE16
Programmers/Software
Engineers
PE7, PE8, PE12, PE13, PE22, PE23, PE24, PE25, PE26, PE27,
PE28, PE29
Test Engineers TE7, TE8, TE44, TE45, TE46, TE47, TE48, TE49
Documentation Engineers DE7, DE8, DE13, DE14, DE43, DE44, DE45
Assumptions and Constraints:
1. Every review or inspection “meeting” task shall be carried by 5
engineers including ONE of the author(s)
2. Every review or inspection “preparation” task shall be carried by 4
engineers excluding the author(s)
3. Any “Rework” task can be executed by one or all authors of the
original task
4. Project Plan shall be reviewed by at least ONE engineer from every
technical area.
5. Risk mitigation and contingency plan shall be reviewed by at least
ONE engineer from every technical area.
6. System Engineers are responsible for creating Analysis and Design
artifacts
Task/Activity Dependencies:
It is expected that you will find the correct task dependencies based on the
material discussed during class and considering the following constraints:
1. There is no technical task prior to requirement phase; project
planning is not a technical task it is a managerial task.
2. Analysis Activity can start as soon as requirement document is
complete
3. Design activity can start as soon as Analysis document is complete
4. Data Model task can start when Detailed Design task finishes
5. Coding can start as soon as design is complete
6. Writing Test Plan can start as soon as requirements are complete
7. Executing Test Plan can start as soon as coding is complete
8. Documentation can start as soon as requirements are complete
9. Any other constraints that you might add, shall be documented
clearly when you submit your homework.
10. Risk mitigation and contingency planning can start after project
plan is complete, and can finish any time before analysis starts.
Task Amount of Work Productivity Rate
Project Plan
Write Plan 129 pages 2 pages/Hour
Review Plan
Preparation for review 5 pages/Hour
Review Meeting 6 pages/Hour
Rework 61 defects 10 defects/Hour
Risk Mitigation and Contingency Plan
Write Plan 21 pages 2 pages/Hour
Review Plan
Preparation for review 4 pages/Hour
Review Meeting 8 pages/Hour
Rework 23 defects 4 defects/Hour
Requirement
Write requirements 145 Req 3 Req/Hour
Write Use Case Model 109 Use Cases 1 use case/4 Hours
Review Requirements/ Use Case Model
Preparation for review 25 Req/Hour
5 Use Cases/Hour
Review Meeting 30 Req/Hour
10 Use Cases/Hour
Rework 137 defects 5 defects/Hour
Analysis
Write Analysis Document 119 pages 5 pages/Hour
Review Analysis Document
Preparation for Analysis Document 5 pages/Hour
Review Meeting 10 pages/Hour
Rework 84 defects 7 defects/Hour
Design
Write DD 147 pages 3 pages/Hour
Review DD
Preparation for DD 5 pages/Hour
Review Meeting 8 pages/Hour
Rework 132 defects 5 defects/Hour
Write Data Model (DM) 37 pages 1 page/5 Hours
Review DM
Preparation for DM 3 pages/Hour
Review Meeting 6 pages/Hour
Rework 59 defects 5 defects/Hour
Coding and unit test
Write Code 4177 SLOC 5 SLOC/Hour
Unit Testing
Prepare/Execute Test Cases 243 test cases 8 Test Cases/Day
Fix Found Defects 142 Defects 8 Defects/Day
Test Fixed Defects 142 Defects 4 Defects/Day
Code Inspection
Preparation for Code Inspection 150 SLOC/Hour
Code Inspection Meeting 200 SLOC/Hour
Rework 167 defects 5 defects/Hour
Testing
Write test plan (TP) 163 pages 5 pages/Day
Review TP
Preparation for TP 5 pages/Hour
Review TP Meeting 10 pages/Hour
Rework 215 defects 5 defects/Hour
Execute TP (test cases) 217 test cases 8 test cases/day
Fix Found Defects 136 defects 5 defects/day
Test Fixed Defects 136 defects 10 defects/day
Documentation
User Documentation 273 pages 2 pages/Hour
Review UD
Preparation for UD Review 8 pages/Hour
Review UD Meeting 10 pages/Hour
Rework 319 defects 23 defects/Hour
