14-06-2012, 03:53 PM
SRS (Software Requirement Specifications)
SRS .docx (Size: 46.15 KB / Downloads: 27)
INTRODUCTION
The SRS (Software Requirement Specifications) is a complete description of the behavior of a system to be developed. This SRS would include a set of use-cases that describe all the interaction the users will have with the software. In addition to use-cases, SRS also contains non-functional requirements. The final product will include all the functionalities that we include in SRS.
Purpose
The purpose of this software requirements specification is to verify that all the specifications are correct and are verified. This document also serves to ensure that the software is traceable throughout its software development life cycle. It describes the detailed design needed to implement the system. It provides the visibility and information needed for software support.
Intended Audience:
This SRS would be used by the following people:
Developers: The developers would use this document to implement the functionalities and to ensure traceability of the software.
Designer: The designers would use this document to design all the user interfaces
required for the easy implementation of the software.
Testers: The testers would use this document to know the interfaces and to test the software accordingly.
Users: The users would use this document to verify if the requirements specified satisfy their needs.
Scope
The proposed software product is the Comfort Tours and Travels Reservation System. Supported by a well designed database, all available flight, cars, buses, hotels information is integrated together and can be accessed easily through a single point. A friendly user interface is provided so that various combinations of search criteria can be fetched from user and generates corresponding database search statements. Comfort Tours and Travels provides both customer and administration interfaces with the latter used for administration purposes.
Definitions, Acronyms and Abbreviations
Administrator: The one who manages and maintains computer systems and software.
ASP: Active Server Pages
Visitor: The one who visits the site to gather the information.
Registered User: The one who already has an account and information stored in travel agency’s database.
Comfort Tours and Travels Reservation System (CTTRS): The project name.
FAQ: Frequently Asked Questions.
IEEE: Institute of Electrics and Electronics Engineering.
SDS: Software Design Specification.
Server: The main computer on a network.
SRS: Software Requirement Specification.
User: People who open the OASPSD website and the administrator of the site.
Web: The network of computers that forms the Internet.
Login ID - A user identification number to enter the system
Password - A word that enables one to gain admission into the system
Web-based application - An application that runs on the Internet
GUI - Graphical User Interface
Overview
The SRS will include two sections, namely:
Overall Description: This section will describe major components of the system like:
• Details about our final product
• The various interfaces involved during the development phase
• The individual details about each module along with the concerned actors.
• The user characteristics and constraints, if any.
• Assumptions and dependencies involved.
• The future scope of the project.
Specific Requirements:
This section will describe the intricate details about each component of the system including the functions of the different actors along with the database designing:
• The details of each screen with which the user interacts, called external interfaces.
• Brief description of the functions along with the validity checks and proper flow of operation.
• The database designing.
• Software system attributes, also called non-functional requirements.
OVERALL DESCRIPTION
This section describes the functions of the project and their aims. It also includes the constraints and the requirements of the project. CTTRS is designed for three types of users, namely administrator, visitors and users. Interactive forms are designed to make it user friendly. Administrator is responsible for creating and maintaining database, updating the records. Visitors are the people who just browse our website. Every user has a unique login id and password, provided by the agency.
Product Perspective
Our software is self contained. We are trying to design an independent project in which all the
modules are linked or interrelated to one another and would run without the help of another
project.
Hardware Requirements:
Server Side:
RAM: 512 MB
HDD: 4 GB or more
Processor4
Client Side:
RAM: 512 MB
HDD: 4 GB or more
Processor: P4
Software Requirements:
Server Side:
OS: Windows Server 2000 or onwards
Client Side:
OS: Any OS
Browser: Any browser compatible with IE 5.0 or onwards
Communication Interfaces
The default communication protocol for data transmission between the server
and client is Transmission Control Protocol/Internet Protocol (TCP/IP). At the upper level
Hyper Text Transfer Protocol will be used for communication between web server and client.
Operations
ADMINISTRATOR:
Check IDs and passwords
Provide access rights
View and respond to feedback.
Delete, update and edit records
VISITOR:
Can browse the website
USER:
Create a new account for himself / herself.
Reserve tickets for flights, buses, hire cars, book hotels.
Can seek information related to reservation.