EGERTON UNIVERSITYDEPARTMENT OF COMPUTER

SCIENCE

SYSTEM REQUIREMENTS SPECIFICATION

FOR

EASYCOACH BOOKING AND RESERVATION SYSTEM Presented by:

BETHUEL K. KIAYS13/20027/07

TO

PROJECT SUPERVISORMR. BOSIRE

A system requirements specification document submitted in partial fulfillment of the requirements for the award of a Bachelor of Science Degree in Computer

Science.

DATE

26th OCTOBER 2010.

i

DECLARATION

I declare that the work contained in this project is my own compiled work and it has never been

presented in any other university or college for the award of any degree, diploma or certificate.

Bethuel K. Kiay DateS13/20027/07

Mr. Bosire. DateProject Supervisor.

ii

ABSTRACT:

This document contains the software requirements specification of EASYCOACH BOOKING

AND RESERVATION SYSTEM. The Easy Coach booking and reservation system is a

proposed system which will automate most of the bus transport industry’s operations concerning

booking and reservations. The system will enable multiple bookings at an instance through

distributed booking points for efficiency. The need to improve service delivery to customers in

terms of booking necessitated the development of this proposed system.

The booking and reservation system is a computer application which can be accessed through

many terminals in a network. This application will automate the reservation of tickets and

enquiries concerning Easycoach bus travels.

The importance of this system to the company is that it automates most company operations thus

improving on efficiency and accuracy in terms of service delivery.

The goal of the Software Requirements Specification (SRS) is to describe the overall

functionality of the Easycoach Booking and Reservation System.

The requirements that are stated in this document will determine the final product and its

functionality. This document will also be used to evaluate the success of the project.

1

Table of ContentsDECLARATION..............................................................................................................................i

ABSTRACT:...................................................................................................................................1

1. INTRODUCTION:..................................................................................................................2

1.1. Purpose..............................................................................................................................2

1.2. Scope.................................................................................................................................2

1.3. Definitions, Acronyms and Abbreviations........................................................................2

2. THE PROBLEM STATEMENT:............................................................................................4

3. OBJECTIVES:.........................................................................................................................4

3.1. MAIN OBJECTIVE..........................................................................................................4

3.2. SPECIFIC OBJECTIVES:................................................................................................4

4. LITERATURE REVIEW:.......................................................................................................5

5. SCOPE AND LIMITATIONS:...............................................................................................6

6. JUSTIFICATION:...................................................................................................................6

7. ANALYSIS/DESIGN:.............................................................................................................7

7.1. OVERALL DESCRIPTION:............................................................................................7

7.1.1. Entity Relationship Diagrams:...................................................................................7

8. IMPLEMENTATION AND TESTING:...............................................................................10

8.1. Phase II: Training System Development........................................................................10

8.2. Phase III: System Testing...............................................................................................11

8.3. Phase IV: Production Rollout.........................................................................................12

9. CONLUSION AND RECOMMENDATIONS:....................................................................13

9.1. CONLUSIONS...............................................................................................................13

9.2. RECOMMENDATIONS................................................................................................13

10. PROJECT SCHEDULE AND BUDGET:..........................................................................14

10.1. PROJECT SCHEDULE..............................................................................................14

10.2. ESTIMATED BUDGET.............................................................................................15

2

1. INTRODUCTION:

1.1.Purpose

The purpose of the System Requirements Specification document is to maintain all the functions

and the specifications of the Easycoach Booking and Reservation system. Besides, it contains a

detailed description of all the requirements of the system.

1.2.Scope

The proposed project will be mainly expected to;

1. Produce information on all available buses and their routes on enquiry.

2. Reserve a seat for a customer on the desired bus.

3. Produce a bus ticket for each booking instance.

4. Allow cancellation of any tickets on request.

5. Perform report generation.

1.3.Definitions, Acronyms and Abbreviations

Administrator: The person who manages and maintains computer systems, database and

software.

Attendant: The person who serves the customers at the booking stations.

IT: Information Technology.

SRS: System Requirements Specification.

Staff: The people who work for Easycoach.

LAN: Local Area Network.

GUI: Graphical User Interface.

DFD: Data Flow Diagram.

3

1.4.References

a) Connolly, T. and Begg, C (2005) Database systems: A practical approach to design, implementa-

tion and management, 4th Ed PP 372-378. Addison Wesley, London ISBN: 0-321-21025-5.

b) Hansen, G, W. and Hansen, J.V (1996) Database management and design, 2nd Ed. Pearson Educa-

tion, Inc. U.S.A, ISBN: 81-203-1465-4.

c) Hawryszkiewyez, 1 (2001) Introduction to system analysis and design, 5 th Ed. Prentice Hall,

ISBN: 1740092805.

d) [IEEE] The applicable IEEE standards are published in “IEEE Standards Collection,”2001 edi-

tion

e) [Bruade] The principal source of textbook material is “Software Engineering: An Object Ori-

