Home Team Sponsors Documents Requirements Solution Technologies Schedule Code

Project Deliverables

Table of Contents

Team Inventory Document

The purpose of the Team Inventory Document is to provide a brief introduction to the members of the team. This document will contain the professional information about each team member. For more personal information, visit the Team page.

Team Inventory Document

Team Standards

The purpose of the Team Standards document is to outline the duties, standards, expectations, and rules that our team intends to follow throughout Capstone.

Team Standards Document

Communication Strategy

The purpose of the Communication Strategy is the outline and detail the expectations and procedures surrounding team meetings.

Communication Strategy

Communication Strategy Memo

Task Reports

The task reports contain the tasks that a given team member(s) have been assigned for a week. They are designed to help break down the task and help monitor the progress of the task. These reports are designed to be constantly updated.

Week of: September 14th
Week of: September 21st
Week of: September 28th
Week of: October 5th
Week of: October 13th
Week of: October 20th
Week of: October 27th
Week of: November 3rd
Week of: November 10th
Week of: November 17th
Week of: January 25th
Week of: February 1st
Week of: February 8th
Week of: February 15th
Week of: February 22nd
Week of: March 1st
Week of: March 8th
Week of: March 15th
Week of: March 22nd
Week of: March 29th
Week of: April 5th
Week of: April 12th
Week of: April 19th
Week of: April 26th

Mini-Intro

The purpose of the Mini-Intro is to provide a brief overview of the project, why the project exists, what it intends to do, and how the project will be approached on a technical level. The intro will act as an elevator pitch as seen in the video below.

Mini-Intro Presentation (Youtube)

Technological Feasibility

The purpose of the Technological Feasibility document is to determine what technologies are needed for this project, to define the criteria that are important, to compare alternatives, and to describe how the chosen alternatives will integrate.

Technological Feasibility Document

Design Review 1 Presentation

The purpose of the Design Review 1 presentation is to communicate our team's work status and to explain the purpose and need for our project in more detail than the Mini Intro presentation.

Presentation Video (Youtube)
Presentation Slides

Design Review 2 Presentation

The purpose of the Design Review 2 presentation is to reiterate some information from Design Review 1, as well as communicate the current progress of the project.

Presentation Video (Youtube)
Presentation Slides

Design Review 3 Presentation

The purpose of the Design Review 3 presentation is to reiterate some information from Design Review 1 and 2, communicate the current progress of the project, as well as provide a demo of the current state of the project.

Presentation Video (Youtube)
Presentation Slides

Requirements Specification

The purpose of the Requirements Specification document is to catalog the requirements for this project to be successful, to explain the solution implementation, and to communicate risks with their mitigations.

Signed Requirements Specification Document

Technical Demo Plan

The purpose of the Technical Demo Plan is to prove that the technologies we have chosen do indeed work as a solution. We identify the main technological integration challenges and build a demo to show that these challenges will be overcome.

Technical Demo Plan

Software Design Document

The purpose of the Software Design Document is to provide an architectural framework for the project. This will give information about the structure and overall design of the project. This will assist with future maintenance of the project as it is passed off to another team after Capstone.

Software Design Document
Software Design Document Draft

Flight Plan

The Flight Plan (also known as the Alpha Prototype Demo) acts like a checklist of required functionality for the project. It will walk a potential user (or even the demonstrator) through the expected requirements for the project, and how to accomplish them.

Technical Demo Plan

Software Testing Plan

The purpose of the Software Testing Plan is to document how product testing will be conducted. It will be broken down into units and observing how well these units are able to integrate with each other. It will also monitor how well a user is able to use to product with minimal to no instructions

Software Testing Plan

UGRADS Capstone Presentation

The UGRADS Capstone Presentation is to act like a selling pitch to potential investors. It is to not only demonstrate to our clients what we have accomplished for our project, but to advertise our product to other people who may be interested in a similar product.

Video Presentation (YouTube)
Poster
UGRADS Symposium

Acceptance Demo Plan

The Acceptance Demo Plan is going to be very similar to the Flight Demo in that it acts like a checklist of required functionality for the project, as well as walk a potential user through accomplishing these requirements. This document has the main purpose of demonstrating to the clients that the requirements of the project have been achieved.

Acceptance Demo Plan

Final Report

The purpose of the final report is to act as a comprehensive report of what was done for the project including the purpose of the project, the solution we envisioned, the requirements, how we accomplished our envisoned solution, and any troubles along the way.

Final Report

User Manual

The purpose of the user manual is to act as a guide to a potential user (the clients in this case) how to install and setup the required environments for maintenance (or future development), how to launch the software into a market environment, and provide any troublehsooting tips.

User Manual