Transport Information System

Software Requirement Specification V0.0

1. Introduction 2 1.1 Purpose 2 1.2 Scope 3 1.3 Definitions, Acronyms and Abbreviations 3 1.4 References 4 1.5 Overview 5 2. 3. Overall Description 8

Table of Contents

Specific Requirements 14 3.1 Functionality 14 3.2 Usability 15 3.3 Reliability 15 3.4 Performance 15 3.4.1Response Time 15 3.4.3Throughput 15 3.4.4Capacity 15 3.4.5Resource Utilization 15

Page 2 of 14

Introduction
With the advancement in technology and increasing demand of uniform transport information, is now gradually adopting the use of computer in the business. Using this system users would be able to easily book cabs or flight online, from anywhere. This system will be cost effective and makes the work easy for the users. The problem with the manual entry system was that separate registers were to be maintained for each of the different department due to which scattered information was available to the employee. But the advantage with the new system is that all information can be made available at a single place which is easily accessible to the users through internet and users need not to stand in queues at the travel agencies to book cabs or flights, which are located only on specific places in a city. This system also provides password protection for data so that it cannot be misused by any of the unauthorized user. This will allow the department head to have a watch over the orders 24x7.

Purpose

If the entire process of booking is done in a manually then firstly it would cause inconvenience to the users. Secondly, it would cause irregularity and non-uniformity in the booking data, in a case where a transport booking firm has many offices at different locations which book the same number of cabs. Hence there comes a need to switch to automated TIS which helps in meeting the current rising demand of people who wish to book cabs/flights online . When the data repository is maintained on the computer then it is more secure compared to repository maintained on registers which are accessible to unauthorized personnel and are also subject to wear and tear with the passage of time.

Scope
Page 3 of 14

The Software Requirements Specification captures all the requirements in a single document. The TIS that is to be developed provides the customers and employees of the firm with the customer information and the status of transport booking. The TIS is supposed to have the following advantages: The process becomes faster. Accurate calculation can be done. Report generation at ease. Search of information at ease. Wastage of resource can be saved.

Definitions, Acronyms and Abbreviations

TIS - Transport Information System - User ID - Employee ID

UID EID

Employee It refers to the designated employee working for the Automobile firm.

Administrator The user full authority/right over the software. He/she has the responsibility for maintenance of software. Customer He/she is the end user who uses the software. ATIS Automated Transport information system. CTIS Conventional Transport information system.

FAQs Frequently asked questions.

Page 4 of 14

References
The SRS document uses the following documents as references: SRS IEEE template

www.wikipedia.org

Overview
Administrator subsystem

User Login subsystem

Tutorial subsystem

TRANSPORT INFORMATIO N SYSTEM

Billing Subsystem

Page 5 of 14 Email subsystem Data Repository Customer Care subsystem Subsystem

 Administrator Subsystem This subsystem will have the full control over the entire software. Maintenance of administrator. the software is done by the

In case of any kind of malfunctioning of system, administrator will take appropriate actions.

The administrator will have full right to view all the user and employee details.

User login Subsystem

The customer who will use this system is required to have a user account. If he/she already owns an account then, in order to login they are required to provide their respective username and password.

But if they are new user then they are required to sign up for an account. The date and time of login of the users (Employee/customer) will be recorded in the database.

Tutorial Subsystem
This subsystem will be optional. This system will provide help to the new customer willing to use the software. This subsystem is complete guide in itself.
Page 6 of 14

But still if needs some kind of help then he/she can send an email to the customer care subsystem.

Billing Subsystem
The task of this subsystem is to generate bill for a particular customer according to his/her bookings. The customer will be given a choice regarding the mode of payment- credit card or cash. It will generate a unique bill number transaction by user i.e. transaction-id . for each

Email Subsystem
This subsystem comes into action after the user has confirmed his/her booking.

The customer booking first goes to billing system for processing and after that an email is sent to the customer for confirming receival of payment.

Data Repository Subsystem

It is a database that contains the details of each and every customer, employee. The customer details include personal information like name, age, address, email, contact number etc. It also includes the booking details of the customer like date of travel, mode(flight/cab), class(in case of flight), number of persons, bill details etc.

This also keeps a record of the flight details issued by the airways companies, details of the different private cabs owned by the firm with seating capacity and cab drivers information.
Page 7 of 14

 Customer Care Subsystem

This subsystem looks into the grievances/complains faced by the user while operating the software. The customer can contact the customer care unit by sending an email to the customer care division. The customer can post his/her queries/complaint which has to be replied within 2 working days. Customer can also contact the division by through the customer care numbers displayed. While filing a complaint the customer has to specify his/her ID and subsequently a complaint ID will be generated.

