Академический Документы
Профессиональный Документы
Культура Документы
Outline
Justify the need for a Use Case diagram
Use Cases
Are the sequence of action that can be provided as a measurable value
to an Actor. These Use Cases are represented using ovals that are
labeled with verbs that represent the systems functions
Each Actor must be linked to a use case, while some use cases may
not be linked to actors.
Use Case
Packages
Is a mechanism that allows you to organize model elements
such as Use Cases into groups.
Types of Actors
Human Actors
Are the people using the system who have a particular purpose or
task to accomplish.
Machine Actors
Are the machines that interact with the computer.
Primary Actors
Primary actors are those who use the systems main functions,
deriving benefits from it directly. Typically, the Primary Actor initiates
functionality with a System.
Primary actors are completely outside the system and drive the system
requirements
Primary actors use the system to achieve an observable user goal
Task:
A function to be performed an objective. This is not an official
UML word. The official word is Use Case.
Step:
One of a series of actions that is a stage in a process.
Sub-Task:
A function that is to be performed as a sub-process of a
higher level task or another sub-task.
For example, when a user uses an ATM, the task might be withdrawing
money from the account. On the other hand, inserting the ATM card into the
ATM is not a task; it is a step or subtask along the way to accomplishing the
task
Include relationships
One use case (base) includes the functionality of another (inclusion
case)
Supports re-use of functionality
Extend relationships
One use case (extension) extends the behavior of another (base)
Generalization relationships
A use case generalization shows that one use case is simply a special kind of
another.
In UML modeling, a generalization relationship is a relationship in which one model element (the child) is based on another model element (the parent). Generalization relationships
are used in class, component, deployment, and use-case diagrams to indicate that the child receives all of the attributes, operations, and relationships that are defined in the parent.
The child use case inherits the behavior and meaning of the parent use case.
Include relationships
In the process of developing a use case model, we may discover that some use
cases share common behaviors.
There are also situations where some use cases are very similar but they have some additional behaviors.
For example, Withdraw Money and Deposit Money both require the user to log-on to an ATM system
Extend relationships
In UML modeling, you can use an extend relationship to specify that
one use case (extension) extends the behavior of another use case
(base). The Extending Use Case adds to the existing functionality and
characteristics of the Base Use Case. This type of relationship reveals
details about a system or application that are typically hidden in a use
case.
The extend relationship specifies that the incorporation of the
extension use case is dependent on what happens when the base use
case executes. The extension use case owns the extend relationship.
You can specify several extend relationships for a single base use
case.
While the base use case is defined independently and is meaningful
by itself, the extension use case is not meaningful on its own.
Extension points
In UML models, an extension point identifies the point in the base
use case where the behavior of an extension use case can be
inserted. The extension point is specified for a base use case and is
referenced by an extend relationship between the base use case
and the extension use case.
A base use case can have several extension points. Each extension
point has a unique name that identifies one or several locations in
the behavior sequence of the base use case.
As the following figure illustrates, the name of the extension is listed
in the Extension Points compartment of the use case.
Summary of Notations
Extend
Include
Scenario
A customer visits the online shopping portal. A customer may buy
item or just visit the page and logout. The customer can select a
segment, then a category, and brand to get the different products in
the desired brand
Thank You !