04-11-2016, 03:50 PM
1464772338-tncrs.docx (Size: 442.53 KB / Downloads: 5)
1 Introduction
1.1 Purpose
The purpose of this software requirement specification document is to describe the behaviour of Tamil Nadu Secretariat Conference Hall Reservation System. The document is intended to serve the main functionalities of the system which is going to be implemented. The requirement specification will form the basis for the application design.
1.2 Scope
The main objective of the Tamil Nadu Secretariat Conference Hall Reservation System is to enhance the usability of Conference halls in Secretariat for meetings. And the sources of the document are gathered from Public Department Secretariat.
• Constraints are enforced for booking and it is limited.
• Transparency is maintained over the process.
• Communication problems have been dropped, since every request is processed in online.
• Flexibility, Adaptability is consistently maintained.
• Extend ability is possible by adding this program basis to all guest houses & circuit houses of the nation.
Overview
The remaining sections of this document provide a general description, functional and quality requirements of the application. System Architecture of the project is discussed in section 2 of this document. Section 3 gives the functional requirements, in which use case of each actor is described. Section 4 describes Quality requirements made while developing the application. Section 5 discusses the hardware interface and software interface requirements.
2. Overall Description
2.1 System Architecture
Three-tier architecture typically comprises a presentation tier, a business or data access tier, and a data tier. Three layers in the three tier architecture are as follows:
1. Presentation Tier: Occupies the top level and displays information related to services available on a website. This tier communicates with other tiers by sending results to the browser and other tiers in the network.
2. Application Tier: Also called the middle tier, logic tier, business logic or logic tier, this tier is pulled from the presentation tier. It controls application functionality by performing detailed processing.
3. Data Tier: Houses database servers where information is stored and retrieved. Data in this tier is kept independent of application servers or business logic.
Model
The model is responsible for managing the data of the application. It responds to the request from the view and it also responds to instructions from the controller to update itself.
View
A presentation of data in a particular format, triggered by a controller's decision to present the data. They are script based templating systems like JSP, ASP, PHP and very easy to integrate with AJAX technology.
Controller
The controller is responsible for responding to user input and performs interactions on the data model objects. The controller receives the input; it validates the input and then performs the business operation that modifies the state of the data model.
User
The role of the user (Department SO/US) is to login to the website & make the reservation request for the hall to the admin (i.e.) Public Secretary of Secretariat.
Admin
The role of admin is to approval phase (i.e.) whether to accept/reject the particular request for reservation
Process flow:
a) The User login into the Tamil Nadu Conference Hall Reservation System, views the hall details for the purpose of reservation.
b) User is requested to select the required option for booking the hall (Reserve your Hall).
c) Then the user is requested to select the date from the calendar, the page redirects the user to the timeslot selection page with the corresponding halls, showing the availability status.
d) Then the user selects the desired timeslot and clicks on submit, a message is displayed with the requested hall and date to admin through mail.
e) Admin acknowledges the user by accepting/rejecting the reservation request from the user. The acknowledgement notification is sent to the user through the mail.
f) After the approval of the admin, the booking is considered as approved one.
g) If the user wants to cancel the booking, user can login and click on the cancel booking link to cancel the reservation for the specified date by selecting the checkbox.
h) Mail communication is established for cancellation process. (Admin & User).
4.0 Non Functional Requirements
4.1 Usability
The system shall provide a uniform look and feel between all the web pages.
This software can be easily operated by the user in a given environment.
4.2 Performance
The system shall be based on web and has to be run from a web server.
The system shall take initial load time depending on internet connection strength
The performance shall depend upon hardware components of the client/customer.
4.3 Security
The system shall use secure sockets in all transactions that include any confidential customer information.
The system shall not leave any cookies on the customer’s computer containing the user’s password.
The customer’s web browser shall never display a customer’s password. It shall always be echoed with special characters representing typed characters.
System will have different types of users and every user has access constraints.