Cab Management System

INDEX
Chapter Contents Page
No.
1. Introduction

2. Scope of work

3. Feasibility Study
4. Need of system

5. Operating Environment – Hardware and software

6. Proposed System
6.1 Objectives to be Fulfilled
6.2 Data dictionary
6.3 ER Diagram
6.4 Data Flow Diagram
6.5 UML Diagrams
6.5.1 Activity Diagram
6.5.2 Sequence Diagram
6.5.3 Class Diagram
6.5.4 Use case Diagram

7. Design of input/output screen and reports

8. Testing

9. Advantages

10. Drawbacks and limitation

11. Future Enhancement

12. Bibliography

4
 Cab Management System

1. Introduction

Today almost every company like IT companies, call centers etc. are providing PICK/DROP
facilities to their Employees. But Existing System for managing Cabs, Drivers is manual which
has lot of drawbacks.

Proposed system CAB MANAGEMENT SYSTEM is fully computerized system

removes all the drawbacks of the existing system providing lot of facilities for
user(Administrator) such as allocating cabs to employees, managing drivers, employees and
cabs.

Computerized CAB MANAGEMENT SYSTEM will help the company by saving money and
the user(Administrator) by reducing work.

5
 Cab Management System

Scope of work

This Project’s aim is to automate the system, collecting fare , collecting all necessary information
of driver and employees. The data used by the system is stored in database that will be centreof
all information held drivers and employees and the base for the remainder of the process after
the initial application has been made. This enables things to be simplified and considerably
quickened,making the job of people involved easier.It supports the current process but
centralizes it and make it possible for decisions to be made earlier and easier way.

6
 Cab Management System

Feasibility Study

Feasibility Study refers to the determination that it is possible to automate the existing
system. Feasibility study forms the most important phase in the system development life cycle so
that the people who are affected by the system benefit from the change. This involves some very
crude estimates of schedules of completion of the proposed system and the cost of the system.
This study ensures that the system meets the objectives of the organization before it can be
approved for development. It also involves the study of different risks involved in developing the
system.
The major areas to consider while determining the feasibility of a system are :-

• Technical Feasibility.

• Financial Feasibility.

• Resources Feasibility.

7
 Cab Management System

Technical Feasibility

It is the study of functions, performance and constraints that may affect the ability to
achieve an acceptable system.

The issues raised during technical feasibility were

• Does proposed equipment have technical capacity to hold data

required to use the new system?
• Will proposed system provide adequate responses to inquires,
regardless number and location of user?
• Can system be expanded if developed?
• Are there any technical guarantees of accuracy, reliability, ease of
access and data security?

Discussing the above mentioned points We found system to technically feasible as

existing equipment were capable to handle system. Data can be added to existing system and
system can provide feature of accuracy, reliability, data security and ease of access.

8
 Cab Management System

Operational Feasibility

Operational feasibility refers to the determination that whether the system will operate
and hence used by the end user or not.
Our input screens are familiar with their existing data processing
environment, as We have checked acceptability of users for the input screens frequently.

The existing system has employees (Admin and guards) so there in no need to
recruit new employees. In the proposed system we don’t require guards. One or two days
training is sufficient to train the Administrator of this system. As system is very user
friendly, they have lot ease at work.

9
 Cab Management System

Economical Feasibility

A system to be developed should be profitable investment for organization. Financial benefits

must equal or exceed cost. In general economical feasibility includes cost benefit analysis. The
main point discussed by me during developing the system were

• Cost of developing system.

• Cost of hardware and software.
• Cost of manpower to handle the system.

Discussing above mentioned points We found the system feasibility as initial investment
was around Rs 35,000.

In the existing system they are paying to Administrator (suppose 3 Admin

3X5000=15000 Rs) and security guards (suppose 6 guards 6X2500=15000 Rs). But the proposed
system they have to pay only to the Administrator(15000 Rs) so Proposed System is saving the
salary of security guards ie. Rs. 15000 monthly. The proposed system will require new hardware
and software setup, and for the Administrator(user) it will require to give the initial training. The
proposed system is economically feasible because it will save valuable time, money and it is
more stable .

10
 Cab Management System

Need of system
Car and bus travel agencies need an effective management platform for handling their respective
transportation services. The existing system relies on manual data recording for management
which is very tedious and time consuming, involving a lot of manpower and paper work. So, the
current system need to be computerized and web-based.

11
 Cab Management System

Operating Environment – Hardware and software

Hardware(requirements)

Hard disk : 20GB and above

RAM : 256 MB and above

