#4 Prototype Presentation and Specification

w/ Prototype Views and Specification: (collaborative) 100 points


In this final group assignment, you will build culminate your work in terms of research, design, and build a hi fidelity proof-of-principle prototype. This work is cumulative with other work you have accomplished as a group. It documents that work in such a way as to explain it to others while explaining your understanding of the problem and addressing why your prototype addresses the problem in the best way.

While this is not a competition, you should think of these rhetorical performances as a sort of “pitch” opportunity for funding. You need to show through careful and thoughtful articulation and documentation, why your firm’s idea is the best and should receive funding to proceed or win a contract.

This assignment consists of three separate rhetorical performances by your design firm:

Presentation: showcase your proof-of-principle prototype views and persuade the your audience that your design choices are appropriate and buildable.

Prototype specification: document your design and design process in a way that communicates to potential developers and/or supporters that your design is viable.

Proof-of-principle prototype: build on your previous low and mid fidelity work from assignment to to build out an interactive example of your digital solution using inVision or other Wireframing/Prototyping tools of your choice.

Prototype specification examples:

Proof-of-principle prototype examples:


1. A presentation outlining your understanding and approach to the project:

  • Executive Summary
  • Introduction and scope
  • Stakeholder analysis and Persona Summary
  • Overview of existing systems
  • Lifestream/workstream visualization, summary, and analysis
  • Argument for tasks helped by the solution drawing on Lifestream/workstream
  • Initial proof-of-principle prototype design description

2. A ten to fifteen page memo detailing the prototype specification

Something like this document this document but shorter.

  • Executive Summary
  • Project background
  • Overview of Existing and Planned Systems (workstream visualization)
  • Stakeholder/Persona Analysis: Methods (journey map)
  • Stakeholder/Persona Analysis: Findings
  • Technical Design (low and mid fi designs)
  • Proof-of-Principle Prototype Design (annotated prototype views)
  • Limitations of Product/Process
  • References (class texts, personal interviews, other firm personas)
  • Resources (software used, other firm personas)


  • Google slides
  • Google doc specification
  • distributable interactive proof-of-principle prototype


  • Presentation: Gslides, varies presentation should be approximately 10 minutes and include live demo of proof-of-principle prototype.
  • Prototype specification: ten to 15 pages including prototype views and screen captures.
  • Proof-of-principle prototype: varies, should provide multiple decision points. More interactions will be graded more favorably.