Face Recognition Attendance System Use Case Diagram

Face Recognition Attendance System Use Case Diagram (UML)

The Use Case Diagram is a structural illustration of Face Recognition Attendance System’s processes that helps programmers in its development. Use Case Diagram shows the processes included in Face Recognition Attendance System as well as its users. It serves as blueprint or core of the said system that will be the basis for building it.

Face Recognition Attendance System Use Case Diagram: Content

The table shows the overview of the face recognition attendance system use case diagram. It tells the overall content of the article to let you know what is the discussion all about.

Name:Face Recognition Attendance System
Abstract:The use-case diagram in UML represents the behavior of the face recognition system and aids in capturing its requirements. It describes a system’s high-level functions and scope. The interactions between the system and its actors are also depicted in these diagrams.
UML Diagram:Use Case Diagram
Users:Establishment’s Admin, Employee/Authorized Personnel, Students or Employees.
Tools Used:Diagram tools that provide activity diagram symbols.
Face Recognition Attendance System Use Case Diagram: Content

What is Use Case Diagram?

A use case diagram is a visual representation of how a user might interact with a program. A use case diagram depicts the system’s numerous use cases and different sorts of users. The circles or ellipses are used to depict the use cases. The features of the system depend on its users of it. So it is a must that you determine the users of the face recognition attendance system so you could make its Use Case Diagram smoothly.

ERP Production Planning Module Deta... x
ERP Production Planning Module Details

To emphasize the connection of every process, it has arrows labeled with include and extend. The arrows labeled with “<<include>>” or “<<extend>>” are called association. An arrow labeled “include” is used to indicate that the proceeding process after another is needed to complete a task. While the label “extend” is an optional process but still part of a task.

By creating the use case of the Face Recognition System, you must determine first the possible features to identify the flow of the system. After that, you can now create the blueprint or core of the system function.

Face Recognition Attendance System Project Use Case Diagram

Here’s the designed Use Case Diagram that you can use for Face Recognition Attendance System development. This designed Face Recognition System Use Case Diagram has two main illustrations to let you know its general processes and its specific processes.

Face Recognition Attendance System General Use Case Diagram – This diagram shows the general processes or functions that the system could do and is based on the transactions needed in doing or conducting an Attendance checking using Face Recognition.

General Use Case Diagram for Face Recognition Attendance System
Face Recognition Attendance System General Use Case Diagram

Face Recognition Attendance System Specified Use Case Diagram – this illustration has a more detailed figure of use case diagram using include and Extend. This is to help you specify the included activities in completing a process or task. That will also help users determine the right way of managing the Face Recognition Attendance System.

Use Case Diagram for Face Detection Recognition System
Face Recognition Attendance System Specified Use Case Diagram

The role of this Use case Diagram using the include and Extend label is to inform your readers and users that some tasks and processes may be completed without invoking all the subtasks. They were only used when they were called or needed.

How to create a Use Case Diagram for Library Management System

Time needed: 5 minutes.

Steps in creating a Use Case Diagram for Library Management System.

  • Step 1: Familiarize Use Case Diagram Symbols

    Use Case Diagram Symbols – are used to create a Use Case Diagram which was presented here. Their symbols and applications must be familiarized before you build the Use Case Diagram.

    • Use Cases – Ovals with a horizontal shape symbolize the various uses that a user might have.
    • Actors (Users) – Stick figures depict people that are using the use cases.
    • Indicators (Association) – are used to know the connection of the system’s function or processes with another process. Its vital role is to figure out which actors are linked to and which use cases are in complex graphs.
    • Container – is a box that limits the scope of a system to specific use situations. Situations, where the system is used outside of the box, would be deemed outside of the system’s scope. In the chainsaw example below, “Psycho Killer” is outside the scope of vocations.

    Each of these use case diagram symbols shows the overall system structure. Emphasizing the System’s structure would be much easier by using these Use Case Diagram symbols.

  • Step 2: Determine the targeted users

    After the symbol familiarization, you’ll need to determine your targeted users. Your targeted users will be the ones to use your project.

    Your project is Library Management System for school, then your users would be the Librarian, Admin, and the students. You may ask them about the common activities that they do when doing tasks in library management. This information will help you in proceeding with the next step.

  • Step 3: Analyze the use cases included

    Analyzation is very important in creating a use case diagram. It will help you understand the work of the diagram and avoid unwanted errors.

    The gathered information from the targeted users is very useful in creating a use case diagram. You just need to evaluate these data and pick the general use cases.

    From the general use cases, you will see the sub-cases that are included in them. But only include the useful processes and circumstances related to the library system. Then you’re ready for the next step.

  • Step 4: Plot the Use Case Diagram

    To plot the use case 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 to have the exact Use Case Diagram.

    To plot your diagram, you need to place first the users involved and the process they will perform.

    Then place the figured use cases included in doing the process.

    After that, you will trace the association of the use cases to know the series of interactions between the user/s and the system.

    Finally, you put the container in the plotted diagram to separate the objects’ (users and system) scope. This is to identify what are the processes that are under them or should be performed.

Additional Knowledge

The objective of a use case diagram is to show the interactions of numerous items called actors with the use case and to capture the fundamental functionalities of a system. As you see through the diagrams, there are the use cases involved to define the core functions of a system. These processes were expected by the users to be connected to produce a certain output. Being a programmer, this could be an important role that the Face Recognition Attendance System General Use Case Diagram should have.

But before the system development, you have to create first its essential blueprint such as the use case diagram. The illustration of the use case diagram is complex and you can emphasize it better with the Use case Description. It is a table explaining the series of processes in the System when a user or the admin uses the Face Recognition Attendance System.

In addition to that thought, developing the Face Recognition Attendance System would be much easier with the use of complete UML Diagrams that can also be found at our site! These are the DFD, ERD, Activity Diagram, and many more.


The Face Recognition Attendance System development will not be completed without having its UML Diagrams. This article is not just about the use case diagrams but also about the other UML Diagrams. This is to make your software development easier and achieve a well-built project. We at ITsourcecode continue to discover more ideas and techniques to help you with your project development.

So that completes our discussion fellas! And I hope that this article will help you a lot. Now let me ask you something. What have you learned through the discussion? May this article help you with your projects in the future!


If you have inquiries or suggestions about Use Case Diagram and Description for Face Recognition System just leave us your comments below.

Keep us updated and Good day!

Leave a Comment