Description
Use the data spreadsheet provided below to achieve the following:
1. Assume it has been requested that this project be started on
3/8/21 after the project in Assignment#1 has been started on
2/22/21. This project and the project in Homework#1 will
use/share the same resources listed in Assignment#1.
2. Create a resource pool in MS-Project that will be shared by
Homework#1 and Homework#2
3. Feed the information provided in this handout in MS Project to
create the Project Plan and the Network Diagram
4. Create a WBS with the required phases and activities to
complete this project
5. Assign the Resources to the Tasks making any assumptions you
consider appropriate (Software Engineering Assumptions).
6. What is the earliest finish date for this project if it is scheduled to
start on 3/8/21? (under this scenario, as soon as engineers
complete their tasks on Homework#1 you will assign them to start
working on tasks for Homework#2 project)
7. Is it feasible to complete this project (Assignment#2 project) 2
weeks after the completion date you identified for the project in
Assignment#1? Explain.
8. Submit your MS Project Files
9. Submit your Comments regarding the start and completion
dates and resources assignments for the two projects in a PDF
document called Analysis.pdf.
10. The documents in step 8 and 9 shall be saved in a zipped file
with name “HW#2- YourLastName, FirstName”.
Resources Available
Important Note: Use the same resources listed in Assignment#1; in essence,
Assignment#1 project and Assignment#2 project will share the same
resource pool. ONLY assign the needed resources to the tasks; for example
writing project plan needs one manager of the available managers,
however, you could use all available requirement engineers to work on
writing the requirements.
In addition to resources listed in Assignment #1, following resources have
been added to the resource pool of available headcounts
1. The following project managers are available: PM4, PM5, PM7
2. The following requirement engineers are available: RE28, RE29,
RE32
3. The following system engineers are available: SE30, SE31, SE32, SE35
4. The following programmers/software engineers are available: PE58,
PE59, PE65, PE66
5. The following test engineers are available: TE71, TE72, TE73, TE74
6. The following Documentation engineers are available: DE81, DE82,
DE84, DE85, DE91
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. Data Model can be created only by system engineers and can be
reviewed by any engineer
6. Lab and Environment Setup Tasks can be assigned and executed by
system engineers only.
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. Coding can start as soon as design is complete
5. Writing Test Plan can start as soon as requirements are complete
6. Executing Test Plan can start as soon as coding is complete
7. Documentation can start as soon as requirements are complete
8. Any other constraints that you might add, shall be documented
clearly when you submit your homework.
9. Lab and Environment Setup Tasks must be completed before
Coding tasks or text case execution tasks can be started.
Task Amount of Work Productivity Rate
Project Plan
Write Plan 113 pages 5 pages/Hour
Review Plan
Preparation for review 5 pages/Hour
Review Meeting 10 pages/Hour
Rework 63 defects 4 defects/Hour
Requirement
Write requirements 243 Req 5 Req/Hour
Review Requirements
Preparation for review 5 Req/Hour
Review Meeting 10 Req/Hour
Rework 133 defects 5 defects/Hour
Lab and Environment Setup
Hardware
Install Network Elements
Routers 2 2 Routers/day
Bridge 4 2 Bridges/day
Install Server 8 servers 1 server/day
Install Clients 73 clients 10 clients/day
Software
Install Development Tools 23 tools 4 tools/day
Install Testing Tools 18 tools 4 tools/day
Analysis/Design Document
Write DD 212 pages 2 pages/Hour
Review DD
Preparation for DD 5 pages/Hour
Review Meeting 10 pages/Hour
Rework 312 defects 5 defects/Hour
Data Model
Create Data Model 62 pages 1 page/Hour
Review Data Model
Preparation for DM 5 pages/Hour
Review Meeting 10 pages/Hour
Rework 166 defects 4 defects/Hour
Coding and unit test
Write Code 6323 SLOC 5 SLOC/Hour
Unit Testing
Prepare/Execute Test Cases 923 test cases 3 Test Case/Hour
Fix Found Defects 723 Defects 20 Defects/Day
Test Fixed Defects 723 Defects 45 Defects/Day
Code Inspection
Preparation for Code Inspection 150 SLOC/Hour
Code Inspection Meeting 200 SLOC/Hour
Rework 513 defects 5 defects/Hour
Testing
Write test plan (TP) 313 pages 10 pages/Day
Review TP
Preparation for TP 5 pages/Hour
Review TP Meeting 10 pages/Hour
Rework 213 defects 4 defects/Hour
Execute TP (test cases) 356 test cases 10 test cases/day
Fix Found Defects 118 defects 5 defects/day
Documentation
User Documentation 213 pages 5 page/Hour
Review UD
Preparation for UD review meeting 5 pages/Hour
Review UD Meeting 8 pages/Hour
Rework 266 defects 10 defects/Hour
Training
Training Handouts (TH) 72 pages 1 page/Hour
Review Training Handouts (TH)
Preparation for TH review meeting 8 pages/Hour
Review TH Meeting 10 pages/Hour
Rework 244 defects 10 defects/Hour