Printer

Software(requirements)

1. Operating system : Linux(Red hat)

2. Technology used :
- Front end : JAVA
- Back end : postgresql

12
 Cab Management System

Proposed system

Objectives of Proposed System

• To reduce manpower.
• To reduce manual work.
• To provide a user friendly system.
• To store large volume of correct and accurate information.
• To provide backup facility.
• To facilitate speedy access to any particular details.

13
 Cab Management System

Data Dictionary
Admin Table:-

Field Name Data Name Size constraint

A_No Text 50 Primary Key

A_Name Text 50

A_Addr Text 50

A_Phone Int8 10

A_Login Text 50

Cab Table:-

Field Name Data Type Size constraint

Cab_No Text 50 Primary Key

Cab_Name Text 50

Cab Capacity Int8 10

14
 Cab Management System

Driver Table: -

Field Name Data Type Size CONSTRAINT

Driver_No Text 50 Primary Key

Driver_Name Text 50
Driver_Addr Text 50
Driver_Phone Int8 10
Cab_No Text 50 Foreign Key
Process Text 50
Date_Join Text 50

Employee Table:-

Field Name Data Type Size CONSTRAINT

Emp_Id Text 50 Primary Key

Emp_Name Text 50

Emp_Addr Text 50

Emp_Phone Int8 10

Emp_Process Text 50

Emp_Loc Text 50

15
 Cab Management System

Log Table:-

Field Name Data Type Size constraint

Driver_No Text 50

Driver_Name Text 50

Cab_No Text 50

TimeIn Text 50

TimeOut Text 50

Date Text 50

MeterIn Int8 10

MeterOut Int8 10

16
 Cab Management System

UML Diagram
 ER Diagram:
TimeIn
A_Addr Cab_No
A_Name Driver_Name
A_Phone TimeOut
Driver_No
A_No A_Login Date

Admin Updated Register

Driver_Name Driver_addr

A_Pass
Driver_no Cab_No

Assign Dr_Phone

Maintain job Driver Date_Join

Process

Alot
Employee Emp_Loc

Emp_Process
Emp_Id
Emp_Addr
Cab
: Emp_Phone
Emp_Name Cab_no Cab_Capacity

Cab_Name

17
 Cab Management System

 Data flow diagram

Admin

Pick up/Drop details

Login CAB Pay for Cab
Maintain Record MANAGEMENT
SYSTEM
Give Details to Driver
Allocated Cab
Give Salary

Driver Employee
Take Payment

Give Payment To Admin

18
 Cab Management System

 Activity Diagram:

Admin Login To System

Maintain Record

Driver Employee

Get pick up\ drop details

Give pick up\drop details

Allocate cab to driver

Take service

Provide Service

Pay To Service
Take Payment

Give Payment To admin

Take Salary

19
 Cab Management System

 Sequence Diagram:

Admin Driver
Employee

contact for inquiry

Give Information

Give pick up/drop details

Contact driver & give pick
Up&drop details &custo-
mer contact number.

Take Responsibility
Ensure & give driver
Contact number
Provide Service
Pay For Service
Give Money
Give Salar

20
 Cab Management System

 Class Diagram

Administrator
Register
A_id:int

A_Name:vachar(20)
Driver_Name:varchar(20)
A_addr:varchar(20)
11 Driver_id:int
A_Phone:int
Time_in
A_Login:

A_Pass: Time_out

# Login() void Date(double)

#Logout()

#Requisteddetails() #Register detail()

#Driver Info()

Cab
Employee Driver

Driver_Name:varchar(
20) -C_no:int
Emp_id:int
Driver_id:int +C_Name: varchar(20)
Emp_Name:varchar(20)
1 1 1 1 +C_capacity:
Process:
Emp_addr:varchar(20) varchar(20)
Driver_Loc: #DriverInfo()
Emp_Loc

Emp_Process Driver_Phone:

Emp_Phone Employee details()

+given location() Pick up() & drop()

-bill pay

21
 Cab Management System

Use case:
Login

Maintain Record

Pick up/drop
details
Admin Driver
Give details
to driver

Allocate cab

Pay for cab

Take
payment

Employee
Give payment to
admin

Give salary

22
 Cab Management System

Design of input/output screen and reports

23
 Cab Management System

24
 Cab Management System

25
 Cab Management System

26
 Cab Management System

27
 Cab Management System

28
 Cab Management System

Testing
 SOFTWARE TESTING
