UML Diagrams and Modelling: A Comprehensive Report on Use Case, Activity, Sequence, and Class Diagrams

In this report we will discuss about UML diagrams & modelling report and below are the summaries point:- Use Case Diagram: Describes the system's functions, including login, new user registration, password recovery, issue selection, complaint registration, and complaint updates. Activity Diagrams: Illustrate the flow control and activities performed by the system, helping visualize the system's dynamic parts and constructing executable applications. Sequence Diagram: Depicts the communication flow between objects in sequential order, showing how they interact and communicate with each other.

Running head: UML DIAGRAMS AND MODELLING REPORT
UML Diagrams and Modelling Report
Name of the Student
Name of the University
Author Note

1UML DIAGRAMS AND MODELLING REPORT
Use Case Diagram:
The use case diagram is the mixture of use cases of a given system. The use case
depicts the single function of a system. The use case diagram help the user to understand the
program. Use Case Diagram are generally stated as behaviour diagram. The use diagram is
generally used to describe the set of actions used to perform for external users. The use cases
used in this report are as follow:
Login: The admin, client and the technicians would login into the system.
New User: if the client is not already a member of the system then the client has to sign up.
Forget password: If the user forgot the password then he has to click the forgor password link
and follow the instructions to recover the account.
Select Issue: The user has to then select an issue for which the complaint will be registered.
Complaint Register: The complaint will be registered in the complaint register.
Update Complaint: The complaint will be updated by the user in case if any update hass to be
made.

2UML DIAGRAMS AND MODELLING REPORT
Activity Diagrams:
The activity diagram is the combination of activities of the given system. An activity
is defined as the function that is performed by the system. The activity diagram is used to
depict the flow control of the system. Activity Diagram is another imperative outline in UML
to portray the dynamic parts of the framework. The control stream is attracted starting with
one activity then onto the next. Activity diagram mainly contains flowchart of the activities
that are performed by the system. The activities in the system is itself the main part of the

3UML DIAGRAMS AND MODELLING REPORT
activity diagram. It is not only used to depict the visual part but also to construct the
executable application. The basic use of the activity diagram is to draw the flow of control in
the system. This project need three-activity diagram because there are various parts and flow
of system.

4UML DIAGRAMS AND MODELLING REPORT

5UML DIAGRAMS AND MODELLING REPORT
Sequence Diagram:
A communication diagram describes how they operates with each other and in what
order. The parallel vertical lines (lifelines) describes various processes are performed
simultaneously and as horizontally arrow, show the message communication between the
orders they occur in. The sequence diagram in simple draws the communication flow
between the objects in sequential order. The actors in the sequence diagrams represent the
user. The Lifeline represent individual participant in the sequence diagram. The sequence
diagram is primarily used to show the communication between the object and the use cases.
The sequence diagram is used to show details of the use case diagram. The sequence diagram

6UML DIAGRAMS AND MODELLING REPORT
are also used to understand the full functionality of the future application. The sending and
receiving the messages is known as Communication.

7UML DIAGRAMS AND MODELLING REPORT
Domain Class Diagram:
The domain class diagram is the static diagram, which is used to represent the image
of the program. The domain class diagram can also be used for creating the executable code
of the of except for the visualization, description and documentation of the software. The
class diagram is also known as structural diagram. The main use of the structural diagram is
to depict the static view of the application. The class diagram is used to provide an overview
of the desired application by depicting the objects and classes that are present inside the
system. The class diagram provide different usage, like modelling the system and detailed
design of the desired application.

8UML DIAGRAMS AND MODELLING REPORT
State Machine Diagram:
The state machine diagram is also known as the State Chart Diagram. It depicts the
flow of control from one state to the other state. The state is defined as the change of
condition of an object from its creation until the termination. The chart diagram is similar to
the activity diagram of the system. The state machine diagram show the possible transition of
a system in various states. The state machine diagram is the behaviour diagram that depicts
the behaviour of the desired system through limited state transformations.

9UML DIAGRAMS AND MODELLING REPORT
User Interface Diagram:
The User Interface Diagrams are the best ways of designing the user interface. These
are used for one of two purposes. The First, they are used to model the communication
between the user and the application. Second, they allow the user to gain the high level
overview of the UI (user interface). The UI designs needs a good understanding of the user
needs. There are a few stages and procedures in the UI structure, some of which are more
requested upon than others, depending upon the project. The desire to develop application
based on specific UI issues in software development. In addition to the prototype, the
literature gives new solutions such as the experimental mixed prototype.

10UML DIAGRAMS AND MODELLING REPORT
The above snapshot shows the user interface diagram of the IT Solutions homepage.
The above snapshot show the issue page of the IT Solutions.

11UML DIAGRAMS AND MODELLING REPORT
The above snapshot show the upadte complaint page of the It Solutions.
Conclusion:
The report can be concluded by stating that the UML specification is the main part that
ensured that the completeness of an information system. The above work concludes that the
UML diagram is a powerful modelling knowledge that helps to solve the scientific problems.
Mapping and designing is the important process of system software development. The
mixture of all modules in one applications will ensures that it will create a perfect platform.
UML class charts are valuable when displaying business information. By precisely
demonstrating characteristics and relationship of class substances, we can undoubtedly
outline class graph particulars to element beans with CMP. Moreover, assortment
documentation decides the right kind for relationship fields, life cycle issues, and formatting
delete attributes.

12UML DIAGRAMS AND MODELLING REPORT
Biblography:
Vyatkin, Software engineering in industrial automation: State-of-the-art review. IEEE Transactions on
Industrial Informatics(Thomas Reuters, 5th ed,2013).
Zielstra, Hochmair and Neis, Assessing the Effect of Data Imports on the Completeness of
OpenStreetMap–A United States Case Study. Transactions in GIS(Hochmair, 7th ed,2013)
Ouchani, Mohamed and Debbabi, M. (2013, September). A probabilistic verification framework of
SysML activity diagrams. In Intelligent Software Methodologies, Tools and Techniques (SoMeT),
IEEE(Debbabi, 6th ed,2013)
Al-alshuhai and Siewe. An extension of UML activity diagram to model the behaviour of context-aware
systems. In Computer and Information Technology; Ubiquitous Computing and Communications;
Dependable, Autonomic and Secure Computing; Pervasive Intelligence and Computing
(CIT/IUCC/DASC/PICOM) (Edward, 5th ed, 2015).
Merah, Messaoudi, Saidi and Chaoui, A. Design of ATL rules for transforming UML 2 communication
diagrams into buchi automata. International Journal of Software Engineering & Its Applications.
(Martin, 6th ed, 2015)
Nikiforova, Ahilcenoka, Ungurs, Gusarovs and Kozacenko, L. Several Issues on the Layout of the
UML Sequence and Class Diagram. In Proc. of the 9th Int. Conf. on Software Engineering
Advances(Oceana Publications, 4th ed, 2016)
Zhou, Baresi and Rossi. Towards a formal semantics for UML/MARTE state machines based on
hierarchical timed automata. Journal of Computer Science and Technology(Cohn ,5th ed,2015)
Jouault and Delatour Towards Fixing Sketchy UML Models by Leveraging Textual Notations:
Application to Real-Time Embedded Systems.(Paul ,6th ed,2016).