Below is an archive of all project deliverables.
| Document | Description |
|---|---|
| Team Inventory | An inventory of the team's talents and abilities. It provides the client with an overview of the team and helps them better understand the team's strengths and weaknesses. It provides the team with an understanding of their collective strengths and weaknesses. |
| Team Standards | A shared agreement on the expectations of how the team will function. These expectations include team member roles, protocols for conduct, and what tools the team will use. |
| Technological Feasibility | An understanding of the key challenging aspects of the project. Includes a discussion of challenges, alternative solutions, and proof of feasibility. |
| Requirements | A description of the project's requirements including specified features and performance details. |
| Design Review 1 | The team’s first Design Review presentation. |
| Communications Strategy | A shared agreement on how the team will communicate. These expectations include meeting times (both team and mentor), communication tools, and expectations regarding meetings and response times. |
| Software Design | A description of our project’s overall architectural design and the design of each individual module. |
| Design Review 2 | The team’s second Design Review presentation. |
| Software Testing | A description of the testing performed for our system. This document describes how we intend to ensure the requirements and design specifications are met. |
| Design Review 3 | The team’s third and final Design Review presentation. |
| UGRADS Poster | The team’s poster created for the UGRADS Capstone Conference. |
| UGRADS Presentation | The team’s presentation created for the UGRADS Capstone Conference. |
| User Manual | The User Manual for our final product. This document describes installation, configuration, maintenance, and troubleshooting. |
| Team Reflection | A final reflection of how our team worked together, the effectiveness of the tools used, and how our project development went overall. |
| Final Report | A summary of the entire project; includes requirements, architecture and implementation, testing, a project timeline, and future work. |
| Team Schedule | A Gantt chart showing a timeline of work for the first and second half of Capstone. |