1. The project plan. December 16, 2004

2. Agenda The project plan –Risks –Language decision –Schedule –Quality plan –Testing –Documentation Program architecture

3. Risks Assumptions –Adequate hardware –XML files –Major features disclosed

4. Risks DescriptionLikelihood Rank Impact Rank Combined Rank Requirements volatility – requirements are somewhat unspecific, features may be added or removed 8513 Difficult Testing – the system will be difficult to realistically test, as a common load involves hundreds of students 9413 Insecurity – many aspects of the system are security- critical 9817 Unfamiliar Tools – not all of the team is familiar with application servers, MS Project 10212 Implementation Complexity – some implementation issues will require further research: sandbox, pushlets, process launching / monitoring 8513 Hardware – the team may not be able to obtain sufficient test/deployment hardware 3710 Parallel development of external interfaces – our system will rely on XML files being implanted by others. 6814

5. Language decision Rich client or web application? J2EE or.NET?

6. Schedule R1 – The Framework (January) –Design doc –Test plan –Stubbed implementation of framework –Prototype for each major user type

7. Schedule R2 – Submit and grade (February) –Professors may create labs –Students may submit answers –Graders may grade submissions –Test suite

8. Schedule R3 – Compile and test (March) –Professors may define tests –Students receive immediate compile and test results –Graders may review test results –Administrators may add / remove privileges –Test suite

9. Schedule R4 – Code complete (April) –All remaining functionality Sandbox UI –Configure for distributed environment –Graders may view standard metrics on submissions

10. Schedule R5 – Gold (May) –All acceptance tests must pass –Documentation finalized

11. Quality plan Change control –Versioned & log changes –Vote Configuration management –Suffixed by build number Defect tracking –Bugzilla

12. Testing Unit System-level Performance Acceptance

13. Documentation SRS Design Javadocs Test plan User’s manual / help Developers manual Administrators manual

14. Any questions? Up next… Program architecture … as presented by Greg