1. Introduction

Important questions

  • How do you know when a design is good enough?

  • What makes a design able to be called a success?

These questions demand (require) some sort of basis for making these judgements or there would be no way for any one to agree on the answers!

Requirements

  • represent the link between understanding stakeholder (customer) needs and potential value creation and the task of technical design and implementation.

  • describe, both high-level and specific terms, the characteristics a system must have to be considered a successful design

  • Clarifying features and behaviors also promotes disciplined thinking and decision making when handling the details of a design.

  • Making the connection between Needs and Details is what makes a design valuable for all of the people involved.

1.1. Requirements handout

Requirements handout (PDF)

1.2. Design

The Science of Design — Kenneth Kuhn

2. Project description

Make a copy of: GDoc — Project description