UML Models: Use Case Diagrams and Sequence Diagrams for Retail

This assignment presents UML models, focusing on use case and sequence diagrams applied to retail scenarios. The student has created use case diagrams for three functionalities: notifying customers about current sales, displaying reminders for online order pickups, and displaying store locations. Each use case includes details such as goal, scope, preconditions, success and failure end conditions, actors, trigger, and a step-by-step description. The assignment also outlines extensions, sub-variations, and related information, such as priority, frequency, and channels to actors. Finally, the assignment includes sequence diagrams for the described use cases, providing a visual representation of the interactions between system components and actors. This detailed analysis of the retail system functionality using UML diagrams demonstrates an understanding of software design principles and system modeling.

Running head: UML MODELS
UML Models
Name of the Student:
Name of the University:
Author Note

1
UML MODELS
Domail Model

2
UML MODELS
Data Flow Diagram

3
UML MODELS
Uses Case Overview

4
UML MODELS
Use Case Description
Notify about current sales
USE CASE # Notify about current sales
Goal in Context To provided notoification to the custometr about the current
oning in in the store
Scope & Level The system should be able to provide the customer with the
infromation about the sale going on cureemtly in the
adjoining location.
The sale infromation is the be updated in the system by the
store staff.
Preconditions The cutomer is already logged in.
Success End
Condition
Successful reception of the notification
Failed End
Condition
Unsecusseful delivery of the notification
Primary,
Secondary
Actors
Customer is the primary actor
Staffs are the secondary actor
Trigger The system automatically dipaches the notification once the
the infromation is uploaded in the system.
DESCRIPTION Step Action
1 Log in to the system.
2 Set up location.
3 Revcieve infromation
EXTENSIONS Step Branching Action
1a <condition causing branching> :

5
UML MODELS
<action or name of sub.use case>
SUB-
VARIATIONS
Branching Action
1 <list of variation s>
RELATED
INFORMATION
Notify about current sales
Priority: Medium
Performance High
Frequency Less Frequency
Channels to actors The customers are to notified vai mail
OPEN ISSUES <list of issues awaiting decision affecting this use case >
Due Date After the infromation has been uploaded
...any other
management
information...
Superordinates <optional, name of use case(s) that includes this one>
Subordinates <optional, depending on tools, links to sub.use cases>
Display the reminder to pick-up online order
USE CASE # Display the reminder to pick-up online order
Goal in Context To provide reminder to the cutomerf for picking up the item.

6
UML MODELS
Scope & Level The system should be able to provide the customer with the
infromation location of pick up of the item.
The pick up oder is the uploade to the system by the staffs in
the store
Preconditions The cutomer is already logged in.
The item is available for the cutomer.
Success End
Condition
Successful reception of the product
Failed End
Condition
Unsecusseful delivery of the product
Primary,
Secondary
Actors
Customer is the primary actor
Staffs are the secondary actor
Trigger The system automatically dipaches the notification once the
the infromation is uploaded in the system.
DESCRIPTION Step Action
1 Log in to the system.
2 Set up location.
3 Revcieve infromation pick up location
4 Pick up product
EXTENSIONS Step Branching Action
1a <condition causing branching> :
<action or name of sub.use case>
SUB-
VARIATIONS
Branching Action
1 <list of variation s>

7
UML MODELS
RELATED
INFORMATION
Display the reminder to pick-up online order
Priority: High
Performance High
Frequency Very Frequency
Channels to actors The customers are to notified via mail
OPEN ISSUES <list of issues awaiting decision affecting this use case >
Due Date One day before the delivery date of the product is the due
date
...any other
management
information...
Superordinates <optional, name of use case(s) that includes this one>
Subordinates <optional, depending on tools, links to sub.use cases>
Display the location of a store
USE CASE # Display the location of a store
Goal in Context To provide store location to the customer
Scope & Level The system should be able to provide the customer with the
infromation about the stores curemtly of the adjoining
location.
The store details is the be updated in the system by the store
staff.
Preconditions The cutomer is already logged in.
Success End Successful reception of the notification

8
UML MODELS
Condition
Failed End
Condition
Unsecusseful delivery of the notification
Primary,
Secondary
Actors
Customer is the primary actor
Staffs are the secondary actor
Trigger The system automatically dipaches the notification once the
the infromation is uploaded in the system.
DESCRIPTION Step Action
1 Log in to the system.
2 Set up location.
3 Revcieve store location
EXTENSIONS Step Branching Action
1a <condition causing branching> :
<action or name of sub.use case>
SUB-
VARIATIONS
Branching Action
1 <list of variation s>
RELATED
INFORMATION
Display the location of a store
Priority: Medium
Performance High
Frequency Less Frequency
Channels to actors The customers are to notified vai mail

9
UML MODELS
OPEN ISSUES <list of issues awaiting decision affecting this use case >
Due Date After the store infromation has been uploaded
...any other
management
information...
Superordinates <optional, name of use case(s) that includes this one>
Subordinates <optional, depending on tools, links to sub.use cases>
Secquence Diagram
Notify about current sales
Display the reminder to pick-up online order

10
UML MODELS
Display the location of a store