Final Report

This document serves as a summary of your senior design experience. It should summarize the scope of your project, highlight critical decisions, provide links to relevant artifacts, reflect on your successes and failures, convince the reader that your team acheived the course outcomes for the senior design sequence.

The document should stand alone. That is, it should be possible for someone unfamiliar with your project to read just the final report and understand the project and your team's accomplishments. If the reader is interested in digging into a particular aspect, links should be provided to help guide them.

A separate GitLab repository should be created to house all of the final project deliverables that are not in the wiki. The final report should summarize many of these and include references when appropriate. The repository should be organized and easy to navigate. The final report itself should contain:

  1. Project Information
  1. Executive summary — two to three paragraphs that:
  1. Project summary — This section provides a summary view of key parts of your broader project documentation. It may include screen captures or photos of your product, selected diagrams, and additional information from those other documents. The goal is to provide an overall technical summary of the project so that key elements can be understood without having to do an exhaustive study of other project documents.
  1. Documentation on how your team addressed the following elements of software engineering in your project (along with links, when appropriate):
  1. Project postmortem
  1. Student Outcome Summary — Links to the wiki pages describing how each team member achieved the student outcomes assigned over the three quarters of senior design.