ented Perspective” by Eric J. Bruade (Wiley 2001).

f) Easycoach Bus Company management records.

g) http://software-quality.blogspot.com/

.

4

2. THE PROBLEM STATEMENT:

The main problem that faces any booking or reservation service is the ability to book for limited

spaces from different places without the conflict of double booking or overbooking. This

problem necessitates the use of a system which will synchronize all bookings from different

places as well as providing an overview of the space status.

The Easycoach Booking and Reservation System is therefore being developed to solve this issue.

Any booking/reservation instance will be entered into one central database. Queries can be made

to this database concerning the bus booking status or any other information stored there.

3. OBJECTIVES:

3.1.MAIN OBJECTIVE

To automate the Company’s Booking and Reservation System.

3.2.SPECIFIC OBJECTIVES:

To improve customer-service access through increased booking spots.

To improve booking/reservation efficiency through automation.

To improve bus fleet management through ease of adding or removing buses/routes.

5

4. LITERATURE REVIEW:

A similar system has been developed and is fully operational in the developed countries where

there is an advancement of technology. These systems are mostly operated online.

In China for instance, there are a number of bus booking/ reservation systems which operate both

from a computer and the mobile form interface. Ticket Goose (www.ticketgoose.com) is an

example of a bus booking/reservation system in China and has been a success according to

statistics and research from Today’s technology 2010 magazine.

.

6

5. SCOPE AND LIMITATIONS:

The proposed project will be mainly expected to;

1. Produce information on all available buses and their routes on enquiry.

2. Reserve a seat for a customer on the desired bus.

3. Produce a bus ticket for each booking instance.

4. Allow cancellation of any tickets on request.

5. Perform report generation.

One of the limitations of the limitations that the system has is that the customers may not be able

to access the booking/reservation services online. This system however can be a foundation for

online booking/reservation once the Company has developed its own website.

6. JUSTIFICATION:

Through the use of the Easycoach Booking and Reservation System, Easycoach Company would

have achieved a computerized and distributed booking system. This system will go a long way in

solving the main problems that the customers and the bus company usually face while making

ticket bookings and reservations.

The computerization of the process by transforming a manual booking system into a database

driven computerized system will ease the work of the company management while the

distribution of booking points all over the country through supermarkets will have brought the

booking/reservation service to a more convenient place to the customers.

The company booking/reservation system will have eliminated the problems of overbooking and

any other booking inconsistencies through this system. The system will synchronize the

company booking/reservation services done at all the booking spots at any time.

7

7. ANALYSIS/DESIGN:

7.1.OVERALL DESCRIPTION:

Easycoach Booking and Reservation System is developed to have an interactive user interface

and also has a database which will keep all the records regarding the buses and the travel times.

The system can be wholly described using the following diagrams.

7.1.1. Entity Relationship Diagrams:

The following E-R diagrams represent the object-relationship pairs in graphical forms. The pri-

mary goal of these E-R diagrams is to represent the data objects along with their relationships.

ER model for data in this case uses three features to describe data:

Entities which specify distinct real world items in an application.

Relationships connecting different entities and representing meaningful dependencies

between them.

Attributes which specify various properties of entities and relations involved in a sys-

tem.

E-R diagram for Reservation

8

Name Address

PASSENGER

Age Ticket no

BOOKING ATTENDANT

Username

RESERVE

Date

E-R diagram for Cancellation

E-R diagram for Enquiry

9

name address

PASSENGER

age Ticket no

BOOKING ATTENDANT

username

CANCEL

date

name address

PASSENGER

age Ticket no

BOOKING ATTENDANT

username

ENQUIRE

E-R diagram for Fare

10

name address

PASSENGER

age Ticket no

BOOKING ATTENDANT

username

PAY

8. IMPLEMENTATION AND TESTING:

Easycoach Booking and Reservation System´s implementation methodology includes four (4)

phases - Discovery, System Development, System Testing and Production Rollout. These

implementation phases are designed to provide users with a seamless transition from an existing

paper-based system to the electronic system while ensuring all aspects of the company’s

operations are accounted for by the software. The system developer is equipped with the skills

and tools to manage the entire process from system requirements gathering to deployment..

The Discovery Phase is preceded by a Project Kick-off Work-session that includes application

demonstrations, completion and review of requirements and configuration questionnaires,

identification of key client documentation, as well as consultation on possible process re-

engineering needs.. Detailed System development Process documents covering all aspects of the

implementation are provided; these include the Project Proposal as well as the Software

requirements specification.

8.1.Phase II: Training System Development

The Discovery process yields the specific client requirements that are used by Easycoach Com-

pany to provide its services to users. Training System Development will include configuration,

data entry and may include customization and data migration identified during the Discovery

process. The Training System Development culminates in the installation of a training system

which then begins the system testing process.

11

8.2.Phase III: System Testing

System Testing includes four critical functions in the project cycle: Training, User Proficiency,

