Exp.NO.

1 Date: 10-01-2025

Study of Unified Modelling Language

Unified Modelling Language (UML)

Unified Modeling Language (UML) is a general-purpose modeling language. The main aim of UML is to
define a standard way to visualize the way a system has been designed. It is quite similar to blueprints used
in other fields of engineering. UML is not a programming language, it is rather a visual language.

What is UML?
Unified Modeling Language (UML) is a standardized visual modeling language that is a versatile, flexible,
and user-friendly method for visualizing a system’s design. Software system artifacts can be specified,
visualized, built, and documented with the use of UML.
• We use UML diagrams to show the behavior and structure of a system.
• UML helps software engineers, businessmen, and system architects with modeling, design, and
analysis.

Why do we need UML?

We need UML (Unified Modeling Language) to visually represent and communicate complex system
designs, facilitating better understanding and collaboration among stakeholders. Below is why we need
UML:
• Complex applications need collaboration and planning from multiple teams and hence require a clear
and concise way to communicate amongst them.
• Businessmen do not understand code. So UML becomes essential to communicate with non-
programmers about essential requirements, functionalities, and processes of the system.
• A lot of time is saved down the line when teams can visualize processes, user interactions, and the
static structure of the system.

Types of UML Diagrams

UML is linked with object-oriented design and analysis. UML makes use of elements and forms associations
between them to form diagrams. Diagrams in UML can be broadly classified as:

1
VELLORESYED ARIFULLA
2022BCSE07AED435
Structural UML Diagrams
Structural UML diagrams are visual representations that depict the static aspects of a system, including its
classes, objects, components, and their relationships, providing a clear view of the system’s architecture.
Structural UML diagrams include the following types:

Class Diagram
The most widely use UML diagram is the class diagram. It is the building block of all object oriented
software systems. We use class diagrams to depict the static structure of a system by showing system’s
classes, their methods and attributes. Class diagrams also help us identify relationship between different
classes or objects.

Deployment Diagram
Deployment Diagrams are used to represent system hardware and its software. It tells us what hardware
components exist and what software components run on them.
• We illustrate system architecture as distribution of software artifacts over distributed targets.
• An artifact is the information that is generated by system software.
• They are primarily used when a software is being used, distributed or deployed over multiple
machines with different configurations.

2
VELLORESYED ARIFULLA
2022BCSE07AED435
State Machine Diagrams
A state diagram is used to represent the condition of the system or part of the system at finite instances of
time. It’s a behavioral diagram and it represents the behavior using finite state transitions.
• State diagrams are also referred to as State machines and State-chart Diagrams
• These terms are often used interchangeably. So simply, a state diagram is used to model the dynamic
behavior of a class in response to time and changing external stimuli.

State Machine Diagram

Activity Diagrams
We use Activity Diagrams to illustrate the flow of control in a system. We can also use an activity diagram
to refer to the steps involved in the execution of a use case.
• We model sequential and concurrent activities using activity diagrams. So, we basically depict
workflows visually using an activity diagram.
• An activity diagram focuses on condition of flow and the sequence in which it happens.
• We describe or depict what causes a particular event using an activity diagram.

3
VELLORESYED ARIFULLA
2022BCSE07AED435
Use Case Diagrams
Use Case Diagrams are used to depict the functionality of a system or a part of a system. They are widely

used to illustrate the functional requirements of the system and its interaction with external agents(actors).
• A use case is basically a diagram representing different scenarios where the system can be used.
• A use case diagram gives us a high level view of what the system or a part of the system does
without going into implementation details.

Sequence Diagram
A sequence diagram simply depicts interaction between objects in a sequential order i.e. the order in which
these interactions take place.
• We can also use the terms event diagrams or event scenarios to refer to a sequence diagram.
• Sequence diagrams describe how and in what order the objects in a system function.
• These diagrams are widely used by businessmen and software developers to document and
understand requirements for new and existing systems.

4
VELLORESYED ARIFULLA
2022BCSE07AED435
Collaboration Diagrams
Collaboration Diagram is a type of Interaction Diagram that visualizes the interactions and relationships
between objects in a system. It shows how objects collaborate to achieve a specific task or behavior.
Collaboration diagrams are used to model the dynamic behavior of a system and illustrate the flow of
messages between objects during a particular scenario or use case.
A collaboration diagram is a behavioral UML diagram which is also referred to as a communication
diagram. It illustrates how objects or components interact with each other to achieve specific tasks or
scenarios within a system.

AgroUML
Overview
AgroUML is an open-source UML modeling tool designed for simplicity and flexibility. It supports all
standard UML diagrams and aims to provide a lightweight alternative to other UML modeling tools.

Key Features
• Platform Independence: Built using Java, AgroUML is cross-platform and can run on Windows,
Linux, and macOS.
• Standard UML Support: Provides support for Use Case Diagrams, Class Diagrams, Sequence
Diagrams, State Diagrams, and Activity Diagrams.
• Lightweight: Minimal resource usage, making it suitable for older systems or low-end devices.
• Customizations: Allows for the addition of plugins and extensions to extend functionality.
• Open Source: Completely free and modifiable under an open-source license.

Advantages
• Cost-effective due to its open-source nature.
• Simple and intuitive interface for beginners.
5
VELLORESYED ARIFULLA
2022BCSE07AED435
 • Cross-platform compatibility.

Limitations
• Outdated user interface compared to modern tools.
• Lacks advanced features like real-time collaboration and integration with other development tools.
• Limited community support and updates.

Best Use Cases

• Educational purposes for beginners learning UML.
• Quick and simple UML modeling for small to medium projects.

StarUML
Overview
StarUML is a robust, feature-rich UML modeling tool widely used for enterprise-level software design and
architecture. It focuses on providing modern UML support with advanced functionalities.
Key Features
• Comprehensive UML Support: Supports all UML 2.x diagrams and SysML diagrams for complex
system modeling.
• Extensibility: Offers extensions through plugins to enhance its functionality.
• Modern Interface: Provides a clean and intuitive user interface.
• Code Generation: Supports automatic code generation for several programming languages,
including Java, C++, and Python.
• Collaboration: Enables team collaboration with version control and integration with tools like Git.
Advantages
• Highly customizable with plugins and scripting capabilities.
• Advanced tools for software architects and developers.
• Supports reverse engineering from code to models.
• Regular updates and active community support.
Limitations
• Commercial tool with a license fee for full functionality.
• Requires more system resources compared to AgroUML.
• Steeper learning curve for beginners.
Best Use Cases
• Large-scale software projects requiring detailed UML diagrams.
• Collaborative projects with integration into version control systems.
• Teams that require reverse engineering and code generation.
6
VELLORESYED ARIFULLA
2022BCSE07AED435
 Exp.NO.2 Date: 10-01-2025

Project Title: Start system management

I. Problem Statement
In today's fast-paced business environment, organizations face challenges in efficiently managing and
coordinating system processes. The lack of a centralized platform leads to issues such as:
Inefficient Task Management: Without a unified system, assigning, tracking, and completing tasks becomes
cumbersome, resulting in missed deadlines and decreased productivity.
Poor Resource Allocation: The absence of a centralized resource management system leads to suboptimal
utilization of assets, causing bottlenecks and increased operational costs.
Communication Gaps: Disjointed communication channels hinder collaboration among team members,
leading to misunderstandings and project delays.
Lack of Real-Time Monitoring: Without real-time insights into system performance and project progress,
decision-making is delayed, affecting overall efficiency.
To address these challenges, the System Management Project aims to develop a centralized platform that
streamlines operations, automates routine tasks, optimizes resource allocation, and enhances team
collaboration.

7
VELLORESYED ARIFULLA
2022BCSE07AED435
 Exp.NO.3 Date: 10-01-2025

Project Title: Start system management

II. Software Requirement Specification (SRS)

1. Introduction
Purpose: Develop a platform to manage tasks, allocate resources, and improve team collaboration.
Scope: Integrates task management, resource allocation, communication, and real-time monitoring.

2. Functional Requirements
User Management: Role-based access, user registration, and profile management.
Task Management: Create, assign, and track tasks with deadlines.
Resource Allocation: Manage and track resources (personnel, budget, etc.).
Real-Time Monitoring: Dashboards and reports.

3. Non-Functional Requirements
Performance: Support multiple users with minimal latency.
Security: Data encryption and access control.
Scalability: Ability to scale with user growth.
Reliability: High availability with backups.

4. System Architecture
Frontend: React.js.
Backend: Node.js or Django/Flask.
Database: PostgreSQL/MongoDB.

8
VELLORESYED ARIFULLA
2022BCSE07AED435