> For the complete documentation index, see [llms.txt](https://krjaeh0.gitbook.io/j-log/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://krjaeh0.gitbook.io/j-log/programming/software-design/uml-and-modeling/uml/use-case-diagram.md).

# use case diagram

You provided the page title "유스케이스 다이어그램 (Use Case Diagram)". How would you like me to proceed?

Choose one (or describe your own):

* Create an explanatory page (definition, purpose, elements) in Korean.
* Provide step-by-step instructions to create a use case diagram (with a stepper).
* Add example diagrams (Mermaid/PlantUML) and sample markdown to embed them.
* Convert an existing use case diagram image or text into GitBook-optimized markdown (please paste the content or image).
* Generate templates/snippets for common UML tools (PlantUML, Mermaid).
* Other — please describe.

Tell me which option you want and any details (language preference, include Mermaid/PlantUML code, number of examples).


---

# 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://krjaeh0.gitbook.io/j-log/programming/software-design/uml-and-modeling/uml/use-case-diagram.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.