SE 477: Software and Systems Project Management
Assignment 3, Due: February 8, 2017

Assignment: Planning and scheduling

• Description – Develop a plan and project schedule for a subsystem.
• Motivation – Apply the information covered in class to develop a schedule. Learn to use project management software.
  
• Summary – Using the information provided develop a schedule plan for a subsystem and write a summary report with the appropriate information for management.
  

1. Reading

• Notes: from Lectures 2-5
• MS-Project Notes - compliments of John Musser, Columbia University. (http://www.projectreference.com/)
  

2. Assignment: Planning and scheduling

• Problem Statement: Develop a plan and project schedule for a subsystem. The start date is March 20, 2017.
• Create a WBS with the required phases and activities to complete this project. We provide you with the rough information for the WBS. You will provide the schedule based on the information below.
  
• Assign the Resources to the Tasks making any assumptions you consider appropriate (see Software Engineering Assumptions below).
• Assumptions and Constraints:
  
  1. Assume the project is using the waterfall SDLC and has the following phases: Requirements, High Level Design, Detailed Design, Coding and Unit Test, Integration and Testing, Documentation. All work is done in serial. That is, no tasks are done in parallel.
  2. Part of the development will include formal reviews of each deliverable: requirements, high-level design, low-level design, coding, integration and test, and user documentation.
     
  3. Each artifact or task is performed by one engineer except for reviews and preparation for reviews.
     
  1. Every artifact/task is written/executed by one author.
  1. Coding and design is done by one person for each phase.
  2. Similarly for testing, documentation, etc.
     
  2. Every review or inspection “meeting” task shall be carried out by 5 engineers including the author. Every review or inspection “preparation” task shall be carried out by 4 engineers excluding the author. Each artifact is reviewed by all of the engineers – that is each engineer reviews the entire artifact, no splitting of the work.
     
  1. Typically a review is performed by one engineer from the group performing the task, e.g Design Engineer, one engineer from the previous phase, e.g Requirements, and one or more engineers from the next phase(s). The theory is to have different people review the artifact with different experience and perspectives.
  3. Any “Rework” task will be executed by the author of the original artifact/document/code.
  4. Start each major phase of the project on a new day.  That is: Requirements, High Level Design, Detailed Design, Coding and Unit Test, Integration and Testing, Documentation.
  5. Unit Testing may be done before Code Inspection or after Code Inspection, your call. But you cannot do them both at the same time.
     
  6. Allow for holidays:  Memorial Day,  Independence Day (July 4th),  Labor Day, and Thanksgiving and the day after, Christmas and Christmas Eve, and New Years. Assume an 8 hour day and no overtime.
     
• Since most of you are not familiar with the activities performed by a development team, I have provided a suggested list of tasks for the project; this is essentially the WBS for the project. I have also provided estimated productivities (given below).  You should use the associated data as a guide for the activities and tasks for use in MS Project to create the Project Plan. In fact you should use the whole task list for your WBS.
  
• Note the start date is  March 20, 2017!

3. Deliverables

• There should be a summary report for management. The students need to provide at a minimum the start and completion date, duration, and effort (in staff-hours). 
  
• Show the duration and delivery schedule, given the start date is  March 20, 2017. What is the earliest finish date for this project if it is scheduled to start on 3/20/2017? [See assumptions and constraints above.]
• Show the total staff time (effort) (in person-hours).
• Give enough information that an executive would not need to look at the Project file to get a good idea of the project.
  
• I would like to see duration in hours or  days; 
• Total effort in person-hours; (optionally total cost – see below).
  
• Start date and  estimated delivery date(s)
• Summary schedule by phase: This should include a breakdown of estimates by phase and/or resource (personnel).
• Breakdown (in hours/days) of each resource used.
• I do not require assignment of salaries. But in my solution I used a range from $50 per hour to $30 per hour depending on the job title. It comes out to an average of $35 per hour.
• You will need MS Project or  ProjectLibre to do this assignment. See the class web page for information.
• Submit your MS Project File or ProjectLibre File as well as the summary report.

4. Submission Requirements:

• The submission should have your name, date and assignment title  on the front page. Use headers and footers, and have your name and title on each page.
• The documents may be in Microsoft Word (.doc) format, HTML, or Adobe PDF. Any included figures must be embedded directly within the document, not bundled separately.
• Since COL does not combine files, your submission must be a single file. Hence the MS Project/OpenProject file and your report should be combined into a ZIP file.
• All assignments must be submitted electronically through Course On-Line (COL) and are due at 11:59 pm CT on the due date.

5. Worksheet and WBS

Engineer Category	Initials
Requirement Engineers	R1, R2, R3
Design Engineers	D1, D2, D3, D4
Programmers/Software Engineers	P1, P2, P3, P4, P5
Test Engineers	T1, T2, T3
Documentation Engineers	C1, C2

Since most of you are not familiar with the activities performed by a development team, I have provided a list of tasks for the project. I have also provided estimated productivities (given below).  You should use the associated data as a guide for the activities and tasks for use in MS Project to create the Project Plan and the Network Diagram. In fact you should use the whole task list for your WBS.

Task	Size	Productivity
Requirement
Write requirements	100 Req	2 Req/Hour
Review Requirements
Preparation for review		10 Req/Hour
Review Meeting		20 Req/Hour
Rework	20 defects	2 defects/Hour
High level design
Write HLD	50 pages	1 page/Hour
Review HLD
Preparation for HLD		2 pages/Hour
Review Meeting		5 pages/Hour
Rework	5 defects	1 defects/Hour
Detailed design
Write DD	150 pages	1 page/Hour
Review DD
Preparation for DD		2 pages/Hour
Review Meeting		5 pages/Hour
Rework	35 defects	1 defects/Hour
Coding and unit test
Write Code	3000 SLOC	10 SLOC/Hour
Unit Testing
Perform Unit Tests		50 SLOC/Hour
Fix Found Defects	5 Defects	1 Defect/Day
Test Fixed Defects	5 Defects	1 Defect/Hour
Code Inspection
Preparation for Code Inspection		100 SLOC/Hour
Code Inspection Meeting		150 SLOC/Hour
Rework	60 defects	5 defects/Hour
Integration and Testing
Write test plan (TP)	45 pages	1 page/Hour
Review TP
Preparation for TP		2 pages/Hour
Review TP Meeting		3 pages/Hour
Rework	25 defects	1 defects/Hour
Execute TP (test cases)	70 test cases	10 test cases/day
Fix Found Defects	15 defects	2 defects/day
Test Fixed Defects	15 defects	5 defects/day
Documentation
User Documentation	100 pages	5 page/Hour
Review UD
Preparation for UD		5 pages/Hour
Review UD Meeting		10 pages/Hour
Rework	20 defects	10 defects/Hour