UML diagrams for the Help Desk Ticket System. Following are the different UML diagrams like Components, Activity, Use Case, and Sequence diagrams of the Help Desk Ticket System.
With the help of these diagrams, one can get a better understanding of the project.
UML Diagram for Help Desk Ticket System
We’ve compiled structural UML diagrams i.e. component diagrams, and three types of behavioural UML diagrams i.e. Activity, Sequence, and Use Case diagrams for the Help Desk Ticket System. We have also explained the data flow diagram (DFD) for this project.
Here, we have multi-user, who will be interacting with the system. With the help of these diagrams, one can get a better understanding of the project. This web application is developed to provide users with an online medium where they can users can share their Tickets. Admin is who will manage the overall application; whereas the user or customers can raise tickets.
Component diagram for Help Desk Ticket System
The component diagram below shows the structural relations between components in a Help Desk Ticket System. The connected components by lines represent relationships within the systems. In the diagram, it can be seen that there are components namely product, order, customer, and account.
This is a web application developed for users to raise a ticket. Then, the admin of the site will view the details of the raised ticket. In this application, there are majorly two roles. One is the Admin who will manage the overall application like viewing tickets, closing tickets, etc. Here, the user is the role that will raise tickets.
Activity diagram for Help Desk Ticket System
Activity diagrams in UML display the functionalities of various activities and flow in management processes and software systems. The flow in the activity diagram can be sequential, branched, or concurrent.
Admin will be responsible for managing the system. On the other hand, Customers can register, log in using the login credentials, and view and raise tickets. Admin can just add products detail and customers can view them and give their valuable feedback.
Sequence diagram for Help Desk Ticket System
Sequence diagrams in UML are used to illustrate the sequence of messages between objects in an interaction. A sequence diagram consists of a group of objects that are represented by lifelines and the messages that they exchange overtime during the interaction.
Admin can View/Add/Remove products, manage tickets raised, customers, etc. Admin will be responsible to view raised tickets and solve them. Users can VIEW/UPDATE/DELETE tickets raised.
Use Case Diagram for Help Desk Ticket System
A UML use case diagram can create a broad, high-level view of the relationship between use cases, actors involved, and systems being performed.
As you can see from the examples below, use cases are represented by oval shapes, and the lines then show at which point an actor/user participates and interacts with their corresponding use case.
Admin will be able to access category, User list, and Raised Ticket use cases whereas, user can raise a ticket, view status, etc. Login, Logout, and My Profile use cases are accessible to both users.
DFD Diagram for Help Desk Ticket System
A data flow diagram represents the flow of information for any process or system. It shows the system with its relationship to external entities.
After logging in, Admin will land on the home page where they can manage their profiles. Admin can add, view categories, view raised tickets, manage user lists, etc. Whereas, users can raise tickets, check the status of their raised tickets, manage their profiles, change passwords, etc.
