---
title: use case
slug: use-case
qid: Q613417
snapshot: use-case-070538-004dd9265ff7b7da
content_hash: 004dd9265ff7b7dab11f4f1f0a75b235bf68047247679abcad9b227d5d0f4a5a
license: CC BY-SA 4.0
source: https://en.wikipedia.org/w/index.php?oldid=1365406765
tags: [20531876, 22897376, 22903779, 22905880, 22959512, 22990540, 23053261, 23060122, 23118434, 23556908, 23603337, 23888906, 24043274, 24623845, 24745122, 27175703, 36406786, 4277052, 4526415, 49773490, 62672628, 7805499, 88057362, 89061531]
---

# use case

> [!note] Provenance
> Snapshot `use-case-070538-004dd9265ff7b7da` · content root `004dd9265ff7b7da…`
> Derived from <https://en.wikipedia.org/w/index.php?oldid=1365406765> · Licensed CC BY-SA 4.0

of a Wiki system. Registered user of Wiki edits an article. In both software and systems engineering, a use case is a structured description of a system’s behavior as it responds to requests from external actors, aiming to achieve a specific goal. The term is also used outside software/systems engineering to describe how something can be used. In software (and software-based systems) engineering, it is used to define and validate functional requirements. A use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language (UML) as an actor) and a system to achieve a goal. The actor can be a human or another external system. In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals. The detailed requirements may then be captured in the Systems Modeling Language (SysML) or as contractual statements.

of a Wiki system. Registered user of Wiki edits an article. In both software and systems engineering, a use case is a structured description of a system’s behavior as it responds to requests from external actors, aiming to achieve a specific goal. The term is also used outside software/systems engineering to describe how something can be used. In software (and software-based systems) engineering, it is used to define and validate functional requirements. A use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language (UML) as an actor) and a system to achieve a goal. The actor can be a human or another external system. In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals. The detailed requirements may then be captured in the Systems Modeling Language (SysML) or as contractual statements. Search for "use case" at IBM Developer
