Index

S.No Title Page No.

1 Introduction 3

2 System Overview 4

3 EV Charge Station Components 5

4 UML Diagrams 6

4.1 Use Case Diagram 7

4.2 Class Diagram 8

4.3 Sequence Diagram 9

4.4 Activity Diagram 10

4.5 Deployment Diagram 11

EV Charging Station

1 Introduction 18

2 UML diagrams of EV Charging Station 21

Online Cab Reservation System

1 Introduction 26

2 UML Diagrams of online cab reservation system 39

UML
 Introduction to UML

UML stands for Unified Modelling Language, which is a graphical language used
for modelling software systems. It provides a standard set of notations and diagrams
that help developers to visualize, specify, construct, and document the software
systems.

UML was developed by Grady Booch, James Rumbaugh, and Ivar Jacobson in the
1990s as away to unify the different object-oriented methodologies that existed at
the time. Today, UML is widely used in software development and is considered the
de facto standard for modelling software systems.

UML is comprised of a set of diagrams, such as class diagrams, use case diagrams,
activity diagrams, sequence diagrams, and others. Each diagram provides a different
perspective on the software system being modelled, and together they form a
comprehensive view of the system.

Using UML, developers can communicate more effectively with stakeholders and
other developers, reduce misunderstandings, and ensure that everyone is on the same
page regarding the design and implementation of the software system.

UML is a widely used modelling language in software development because it

offers several benefits for developers, stakeholders, and the overall software
development process.

One of the primary benefits of UML is that it provides a standardized notation and
language for modelling software systems. This allows developers and stakeholders to
communicate more effectively and accurately, and reduces the risk of
misunderstandings or errors. Additionally, UML provides a range of diagrams and
notations that can be used to model various aspects of a software system, including
its structure, behavior, and interactions.
Another benefit of UML is that it promotes a modular and reusable approach to
software development. By using UML diagrams and notations to model software
systems, developers can create modular components that can be reused in different
contexts, reducing the time and effort required for software development.

UML also supports an iterative and incremental approach to software development,

allowing developers to easily modify and refine their models as they learn more
about the system being developed. This can help to reduce the risk of project failures
or delays and improve the overall quality of the software system.

Finally, UML is widely used in the software industry, and there are many tools and
resources available for developers to learn and use the language effectively. This
makes it easier for developers to collaborate on projects and share their work with
others in the industry.

Overall, UML offers many benefits for software development, including improved
communication, modularity, flexibility, and a standardized approach to modelling
software systems.

The Building Blocks of UML:

In UML, the building blocks are the basic elements that are used to model a
software system. The following are the building blocks in UML:

1. Class: It represents a template for creating objects that share common attributes,

operations, methods, and relationships. It is represented using a rectangle with

three compartments: name, attributes, and operations.

2. Object: It represents a specific instance of a class at runtime. It is represented

using a rectangle with the name of the object.

3. Interface: It represents a contract that specifies a set of methods that a class must
 implement. It is represented using a circle with the name of the interface.

4. Package: It is used to group related classes, interfaces, and other packages into a single

unit. It is represented using a rectangle with the name of the package.

5. Use case: It represents a specific functionality or feature that the system provides to its

users.

It is represented using an ellipse with the name of the use case.

6. Actor: It represents a person, system, or device that interacts with the system by using one
or more use cases. It is represented using a stick figure or a small icon.
7. Relationship: It represents a connection or association between two or more building
blocks.

The most common types of relationships in UML are inheritance, association, aggregation,
and composition.
Advantages of UML:

There are several advantages of using UML in software development:

1. Standardization: UML provides a standard set of notations and diagrams, which
helps to standardize the way software systems are modelled, designed, and
documented. This allows developers to communicate more effectively and reduces
the risk of misunderstandings and errors.
2. Visualization: UML provides graphical notations and diagrams that help to
visualize the software system and its components. This makes it easier for
developers to understand the system's structure and behavior, identify potential
issues, and make design decisions.
3. Communication: UML provides a common language for developers, stakeholders,
and other members of the software development team to communicate with each
other. This helps to ensure that everyone is on the same page regarding the design
and implementation of the software system.
4. Analysis: UML provides tools for analyzing the software system, such as
identifying potential problems, testing scenarios, and modelling system behavior.
This helps to identify and address potential issues early in the development process,
 reducing the risk of expensive changes later on.
