Se Practical 2 (sample Srs Document).docx

SE (IT307)

[ID No.]

Practical-2 Aim: Develop the Software Requirements Specifications (SRS) document for a specific system. Tourism Management 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. 2.1.2 Scope of the system: Tourism management system is an application that allows travel agents to formulate efficient records of various packages, facilities & customers. This facilitates, the travel agent to book the package & to receive payment. It generates and decides the most optimal schedule for the passenger. Not only should the application deliver what it promises, it should also provide options to integrate the product into the user's life. The common themes and primary focuses of the developers throughout the software are usability, efficiency, and compatibility.

2.2 General description of the system: 2.2.1 Overall description: [Describe the general functionality of system information, user characteristics, user objective, general constraints placed on design team. Describe the features of the user community with software system and the application domain.]

Customer

Give records,payment Package details, Bill receipt

Travel agency

Travel agent

Packages Details

Customer records

2.2.2 Feasibility study: 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.

6th Semester

[Page No.]

SE (IT307)

[ID No.]

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.3 Functional Requirements: 2.3.1 Module description: 1. Secure registration and profile management facilities for Customers 2. Browsing through the website to see the packages that are there in each category of packages like family, religious, honeymoon packages. 3. Adequate searching mechanisms for easy and quick access to particular packages, schemes and services. 4. Regular updates to registered customers of the TMS about new arrivals. 5. Uploading ‘Most visited’ packages in each category of packages. 6. Strategic data and graphs for Administrators and agents about the tours that are popular in each category and age group. 7. Maintaining database of regular customers of different needs. 8. Travel agents are responsible for internal affairs like processing payments, getting customer's feedback, updating status and answering client's queries online. 9. Feedback mechanism, so that customers can give feedback for the tour which they have visited. Also facility rating of individual place by relevant customers. Also feedback can be given on the services provided by the agency. 10. Adequate payment mechanism and gateway for all popular credit cards, cheques and other relevant payment options, as available from time to time.

6th Semester

[Page No.]

SE (IT307)

[ID No.]

2.3.2 Functions of various user of the system: There are mainly 3 user of the product: travel agency, agents & customer 1. Travel agency: The travel agency is the main user of the system .it will decide the packages, tours, hotels & price of various packages. 2. Travel agent: The travel agency hire various agents at various locations to manage the records of customers in each city.  Functions of agent:  Database management of tours, payment details & customers.  Advertising  Communicate with customers  Management of payment  Take feedback from customers  Solve queries 3. Customers:  Login  Give personal details  Choose tour package  Payments  Ask queries  Feedback

2.4 Non- Functional Requirements: 2.4.1 Security: o It should be providing password to log on to the system. o He/she should be able to see the record of package & edit it. 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 registrationId. 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:

6th Semester

[Page No.]

SE (IT307)

[ID No.]

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.

2.5 Interface Requirements: 2.5.1 GUI 2.5.2 Hardware Interface [Hardware equipment used] 2.5.3 Software Interface [Software languages & tools used]

2.6 Data Dictionary: 2.6.1 Table Name: login_table Description: To store the admin, customer, Traveler Login Details Primary Key: User Name Sr. No. 1

Name

Datatype

Constraint

Description

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

2.6.2 and so on…

6th Semester

[Page No.]