The software engineering process can be viewed as a spiral. Initially system engineering
defines the role of software and leads to software requirement analysis where the information
domain, functions, behavior, performance, constraints and validation criteria for car booking
management system software are established. Moving inward along the spiral, we come to
design and finally to coding. To develop computer software we spiral in along streamlines that
decrease the level of abstraction on each turn.

A strategy for car booking management system software testing may also be viewed in
the context of the spiral. Unit testing begins at the vertex of the spiral and concentrates on each
unit of the software as implemented in source code. Testing progress by moving outward along
the spiral to integration testing, where the focus is on the design and the construction of the
software architecture. Talking another turn on outward on the spiral we encounter validation
testing where requirements established as part of software requirements analysis are validated
against the software that has been constructed. Finally we arrive at system testing, where the
software and other system elements are tested as a whole.
 Unit Testing

Unit testing focuses verification effort on the smallest unit of software design, the module. The
unit testing we have is white box oriented and some modules the steps are conducted in parallel.

1. WHITE BOX TESTING

This type of testing ensures that
 All independent paths have been exercised at least once
 All logical decisions have been exercised on their true and false sides
 All loops are executed at their boundaries and within their operational bounds
 All internal data structures have been exercised to assure their validity.

29
 Cab Management System

2. BASIC PATH TESTING

Established technique of flow graph with Cyclomatic complexity was used to derive test cases
for car booking management system all the functions. The main steps in deriving test cases were:
Use the design of the code and draw correspondent flow graph.
Determine the Cyclomatic complexity of resultant flow graph, using formula:

V(G)=E-N+2 or
V(G)=P+1 or
V(G)=Number Of Regions

Where V(G) is Cyclomatic complexity,

E is the number of edges,
N is the number of flow graph nodes,
P is the number of predicate nodes.

Determine the basis of set of linearly independent paths.

3. CONDITIONAL TESTING

In this part of the testing each of the conditions were tested to both true and false aspects. And all
the resulting paths were tested. So that each path that may be generate on particular condition is
traced to uncover any possible errors.

4. DATA FLOW TESTING

This type of testing selects the path of the program according to the location of definition and use
of variables. This kind of testing was used only when some local variable were declared. The
definition-use chain method was used in this type of testing. These were particularly useful in
nested statements.

30
 Cab Management System

5. LOOP TESTING

In this type of testing all the loops are tested to all the limits possible. The following exercise
was adopted for car booking management system all loops:

 All the loops were tested at their limits, just above them and just below them.
 All the loops were skipped at least once.
 For car booking management system nested loops test the inner most loop first and then work
outwards.
 For car booking management system concatenated loops the values of dependent loops were
set with the help of connected loop.
 Unstructured loops were resolved into nested loops or concatenated loops and tested as
above.

Each unit has been separately tested by the development team itself and all the input
have been validated

31
 Cab Management System

Advantages

• Reduced manpower for system

• Humans error are reduced
• Working is fast i.e. time saved
• Searching is fast
• Reduced paper work and maintained
• System is more secure (only admin can access the system)
• required information is stored in one central location and thus is easily accessible
• Human error could also be a factor in that mistakes could be made in the filing process
which would not occur in a well written database system and mistakes or changes on
physical records can be messy to correct.

32
 Cab Management System

Drawback and Limitations

 Drawback

 System is dependent on good individuals.

 Reducation in sharing information and customer services
 Lack of security.

 Limitations

Cool Cab Services is a Web application and it is restricted to only limited type of users. In this
application ,Different types of managers have been given access rights and they are restricted up
to their functionalities, so that the data is maintained securely and redundant data is prevented.
As the Data is stored electronically, it is necessary to have a Computer and Network connection
to access the Application. Here The Details of Employees and Drivers, cabs are maintained but
accounts to these people are not created. using this application mangers do assign or update the
batch,shift of cabs to drivers and employees. But employees are unable to view their details .

33
 Cab Management System

FUTURE ENHANCEMENT

The system can be enhanced so that it will be suitable for a very big organization .

Diagram :Future Enhancement of Proposed System

Adding two Security personal at the two gates to maintain the Driver Log entries.
All Log entries will be done at the gates by the Security person in their corresponding computers
and this entry will automatically stored at Admin’s computer (server). So Admin has only to
print Roaster for Driver. This will reduce the load of the administrator. Thus limitation of the
Proposed system can be removed easily.

34
 Cab Management System

References and Bibliography

References:-

• Java Complete Reference: - HerbertSchildt.

• Black Book : - StevenHolzener.

• Software Engineering :- Roger Pressman

Websites:-
 www.google.com

35