31-03-2012, 10:32 AM
SOFTWARE REQUIREMENT SPECIFICATION
SOFTWARE REQUIREMENT SPECIFICATION.docx (Size: 73.1 KB / Downloads: 56)
. INTRODUCTION:
1.1 SYSTEM OVERVIEW:
• EXISTING SYSTEM
In few countries if a person wants to book a flight ticket, he use to follow one of these things:
Manually goes to the Airport and book his ticket.
Downloading the ticket form as paper document, filling it manually and submitting it at Airport.
Fill the Ticket form on system and get the print out as paper documents to submit it at Airport.
Booking the Ticket at some particular registered ticket counters in online.
Even above approaches make a ticket booking online, it was not completely done on online. Passenger may not have much freedom over this approach.
Hence the Passenger may or may not be satisfied with this approach as it includes manual intervention like travelling to Airport for booking his ticket.
• PROPOSED SYSTEM
The Proposed system ensures the complete freedom for users, where user at his own system can logon to this website and can book his ticket. Our proposed system allows only registered users to book the tickets, view timings and cancel their tickets.
In this Proposal the entire work is done on online and ticket with id is also provided for passengers as a print document. Here passengers can send their queries and suggestions through a feedback form.
1.2 SYSTEM ARCHITECTURE:
The application will follow three-tier architecture. In three-tier architecture application will run the traditional client/server model but from the web server. The client only displays the GUI and data but has no part in producing results.
Internet,LAN or
WAN Connection LAN Connection
Or Same
Computer
Thin Client Workstation Application Server Database Server
(Tier 1) (Middle Tier) (Tier 3)
Three-tier architecture will contain the following tiers
• Client/Presentation Tier
This tier includes all the HTML content or forms to be displayed on the client browser. It is the form which provides the user interface to end user. Programmer uses this tier to get or set the data back and forth.
• Business Logic Layer
In the Business logic tier, the actual processing of the data and the logic behind the implementation of the application will be present. This tier can contain a class, which can be used to write the functions, and also works as a mediator between the presentation tier and data tiers.
• Data Tier
Data Tier contains methods and classes that deal with passing and storing data to the data Storage Layer. Queries or stored procedures are used to access the data from the database or to perform any operation to the database. It stores the data passed by the presentation tier.
1.3 DEFINATIONS,ACRONYMS & ABBREVATIONS :
HTML: Hypertext Markup Language is a markup language used to design static web pages.
Asp: Active server pages is used to develop web application
IIS: Internet Information Service is a web server to run web application
VS :Visual Studio is application where we can develop application by using this IDE
HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server.
HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).
TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP.
2.SOFTWARE REQUIREMENT SPECIFICATION:
A software requirements specification (SRS) is a complete description of the behavior of the software to be developed. It includes a set of use cases that describe all of the interactions that the users will have with the software. In addition to use cases, the SRS contains functional requirements, which define the internal workings of the software: that is, the calculations, technical details, data manipulation and processing, and other specific functionality that shows how the use cases are to be satisfied. It also contains nonfunctional requirements, which impose constraints on the design or implementation (such as performance requirements, quality standards or design constraints).
The SRS phase consists of two basic activities:
• Problem/Requirement Analysis
The process is order and more nebulous of the two, deals with understanding the problem, the goal and constraint.
• Requirement Specification
Here, the focus is on specifying what has been found giving analysis such as representation, specification languages and tools, and checking the specifications are addressed during this activity.
The Requirement phase terminates with the production of the validate SRS document. Producing the SRS document is the basic goal of this phase.
• Role of SRS
The purpose of the Software Requirement Specification is to reduce the communication gap between the clients and the developers.Software Requirement Specification is the medium though which the client and user needs are accurately specified. It forms the basis of software development. A good SRS should satisfy all the parties involved in the system.
2.1MODULAR DESCRIPTION & FUNCTIONAL REQUIREMENTS
The list of modules incorporated with “AIRLINE RESERVATION SYSTEM” are
a.Registration module
b.Administrative module
c.Passenger module
a. Registration module
In registration module first we ask passenger to give his details.After registering with us the passenger can logon to his/her own account and can view all flight details such as Timings, Prices,Availability of seats and can book the ticket with unique ticket id.Once Passenger registered with us can book any number of tickets.
b. Administrative module
Administrative module is provided for the sake of administrators to manage the site and update the content at regular intervals, The major operations included in this module are:
Create and maintain airline schedule, fare and timings of the Flight.
View the passenger list.
View the available seats in the flights.
Cancel the tickets.
Updating the flight schedule and timings and fare.
c. Passenger module
This module is meant for passengers, where a user logging into his/her owns account will view this panel. The major operations included in this module were
View all airline schedules, timings, fare details and seats availability.
Book for the tickets.
View and cancelling of the ticket.
Send feedback.
Behind these modules, it also includes additional WebPages like Password recovery console, Tips regarding journey, Traveling news around world and help regarding our site.
2.2 Product Perspective:
The web pages (ASP) are present to provide the user interface on customer side
Communication between customer and server is provided through HTTP/HTTPS protocols.
The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used.
On the Server Side web server is for EJB and database server is for storing the information.
2.3 Software Interfaces
Development Environment
Operating System : Windows XP
Application System : IIS 5.4
Database : SQL Server 2005
Programming language : .Net
Development IDE : Visual Studio 2008
Client Environment
Operating System : Any
Web Browser : Any
Server side
Operating System: Any
Application Server : IIS 5.1
DBMS : SQL Server 2005
2.4 Hardware Interface
Developer side
Processor: Intel p4 or equivalent
RAM: 512MB
Disk Space: 2 GB
Client Side
Processor: Intel p4 or equivalent
RAM: 512MB
Disk Space: 1GB
Server Side
Processor: Server Environment Capable Hardware
RAM: 2 GB
Disk Space: As per the Size of the required Data base
2.5 Communication Interface
Client on internet will be using HTTP/HTTPS protocol
Client on internet will be using TCP/IP protocols
2.6 Software System Attributes:
There are a number of attributes of software that can serve as requirements. It is important that required attributes by specified so that their achievement can be objectively verified. The following items provide a partial list of examples. These are also known as non-functional requirements or quality attributes.
These are characteristics the system must possess, but that pervade (or cross-cut) the design. These requirements have to be testable just like the functional requirements. Its easy to start philosophizing here, but keep it specific.
Reliability
The performance of the software is better which will increase the reliability of the software.
Availability
The availability of the software is easy and for everyone
Security
Specify the factors that would protect the software from accidental or malicious access, use, modification, destruction, or disclosure. Specific requirements in this area could include the need to:
The external security can be provided by given the login authentication.
The data that are stored in the database must be private.
There is also required a user authentication.
There is also the facility that the admin can lock his private data that will not beaccessed by anyone.
The whole software is secure from the outside accessing
Maintainability
After the deployment of the project if any error occurs then it can beeasily maintain by the software developer
Portability
The software can be deployed at any machine.
Performance
Any interface between a user and LMS should have a maximum response time of 5 seconds.
The response should be fast enough to avoid users’ response collisions.
The IMS should be available for use 24 hours per day, 365 days per year.
The IMS should support 500 patrons and 1000 requests/min simultaneously