Project deliverables by date
CS 284 (MCA), Spring 2022
The CS 284 project is carried out using a structured process, and your project grade is based on how well you and your team carry out the process as well as your software itself.
The software design process is structured as a series of deliverables whose descriptions and due dates are presented during class time and in web pages such as this one.
Team deliverables need only be submitted once by one member of a team, on behalf of that entire team.
Individual deliverables should be submitted by each individual, often after coordinating with other team members.
Besides the deliverables described here:
Each student should report their activities daily using the log form. Log submissions that are submitted more than 24 hours after an activity takes place will receive less credit and will not show up in the log reports.
All code should be submitted using the team stogit repository.
All team members are expected to attend class and participate in team meetings.
Table of project deliverables and deadlines
Note: Click on the name of a deliverable to see a description
| due | name | type | format | how to deliver | |
| 1. | Tue 4/19 | Project ideas | individual | form | project ideas form |
| 2. | Fri 4/22 | Project ideas ratings | individual | form | project ideas rating form |
| 3. | Sat 4/23 | Project team proposals | team | form | project team form |
| 4. | Mon 4/25 | Introductory project presentation - feedback | individual | form | feedback form (2min) |
| 5. | Mon 4/25 | Introductory project presentation slides | team | project submit form | |
| 6. | Wed 4/27 | Features list - draft | team | project submit form | |
| 7. | Wed 4/27 | Storyboard diagrams - initial | team | project submit form | |
| 8. | Thu 4/28 | Database table diagram - initial | team | project submit form | |
| 9. | Mon 5/2 | Project update 1 - feedback | individual | form | feedback form (update 1) |
| 10. | Tue 5/3 | Project architecture diagram - first version | team | project submit form | |
| 11. | Tue 5/3 | Features list - update 1 | team | project submit form | |
| 12. | Tue 5/3 | Storyboard diagrams - update 1 | team | project submit form | |
| 13. | Tue 5/3 | Database table diagram - update 1 | team | project submit form | |
| 14. | Fri 5/6 | Project update 2 - feedback | individual | form | feedback form (update 2) |
| 15. | Sun 5/8 | Features list - update 2 | team | project submit form | |
| 16. | Sun 5/8 | Project architecture diagram - update | team | project submit form | |
| 17. | Sun 5/8 | Storyboard diagrams - update 2 | team | project submit form | |
| 18. | Sun 5/8 | Database table diagram - update 2 | team | project submit form | |
| 19. | Fri 5/13 | Final project presentation - slides | team | form | project submit form |
| 20. | Sun 5/15 | Features list - final | team | project submit form | |
| 21. | Sun 5/15 | Project architecture diagram - final version | team | project submit form | |
| 22. | Sun 5/15 | Database table diagram - final | team | project submit form | |
| 23. | Sun 5/15 | Storyboard diagrams - final | team | project submit form | |
| 24. | Sun 5/15 | Team report form | team | form | team report form |
| 25. | Sun 5/15 | Individual report form | individual | form | individual report form |
Descriptions of deliverables
- 90-sec project idea (individual)
- ______
- 3-min project idea (team)
- ______
- Features list (team)
- ______
- Outline of user manual (team)
- ______
- First draft of UML (team)
- ______
- Updated features list (team)
- ______
- Updated UML (team)
- ______
- 3+-page user manual (team)
- ______
- Draft one important class spec (individual)
- ______
- Demo 1 image (team)
- ______
- Updated features list (team)
- ______
- Updated UML (team)
- ______
- Ethical analysis (team + individual)
- ______
- Demo 2 images (team)
- ______
- Tarball test (teams)
- Uploaded to the wiki and linked to the project wiki page.
- Final presentation images (team)
- PDF of slides and important screen shots, submitted using this form (multiple submissions are fine).
- Annotated features list (team)
- See this description
- Final version of UML
- Updated to indicate all (used) classes in the final version of the software.
- Wiki page of deliverables (team)
- See this description
- Team report (team)
- Fill out this form as a team, one submission per team.
- Individual report (individual)
- Each student in the class should fill out this form
- Final user manual (team)
- Complete user manual, approximately 7 pages