Cab booking system management, Lab Reports of Web Application Development

Download Cab booking system management and more Lab Reports Web Application Development in PDF only on Docsity!

Software Requirements

Specification

for

Online Taxi booking

Version 1.0 approved

Prepared by:

Chavan Vinayak Jitendra

Choudhari Sangita Vagaram

Suryawanshi Anita Anandrao

Table of Contents

Table of Contents...........................................................................................................................ii

Revision History

• 1. Introduction.............................................................................................................................. Revision History.............................................................................................................................ii
  • 1.1 Purpose...........................................................................................................................................
  • 1.2 Document Conventions...................................................................................................................
  • 1.3 Intended Audience and Reading Suggestions.................................................................................
  • 1.4 Product Scope.................................................................................................................................
  • 1.5 References......................................................................................................................................
• 2. Overall Description..................................................................................................................
  • 2.1 Product Perspective........................................................................................................................
  • 2.2 Product Functions...........................................................................................................................
  • 2.3 User Classes and Characteristics.....................................................................................................
  • 2.4 Operating Environment...................................................................................................................
  • 2.5 Design and Implementation Constraints.........................................................................................
  • 2.6 User Documentation.......................................................................................................................
  • 2.7 Assumptions and Dependencies......................................................................................................
• 3. External Interface Requirements...........................................................................................
  • 3.1 User Interfaces................................................................................................................................
  • 3.2 Hardware Interfaces........................................................................................................................
  • 3.3 Software Interfaces.........................................................................................................................
  • 3.4 Communications Interfaces............................................................................................................
• 4. System Features.......................................................................................................................
  • 4.1 System Feature
  • 4.2 System Feature 2 (and so on)..........................................................................................................
• 5. Other Nonfunctional Requirements.......................................................................................
  • 5.1 Performance Requirements.............................................................................................................
  • 5.2 Safety Requirements.......................................................................................................................
  • 5.3 Security Requirements....................................................................................................................
  • 5.4 Software Quality Attributes............................................................................................................
  • 5.5 Business Rules................................................................................................................................
• 6. Other Requirements................................................................................................................
• Appendix A: Glossary...................................................................................................................
• Appendix B: Analysis Models.......................................................................................................
• Appendix C: To Be Determined List............................................................................................

1.4 Product Scope.................................................................................................................................

This project’s aim is to automate the system, calculating the fare, collecting fare,

collecting all necessary information of the client and then serve the client. The data

used by the system is stored in a database that will be the centre of all information

held clients 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 jobs of the people involved easier. It supports the

current process but centralizes it and makes it possible for decisions to be made

earlier and easier way.

Goals The main goal of the system is to automate the process carried out in the organization with improved performance and realize the vision of online booking. Some of the goals of the system are listed below:

 Manage large number of client details.

 Manage all details of clients who registered and requested for getting the service.

 Create employee accounts and maintain the data’s effectively.

 View all the details of the clients and employees.

 Showing available vehicles to book for the client.

 Calculating and showing the fare to client before booking.

 Create the statistical reports to facilitate the finance department work.

 Getting the feedback from the client to facilitate future improvement.

Ultimately it focuses on

 Passenger Revenue Enchantment  Improved and Optimized service

1.5 References......................................................................................................................................

 http://msdn.microsoft.com/en-us/library/ms  http://www.chambers.com.au/glossary/software_requirements_specification.php

 http://ac.aup.fr/~croda/SampleStudentsWork/cs348/finalProjectS07/final %20presentation/final/Volere_Specifications_FV.pdf

2. Overall Description..................................................................................................................

2.1 Product Perspective........................................................................................................................

A online taxi booking system contains the following information:

1. customer details – It contains the customer name , phone number and email id. A separate account is created for each customer so that they can login using any device and book their rides with ease. It also enables the customers for discount coupons.
2. driver details – It contains driver’s name , address ,phone number ,driving license details and the vehicle details. The driver also has a specific account login enabling him to see the potential riders nearby and accept their ride requests.
3. taxi details – It contains all the details about the taxi being used by the company and driven by the drivers such as RC number ,insurance details and license plate details. It also has a gps system fitted for the gps to show correct way to both the driver and the rider. The taxi is also fitted with a speed controller to ensure the driver follows the given guidelines.

2.2 Product Functions...........................................................................................................................

The functions which can be performed using this application are:

1. check the availability of taxi near you
2. book a taxi for your desired destination
3. get the details of the driver and the vehicle
4. ride the taxi
5. make payment for your ride
6. rate your ride experience
7. check past rides and billings

2.3 User Classes and Characteristics.....................................................................................................

The different user classes for this application are :

