> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/internet-of-things-project/iot-project-outline/5-1-evaluate-smart-device-and-web-app.md).

# 5-1 Evaluate Smart Device and Web App

Once integration testing is completed, your team needs to evaluate your smart device and web app by testing it with stakeholders to gather feedback on what is working well and what could be improved.

The evaluation will focus on testing the functionality, usability, and user experience of your solution. This evaluation can provide evidence of how well your solution meets your [design requirements](/cxd/internet-of-things-project/iot-project-outline/2-7-define-design-requirements.md).

## YOUR TASK

1. Identify one or more tasks that people could complete using your smart device and web app. Create a brief scenario describing a realistic context in which someone would need to complete the task(s).
   * For example, a scenario and task might be something like:  "*Imagine you are a student that needs to get something from your locker before your next class starts. Open up your smart locker, and then lock it again when you're done.*"
2. Recruit 3-5 participants that match one of your target stakeholder groups, as represented by your [personas](/cxd/internet-of-things-project/iot-project-outline/2-4-construct-personas.md). Each participant will individually evaluate your team’s solution.  Each evaluation will take about 5-10 minutes.
3. At the start of each evaluation, briefly introduce your solution to the participant using your team's [value proposition](/cxd/internet-of-things-project/iot-project-outline/2-6-define-value-proposition.md). Be sure to mention that:
   * the product is being tested, **not** the participant
   * the product consists of a smart device and a web app that work together
   * the product is an early prototype, so you want constructive feedback on what’s working well and what could be improved
4. Describe the scenario to the participant, and identify the task that he or she should complete using the device and web app. (*If you have multiple tasks to test, give the participant one task at a time.*) Tell the participant to provide feedback by “[Thinking Aloud](https://www.nngroup.com/articles/thinking-aloud-the-1-usability-tool/)” as he or she interacts with the device and web app.
   * Since the device is an early prototype (which may be very unfamiliar), it may be necessary at times to provide **limited** help if the participant doesn't understand what to do next.
   * However, as much as possible, let the participant figure out how to interact with the device.
5. As the participant completes the task(s), record notes on the feedback being provided.
6. At the end, have the participant complete this [online evaluation survey](https://drive.google.com/open?id=1_FzSpnhZk2HSHMYiNIEdhIYHHhO8RDOHsv26l-0yjMs).

**Repeat Steps 3-6 with each participant.**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.launchboard.app/cxd/internet-of-things-project/iot-project-outline/5-1-evaluate-smart-device-and-web-app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.