Fall 2012 Class

1. Fall 2012 Class Pretty large spread: • 589 pd (580 x 6hr/pd = 3480 person hours) • 800 person hours • 129 person hours • 28 pd (28 x 6 = 168 person hours) • 46 pd (46 x 6 = 276 person hours0 • 4 to 6 pm ( 4 x 20days/m x 6hr/day = 480 person hours to 720 ph) • 265 pd (265 x 6 = 1590 person hours) • 63.5 pd (63.5 x 6 = 381 person hours) • 1000 person hours • 17.3 pm (17.3 x 20 x 6 = 2076 person hours) 16 times difference ! Which estimate would you go with? ---- look at the explanation & details!

2. Discussion on Project Assignment (Using WBS Approach) • After reading and studying the assignment’s “project description”: • Decide on how much of the description will be included (all 6 major features or just some of them) • decide on what deliverables will provided (e.g. requirements doc, design doc, source code, web-site, test cases, etc.) • Based on the deliverables and content of deliverables, 1) lay out the task sequenceof completing the deliverables, 2) estimate (assume) the size of each of the deliverables, 3) estimate (assume) the productivity of people assigned to produce the deliverables, and 4) compute the estimated effort (or cost) in “person hours” for each deliverable. • Use the above task sequence and effort estimate of each deliverable and lay out the rough schedule.

3. Discussion on Project Assignment (Using COCOMO I approach – only partially good) • After reading and studying the assignment’s “project description”: • Decide on how much of the description will be included (all 6 major features or just some of them) • decide on what deliverables will provided (e.g. requirements doc, design doc, source code, web-site, test cases, etc.) • Estimate the sizeof the source code (based on the features considerations) that will be delivered - - - in KLOC • Decide (assume) the modeof project after considering the 8 key characteristics • Consider the 15 adjustment factors and compute the product. • Use the provided “formula” and compute the estimated “effort” (cost) in person-month • If the deliverables included requirements, then add 8% more to the “effort estimate” • Rough Schedule ---- Lay out the task sequence of completing the deliverables: • 8% of effort goes to requirements • Problem with laying out the other tasks! (all “guess” from previous experiences); can only get an over-all elapsed time estimate --- but not laying out a task schedule • Use prev. exper. if you have: e.g. (req/des/code/test/integration ≡20%/15%/35%/25%/5%)

4. Discussion on Project Assignment(using only prior experience) • Be able to relate general project type (interactive web app, server app, high db info retrieval, high computational, high transactional and performance gated, etc.) --- same idea as COCOMO’ s “mode” • Consider the deliverables --- • For each deliverable, recall the work required for each deliverable from past experience (e.g. 100 pages of req doc ≡ 15 person-days; 150 test cases developed and executed ≡ 45 person days; 150 loc module designed and coded ≡ 4 person days ) (this is where people tend to grab from thin air) • Lay out the tasks and extrapolate using previous experience to get rough effort estimates for the deliverables of this project --- don’t forget to add in buffers. • Set up schedule: • Lay out task sequences, • Overlap where reasonable • Use the effort estimates from above • Consider the number of resources and get the “elapsed time” for each task for calendar