definition of the sequence of action s a system performs that yields an observable result of value to a part icular actor. A use-case class contains all main, alternate flows of event s related to producing the "observable result of value". [D04892] RUP
A task that is part of the business process, for example, renewing insurance policies in an insurance application.
A use-case model consists of actors, use cases, and relations among them. Actors represent everything that must exchange information with the system, including what are typically called users. When an actor uses the system, the system performs a use case. A good use case is a sequence of transactions that yields a measurable result of value for an actor. The collection of use cases is the system's complete functionality. [go to site
(class) A description of system behaviour, in terms of sequences of actions. A use case should yield an observable result of value to an actor. A use case contains all alternate flows of events related to producing the "observable result of value". More formally, a use case defines a set of use-case instances or scenarios. The specification of a sequence of actions, including variants, that a system (or other entity) can perform, interacting with actors of the system. See use-case instances.
a general way of using a blackbox business, application, component, or framework to achieve a goal of some external, primarily specified in terms of its normal and exceptional use case paths. Contrast with usage scenario and use case path. Contrast with change case and misuse case. For example, the use cases for an automatic teller machine application could include customer deposits funds, customer withdraws funds, customer obtains account balances, customer transfers funds, and customer makes payment. Note that a use case is a single, complete functional abstraction.
The specification of sequences of actions that a system, subsystem, or class can perform by interacting with outside actors.
A UML notation for capturing requirements of a system or sub-system. See Section 3.3, "Output of the Requirements Capture Process" for more information.
A transaction with the system from interface to interface initiated by the user or another system. The use case captures the essence of a single, simple system responsibility and is the basis for object-oriented modeling. Use cases are used to detail requirements, drive testing, and validate the object model.
Synonym for Scenario.
A specific end-user task or set of tasks performed by a distributed enterprise application, and used as a basis for designing, testing, and measuring the performance of the application.
A use case defines a piece of behavior of a classifier without revealing its internal structure by describing the behavior of a system from a user's standpoint, providing a functional description of a system and its major processes, and providing a graphical description of users and interactions.
A graphical depiction of the actors and operation of a system.
a coherent unit of functionality provided by a system or class as manifested by sequences of messages exchanged among the system and one or more outside interactors (called actors ) together with actions performed by the system
a collection of possible sequences of interactions between the system under discussion and its external actors related to a particular goal
a collection of scenarios, tied together through the aim of meeting a particular user goal
a complete sequence of steps that provides an actor with a result of value
a context diagram describing all the actors (i
a description of a cohesive set of possible dialogs (i
a description of a major function that the system performs for external actors
a description of a realistic business activity involving end-users and their interactions with software components and systems
a description of a set of sequence of actions, including variants, that a system performs to yield an observable result of value to an actor
a description of a single complete user interaction with a system
a description of a system's external behaviour, in the form of a sequence of actions that provide the user with a result of value
a description of a task somebody might want to complete using the Web site
a description of a typical use of a software
a description of how an End User Persona Profile would typically use the results of a Project to solve a problem
a description of how end-users will use a software code
a description of some activity usually involving a person and a computer system or between two or more systems
a description of what a person does, uses, or sees in an existing or planned business role
a formal description of functionality the system will have when constructed
a form of Hierarchical Task Analysis which has found favor in the software engineering community
a functionality of a system, and actor is a user (person or device) of the system
a generic description of an entire transaction involving several objects
a methodology used in system analysis to identify, clarify, and organize system requirements
an abstraction that describes a class of scenarios
a narrative document that describes the sequence of events of an actor (an external agent) using a system to complete a process
a narrative of the use of the system by a user, with alternating system and user actions, and a focus on what the user does and sees at some abstract level
an end-to-end sequence of actions (including variants) that result in an observable and useful result
an external view of the system that represents some action the user might perform in order to complete a task
an implicit definition of a set of interaction sequences
an instance of how an actuor would use a software system or a service offered by the system
a pattern of behavior a System exhibits
a piece of functionality in the system that gives a user a result of value
a process that will be performed - For example "Student enrolls in class" Usually a phrase rather than a one word label - A UseCase is always initiated by an actor that sends a message to it
a sample of how the system is used by an actor to accomplish some goal
a scenario of usage and what should happen - that is, a person does this, that, and the other thing, and this is what the software does in response
a scenario that describes the steps needed to resolve a problem
a scenario that describes the use of a system by an actor to accomplish a specific goal
a scenario that walks through an example of how a software system can be used
a scenario which involves the computer system and a number actors (users and external computer systems)
a script like specification of a single user carrying out a single task with a system
a segmented textual description of goal-directed interactions between a primary interactor (person or external system) and the system being used
a sequence of actions a system performs that yields an observable result of value to a particular actor (user)
a sequence of actions that provide a measurable value to an actor
a sequence of interactions that the user makes with the product to achieve a goal
a sequence of related transactions performed by an actor in the system
a sequence of transactions performed by the system that yields a measurable result of values for a particular actor
a series of steps an actor performs to accomplish a goal
a situation where the system is used to satisfy a user goal, providing something of value to the user
a specific way of using the system by using some part of the functionality
a specific way of using the system to perform some part of the functionality
a step by step description of the interaction of a user with the proposed system in order to complete a task or accomplish a discrete goal
a step-by-step description of the user's (actor's) actions (stimuli) and the software reactions
a summary of scenarios for a single task or goal
a systems analysis tool (or task analysis tool)
a tactic used in system analysis to identify, clarify, and categorize system requirements
a textual description of the interaction of the system and the user, in the language of the domain
a UML model element that describes how a user of the proposed system will interact with the system to perform a discrete unit of work
a Unified Modeling Language (UML) diagram type designed to capture the interaction of any person or external device with the system under design
a users steps to achieve a goal
a way of describing the required behavior of a system, centered around what the system offers its users
A typical interaction between a user (or agent) and a computer system. It captures some function visible to the user. The use case achieves a goal for the user.
In a Use Case Diagram, represents an action that the system takes in response to some request from an Actor.
A part of UML that describes how a computer-user interaction, sequence of actions, a computer system or object works by describing interactions with an external “actor” or user.
An implementation-neutral description of a reasonable action or task that an end user might want to accomplish. For example, a user might want to browse a site, but not necessarily view a site map. The action is general, and the use case is a tool for evaluating whether the general action can be accomplished in the particular instance of the site.
A detailed description of one system function. Includes inputs outputs expected results and potential errors (if any).
A description of the process used to perform a particular modeling task on a particular model. It is a user-centered description of the activities performed by a user to accomplish a particular goal. Contrast to a walkthrough.
A behaviorally related sequence of interactions that an actor performs in a dialog with a system to provide some measurable value to the actor; a collection of scenarios.
The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.