160 likes | 172 Vues
try again, er something. February 17, 2005. Greg Giacovelli – Nick Mancuso – Shaun Newsum – Jean-Paul Pietraru – Nick Stroh. Agenda. Project description Project plan Risks Requirements Design Current status Domain experience. Project Description. The current “try” system
E N D
try again, er something. February 17, 2005 Greg Giacovelli – Nick Mancuso – Shaun Newsum – Jean-Paul Pietraru – Nick Stroh
Agenda • Project description • Project plan • Risks • Requirements • Design • Current status • Domain experience
Project Description • The current “try” system • submission, testing & grading • collection of scripts • New system goals • ease learning curve & assignment management • portability • performance
Major Use Cases • Students • Submit assignments • View test results • View grades • Graders • View submitted files • View test results • Assign grades • Professors • Create assignments / activities / tests
Process • Spiral • R1 – The Framework (January) • R2 – Submit & Grade (February) • R3 – Compile & Test (March) • R4 – Code Complete (April) • R5 – Gold (May) • Why • immediate feedback • ship even if slip
Risks Key: 1 = low risk / impact 5 = high risk / impact
Requirements - Elicitation • Sources: • project proposal • customer engagement • existing interface documents (XML) • old “try” system • manuals • sample lab • personal experience • Use cases • Preliminary database & architecture designs
Requirements • All known system requirements documented • prioritized (1-3) • divided among iterations • tested against old “try” manuals • Data dictionary is critical to the system • Each requirement is independent & numbered • Bugzilla used to track bugs
Design • Justifications • Web based system • J2EE • Distributed test processing • Process • Finalized requirements • Designed database / file structure • Presentation / business logic / data
Current Status Key: white = pending; green = delivered on time; red = late
Experience so far • Active customer involvement crucial • the bad… • Slipping schedule • Project management • resource allocation • time estimates • multitasking • minutes • …and the good: • Solid requirements & design will ensure smooth sailing from here • Good communication / teamwork • Constant customer interaction