5. Reusability: UML provides a way to model and document software systems that can
be easily reused in other projects. This helps to reduce development time and costs,
as well as improve the quality of software systems.
6. Evolution: UML allows developers to easily modify and evolve the software system
over time. By using UML diagrams and notations, developers can easily identify the
impact of changes and make informed decisions about how to modify the system.
7. Overall, UML provides a powerful set of tools for modelling, designing, and
documenting software systems. It helps to improve communication, reduce errors.

Relationships in UML:

In UML, relationships are used to represent the connections between elements in a

software system. There are several types of relationships in UML, including:

Sure, here is a point-wise description for each type of relationship in UML:

1. Association:
• Represents a connection between two elements.
• Shows how the elements are related and what type of relationship exists between them.
• Can have a name, direction, and multiplicity.

• Can be bidirectional or unidirectional.

2. Aggregation:
• Represents a "part-of" relationship between two elements.
• One element (the "part") is a component of the other element (the "whole").
• The "part" can exist independently of the "whole".
• Represented by a diamond symbol on the end of an association line pointing
towards the "whole" element.
3. Composition:
• Similar to aggregation, but with a stronger "part-of" relationship.
• The "part" element is a component of the "whole" element and cannot exist
 independently of it.
• Represented by a filled diamond symbol on the end of an association line
pointing towards the "whole" element.

4. Inheritance:
• Represents a "is-a" relationship between two elements.
• One element (the "subclass" or "derived" class) inherits the properties and
behavior of another element (the "superclass" or "base" class).
• The subclass can add its own properties and behavior in addition to those
Of the super class.

• Represented by an arrow pointing from the subclass to the superclass, with a

solid line and a hollow arrowhead.

5. Realization:

• Represents an implementation of an interface by a class or component.

• A realization is a specific way of implementing the functionality defined in an

interface.

• Represented by a dashed line with a hollow arrowhead pointing from the

implementing element to the interface.

6. Dependency:

• Represents a dependency between two elements.

• Changes to one element may affect the other element.

• The dependent element uses or depends on the independent element.
• Represented by a dashed line with an arrowhead pointing from the dependent
element to the independent element.
 UML DIAGRAMS:

Class Diagram:

• Describes the static structure of a system.

• Shows classes, interfaces, attributes, operations, and relationships between them.
• Represents the classes and their associations, which depict the overall system design.
• Is widely used for modelling object oriented-
systems. Example:

Use Case Diagram:

• Describes the functional

requirements of a system.
• Shows the actors (users) of the
system and their interactions
with the system.
• Describes the system's behavior
from a user's perspective.
Sequence Diagram:

• Describes the interaction between objects in a system.

• Shows the messages exchanged between the objects over time.
• Represents a single scenario of a use case or an operation.
Activity Diagram:

• Describes the dynamic behavior of a system.

• Shows the flow of activities, actions, and decision in system.
• Represents the steps in a process, such as a business process or a software
algorithm.
• Used for modelling workflows and complex processes.
State Chart Diagram:

• Describes the behaviour of an object or a system in response to internal

or external events.
• Shows the states that an object or system can be in and the transitions
between the states.
• Represents the behaviour of an object or system over time.
• Used for modelling real-time and event-driven
systems.
Component diagram:

•Describes the physical components of a system and their dependencies.

•Shows the software components, libraries, and other modules that make up a
system.
•Represents the relationships and dependencies between the components.
•Used for designing, documenting, and implementing large software

Example:
Deployment Diagram:

• Describes the physical deployment of a system on hardware or software

platforms.
• Shows the nodes (hardware or software) that make up the
system and their relationships.
• Represents the physical architecture of a system.
• Used for designing and documenting the deployment of a system
on different platforms.
Object diagram:

