DTC Route Information: Online information about the bus

routes and their frequency and fares

For detailed information about Delhi Transport Corporation (DTC) bus routes,
frequencies, and fares, you can visit the official DTC website or use their mobile app
if available. These platforms typically provide up-to-date information on routes,
timings, fares, and any recent updates or changes to the services.

Additionally, you can also find this information on various third-party transit apps
or websites like Google Maps, Moovit, or Delhi Bus Info, which often integrate real-
time data to provide accurate route information, including schedules and fares.
These platforms can be particularly helpful for planning your journey in real-time
and finding the most efficient routes.

Key Features:

1. Route Maps: Visual representations of the entire DTC bus network, aiding
users in understanding route connections.
2. Search Functionality: Enables users to input their starting point and
destination to find relevant bus routes.
3. Route Details: Provides information about starting and ending points, major
stops, and landmarks served by each route.
4. Frequency of Service: Indicates the frequency of buses during different times of
the day.
5. Real-Time Updates: Integration with GPS data for live updates on bus
locations, arrivals, and delays.
6. Fare Information: Details about fares, discounts, and concessions available.
7. Accessibility Features: Information about wheelchair ramps and priority
seating.
8. Feedback Mechanism: Allows users to report issues and provide feedback for
service improvement.
9. Language Support: Supports multiple languages for accessibility.
10. Integration with Other Modes: Seamless integration with other modes of
transport for multi-modal journey planning.

PAGE|1
Uses:

● Planning daily commutes.

● Exploring unfamiliar areas.

● Finding the most efficient routes.

● Checking bus schedules and fares.

● Accessing real-time updates during travel.

Purpose: The purpose of the DTC Route Information platform is to:

● Enhance accessibility and usability of public transportation information.

● Empower users to make informed decisions about their journeys.

● Improve the overall efficiency and effectiveness of the DTC bus network.

● Encourage the use of public transportation for sustainable urban mobility.

Objectives:

● Provide accurate and up-to-date information about DTC bus routes,

frequencies, and fares.
● Ensure ease of use through intuitive design and user-friendly features.

● Foster transparency and accountability by enabling user feedback.

● Promote the accessibility of public transportation for all residents and visitors.

● Contribute to the improvement of public transportation services in Delhi.

PAGE|2
 Use Case Diagram

A use case diagram for the DTC Route Information system might look
something like this:

Actors:

● User: Represents the person interacting with the DTC Route Information
system.

● Administrator: Manages and maintains the DTC Route Information system.

Use Cases:

● Search Routes: Users can search for bus routes based on their starting point
and destination.

● View Route Details: Users can view detailed information about a specific bus
route, including stops, timings, and fares.

● Check Bus Frequency: Users can check the frequency of buses on a particular
route during different times of the day.

● Get Real-Time Updates: Users can receive real-time updates about bus
locations, arrivals, and delays.

● Provide Feedback: Users can provide feedback or report issues regarding the
DTC Route Information system.

● Manage System: Administrators can manage and maintain the DTC Route
Information system, including updating route information and handling user
feedback.

PAGE|3
This diagram illustrates the interactions between the actors (User and
Administrator) and the various functionalities (Use Cases) of the DTC Route
Information system.

Use Case Diagram

PAGE|4
Class Diagram

PAGE|5
Overview:

The class diagram represents the structural aspects of the DTC Route Information
system, highlighting the key classes, their attributes, methods, and
relationships. It provides a blueprint for understanding how the system is
organized and how different components interact with each other.

Working:

1. DTCRouteInfo Class:
● This class serves as the central component responsible for managing routes
within the system.
● It contains an attribute route, which stores an array or list of Route objects
representing different bus routes.
● The addRoute() method allows new routes to be added to the system.

● The removeRoute() method enables the removal of existing routes from the
system.
● The getRoutes() method retrieves all available routes stored in the system.

● The searchRoutes() method facilitates searching for routes based on specified

start and end locations.

2. Route Class:
● Represents individual bus routes within the system.