1. the rider – rider has a account created on the app which is used to book taxi and ride it to destination. Also rider can cancel the ride and has limited access to the driver information.
2. the driver – a driver can accept the ride request or reject the request. He can also cancel the ride before starting the ride and receive payments for the ride after ending. Driver also has limited access to the customer information i.e. only the name and phone number.
3. company – the company has complete info about both the rider and the driver and can access their current locations and also provide discount coupons to the rider and make payments to the driver.

3. External Interface Requirements...........................................................................................

3.1 User Interfaces................................................................................................................................

Since the System is used different user interface(UI) is depending on the function the user is authorized to perform. User access such as login and then to homepage is provided. Through this homepage interface ,all basic user’s function is show but can be accessed after login and based on user access authorization. This system is very user friendly which the new user of the system that can be sign up and then drop feedback form the experience user before operating it.

3.2 Hardware Interfaces........................................................................................................................

Just like any other system requires basic computer that consists of CPU, monitor, keyboard, and mouse or laptop and smartphone for input and output. Printer is needed for print function if required. Beside, for direction the system is connected with GPS device in every organization transportation vehicle to get transportation details.

3.3 Software Interfaces.........................................................................................................................

The System will require software JAVA or PYTHON,PHP to perform and create the online transport Booking system Booking process of the system that organize the distribution of user in the local network and to do this online booking.

3.4 Communications Interfaces............................................................................................................

The System communication Interface is completely depend on server software to ensure correct send and retrieve data from database other than that is an online protocol to connect between GPS and the System.

4. System Features.......................................................................................................................

4.1: BACK-END

4.1.1 : View Available Vehicles: The client must able to see all details about the available

vehicles without any constraints.

4.1.2 : Calculate Fare: The client must be available to check the fare they should pay

for the vehicles.

4.1.3 : Feedback: The administrator can able to see the feedback given by

each client so that he can take appropriate actions for future

improvement.

4.1.4 : Report Generation: The system supports generation of reports based on diff. bases.

4.1.5 : Record maintenance: The system also must keep track the statistical reports of daily

activities of the online booking.

4.1.6 : Discount Offer: The admin can create discount codes and the client can get discount on

fares using the codes.

4.2: FRONT-END

4.2.1 : Taxi Details: Customers may view the taxi timings on the same date of the

booking, or on the scheduled date and time

4.2.2 : Booking: Users to be given a choice of the type of vehicle to be chose, and

the fares Accordingly.

4.2.3 : Billing: The fares to be displayed inclusive of taxes and duties.

4.2.4 : Cancellation: The user may also cancel their booking if they got other plans.

4.2.5 : Driver Info: Information of the driver driving the vehicle is displayed, along

with his/her credentials and all important information.

5. Other Nonfunctional Requirements.......................................................................................

5.1 Performance Requirements.............................................................................................................

1. 24 X 7 availability

Apache is used to develop the product. So it is easiest to port the software in any environment. Android , Blackberry, windows version should be there.

3. Availability The System should be available 24* 7 .Customer Friendly Software Should be there.in Case of hardware or database failure there should be a replacement page should be _shown.And in case of database failure there should be backup of database.

4. Maintainability_ _The user will be able to reset all options and all stored user variables to default settings.
5. Reliability_ Some of the attributes identified for the reliability is listed below:  All data storage for user variables will be committed to the database at the time of entry.  Data corruption is prevented by applying the possible backup procedures _and techniques.
6. Usability requirements_ Some of the usability requirements identified for this system are listed below:  A logical interface is essential to an easy to use system, speeding up common tasks.  Error prevention is integral to the system and is provided in a number of formats from sanity checks to limiting free-text input.

5.5 Business Rules................................................................................................................................

1. Cancelation of booking -Policy:  Rides booked on your platform can be cancelled before the ride is started. A valid cancellation reason needs to be sent in the request, which needs to be chosen by the user out of given options.  Any previous ride cancellation charges which will be collected in the current ride 2. There can be multiple booking at a time.

6. Other Requirements................................................................................................................

6.1 6.1: Administrator Aspect

1. Perform weekly roster of Employees

2. Print reports annually, weekly, and daily

3. Check feedbacks

4. Send newsletters

5. Manage user portfolio

6. Changing the super password.

6.2 6.2: Employee Aspect

1. Logging into the system.

2. To check their rosters.

3. Maintain daily logs

4. Select availability.

5. Check online bookings

6.3 6.3: Client Aspect:

1. Make a booking
2. Check their booking status
3. Fair calculation
4. Driver history

5. Changing password.

6. Resetting of forgotten password.

6.4 6.4: Analysis

1. Authenticating users based on username and password.

2. Keeping session track of user activity.

3. Recording client’s request for booking.

4. Checking whether the vehicle is available for booking.

5. Keeping history of courses bookings.

6. Keeping record of feedbacks received from the clients.

6.5 6.5: Mailing

1. Temporary password will be mailed to the user incase the user forgets

the password.

2. Newsletters should go the clients email addresses.

3. The client should get notification email of the booking while confirmed.