Assignment #1 Solution

Using the data spreadsheet provided below to achieve the following:




 
Feed the information provided in this handout in MS Project to create the Project Plan and the Network Diagram




 
Create a WBS with the required phases and activities to complete this project




 
Assign the Resources to the Tasks making any assumptions you consider appropriate (Your assumptions should be based on Software Engineering Assumptions).




 
What is the earliest finish date for this project if it is scheduled to start on 2/12/18?




 
If you are not allowed to use more than 25% 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/12/18?




 
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






System Engineers


SE7, SE8, SE9, SE11, SE12, SE13, SE14






Programmers/Software


PE7, PE8, PE22, PE23, PE24, PE25, PE26, PE27, PE28, PE29
Engineers










Test Engineers


TE7, TE8, TE44, TE45, TE46, TE47, TE48, TE49






Documentation Engineers


DE7, DE8, DE43, DE44, DE45






Assumptions and Constraints:




 
Every review or inspection “meeting” task shall be carried by 5 engineers including ONE of the author(s)

 
Every review or inspection “preparation” task shall be carried by 4 engineers excluding the author(s)

 
Any “Rework” task can be executed by one or all authors of the original task

 
Project Plan shall be reviewed by at least ONE engineer from every technical area.

 
Risk mitigation and contingency plan shall be reviewed by at least ONE engineer from every technical area.

 
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:

 
There is no technical task prior to requirement phase; project planning is not a technical task it is a managerial task.




 
Analysis Activity can start as soon as requirement document is complete

 
Design activity can start as soon as Analysis document is complete




 
Data Model task can start when Detailed Design task finishes




 
Coding can start as soon as design is complete




 
Writing Test Plan can start as soon as requirements are complete




 
Executing Test Plan can start as soon as coding is complete




 
Documentation can start as soon as requirements are complete




 
Any other constraints that you might add, shall be documented clearly when you submit your homework.

 
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


90 pages
2 pages/Hour
Review Plan






Preparation for review




5 pages/Hour
Review Meeting




6 pages/Hour
Rework


57 defects
10 defects/Hour








Risk Mitigation and Contingency Plan






Write Plan


17 pages
2 pages/Hour
Review Plan






Preparation for review




4 pages/Hour
Review Meeting




8 pages/Hour
Rework


13 defects
4 defects/Hour








Requirement






Write requirements


134 Req
3 Req/Hour
Write Use Case Model


65 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


59 pages
3 pages/Hour
Review DD






Preparation for DD




5 pages/Hour
Review Meeting




8 pages/Hour
Rework


63 defects
5 defects/Hour
Write Data Model (DM)


25 pages
1 page/5 Hours
Review DM






Preparation for DM




3 pages/Hour
Review Meeting




6 pages/Hour
Rework


34 defects
5 defects/Hour



Coding and unit test




Write Code


3156 SLOC
5 SLOC/Hour
Unit Testing






Prepare/Execute Test Cases


189 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)


127 pages
5 pages/Day
Review TP






Preparation for TP




5 pages/Hour
Review TP Meeting




10 pages/Hour
Rework


99 defects
5 defects/Hour
Execute TP (test cases)


217 test cases
10 test cases/day
Fix Found Defects


119 defects
5 defects/day
Test Fixed Defects


119 defects
10 defects/day








Documentation






User Documentation


161 pages
3 pages/Hour
Review UD






Preparation for UD Review




8 pages/Hour
Review UD Meeting




10 pages/Hour
Rework


268 defects
15 defects/Hour