• An object diagram shows this relation between the instantiated

classes and the defined class and the relation between these
objects in the system.

• They are useful to explain smaller portions of your system, when

your system class diagram is very complex, and also sometimes
modelling recursive relationship in diagram.

Example:
EV CHARGING
STATION
 Introduction

The rise of electric vehicles (EVs) has led to an increased demand for efficient charging

infrastructure. EV Charge Stations play a crucial role in ensuring that EV users have access

to reliable power sources. These stations are equipped with various components such as fast

chargers, mobile app integration, and payment gateways.

An EV Charge Station consists of advanced systems that monitor energy consumption, track

user activity, and manage billing transactions. As cities move toward smart infrastructure,

integrating EV Charge Stations with data analytics can help optimize charging availability and

reduce energy consumption. EV charging stations play a crucial role in supporting sustainable

transportation. These stations provide the necessary infrastructure to recharge EV batteries,

much like gas stations do for traditional vehicles.

EV charging stations come in different types, ranging from slow home chargers to high-speed

public charging networks. They are located in residential areas, workplaces, shopping centers,

highways, and other public spaces to ensure convenient charging options for EV owners.

With advancements in battery technology and charging speed, modern charging stations now

offer faster and more efficient charging solutions. Governments and businesses worldwide are

investing in EV infrastructure to promote clean energy and reduce dependence on fossil fuels.
The expansion of EV charging stations is essential for the widespread adoption of electric

vehicles, making them more practical and accessible for daily use and long-distance travel.

2. System Overview

An EV Charge Station operates through interconnected hardware and software components.

Each station is designed to handle multiple vehicle types, offering different charging speeds

ranging from standard AC charging to rapid DC charging.

A typical charging session involves:

- **User Authentication**: A user accesses the station via RFID, mobile app, or payment card.

- **Charging Initiation**: The system verifies payment before allowing charging.

- **Energy Distribution**: Power is delivered to the vehicle, monitored by smart meters.

- **Payment Processing**: Users are billed based on energy consumed or time spent
charging.

- **Remote Monitoring**: Operators track station performance through a cloud-based system.

As technology evolves, future charging stations will integrate renewable energy sources, smart

grid interactions, and predictive maintenance to enhance efficiency.

3. EV Charge Station Components

EV Charge Stations consist of several key components that ensure smooth operation. These

include:
1. **Charging Unit**: The core component that supplies power to the EV. Modern stations

support multiple connectors such as CCS, CHAdeMO, and Type 2, ensuring compatibility with

various vehicles.

2. **User Interface**: Users interact with the charging station via a touchscreen display or

a mobile application. The interface provides real-time charging status, payment options, and

estimated time for a full charge.

3. **Payment System**: Integrated with digital wallets, credit/debit cards, and contactless

payments ,the payment system ensures secure transactions. Some stations also offer

subscription-based plans.

4. **Network Connectivity**: Many stations are cloud-connected, allowing remote

monitoring and real-time updates on availability. Operators can track energy usage and

perform diagnostics remotely.

5. **Safety & Security Mechanisms**: To prevent electrical hazards, stations include built-

in surge protectors, circuit breakers, and emergency stop buttons. Data security measures

protect user information and prevent fraud.

4.1 Use Case Diagram

The Use Case Diagram represents interactions between users, administrators, and the

charging station. It highlights key functions such as charging, monitoring, and

payments.
4.2 Class Diagram

The Class Diagram outlines the structure of the EV Charge Station, showing

relationships between entities such as Users, ChargingStations, Payments,

and System Administrators.

4.3 Sequence Diagram

The Sequence Diagram demonstrates the step-by-step process of

a charging session, from user authentication to payment

confirmation.
4.4 Activity Diagram

The Activity Diagram details the workflow of an EV charging session,

including user verification, energy distribution, and payment completion.

4.5 Deployment Diagram

The Deployment Diagram illustrates the hardware and software

components involved, such as mobile applications, cloud servers,

and charging units.