Overall Descriptions
Product Perspective
The Transport Information system is a package to be used by Travel Agencies and its customer to improve the efficiency of employees working for the firm and end users. In this era, where time matters a lot, this will benefit the customers by saving their time. This software is intended to help the customers to book cab/flight over the net just by entering source and destination place. This software will reduce the complexity of analyzing the huge information of the routes of various transports and then analyzing the cost which is done in conventional booking. Conventional means of maintaining transport information includes maintenance of records of different department
Page 8 of 14

like route and timing information of transport, customer details, customer booking, billing system etc. in separate registers. The problem with this system is that scattered data is available to the employees which have to be integrated before processing. This increases the workload and also demands lot of man power. This software will also save the time of the customer because now she/he is able to book the transports(cab/flight) over the net instead of waiting at the booking counters. It will also benefit the people who dont have easy access to airport authority offices or cab booking counters. This software will enhance the security of data by providing passwords to customers so that only authorized user could view or modify the data. The software will maintain a database regarding the personal details of customer, their requirements, mode of payment etc. The product has to interact with other systems like: Internet, Billing System and the Information Security System.

Product Function
The Transport Information System provides online real time information about the current status of availability of flight/cab. The Product functions are more or less the same as described in the product perspective. The functions of the system include the system providing different type of services to the customer.

In order to book the flights or cabs online the system provides login facility to the users. In case, the user doesnt has an account, system will provide guest booking facility.

Page 9 of 14

 The system will contain 2 portals: flight booking and cab booking. The user can choose the one according to his need. The customer will be required to enter the information like date of journey, number of passengers etc. and corresponding to the dates and availability, the flights/cabs will be displayed accordingly. The customer will also be asked about the mode of payment - credit card or cash. The customer will get the booking confirmation through an email. In case of cab booking, the cab driver will receive an email regarding the customer details and the date of journey. The customer care subsystem provides an additional feature to the customer for registering their queries/complaints about the software. The tutorial subsystem will guide the end user i.e. customers about the usage of the software by providing necessary tutorials on various topics. It also includes FAQs. Finally a report will be generated mentioning customer name, ID, his/her bookings, amount paid etc.

USER CHARACTERISTICS
This system is used by three kinds of users namely the administrator, employee working for the firm and the customer (or the buyer).

Administrator
The administrators of the system who have more knowledge of the internals of the system and are able to rectify the small problems that may arise due to disk
Page 10 of 14

crashes, power failures and other catastrophes to maintain the system.

They have the right to view all the user information, their bookings etc.

Customer

Customer is the end user who is going to operate this software.

Compared to other users he/she has very basic knowledge about computers. Customer is assumed to have some basic knowledge about automobiles.

Constraints The information of all the customers must be stored in a database that is accessible by the administrator and the designated employees. The TIS must be compatible with the Internet applications. The TIS is connected 24X7 to the server. The users access the TIS from any computer that has Internet browsing capabilities and an Internet connection. The booking system is connected to the TIS and the database used by the booking system must be compatible with the interface of the TIS. The users must have their correct usernames and passwords to login to the database. No multilingual language support.

Page 11 of 14

 Assumptions and dependencies The users have sufficient knowledge of computers. The computers used by the firm should have Internet connection and Internet server capabilities. The users know the English language, as the user interface will be provided in English The product can access the customer database.

Specific Requirements

Functionality Logon Capabilities

The system shall provide the Administrator and customers with logon capabilities.

The users login shall be allowed 24 hours a day. Status Capabilities

The system shall update the current status of flights and cabs which includes the seats availability.

Information Capabilities The system shall provide the information regarding the procedure of application to the applicants.

The system should have tutorial for the users which are unfamiliar with software.

Feedback and Enquiry capabilities

There shall be a provision for the customer to submit feedback regarding the services.

Page 12 of 14

 The contact numbers of the concerned authorities should be provided for enquiry. Usability requirements The system shall allow the users to access the system from the Internet using HTML or its derivative technologies. The system uses a web browser as an interface. Since all users are familiar with the general usage of browsers, no specific training is required. The system is user friendly and self-explanatory. Reliability requirements The system has to be very reliable due to the importance of data and the damages incorrect or incomplete data can do. Under ideal condition system is available 100% for the user and is used 24 hrs. a day and 365 days a year. The system shall be operational 24 hours a day and 7 days a week.

The accuracy of the system is limited by the accuracy of the speed at which the employees/administrator and user of the designed software.

Performance requirements

Response Time The Splash Page or Information page should be able to be downloaded within a minute using a 56K modem. The information is refreshed every two minutes. The system shall be allowed to take more time when doing large processing jobs. Throughput The number of transactions is directly dependent on the number of users; the users may be the client, administrator and employee.

Page 13 of 14

 Capacity The system shall be capable of handling more than one user at a time. Resource Utilization The resources are modified according the clients requirements and also according to the feedback submitted by the users.

Page 14 of 14