Overview

The Final Report is a report written collaboratively by the team, which summarizes the team’s third iteration (”Loop 3”) design.

It is essential that your Report relates your design decisions to both technical and human factor aspects of your Design Brief.

The Final Report is independent of the Milestone Reports; it is a “standalone” document that reflects the current state of your design.

<aside> ⚠️ You may copy-paste any information from Milestone 1 or Milestone 2 that is still relevant, but do not discuss changes made since Milestone 2. Discuss only the state of the design as of the end of Loop 3. The Final Report must not depend on the Milestones; it must be a “standalone” report.

</aside>

The Final Report will be graded according to this rubric.

There is no overall page limit for this Report; however, there are some page limits on certain sections of the Report.

The Final Report shall include the following sections.

Report Prep

This is an overarching category, including preparation of the Report itself, reviewing and editing the language for clarity and conciseness, checking spelling, ensuring all formatting is correct, ensuring references are properly cited, etc. This category applies to the Report as a whole.

The language of a Report must be concise and precise. The target reader of these documents are technical project leads and managers. They will not accept reports written as sales brochures or marketing reports. They will be aware of fallacious rhetoric and will refuse to support projects using it. Proper use of paragraphs and Extended Point Form is also expected.

Page limits must be strictly observed; exceeding the page limit even by one word will result in a substantial penalty. Changing the format (font size, line spacing, etc.) will also result in a substantial penalty.

Table of Contents

Use the Google Docs function to insert a table of contents.

The command is under the menu item: Insert > Table of contents. Note that the TOC menu item is right at the very bottom of the Insert menu - you may have to scroll the dropdown menu to see it.

Of the two TOC options, select the one that inserts links to the various sections.

IMPORTANT: the TOC is not dynamic. If you insert the TOC before you finish the report, it will not be accurate. Insert the TOC once you’ve finished writing the report. If you insert the TOC before finishing the report, remember to refresh the TOC after you finish the report.

For more info, see this Google Docs Support page.

Cover Page

Replace the image of the Vari Engineering Building with a photorealistic rendering of the CAD model of your design.

Turn on perspective and multiple light sources, colour the exterior in a sensible way, turn off wireframe rendering, etc. Use a background image to place the rendering in a typical environment of usage. Include a human figure for scale.

Executive Summary (1 page maximum, long-form text)

The Executive Summary must provide a technical overview of the design so far. It must be factual (neither judgemental nor opinionated), and link extensively to relevant sections of the four key specification documents.

The Executive Summary is not an “introduction” to the report; it is a summary of every important fact about your design.

Design Brief Summary (1 page maximum, long-form text)

Must include a link to the original Design Brief.
Must highlight what your team thinks are the most important aspects of the Brief.
Must summarize your team’s goals (per the Situation Scan).

Background (2 pages maximum, Extended Point Form)

Summarize the elements of the Situation Scan that are most relevant to your final intervention design.

Personas & Situated Use Cases (no page limit)

Present each Persona and corresponding SUC together, in the requisite formats.
No introductory or discussive remarks are needed.

Requirements (no page limit)

Must include all Requirements relevant to Loop 3, in the requisite format.
No introductory or discussive remarks are needed.
Do not include requirements from Loop 1 and 2 that are no longer relevant.
Remember to keep situational and internal requirements in separate lists.

Integrated Design Concept

Must include the most up-to-date Integrated Concept.
Must observe the page limit and format as described on the page Integrated Concept.
- Include a brief explanation of any Creativity Methods used in the concept description text.
- Include links to the section of the Product Design Specification containing earlier Design Concepts.

Systems Analysis

A complete System Model includes:

the Subsystem Identification Matrix for your Integrated Concept in the requisite format;
the System Diagram of your Integrated Concept in the requisite format;
the specification of the quantified System Interfaces in the requisite format; and
up to one page of explanatory text.