Deliverable | Due Date | Description | Team Standards | September 14th, 2020 | This document lists out the standards and expectations of each group member. |
---|---|---|
Team Inventory | September 14th, 2020 | This document offers a brief introduction to each of our team members. |
Mini Intro | September 21st, 2020 | A brief video introducing our team and the purpose of our topic. |
Technical Feasibility Draft | October 5th, 2020 | This document serves as a layout and general guideline to how we will be approaching the many facets of this project. |
Technical Feasibility Final | October 23rd, 2020 | Outlines and details anticipated challenges, technologies, and integration for the continuation of the Licht software for Lowell Observatory. |
Design Review | October 26th, 2020 | This presentation looks at the design of our project to give a high level overview of our requirements. |
Requirements Document V.1 | November 11th, 2020 | Draft outlines the project requirements of Team Triaxis, as well as the potential risks and current project plan for further developing the Licht software for Lowell Observatory. |
Requirements Document V.2 | November 20th, 2020 | Document outlines the project requirements of Team Triaxis, as well as the potential risks and current project plan for further developing the Licht software for Lowell Observatory. |
Tech Memo Demo | November 25th, 2020 | Communicate the extent to which our team has identified key challenges in the project, and has proven solutions to those challenges. |
Communication Strategy Memo | January 20th, 2021 | This document outlines and details Team Triaxis’ intended plans and expectations for communications and routine meetings. |
Software Design Document Draft | February 5th, 2021 | This document drafts the details of the architectural design of the Team Triaxis’ project. |
Software Design Document | February 15th, 2021 | This document outlines and details the architectural design of the Team Triaxis’ project. |
Design Review II | March 26th, 2021 | The purpose of this presentation is to look at the design of our project, give a high level overview of our requirements, and give an example of an in depth breakdown for one of our requirements. It also examines some demos and challenges faced. |
Software Testing Plan | March 26th, 2021 | This document outlines activities that are aimed at ensuring that our project's implementation exhibits the necessary functional and non-functional characteristics. In it, we describe how we intend to ensure that the expectations presented in the requirements and design specification documents are met, via a well-planned software testing regime. |
Design Review III | April 2nd, 2021 | The purpose of this presentation is to look at the last design of our project, give a high level overview of our requirements, and give an example of an in depth breakdown for one of our requirements. It also examines some demos and challenges faced. |
Final Report | April 29th, 2021 | The purpose of this document is to provide users an overview of the the software and how to use it to its fullest extent. This guide covers installation, use, and troubleshooting, as well as other smaller topics. |
User Manual | April 29th, 2021 | The purpose of this document is provide an extensive overview of the project. The document covers the process overview, requirements, architecture, testing, timeline, and future work of the project. |