● It holds attributes such as id, startingPoint, endingPoint, stops, frequency, and

fare to describe the characteristics of each route.
● Methods like getId(), getStartingPoint(), getEndingPoint(), getStops(),
getFrequency(), and getFare() provide access to these attributes.
● Users can retrieve information about specific routes using these methods.

3. Location Class:
● Represents geographical locations, such as starting points, ending points, and
stops along the routes.
PAGE|6
● Attributes include name, latitude, and longitude to specify the location's
details.
● Methods like getName(), getLatitude(), and getLongitude() allow access to
these attributes.

Interactions:

● Users can interact with the DTCRouteInfo class to add, remove, retrieve, and
search for routes.
● Each Route object contains information about a specific bus route, including its
starting point, ending point, stops, frequency, and fare.
● Location objects provide details about geographical locations associated with
routes.

Overview of Workflow:

● Users interact with the DTC Route Information system to perform tasks such
as adding or removing routes, retrieving route information, or searching for
routes based on specific criteria.

● The DTCRouteInfo class manages the routes stored in the system, facilitating
these user interactions and operations.

● Route objects represent individual bus routes within the system, storing
detailed information about each route.

● Location objects describe the geographical locations associated with routes,

such as starting points, ending points, and stops.

Overall, the class diagram provides a structured representation of the DTC Route
Information system, offering insight into its components and how they
collaborate to manage and provide information about bus routes.

PAGE|7
Class Diagram

PAGE|8
PAGE|9
 Sequence Diagram

A sequence diagram illustrates the interactions between different objects or

components within a system over time. In the context of the DTC Route
Information system, let's create a sequence diagram that illustrates how a user
searches for a bus route and retrieves route information.

Overview:
● The sequence diagram will depict the sequence of steps involved when a user
interacts with the DTC Route Information system to search for a bus route and
retrieve detailed information about it.
● It will show the flow of messages between the user and the system components,
such as the user interface and the backend system responsible for route
management.
● The diagram will capture the chronological order of events, showing how each
step leads to the next in the process of searching for and retrieving route
information.

Working:
1. User Interaction:
● The sequence begins with the user interacting with the system, typically
through a user interface.
● The user inputs the start and end locations for their journey.

2. Request Processing:
● The user input is received by the system, which processes the request.

● The system initiates the search for routes based on the provided start and end
locations.

PAGE|10
● The system searches its database or repository for routes that match the
specified criteria.
● This involves querying the database for relevant route information.

3. Route Presentation:
● Once the matching routes are found, the system presents them to the user.

● The user interface displays the list of routes for the user to choose from.

4. Route Selection:
● The user selects a specific route from the list presented by the system.

● This selection is communicated back to the system.

5. Detailed Information Retrieval:

● Upon receiving the user's selection, the system retrieves detailed information
about the chosen route.
● This may involve querying additional data or accessing specific route details
stored in the system.

6. Information Presentation:
● The detailed route information is presented to the user through the user
interface.
● This includes information such as the route's starting point, ending point,
stops, frequency, and fare.

7. User Interaction (Continued):

● The user can interact with the presented route information, such as viewing it
or making further selections.
● This step marks the end of the sequence, but the user may continue to interact
with the system as needed.

PAGE|11
This sequence diagram provides an overview of the interaction flow between the
user and the DTC Route Information system, illustrating how user requests for
route information are processed and fulfilled by the system.

PAGE|12
PAGE|13
 Collaboration Diagram

A collaboration diagram, also known as a communication diagram, illustrates

how objects or components within a system interact with each other to achieve
a particular task or functionality. It emphasizes the communication flow
between the objects rather than the sequence of messages like in a sequence
diagram. Let's create a collaboration diagram to illustrate how different
components collaborate in the DTC Route Information system:

Overview:
● The collaboration diagram provides a visual representation of the
communication and interactions between the various components of the DTC
Route Information system.
● It emphasizes the relationships and interactions between objects, showing how
they collaborate to fulfill a user request.
● The diagram depicts the flow of messages or information between objects,
highlighting the dependencies and interactions that occur during the execution
of a specific task or functionality.

Working:
1. User Interface (UI):
● The user interacts with the system through the user interface, providing input
such as start and end locations for their journey.

2. DTCRouteInfo System:
● The DTCRouteInfo system is the main component responsible for managing
routes and processing user requests.
● It receives the user input from the UI and initiates the process of searching for
routes.

3. Route Manager:
● The Route Manager component within the DTCRouteInfo system handles
route-related functionalities, such as searching for routes and retrieving route
information.

PAGE|14
● It communicates with the Route objects to retrieve relevant route data from the
system's database.

4. Route Objects:
● Route objects represent individual bus routes within the system.

● They contain information about specific routes, including their starting point,
ending point, stops, frequency, and fare.

5. Location Objects:
● Location objects represent geographical locations associated with routes, such
as start points, end points, and stops.
● They provide detailed information about the geographical coordinates and
names of locations.

6. Database:
● The database stores and manages the route information, including details
about routes, locations, and other related data.
● It serves as a repository for storing and retrieving route information as
requested by the Route Manager component.

Working Process:
● The user interacts with the UI to input the start and end locations for their
journey.
● The UI forwards the user input to the DTCRouteInfo system.

● The DTCRouteInfo system, specifically the Route Manager component,

processes the user request and communicates with the database to search for
relevant routes.
● The Route Manager retrieves route information from the database and
communicates with Route and Location objects to gather additional details.
● The gathered route information is then passed back to the UI, where it is
presented to the user for viewing and selection.

PAGE|15
PAGE|16
PAGE|17
 State Diagram

A state diagram, also known as a state machine diagram, depicts the various
states that an object or system can be in and how it transitions from one state
to another in response to events. In the context of the DTC Route Information
system, let's create a state diagram to illustrate the different states and
transitions involved in the user interaction process:

Overview:
● The state diagram provides a visual representation of the states that the DTC
Route Information system can be in and how it transitions between these states
in response to user interactions or system events.
● It captures the behavior of the system, showing how it responds to different
stimuli and progresses from one state to another over time.
● The diagram helps in understanding the overall behavior and flow of the
system, including the various states it can be in and the events that trigger
transitions between these states.

Working:
1. Initial State (Idle):
● The system starts in the initial state, typically an idle state where it is waiting
for user input or events to occur.

2. User Interaction (Input Received):

● When the user interacts with the system by providing input, such as entering
start and end locations for their journey, the system transitions to a state where
it processes the input.

3. Processing Input:
● In this state, the system processes the user input, validates it, and initiates the
process of searching for routes based on the provided information.

4. Searching for Routes:

PAGE|18
● The system enters this state while it searches for routes that match the
specified criteria, such as start and end locations.

5. Routes Found (Results Displayed):

● Once the system finds matching routes, it transitions to a state where it
displays the results to the user, typically presenting a list of available routes.

6. Route Selection (User Choice):

● In this state, the user selects a specific route from the list of available options
presented by the system.

7. Retrieving Route Information:

● Upon receiving the user's selection, the system transitions to a state where it
retrieves detailed information about the chosen route from its database or
repository.

8. Route Information Displayed:

● Once the system has successfully retrieved the route information, it enters a
state where it displays the detailed route information to the user, typically
showing information such as starting point, ending point, stops, frequency, and
fare.

9. End State (Interaction Completed):

● Finally, when the user has finished viewing the route information and
interacting with the system, the system returns to an idle state, ready to
process further user interactions or events.

Working Process:
● The state diagram captures the different states that the DTC Route Information
system can be in during the user interaction process, from receiving user input
to displaying route information and completing the interaction.

PAGE|19
● It illustrates how the system transitions between these states in response to
user interactions, events, or internal processes, providing a clear overview of
the system's behaviour and flow.
● By visualizing the states and transitions, the diagram helps in understanding
the overall behaviour of the system and ensures that all possible states and
transitions are accounted for in the system design and implementation.

PAGE|20
PAGE|21
 Activity Diagram

An activity diagram is a type of behavioural diagram in the Unified Modeling

Language (UML) that illustrates the flow of activities or actions within a system or
process. It is particularly useful for visualizing the sequence of steps, decision
points, and parallel activities involved in completing a task or achieving a specific
functionality. In the context of the DTC Route Information system, let's create an
activity diagram to illustrate the workflow of searching for a bus route and retrieving
route information:

Overview:

● The activity diagram provides a visual representation of the sequence of

activities involved in the process of searching for a bus route and retrieving
route information within the DTC Route Information system.
● It breaks down the process into individual actions or steps, showing how they
are sequenced, branched, and merged to achieve the desired functionality.
● The diagram helps in understanding the flow of activities, decision points, and
possible paths that can be taken during the execution of the process.

Working:

1. Start:

● The activity diagram begins with a start node, indicating the start of the
process.

2. Input Start and End Locations:

● The user provides input by entering the start and end locations for their
journey.

3. Validate Input:

● The system validates the user input to ensure that it is in the correct format
and within acceptable parameters.

4. Search for Routes:

● The system initiates the process of searching for routes based on the provided
start and end locations.

5. Routes Found? (Decision Point):

PAGE|22
● The system checks whether any routes matching the specified criteria have
been found.
● If routes are found, the process continues to the next step.
● If no routes are found, the process ends, and an appropriate message may be
displayed to the user.

6. Display Route Options:

● If routes are found, the system displays the available route options to the user.
● This may involve presenting a list of routes or other visual representations of
the available options.

7. User Selects Route:

● The user selects a specific route from the list of options presented by the
system.

8. Retrieve Route Information:

● Upon receiving the user's selection, the system retrieves detailed information
about the chosen route, such as starting point, ending point, stops, frequency,
and fare.

9. Display Route Information:

● The system displays the detailed route information to the user, typically in a
formatted and easy-to-read manner.

10. End:

● The activity diagram ends, indicating the completion of the process.

Working Process:

● The activity diagram outlines the step-by-step workflow of searching for a bus
route and retrieving route information within the DTC Route Information
system.
● It shows how the process begins with user input, progresses through various
validation and decision points, and ultimately ends with the display of route
information to the user.
● By visualizing the activities and their relationships, the diagram helps in
understanding the overall flow of the process and ensures that all necessary
steps are accounted for in the system design and implementation.
PAGE|23
PAGE|24
PAGE|25
 Deployment Diagram

A component diagram in Unified Modeling Language (UML) represents the

components of a system and their relationships. It illustrates how different parts of
a system are organized and interact with each other to achieve specific
functionalities. In the context of the DTC Route Information system, let's create a
component diagram to illustrate its structure and relationships:

Overview:

● The component diagram provides an overview of the various components that

make up the DTC Route Information system and how they are interconnected.
● It shows the high-level structure of the system, including the main
components, subsystems, libraries, and interfaces.
● The diagram helps in understanding the modularization of the system, the
dependencies between components, and how different parts work together to
achieve the system's goals.

Working:

1. User Interface (UI) Component:

● Represents the user interface of the DTC Route Information system, including
screens, forms, and interaction elements.
● Responsible for presenting information to users and capturing user input.
● May include components such as web pages, mobile app interfaces, or desktop
application screens.

2. DTCRouteInfo System Component:

● Represents the main system component responsible for managing routes and
processing user requests.
● Includes subcomponents for route management, user input processing, route
search, and route information retrieval.

3. Route Manager Component:

● Subcomponent of the DTCRouteInfo system responsible for managing routes
within the system.
● Handles functionalities such as route searching, route addition, route removal,
and route information retrieval.

4. Database Component:
● Represents the database or data storage component used by the DTC Route
Information system to store route information.

PAGE|26
● Stores data related to routes, locations, user preferences, and other system
data.
● May utilize a relational database management system (RDBMS) or other data
storage technologies.

5. External Services Component:

● Represents external services or APIs used by the DTC Route Information
system to retrieve additional data or integrate with external systems.
● Examples include geolocation services, mapping services, transit APIs, or
payment gateways.

6. User Interface Library:

● Represents libraries or frameworks used to develop the user interface of the
system.
● Provides pre-built components, templates, and functionalities for designing
and implementing user interfaces.

7. Route Data Library:

● Represents libraries or modules used to manage and manipulate route data
within the system.
● Provides functionalities for route searching, route validation, data formatting,
and other route-related operations.

8. Communication Interface:
● Represents communication interfaces or protocols used for communication
between different components of the system.
● Ensures seamless interaction and data exchange between components, such as
API endpoints, messaging protocols, or network communication protocols.

Working Process:

● The component diagram provides an overview of the structural organization of

the DTC Route Information system, including its main components,
subsystems, libraries, and interfaces.
● It shows how different parts of the system are organized and interconnected to
perform specific functionalities, such as route management, user interaction,
data storage, and external service integration.
● By visualizing the components and their relationships, the diagram helps in
understanding the architecture of the system and facilitates system design,
development, and maintenance.

PAGE|27
PAGE|28
PAGE|29
 Component Diagram

A component diagram in Unified Modeling Language (UML) represents the

components of a system and their relationships. It illustrates how different parts of a
system are organized and interact with each other to achieve specific functionalities.
In the context of the DTC Route Information system, let's create a component
diagram to illustrate its structure and relationships:

Overview:

● The component diagram provides an overview of the various components that

make up the DTC Route Information system and how they are interconnected.
● It shows the high-level structure of the system, including the main
components, subsystems, libraries, and interfaces.
● The diagram helps in understanding the modularization of the system, the
dependencies between components, and how different parts work together to
achieve the system's goals.

Working:

1. User Interface (UI) Component:

● Represents the user interface of the DTC Route Information system, including
screens, forms, and interaction elements.
● Responsible for presenting information to users and capturing user input.
● May include components such as web pages, mobile app interfaces, or desktop
application screens.

2. DTCRouteInfo System Component:

● Represents the main system component responsible for managing routes and
processing user requests.
● Includes subcomponents for route management, user input processing, route
search, and route information retrieval.

3. Route Manager Component:

● Subcomponent of the DTCRouteInfo system responsible for managing routes

within the system.
● Handles functionalities such as route searching, route addition, route removal,
and route information retrieval.

4. Database Component:

PAGE|30
● Represents the database or data storage component used by the DTC Route
Information system to store route information.
● Stores data related to routes, locations, user preferences, and other system
data.
● May utilize a relational database management system (RDBMS) or other data
storage technologies.

5. External Services Component:

● Represents external services or APIs used by the DTC Route Information

system to retrieve additional data or integrate with external systems.
● Examples include geolocation services, mapping services, transit APIs, or
payment gateways.

6. User Interface Library:

● Represents libraries or frameworks used to develop the user interface of the

system.
● Provides pre-built components, templates, and functionalities for designing
and implementing user interfaces.

7. Route Data Library:

● Represents libraries or modules used to manage and manipulate route data

within the system.
● Provides functionalities for route searching, route validation, data formatting,
and other route-related operations.

8. Communication Interface:

● Represents communication interfaces or protocols used for communication

between different components of the system.
● Ensures seamless interaction and data exchange between components, such as
API endpoints, messaging protocols, or network communication protocols.

Working Process:

● The component diagram provides an overview of the structural organization of

the DTC Route Information system, including its main components,
subsystems, libraries, and interfaces.
● It shows how different parts of the system are organized and interconnected to
perform specific functionalities, such as route management, user interaction,
data storage, and external service integration.

PAGE|31
● By visualizing the components and their relationships, the diagram helps in
understanding the architecture of the system and facilitates system design,
development, and maintenance.

PAGE|32
PAGE|33