Developing Use Cases
Use Case :
A use case is a software and system engineering term that describes how a
user uses a system to accomplish a particular goal.
Step One – Define the set of actors.
Step Two – Develop use cases, where each one answers a set of questions.
Purpose of Use Case Diagram:
Use case diagrams are typically developed in the early
stage of development and people often apply use case
modeling .
• Specify the context of a system.
• Capture the requirements of a system.
• Validate a systems architecture.
• Drive implementation and generate test cases.
• Developed by analysts together with domain experts.
Questions: o
o
Who is the primary actor, the secondary actor(s)?
What are the actor’s goals?
o What preconditions should exist before the story begins?
o What main tasks or functions are performed by the actor?
o What exceptions might be considered as the story is described?
o What variations in the actor’s interaction are possible?
o What system information will the actor acquire, produce, or change?
o Will the actor have to inform the system about changes in the external
environment?
o What information does the actor desire from the system?
o Does the actor wish to be informed about unexpected changes?
Use Case Diagram at a Glance
A standard form of use case
diagram is defined in the
Unified Modeling Language
as shown in the Use Case
Diagram.
Use Case Diagram at a Glance (Contd)..
System:
The project that we are developing is a system.
System Name Helps in defining the scope of the project which
we are going to develop.
Example: Application software, website, software
component, business process etc.
Considering Example – (Swiggy).
Use Case Diagram at a Glance (Contd)..
Actor:
Actor are generally called users.
Knew to perform the action inside the system.
Example: Customer, admin, system related workers etc.
Generally there are two types of actors
• Primary actor – Initial user of the system (Swiggy
user).
•Secondary actor – Reactionary or More response to
the primary (Hotel or cook).
Primary actor are always shown on the left.
Secondary actors on the right.
Use Case Diagram at a Glance (Contd)..
System Name
Primary Actor Secondary Actor
Use Case Diagram at a Glance (Contd)..
Use Case :
Login
➔ List of tasks performed by actors
inside a system.
Search Hotels
➔ Denoted by oval shape.
Order Food ➔ Example: Login, Search hotel,
Order food, Make payment.
Make Payment
Use Case Diagram at a Glance (Contd)..
Login Login
Relationship :
<<Extended>>
<<include>>
Solid line between the actor and the use case.
Verify Display Error
message
Login There are three types of relationship
• Include relationship
Payment
• Extended relationship
Master • Generalisation or Inheritance
Visa Card
Swiggy
lu Enter
< inc
< >> Location
de < <
Login nd Ex
>> te
Not
Customer service
Search able
hotel or
food
Swiggy
Food sales
person
Payment
Track
Hotel
order
Chef
UML DIAGRAMS
Activity diagram
➔ Graphical representations of workflows of stepwise activities and actions
➔ Rounded rectangles represent actions;
➔ Diamonds represent decisions;
➔ Bars represent the start (split) or end (join) of concurrent activities;
➔ A black circle represents the start (initial state) of the workflow;
➔ An encircled black circle represents the end (final state).
Thanks!
