CSC 402 Proposed Project Timeline
Week | Team | Activity |
1 | Rqmts | Initial Interviews Scheduled as much as Possible |
Proto | Begin work on Eric's current system | |
Infra | SVN repo set up and checked out by all; wiki tools reviewed | |
2 | Rqmts | Conduct interviews, begin scenarios |
Proto | Determine deployment mechanisms | |
Infra | Wiki operational, tested by teams | |
3 | Rqmts | Pre-release to teams, Phase 1 |
Proto | Pre-release to teams, Phase 1 | |
Infra | Wiki in full use by teams; plans for usability lab infrastructure | |
4 | Rqmts | Release to clients, Phase 1 (Friday) |
Proto | Release to clients, Phase 1 (Friday) | |
Infra | Wiki in use by clients; usability lab pilot use by students | |
5 | Rqmts | Prioritization based on client feedback |
Proto | Prioritization based on client feedback | |
Infra | Draft 1 of maintenance and marketing plans | |
Model | Begin work | |
6 | Rqmts | Continued work |
Proto | Continued work | |
Infra | Continued work; annoyingsoftware.org pre-release to teams | |
Model | Core model 50% | |
7 | Rqmts | Release to clients, Phase 2 (Friday) |
Proto | Release to clients, Phase 2 (Friday) | |
Infra | annoyingsoftware.org release to public; usability lab use by clients | |
Model | Core model 75%; begin formal specs | |
8 | Rqmts | 60% complete |
Proto | 60% complete | |
Infra | Initial data analysis of annoyingsoftware.org | |
Model | Core model 100%; formal specs 30% | |
9 | Rqmts | 70% complete |
Proto | 70% complete | |
Infra | 2nd draft marketing and maint plans; continued work as necessary | |
Model | Formal specs 50% | |
10 | Rqmts | 80% complete |
Proto | 80% complete | |
Infra | Continued work as necessary | |
Model | Formal specs 70% | |
11 | Rqmts | Release to clients, Phase 3 (Monday) |
Proto | Release to clients, Phase 3 (Monday) | |
Infra | Usability testing with students and clients (all week) | |
Model | Formal specs 90% | |
F | Rqmts | 100% complete |
Proto | 100% of as much prototyping as we choose to do | |
Infra | Final draft of maint plan, market plan, annoying white paper | |
Model | Formal specs 100% (of features considered core) |