> For the complete documentation index, see [llms.txt](https://docs.idew.org/project-internet-of-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idew.org/project-internet-of-things/project-instructions/1-discover-and-define-problem/1.7-design-requirements.md).

# 1.7 Design Requirements

{% tabs %}
{% tab title="✓ TASK" %}
Discuss and establish a list of [design requirements](https://docs.idew.org/principles-and-practices/practices/design-practices/design-requirements) that your team’s smart device and web app will have to meet. Your team's design requirements should list a minimum of:

* 3 Functional Requirements
* 3 Usability Requirements
* 3 User Experience (UX) Requirements
* 1 Other Requirement

[Design Requirements Template](https://drive.google.com/open?id=1s90kNoqE8tlwiD8g6EMzBsmf9aAJUIFmllBKfHcyf7c)

### **❏ Deliverable**

Submit a document with your team's design requirements
{% endtab %}

{% tab title="➤ EXAMPLE" %}
![](/files/-LHnhYdENDbagrE-Yyjd)
{% endtab %}

{% tab title="★ RUBRIC" %}

| **✓- Below Standard**                                                                               | **✓ Meets Standard**                                                                                                                                                                                | **✓+ Exceeds Standard**                                                                  |
| --------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| Design requirements are incomplete, unclear, not measurable, or not helpful for designing solution. | Design requirements are clear, complete, and measurable. Requirements are informed by team's previous research and ideation. Requirements provide useful guidance for designing effective solution. | Requirements provide particularly insightful guidance for designing a valuable solution. |
| {% endtab %}                                                                                        |                                                                                                                                                                                                     |                                                                                          |
| {% endtabs %}                                                                                       |                                                                                                                                                                                                     |                                                                                          |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.idew.org/project-internet-of-things/project-instructions/1-discover-and-define-problem/1.7-design-requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.