CpSc 461, Software Engineering Techniques
Software Project Milestone Exercise
In this exercise, you will start to map out the milestones for projects. The following are last week's estimates of the effort (in programmer-months) derived from the Function Point estimates for the Library and Pay Phone projects:
Assume that each member of your team will be a programmer on the project, then use each of the estimates above to compute a time frame for the project. Given those estimates, begin creating high-level schedules. Use the following estimates from the NASA Software Engineering Laboratory's Manager's Handbook for Sofware Development:
||Pay phone project
Estimate the project as follows (you will probably want to use a spreadsheet):
||Percent of Time Schedule
||Percent of Effort
You now have a rough schedule for the project, showing how many programmers will be working on the project at each phase, and how long each phase will last. Repeat this process for each estimate.
- Begin by calculating the length of the project given the number of programmers on your team If the size of the estimate is very small, you may wish to use programmer-days instead of programmer-months.
- Use the "Percent of Time Schedule" column to compute time estimates for each phase of the software lifecycle.
- Now that you have the amount of time to spend on each phase, use the "Percent of Effort" column to figure out how many programmer-months to allocate for each phase.
- Combine these last two figures to determine how many programmers should be working on each phase.
- Do you notice anything about the number of programmers allocated to each phase? What does this imply about when work on the various phases should begin? Specifically, what does it imply about the Implementation phase?
- Which estimates are realistic?