In this section, we will outline the deliverables for the semester. Make sure you prepare everything! Make submission on blackboard. Team deliverables need only one submission per team.Deliverables are comprised of the following: Recurring | Major Docs | In-Class Presentations | Project Wrap Up | In-Class Exercises
Most documentation deliverables in this course use LaTex. Here are some resources for you:
- Guides to LaTeX: The Not So Short Introduction to LaTeX (LaTeX in 139 minutes) | Wikibooks | NYU
- Online Environments If you don't want to install LaTeX, Overleaf is an online environment which compile previews of your LaTeX documents as you type. They also allow you to share your LaTeX with others.
- LaTeX Editors There are many LaTeX editors which allow you to use GUI to edit your LaTeX. LyX is a free one.
- Finding symbols Detexify lets you draw the symbol that you are looking for and get LaTeX code.
| Name |
Date |
Summary |
| Individual Sprint Retrospective |
Every other week (first due 1/28) |
The Sprint Retrospective is an opportunity for the Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. (template up on blackboard). |
| Team Meeting Report |
N/A |
Team Meeting Reports must be given for each scheduled team meeting. There are nine scheduled mandatory team meetings. Team meeting reports must follow the Team Meeting Report Form. |
| Name |
Date |
Summary |
| System Requirement Specification |
2/4 at 11:59pm |
A System Requirements Specification is a structured collection of information that embodies the requirements of a system. We will use this template to help solidify the requirements you must deliver on (LaTex template up on blackboard). |
| Project Plan |
2/18 at 11:59pm |
A project plan is a statement of the scope, objectives, and participants in a project (LaTex template up on blackboard). |
| Architecture Design Specification |
3/17 at 11:59pm |
Your architecture describes the decomposition of the software into components. This document focuses on the interaction between components and not low-level implementation details (LaTex template up on blackboard). |
| Detailed Design Document |
3/31 at 11:59pm |
The Detailed Design Document describes how overall system architecture outlined in the ADS will actually be developed and implemented (LaTex template up on blackboard). |
| System Test Plan |
4/21 at 11:59pm |
A test plan is a document detailing the objectives, resources, and processes for a specific test for a software or hardware product. The plan typically contains a detailed understanding of the eventual workflow (LaTex template up on blackboard). |
| Name |
Date |
Summary |
SRS Presentation |
2/4 |
10 minute presentation summarizing key points in your SRS. |
| Early Prototype Demo |
2/11 |
Demos will be informal, features should be in-progress. |
| ADS Presentation |
3/17 |
10 minute presentation summarizing key points in your ADS. |
| Mid-Stage Prototype Demo |
3/24 |
You are expected to have high priority requirements implemented and mid to low priority requirements under development. |
| DDD Presentation |
3/31 |
10 minute presentation summarizing key points in your DDD. |
| Late-Stage Prototype Demo |
4/21 |
Teams should present a (nearly) working project with only minor functionality missing. Demos will be presented to the instructor and classmates. |
| STP Presentation |
4/21 |
STP will be explained and shown in action during the late stage demo. |
Make sure you deliver a complete package at the end of the semester.
| Name |
Date |
Summary |
| Teammate Assessment |
5/4 at 11:59 pm |
Evaluate each one of your teammates, as well as yourself. Submit on Blackboard, one per person. |
| Project Advisor Meeting Diary |
5/4 at 11:59 pm |
A team must meet regularly with their project advisor. A team must have at least 7 consultations with the project advisor and this will be captured by the meeting diary. |
| Final project wrap up |
5/4 at 11:59 pm |
Submit on Blackboard a ZIP file, containing the following:
- Your final Project Plan
- Your final SRS
- Your final ADS
- Your final DDS
- Your final STP
- Final source code files: your source code should also be on github, and each member must have at least one commit
- Guide to install and run your project
- User Manual: Feature oriented
- Final Presentation PPT
- Anything else you think we need to properly assess your project
|