0% found this document useful (0 votes)
7 views

Use Case

The document outlines the concept of use cases, which describe a system's behavior in response to user interactions. It defines actors as external entities that interact with the system, categorized into primary and secondary actors. Additionally, it explains components of use case models, relationships between use cases, and levels of use case descriptions.

Uploaded by

Niaz Tanha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views

Use Case

The document outlines the concept of use cases, which describe a system's behavior in response to user interactions. It defines actors as external entities that interact with the system, categorized into primary and secondary actors. Additionally, it explains components of use case models, relationships between use cases, and levels of use case descriptions.

Uploaded by

Niaz Tanha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Use Case

A use case depicts a system’s behavior or functionality under various conditions as it


responds to user requests.

Actor

The actor is an external entity that interacts with the system. Most actors represent
user roles, but actors can also be external systems. An actor is a role, not a specific
user; one user may play many roles, and an actor may represent many users.

Actor Types

Primary Actor

 The main entity that initiates a use case.

 Directly interacts with the system to achieve a specific goal.

 Example: A customer using an ATM to withdraw money.

Secondary Actor

 Supports the system but does not initiate the use case.

 Assists in completing a process or providing necessary data.

 Example: A bank server that processes transactions for an ATM.

Use Case Model

A use case model consists of actors and use cases.

Use Case Diagram

A picture showing system behavior along with the key actors that interact with the
system.

Abstract Use Case

Abstract use case is when a use case is initiated by another use case. A use case
represents complete functionality.

Use Case Components

Actor

 An actor is a role, not an individual.

 Involved with the functioning of the system at some basic level.

 Represented by stick figures.

Use Case Representation

 Use case represents a single system function.

 Represented as an eclipse.

System Boundary

 Includes all the relevant use cases.


 A boundary is the dividing line between the system and its environment.

 Use cases are within the boundary.

 Actors are outside of the boundary.

 Represented as a box.

Connection

 Connection is an association between an actor and a use case.

 Depicts a usage relationship.

 Connection does not indicate data flow.

 Actors are connected to use cases with lines.

 Use cases are connected to each other with arrows.

Extend Relationship

 An association between two use cases where one adds new behaviors or actions
to the other.

 Extends a use case by adding new behavior or actions.

 Specialized use case extends the general use case.

 Example: A "Request Book Extension" use case extends the "Borrow Book" use
case.

Include Relationship

 An association between two use cases where one use case uses the
functionality contained in the other.

 Indicates a use case that is used (invoked) by another use case.

 Links to general-purpose functions, used by many other use cases.

 Example: A "Process Payment" use case includes the "Validate Payment Details"
use case.

Use Case Specification Document

 Contains detailed specifications for a use case.

 Contents can be written as simple text or in a specified format.

 Step-by-step description of what must occur in a successful use case.

Levels of Use Case Description (Cockburn)

 White – as seen from clouds.

 Kite – “birds-eye view.”

 Blue – sea-level view.

 Fish – below sea-level.


 Black – bottom of the sea.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy