Bus Depot Information System

Introduction

Odisha State Road Transport Corporation is a State Government undertaking to provide efficient,
adequate, economical and consistently high quality of services and to continuously improve the
services through a process of teamwork for the utmost satisfaction of the passengers and to attain
a position of pre-eminence in the Bus Transport sector.

 Provide safe & comfortable road transport to the passengers so that they can have
confidence in the service rendered by the organization.
 Connect remote / tribal areas and hilly terrains to the mainstream which are otherwise not
well connected – thereby fulfilling the social commitment.
 Provide service during emergent situations.
 Provide passenger amenities at Bus Stands managed by OSRTC.

The main purpose of the project is to provide the smooth execution of default operation
done in OSRTC HQ and in different depot in the state.

Previously all information are maintained manually .so it is very difficult to track the
information in deputize.

OBJECTIVE/SCOPE OF PROJECT

A web based interactive automation system would be developed and hosted on the server.
The system will have facilities like generating list of Vehicles, Depo, Vehicle History, Vehicle
various parts information, purchase to utilization process with stock and inventory
management, Managing accounts & Billing Application etc. The main objective of the
portal is to automate and increase the efficiency of the OSRTC workflow. The process of
automation should start immediately which will reduce the time for retrieval of
information required by concerned officers.

The main modules of the system would be;

 Vendor management System

 Spares (Procurement, receipt to utilization process)
 Maintenance (Runtime, Daily, Weekly, Periodic)
 Repair (Local/Empanel vendor, OEM authorized facility center)
1.1 MODULES OF PROJECT

MODULE 1:- ADMIN

The Administrator plays vital role in this project. Only one administrator is permitted to open an
account. The privilege is given to the administrator to allow to do some general setup like Depot
information, Approve Maintenance info send by depot manage and many other things.. The
Administrator can approve depot manager, maintenance info and vendor to create an account.
Whenever he wants, he can cancel the account of Depot manager, Dealer and Vendor.

MODULE 2:- THE DEPOT MANAGER

After getting permission from Administrator, he has the power to do manipulate the entire into
the website. He also manages all the set up done by the administrator. He manipulates
information about vehicle, route and maintenance info.

MODULE 3:- VENDOR

After getting permission from Administrator, the vendor can manipulate details of spare parts of
vehicle and set the spare parts’ prices. Only vendor can allow the account of dealer. he approves
the appropriate dealer to request necessary spare parts.

MODULE4:- DEALER
After getting permission from vendor, dealer views the requisition sent by vendor and then
transport the items to depot. He also maintains the stock of spare parts.
CONTEXT DIAGRAM:
A DFD may consist of a number of levels. The top-level diagram is called a Context Free Diagram, which
consists of one single process.

LEVEL-0:
LEVEL-1(ADMIN’S REGISTER):-

LEVEL-1(DM’S REGISTER):-
LEVEL-1(VENDOR’S REGITRATION):-
LEVEL-1(DEALER’S REGISTRATION):-
LEVEL-2(ADMIN):-
LEVEL-2(DEPOT MANAGER):-

LEVEL-2(VENDOR):-
LEVEL-2(DEALER):-
3.6 ENTITY RELATIONSHIP DIAGRAM :-

The Entity Relationship(ER) data model is based on a perception of a real world that consists of a real
world that consists of a set of objects called ENTITY/ENTITIES., and of relationships among these objects.
There are the three basic notations that ER data model employs: Entity Set, Relationship Set and
Attributes.

This symbol represents the Entity.

This symbol represents the Relationship set.

This symbol represents the Attributes.

ENTITY RELATIONSHIP DIAGRAM :-

3.7 UML DIAGRAM:
3.7.1 USECASE DIAGRAM:
  A use case diagram is a diagram that shows a set of use cases and actors and
relationships.
Contents

 Use case commonly contain

 Use cases
 Actors
 Dependency, generalization and association relationships

A use case is a set of scenarios that describing an interaction between a user and a system. A use
case diagram displays the relationship among actors and use cases. The two main components of
a use case diagram are use cases and actors.

It represents the actor.

It represents the use case.

It represents the system.

3.7.2 class diagram
In software engineering , a class diagram in the unified modelling language is a
type of static structure diagram that describes the structure of a system by showing
the system’s classes, their attributes, operations(or methods),and the relationships
among objects.
Notation: