Sunteți pe pagina 1din 11

Software Requirements Specification

For Road transport booking system


Prepared by,
Batch No: 14

A. Stephen M.Alagumurugan K.Natarajan

91309134035 91309134501 91309134021

Astephen92@gmail.com rajaindia1988@gmail.com plantandsavetrees@yahoo.com

Instructor: Course: Teaching Assistant:

Mrs. B.Sujatha B.Tech.I.T.

Mrs. B.Sujatha

Contents
PREFACE............................................... ERROR! BOOKMARK NOT DEFINED. 1 INTRODUCTION ..............................................................................................4 1.1 DOCUMENT PURPOSE ..................................................................................4 1.2 1.3 1.4 1.5 1.6 2 PRODUCT SCOPE ................................. ERROR! BOOKMARK NOT DEFINED. DEFINITIONS, ACRONYMS AND ABBREVIATIONSERROR! BOOKMARK NOT DEFINED. DOCUMENT CONVENTIONS .................. ERROR! BOOKMARK NOT DEFINED. REFERENCES AND ACKNOWLEDGMENTSERROR! BOOKMARK NOT DEFINED.

INTENDED AUDIENCE AND DOCUMENT OVERVIEWERROR! BOOKMARK NOT DEFINED

OVERALL DESCRIPTION .............................................................................6 2.1 PRODUCT PERSPECTIVE ...................... ERROR! BOOKMARK NOT DEFINED. 2.2 2.3 2.4 PRODUCT FUNCTIONALITY ................... ERROR! BOOKMARK NOT DEFINED. USERS AND CHARACTERISTICS............ ERROR! BOOKMARK NOT DEFINED. ASSUMPTIONS AND DEPENDENCIES .... ERROR! BOOKMARK NOT DEFINED.

SPECIFIC REQUIREMENTS .........................................................................9 3.1 EXTERNAL INTERFACE REQUIREMENTSERROR! BOOKMARK NOT DEFINED. 3.2 3.3 FUNCTIONAL REQUIREMENTS .............. ERROR! BOOKMARK NOT DEFINED. BEHAVIOUR REQUIREMENTS ................ ERROR! BOOKMARK NOT DEFINED.

Preface
The document contains the Software Requirements Specification of ROAD TRANSPORT BOOKING SYSTEM (RTBS), which can be used for the all of the internet users. The Ticket Reservation System is an Internet based application that can be accesses throughout the Net and can be accessed by anyone who has a net connection. This application will automate the reservation of tickets and Enquiries about availability of the tickets. This application includes email information for the tickets. The Goal of the Software Requirement Specification is to describe overall Functionality of the ROAD TRANSPORT BOOKING SYSTEM (RTBS). This system is prepared according to IEEE standard. The Software Requirements Specification is in content compliance with the IEEE standard in which the contents of this standard are rearranged and a mapping is provided. That is, the content compliant Software Requirements Specification is mapped into various clauses and sub clauses of the IEEE standard. 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 Introduction
Road transport booking system (RTBS) is an advanced booking service for the roadways. RTBS enables the user to book for the road transporting services such as bus booking, taxi booking services and tourism travels service. It offers the service form any city to any city in the form of above services. 1.1 Document Purpose: The purpose of the Software Requirements Specification document is to maintain all the functions and the specifications of the Road transport booking system. Besides, it contains the detailed descriptions of all the requirements specified before. 1.2 SCOPE: The scope of the RTBS is: 1. A person should be able to

Login to the system through the first page of the application. Change the password after logging into the system Should be able to create a new login for the accessing the reservation facility. Query the buses for two weeks (Only two weeks advance reservation is available). No reservation before two days can be done. See his/her current reservations on different buses along with the details and also for travels and taxi reservations. Able to choose the seats which can are available for a certain class. Able to carry their booking for travels and call taxies for different boarding points.

1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS Acquirer: specifies requirements for and accepts delivery of a new or modified software product and its documentation. Administrator: The one who manages and maintains systems and software. Calendar: it is a tool which user enters monthly program

ROAD TRANSPORT BOOKING SYSTEM (RTBS) Our project name. FAQ: Frequently Asked Questions. IEEE: Institute of Electrics & Electronics Engineering IS: Information Systems IT: Information Technology Marquee: A piece of text that scrolls across a browser document window SDD: Software Design Document Server: The main computer on a network. SPMP: Software Project Management Plan SRS: Software Requirements Specification Staff: The people who works for Red Bus Company. Team: The name of the developer group. User: People who open the RTBS domain and the administrator of the RTBS domain. Web: The network of computers that forms the Internet. 1.4 REFERENCES [1] IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans [2] IEEE STD 830-1998, IEEE Recommended Practice for Software Requirements Specifications [3] IEEE STD 1016-1998, Recommended Practice for Software Design Descriptions [4] Pressman, Roger S., Software Engineering A Practitioners Approach, Fifth Edition, McGraw-Hill, 2000. [5] http://httpd.apache.org/ [6] http://www.macromedia.com 1.5 OVERVIEW: After giving a brief introduction about the project, the body of the report is divided into two parts. They are; The 2 chapter contains a full description of the functions, their properties, their aims, the constraints and the requirements of the project.

2 Overall Description
2. OVERALL DESCRIPTION
This section describes the functions of the project and their aims. It also includes the constraints and the requirements of the project. 2.1 PRODUCT PERSPECTIVE ROAD TRANSPORT BOOKING SYSTEM (RTBS) provides a group of works with interface environments. Also there will be a database which will keep all the records that done by user while visiting the page.

2.1.1 SYSTEM INTERFACES ROAD TRANSPORT BOOKING SYSTEM (RTBS) is connected with company server database, thus no more connection with other systems is needed. No system interface is needed during the development of this project. 2.1.2 USER INTERFACES The RTBS shall be designed as a web based that has a main user interface. Format of main screen shall be standard and flexible. The system shall be user friendly designed. Pages shall be connected each other in a consistent way. Operations can be done with the system shall be repeatable. The design of the pages should allow users to do all processes as prescribed in the application. 2.1.3 HARDWARE INTERFACES There is no need any hardware interface for Road Transport Booking System (RTBS) System. 2.1.4 SOFTWARE INTERFACES (a)Microsoft visual basic 6.0: Our application is mainly designed with VB as a front end tool and to design all user interfaces and each operation is carried out in a step by step manner. As our application is web oriented any optimized internet browsers can be used as an interface.

(b)Microsoft access2007: The database used in our application is MS Access as a backend tool and data is stored in a secure manner. (c) Operating system: The operating system used for our product is Microsoft windows XP. 2.1.5 COMMUNICATION INTERFACES The default communication protocol for data transmission between server and the client is Transmission Control Protocol/ Internet Protocol (TCP/IP). At the upper level Hyper Text Transfer Protocol (HTTP, default port=80, default of apache port=8080) will be used for communication between the web server and client. 2.1.6 MEMORY CONSTRAINTS There is not a specific memory constraint for RTBS. 2.2 PRODUCT FUNCTIONS RTBS is: 1. Login to the system through the first page of the application 2. Change the password after logging into the system 3. Should be able to create a new login for the accessing the reservation facility. 4. Query the buses for two weeks (Only two weeks advance reservation is available) and for taxies before two days. 5. No reservation before two days can be done. 6. See current reservations on different buses along with the details. 7. Able to choose the seats which can are available for a certain class. 8. Give details about the details about the credit card details. 9. A mail should be send to the concerned person about the confirmation of the ticket to the specified email address. 10. The login Id and password should be sent to the mentioned email address if a new account is created. 11. A calendar should be there which helps the person to select dates. It should also show the public and nation holidays. 12. The system should automatically show the fare for the corresponding seat and amount of money needs to be pay for selected seats. 13. The administrator of the web site should used an admin tool for customize the web site.

14. The admin tool shall handle followings: a) Shall change the logo b) Shall add or remove links onto the main bar c) Shall give options for search tools d) Shall add, remove or update links on the menu e) Shall add, remove or update events on the event calendar 15. Logout from the system. 2.3 USER CHARACTERISTICS The user types that would use the OBTRS are as follows
:

Administrator: Administrators shall usually do anything on the site, in all pages. Administrator is responsible for updating and the maintenance of the web site content such as adding/removing information about the company, adding/removing links onto the main bar, adding/removing medias in the content menu, adding/removing/updating links on the event calendar and the menu, changing the logo. Customer: Customers are people who shall use RTBS. To use this service people should have the basic computer using ability. They shall see the buses information which is belong to current time. User can see all general information, FAQ can use search. External Users: External users are people who have not got any user account for the web site. They shall use the general information, FAQ. 2.4 ASSUMPTIONS AND DEPENDENCIES The user must have the ability to use the internet. The user must have connected to the internet to use the system. The users computer must be Windows 95 or later version platforms and Microsoft Internet Explorer version 5.5 or later TCP/IP protocol must be installed to communicate through HTTP messages. The accuracy of the information of users is the responsibility of all users.

3 Specific Requirements 3. SPECIFIC REQUIREMENTS


3.1 EXTERNAL INTERFACE REQUIREMENTS Interfaces external to the RTBS can be explained as User Interfaces. The section 2.1.2 User Interfaces provide details of the user interfaces. 3.2.1 FUNCTIONS: The following are the use cases used in our project
i. ii. iii. iv. v. vi. Login Signup Select category Book ticket Make payment Logout

3.3DESIGN CONSTRAINTS
All documentation of the system shall be prepared related to IEEE standards. Furthermore, the content shall be compliance with IEEE standards [1, 2 and 3].

3.4 SOFTWARE SYSTEM ATTRIBUTES


3.4.1 RELIABILITY The system shall operate 95% of the time. The number of defect should not exceed 10 per function. In addition, before the submission of the final release the calendar must be tested in case of the defects over 10 per function. 3.4.2 AVAILABILITY The availability of the RTBS is up to the internet connection of the client. Since this is client-server related web-site, web-site shall be attainable all the time. User should have an account to enter the system, if user does not have an account; for the availability of the RTBS user should sign up to the system by clicking the sign up link from the home page.

3.4.3 SECURITY The authorization mechanism of the system will block the unwanted attempts to the server and also let the system decide on which privileges may the user have. The system has different types of users so there are different levels of authorization. There will be also a firewall installed on the server so the incoming transactions can be filtered. Data integrity for critical variables will also be checked. 3.4.4 MAINTAINABILITY The requirements, modules that are explained in this document are enough to satisfy the customers needs and wants. The maintainability shall be easily done by integrating new modules and offering new software solutions for the system.

3.4.5 PORTABILITY The RTBS is an online service. So, anyone can use the service. One and only the server of the system must have the required software including MySQL, Apache. 3.6 OTHER REQUIREMENTS There are no other requirements in this phase. If some extra requirements are wanted by the customer or acquirer, these are added in this part later.

S-ar putea să vă placă și