636-530-7776
Legend: RUP Notation
Workflow > Detail > Activity

Activity: Detail A Use Case

Describing how actors interact with the application under development allows the team to focus on application usage and address explicit and implicit user needs. Each Artifact: Use Case defines interactions that allow actors to achieve their goals while using the application or website.

More detail: Purpose - Frequency - Steps

Click the icons for definition

Use Case Modeling Guidelines (from Environment)GlossaryBusiness Rules (from Business Strategy)
Subject Matter Expert
Information Architect
Requirements AnalystDetail a Use CaseStructure the Use Case ModelManage Dependencies
Requirements Analyst
Subject Matter Expert
Stakeholder
Actor CatalogWireframesUse CaseUse Case ModelRequirements Attributes
Requirements ReviewerReview Requirements Site Map
Review Record

Description

To define requirements by writing and revising an Artifact: Use Case. A Use Case defines a sequence of actions initiated by an actor in order to achieve a goal. The sequence of actions is described in terms of interactions between actors and the system, application, or website. The Use Case uses domain (i.e., stakeholder and subject matter expert) terminology. It does not describe user interface details such as menus and buttons; it focuses on functional behavior from a black box perspective.