1 / 15

Prelude to the Project

Prelude to the Project. The course project will involve roleplaying Here is the (fictional) backstory…. Backstory: The Grad-Tracker Project. UofM CS Dept contracts external company to build grad-tracker system System helps keep track of student progress Similar to UMDegree.

daughertyt
Download Presentation

Prelude to the Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Prelude to the Project

  2. The course project will involve roleplayingHere is the (fictional) backstory…

  3. Backstory:The Grad-Tracker Project • UofM CS Dept contracts external company to build grad-tracker system • System helps keep track of student progress • Similar to UMDegree

  4. Backstory:Failure Most Foul • CS Dept not satisfied with company’s work • Didn’t build what we asked for • Long periods with no apparent progress and no communication • Litigation ensues • CS Dept gets code – such as it is • Everyone loses money

  5. Backstory:Your Development Team • UofM has in-house development group • Your team is one of several

  6. Backstory:Your New Customer • CS Dept contracts with in-house group to finish project • Your team assigned to the job Here’s a quick demo of the project

  7. Project Process Analysis Requirements Design InitialPlanning Implementation Planning 2 weeks 2 iterations,~4 weeks each Testing Evaluation Deployment

  8. Initial Planning Process • Gather requirements • File bug reports • Estimate and plan work • May also involve a bit of • Program comprehension • Software design • Culminates in Alpha Iteration Plan

  9. Iteration Process • Plan/Build/Collect feedback • Productivity tracked weekly • Culminates in • Working code! (submission milestone) • Demo for class

  10. Detailed Initial Planning Schedule • Tue 8 Oct • Gather requirements from customer • Thu 10 Oct • Submit first pass on requirements (before class) • Receive feedback on your requirements • Estimate your requirements • Thu 17 Oct • Submit second pass on requirements + estimates (by 9am) • Receive priority assignments from customer (before class) • Choose requirements to build in Alpha Iteration, and break them down into detailed tasks (with estimates) • Tue 22 Oct • Submit requirements (w/ estimates) and iteration tasks (w/ estimates and assignments)

  11. Several Development Principles in Play • Customer sets priorities • He/she knows the benefits, but not the costs – unless you tell him/her! • Even detailed tasks should reflect incremental development • Each task should result in working code • The bigger the estimate, the less accurate • Put limited effort in estimating over all requirements • Put a bit more effort into estimating requirements/tasks for next iteration

  12. Detailed Initial Planning Schedule • Tue 8 Oct • Gather requirements from customer • Thu 10 Oct • Submit first pass on requirements (before class) • Receive feedback on your requirements • Estimate your requirements • Thu 17 Oct • Submit second pass on requirements + estimates (by 9am) • Receive priority assignments from customer (before class) • Choose requirements to build in Alpha Iteration, and break them down into detailed tasks (with estimates) • Tue 22 Oct • Submit requirements (w/ estimates) and iteration tasks (w/ estimates and assignments) Customer sets priorities

  13. Detailed Initial Planning Schedule • Tue 8 Oct • Gather requirements from customer • Thu 10 Oct • Submit first pass on requirements (before class) • Receive feedback on your requirements • Estimate your requirements • Thu 17 Oct • Submit second pass on requirements + estimates (by 9am) • Receive priority assignments from customer (before class) • Choose requirements to build in Alpha Iteration, and break them down into detailed tasks (with estimates) • Tue 22 Oct • Submit requirements (w/ estimates) and iteration tasks (w/ estimates and assignments) Less estimation effort More estimation effort

  14. Detailed Initial Planning Schedule • Tue 8 Oct • Gather requirements from customer • Thu 10 Oct • Submit first pass on requirements (before class) • Receive feedback on your requirements • Estimate your requirements • Thu 17 Oct • Submit second pass on requirements + estimates (by 9am) • Receive priority assignments from customer (before class) • Choose requirements to build in Alpha Iteration, and break them down into detailed tasks (with estimates) • Tue 22 Oct • Submit requirements (w/ estimates) and iteration tasks (w/ estimates and assignments) Incremental development

  15. What’s next? • Next class: Exam 1 • HW5 due before next Tuesday • Next Tuesday: Gathering requirements for the project

More Related