Point of Sale System Use Case Diagram

The use case diagram for POS system is used to show the processes involved when users invoke the software. It depicts the structure of the system behavior.

Additionally, the diagram consists of processes (use cases) and users or “actors”. It uses defined symbols to describe the overall flow of the system.

Check out the linked and suggested articles below to learn more about Diagrams and other topics.

Project Overview

Name:Point of Sale System Use Case Diagram
Users:Business Owner or Admin, and Employees.
Tools Used:Any Diagram tools that provide use case diagram symbols.
Project Overview

What is a Use Case Diagram?

The use case diagram for POS system shows the sample behavior of the software. It includes the project functions using use cases, actors, and their connections.

Moreover, the diagram assists you to define and organize project needs. This also provides a clear picture of the user and system relationships. Therefore, this diagram depicts the complex functions of a system including how the user reacts to it.

What is the Importance of POS use case diagram?

Helping the developers and businesses with system management is one of the importance of the UML use case diagram. It includes the procedures from the viewpoint of users.

Use case diagram for POS system

The designed POS system use case diagram has two main illustrations. These illustrations describe the system’s general and specific processes using include and extend.

POS (Point of Sale) System General Use Case Diagram

The general use case diagram for point of sale system shows the main functions of the system. It is based on the transactions done during the processing point of sale.

The general use case is the most common application of a use case diagram. The use case diagrams depict the system’s main components as well as the flow of information between them.

Use case diagram for point of sale system using Include and Extend

The use case diagram using include and extend is used to elaborate the proceeding diagrams. The terms include and extend in the use case diagram are known as indicators.

The label include indicates that the sub-processes of the main processes must be included to complete the task. Extend, on the other hand, declares that the sub-processes can only be performed when needed.

Manage Purchasing’s Information and Status Use Case Diagram

This is where the admin manages the important information of the purchasing that will serve as a basis during the sales processing and monitoring. This information will be based on the customers’ purchases.

Manage Purchasing’s Information and Status Use Case Diagram

Manage Products Info and Status Use Case Diagram

This process involves the encoding of the basic information of each product offered to determine the price and the count of the sales.

Point of Sale (POS) System UML Use Case Diagram
Manage Products Info and Status Use Case Diagram

Manage Sales Information Use Case Diagram

It explains how the admin manages all the transactions that are related to the sales and determines the count of product sales on a certain date. The system needs to automate the monitoring of sales per purchase.

Point of Sale (POS) System Use Case Diagram
Manage Sales Information Use Case Diagram

You can add more to this illustration and it is up to you how will you create your diagram. But make sure to have precise information and consider the included use cases.

Use Case Diagram for POS (Point of Sale) System Pdf

How to draw a Use Case Diagram?

Time needed: 2 minutes

Here’s the complete guide on how to draw a use case diagram for POS system.

  • Step 1: Familiarize Use Case Diagram Symbols

    For beginners, you need to familiarize first with use case symbols to be used.

  • Step 2: Determine the system processes

    The next step is to determine the system’s processes. They will be the use cases of your project.

    You may ask the users about the typical activities done in point of sale management.

  • Step 3: Analyze the use cases included

    The gathered information from the users needs to be evaluated to know the general use cases.

    From the general use cases, you will see the sub-cases that are included. But, only include the useful processes related to the POS system.

  • Step 4: Plot the Use Case Diagram

    To plot the diagram you will need the users, use cases, container (scope), and their indicators (association). You will base the flow of use cases on the evaluated information from the users.

    Your first move is to place the users involved.

    Next, put the container in the plotted diagram to separate the objects (users and system) scope.

    Then place the use cases of the point of sale management.

    Finally, you need to map out the association of the use cases to show the interactions between the user/s and the system.


One of the methods that contribute to point of sales system development is the UML use case diagram. It helps developers know the possible inputs that the project should process and perform.

Furthermore, you will find out the needed processes and connect them to the other UML Diagrams. The diagram is also applicable in modeling the software’s use cases (processes). It captures the system’s flow from one process to the next.


If you have concerns about the Use Case Diagram for POS (Point of Sale) System, just leave us your comments below.

Leave a Comment