Documente Academic
Documente Profesional
Documente Cultură
Practical-2
Aim: Develop the Software Requirements Specifications (SRS)
document for a specific system.
2.1 Introduction:
2.1.1 Purpose of the system:
This system provides an easy solution to travel agency to keep track of customers & their
booking details, available seats, hotels & payment.
Customer
records
1. Technical Feasibility:
In this project technically it is possible for administrator to contact the wide range
of customers virtually (without being in physical contact with them). Customers also get
knowledge of various packages & schemes without visiting the travel agency physically.
2. Operational Feasibility:
It is feasible for our project to make use of functions like count bill () which will
calculate the payment according to no. of passengers selected. Various functions are also
possible e.g. selection of means of travel (by air or by bus or train) & type of hotel (2, 3,
or 5 star)
3. Implementation Feasibility:
Implementing our project is very feasible as it is very user friendly, what it requires
from us is to just connect few PC’s in LAN and then it is possible for customers to give
feedback parallel, from travel agent’s point of view also it is very feasible since he just has
to enter the name of package & customer for which he wants to book the ticket.
4. Economic Feasibility:
The system should provide cost effective interface by considering less power
consumption approach.
5. Resource Feasibility:
It is also an essential part of a feasibility study. It includes questions regarding time
required to complete the project, type and amount of resources required and dependent
factors.
6. Market Feasibility:
A market feasibility study determines the depth and condition of a particular real
estate market and its ability to support a particular development. The key concern of a
market feasibility study for multifamily development is a project's ultimate marketability.
2.4.2 Reliability:
o Application should be highly reliable
o It should generate all the updated information in correct order.
2.4.3 Availability:
o Any information about customer should be quickly available from any computer to the
authorized user. The previously visited customer’s data must also be maintained and
should be made available to the system authorized by simply entering his registration-
Id.
2.4.4 Maintainability:
o The application should be maintainable in such a manner that if any new requirement
occurs then it should be easily incorporated in an individual module.
2.4.5 Portability:
o The application should be portable on any windows based system incorporating any
hardware interface.
2.4.6 Reusability:
o The same system will be used in each new agency.
Sr.
Name Datatype Constraint Description
No.
1 user_name Varchar(10) Primary key To store the user name
2 user_type Varchar(10) Not null To store user type
3 password nvarchar(10) Not null To store the password