Team Standards

The key to effective teamwork is shared agreement on the expectations of teammates concerning how the team will function. Standards may range from assigning specific roles to each team member, to establishing protocols for conduct and communication, to agreeing on what tools (version control, word processor, etc.) the team will use. Team standards -- of all these kinds -- establish a common understanding of expectations, and facilitate efficient and effective collaboration. Without these norms teams have difficulty communicating and cooperating since each individual may have a different interpretation of how things should be done.

Team Inventory

The first task for a newly-formed team is to take an inventory of what talents exist on the team...and what gaps there might be in the team's capabilities that one should think about planning to fill. On a more personal side, it's nice to get to know a little more the team members, including some hobbies or special interests.

Technological Feasibility

Technical feasibility is one of the most important criteria for selecting material for digitisation. Conducting a Technical Feasibility is part of our process for creating engineering solutions for technically difficult designs and products.

Requirements Specification Document

This document is a description of the project's requirements including specified features and performance details.

Communication Strategy Memo

This memo is a description of the meeting schedule with our clients and mentor, as well as the expectations of communication.

Software Design Document

This document goes in depth on our implementation, architecture and modules that we planned to use for our project.

Software Testing Plan

This document describes a carefully planned software testing mechanism to ensure that the expectations presented in the requirements and design specification documents are met.

Poster

Click here to download the poster.

Final presentation

Click here to download the video.

Final Reports

A summary of the entire project; includes requirements, architecture and implementation, testing, a project timeline, and future work.

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.