UML – Unified Modeling Language

UML – Unified Modeling Language
Introduction:
       UML (Unified Modeling Language) is a standard visual modeling language used to visualize, specify, design, and document software systems.
UML helps software developers and designers understand a system before writing the actual code. It represents the structure, behavior, and interactions of a system using different types of diagrams.
Types of UML Diagrams :
UML diagrams are mainly divided into two types :
Structural Diagrams :
        Structural diagrams represent the static structure of a software system. They show the different elements of a system and the relationships between them.
The main structural diagrams are:
 Class Diagram – Shows classes, attributes, methods, and relationships.
 Object Diagram – Shows objects and their relationships.
 Component Diagram – Shows software components and their dependencies.
 Deployment Diagram – Shows the physical deployment of software on hardware.
 Package Diagram – Shows packages and their dependencies.
 Composite Structure Diagram – Shows the internal structure of a class or component.
 Profile Diagram – Shows UML extensions and customizations.
Behavioral Diagrams :
        Behavioral diagrams represent the dynamic behavior of a software system. They show how the system works and how different elements interact with each other.
The main behavioral diagrams are:
 Use Case Diagram – Shows interactions between users and the system.
 Activity Diagram – Shows the workflow of activities.
 Sequence Diagram – Shows the sequence of messages between objects.
 Communication Diagram – Shows communication between objects.
 State Machine Diagram – Shows the different states of an object.
 Interaction Overview Diagram – Gives an overview of interactions.
 Timing Diagram – Shows changes in behavior with respect to time.
UML Views :
        A UML View represents a software system from a particular perspective. It helps developers and designers understand different aspects of a system, such as its requirements, structure, behavior, implementation, and deployment.
The UML View is divided into five views.
The five views are:
 Use Case View 
 Design / Logical View 
 Process View 
 Implementation
 Deployment / Physical View

Use Case Diagram for Passport Management System

      A Use Case Diagram in UML shows how users interact with a system. In a Passport Management System, it shows the interaction between users (actors) and the system functions (use cases), such as applying for a passport, uploading documents, tracking application status, verifying documents, approving applications, and issuing passports. It helps us understand how the system works and what services it provides in a simple and clear way.
What is a Use case diagram?
    Use Case Diagram, referred to as a Behavior model or diagram. It simply describes and displays the relationship or interaction between the users or customers and providers of the application service or the system. It describes different actions that a system performs in collaboration to achieve something with one or more users of the system. A use-case diagram is used a lot nowadays to manage the system.
Use Case Diagram Notations
Use Case Diagram consists of the following components:
Actor: Actors are external entities that interact with the system. These can include users, other systems, or hardware devices. In the context of a Use Case Diagram, actors initiate use cases and receive the outcomes. 
Case: Use cases are like scenes in the play. They represent specific things your system can do.
System Boundary: The system boundary is a visual representation of the scope or limits of the system you are modeling. It defines what is inside the system and what is outside. 
Relationships: Relationships are represented by lines between actors and use cases. There are three types of relationships in use case diagrams:

Association: An association shows that an actor interacts with a specific use case. It is represented by a solid line.
 
Generalization: A generalization shows that one use case is a more specific version of another use case. It is represented by a solid line with a triangle pointing to the more general use case.
 
Include: An include shows that one use case includes another use case as a step in its process. It is represented by a dotted line with an arrow pointing to the included use case.

 
Use Case Diagram for Passport Management System
      
        The Use Case Diagram shows how the users interact with the Passport Management System.
Actors:
 Applicant 
 Passport Officer 
 Police Officer 
 Administrator
Use Cases:
 Register 
 Login 
 Apply for Passport 
 Upload Documents 
 Verify Documents 
 Schedule Appointment 
 Track Application Status 
 Police Verification 
 Approve/Reject Application 
 Issue Passport 
 Renew Passport 
 Update Passport Details
System Boundary:
 The system boundary contains all the above use cases. It represents the functions of the Passport Management System.

Passport Management System – Use Case Diagram

Explanation of Use Case Diagram of a Passport Management System 
Here, we will understand the designing use case diagram for the Passport Management System. Some scenarios of the system are as follows:
1. A person who wants to apply for a passport for the first time is considered a New Applicant. A person who already has an account or an existing passport is considered an Existing Applicant. 
2. A New Applicant must register in the system by providing the required personal details. After successful registration, the applicant can log in to the system. 
3. After logging in, the Applicant can create a passport application by entering the required information. 
4. While creating the application, the applicant must upload the required documents, select a processing office or appointment slot, and submit the application with the required fee. These are important steps in the passport application process. 
5. After submitting the application, the applicant can check the application status at any time to track the progress of the passport application. 
6. If the applicant needs to renew an existing passport, the applicant can use the Apply for Renewal option. The Passport Officer then processes the renewal application. 
7. The Passport Officer processes the new application and verifies the submitted information and documents. Based on the verification, the officer can approve or reject the application. 
8. Before the passport is issued, the Police Department conducts police verification to verify the applicant's details. The verification result is then updated in the system with the police report. 
9. After successful application processing and required verification, the Passport Officer can issue the passport to the applicant. 
10. The System Administrator manages the system database, reviews action records, audits system logs, and configures system rules to ensure that the passport management system operates properly. 
11. If an application requires changes or additional information, the applicant can edit the application details or respond to a re-submission request as required. 
12. If a passport is lost or stolen, the applicant can use the Report Lost/Stolen Passport option to inform the system and update the relevant records.
Conclusion 
         The Passport Management System Use Case Diagram shows the interaction between the Applicant, Passport Officer, Police Officer, and Administrator. It explains the passport application process in a simple and clear way.
                                             Prepared by :-
                                      Madhavan S (24USC036)
                                    Dharanidharan C (24USC005)
                                          3rd B.Sc Computer science
                           Sri Ramakrishna Mission Vidyalaya College                                          of Arts and Science (SF Wing)
                                         Periyanaickenpalayam
                                           Coimbatore -641020
                                                  Tamil Nadu.

Comments

Popular posts from this blog

Role of Data Visualization in Decision-Making

Polynomial Addition Using an Array

Blockchain in Supply Chain Management