Process Definition and Finalization of Specifications including Configuration, Customization

and Data Migration. The process starts with a series of formal on-site user training sessions fol-

lowed by hands-on system use, allowing the company staff to practice using the system, conduct

additional internal training sessions and begin creating task level procedural documentation. Ad-

ditionally, this will provide users with more in-depth knowledge of the system’s functionality.

System testing is performed in a controlled test environment to ensure that all requirements iden-

tified during the development have been met by the system design. System testing during the val-

idation phase includes functional, performance and regression testing.

Functional Testing - Ensures that all functional requirements of the system are met. A re-

quirements matrix should be used to ensure that requirements are tested and acceptable.

Performance Testing - Ensures that timing requirements such as throughput, response

time, and latency are met through design or optimization.

Regression Testing - As modifications are made to system design or configuration param-

eters during the validation phase, regression testing must be performed to ensure that

other system functions and throughput capabilities have not been degraded.

The testing process will be carried out in the presence of Easycoach company representatives

and any other interested parties. They will be open to criticize the system and give sugges-

tions on any modifications to suit their needs.

The process will be done with ten dummy customers who will be making a booking/reserva-

tion through three different computers linked to one server. The three computers will be in-

terconnected using Ethernet cables. This will simulate booking of buses from different points

or towns.

Any defect from the system will be noted and corrected immediately or within the shortest

time frame depending on its complexity. Any minor modifications may be made to the sys-

tem to more appropriately suit the user’s needs.

12

Once the testing stage is completed, the system will have qualified for implementation. The

development process therefore moves to the implementation stage.

8.3.Phase IV: Production Rollout

During this final phase, a master Production Rollout Plan is developed, which details product in-

stallation, staff communication and training schedule. The plan also includes identification of

power users who serve as the company’s functional experts, as part of the "Train the Trainer"

model, as well as individuals who will require specialized or more focused training. Addition-

ally, an internal communication plan is established to notify users of the transition to the new

system and of any expected impact on staff responsibilities.

13

9. CONLUSION AND RECOMMENDATIONS:

9.1.CONLUSIONS

The application EASYCOACH BOOKING AND RESERVATION SYSTEM has been prepared

with great excitement and enthusiasm. It required a lot of efforts and hard work, It may contain

minor errors and omissions due to the short time frame but they are going to be corrected once

detected. The characteristics of this software which make it more effective and efficient from ex-

isting system are as follows:

(a) It provides a better GUI environment to user.

(b) It provides an efficient security system to the software.

(c) The database is flexible.

(d) Most work is computerized, so, less man power is required.

(e) The application provides platform independent software.

(f) It is easily understandable and reliable.

(g) The user’s requirement is fulfilled.

9.2.RECOMMENDATIONS

As the developer of this system recommends EASYCOACH COMPANY through its

management to develop the company website and also embrace the currently available electronic

money transfer services such as zap and mpesa. This will enable the upgrading of this system to

an online booking system which is more efficient.

Due to the large number of players in the transport industry, the stiff competition they portray

and the ever advancing technology, it is paramount for the company management to consider my

recommendation as a priority plan.

14

10. PROJECT SCHEDULE AND BUDGET:

10.1. PROJECT SCHEDULE

ACTIVITY STARTDATE ENDDATE MILESTONE

Feasibility study 10-09-2010 21-09-2010 Completed project

proposal

Intelligence & logistics

gathering

22-09-2010 02-09-2010 Domain skills

Data mining 03-10-2010 10-10-2010 System requirements

Requirements

specification

11-10-2010 28-11-2010 Requirements

specification document

(RSD)

System design 1st week of 2nd sem 3rd week of 2nd sem System design

document(SDD)

System implementation 4th week of 2nd sem 6th week of 2nd sem Initial system version

System implementation 7th week of 2nd sem 8th week of 2nd sem Intermediate system

version

System implementation 9th week of 2nd sem 11th week of 2nd sem Final working system

Presentation 12th week of 2nd sem 12th week of 2nd sem Assessed system

15

10.2. ESTIMATED BUDGET

Item description Function Cost

Processor 2.8 GHz Computation/processing tasks 7,000

RAM 256 MB Main memory 3,000

HDD 80GB Data storage 5,000

Flash disc 512 MB Source-Code back-up 1,000

MySQL Database server -(open source)

Commuting Data collection 500

Networking Client communications 3,000

V.Basic.NET Programming tool -(open source)

Stationary Documentation 600

Monitor Visual display Unit 5,000

Motherboard System requirement 4,000

Chassis ’’ 1,,500

Programming efforts Implementation (My work) 40,000

Others miscellaneous 2,000

Total estimation 72,600

NB

Since this is my individual project sponsored by the department of computer science with free

computers, programming efforts and computer system requirements need not to count on the

overall budget. I have only indicated them from the end user perspective. I therefore wish to

state that this is just a mere estimation which might change with time in the development

process.

16