Difference between revisions of "Use case"
Karl Jones (Talk | contribs) |
Karl Jones (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | A '''use case''' is a list of steps, typically defining interactions between a role ( | + | A '''use case''' is a list of steps, typically defining interactions between a role (sometimes called an "'''actor'''") and a system, to achieve a goal. |
The '''actor''' can be a human, an external system, or time. | The '''actor''' can be a human, an external system, or time. | ||
Revision as of 11:01, 19 April 2016
A use case is a list of steps, typically defining interactions between a role (sometimes called an "actor") and a system, to achieve a goal.
The actor can be a human, an external system, or time.
Use cases are used in systems engineering and software engineering.
Contents
Systems engineering
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 Systems Modeling Language (SysML) or as contractual statements.
Software engineering
Use cases are an important requirement technique that have been widely used in modern software engineering since their formal introduction by Ivar Jacobson in 1992.
Use case driven development is a key characteristic of process models and frameworks such as the Unified Process (UP), Rational Unified Process (RUP), and Oracle Unified Method (OUM).
Agile software development
With its iterative and evolutionary nature, the use case is also a good fit for Agile software development.
See also
External links
- Use case @ Wikipedia
