> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/the-blank-instruments/the-use-case-model.md).

# The use case model

Every goal that a person has in the service, named, and each tied to the entries of the register that it serves. The model is complete when every goal serves an entry and every entry is served by a goal.

|                            |                                  |
| -------------------------- | -------------------------------- |
| **Document of the twelve** | 4                                |
| **Who writes it**          | One named architect              |
| **What goes in**           | Documents 2 and 3                |
| **Who accepts it**         | The model's owner, at the review |
| **Taught in**              | 2.4                              |

## How to use this blank instrument

Copy this page into your own document. Fill in the answer to every line. Do not leave a line empty: write "none" where nothing applies, and where the answer is not yet known write an open question with the name of its owner and a date. Do not guess an answer to close a question. When the document is finished, give it to the person who accepts it, together with the questions at the end of this page.

## One goal

Write one row for each goal of a person in the service.

| Line                              | What to write                                                                | Your answer |
| --------------------------------- | ---------------------------------------------------------------------------- | ----------- |
| **Reference**                     | A number given once and never reused                                         |             |
| **Name**                          | A verb and its object, from the point of view of the person whose goal it is |             |
| **Level**                         | Summary, user goal or sub-step                                               |             |
| **Main actor**                    | The person or body whose goal this is                                        |             |
| **Entries it serves**             | The references of the entries of the register of requirements                |             |
| **Records it reads or changes**   | By name, from the entity model                                               |             |
| **Business rules that govern it** | The references of the rules                                                  |             |
| **Relationships**                 | Goals it includes, and goals that extend it                                  |             |
| **Status and priority**           | Draft, reviewed or baselined; priority set by value and risk                 |             |

## The model as a whole

Write these once.

| Line                            | What to write                                            | Your answer |
| ------------------------------- | -------------------------------------------------------- | ----------- |
| **Boundary**                    | The system the goals are goals of, and who is outside it |             |
| **Actors**                      | Every actor, with what each wants from the system        |             |
| **Goals that serve no entry**   | None; or each, with the question raised                  |             |
| **Entries that no goal serves** | None; or each, with the question raised                  |             |
| **Open questions**              | Each with an owner and a date                            |             |

## Before you accept it

1. Does every goal serve at least one entry of the register?
2. Is every entry of the register served by at least one goal?
3. Is every goal named from the point of view of the person who has it?
4. Does every goal that serves no entry, or entry that no goal serves, have a question with an owner?


---

# 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://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/the-blank-instruments/the-use-case-model.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.