SOFTWARE REQUIREMENT SPECIFICATION 1.

INTRODUCTION:
The main objective of the Hostel Management system is to allow the students to check the availability of the rooms in Hostel. Also it gives the details about the status of the rooms so that the students can change their rooms later. The system facilitates the view of the list of rooms that are available for registration. The System keeps the detailed records of the financial transactions considering the registration of rooms.

1.1. PURPOSE:
The purpose of Software Requirements Specification (SRS) document is to describe the external behaviour of the Hostel Management System. Requirements Specification defines and describes the operations, interfaces, performance, and quality assurance requirements of the Hostel Management System. The document also describes the non-functional requirements such as the user interfaces. It also describes the design constraints that are to be considered when the system is to be designed, and other factors necessary to provide a complete and comprehensive description of the requirements for the software. The Software Requirements Specification (SRS) captures the complete software requirements for the system, or a portion of the system.

1.2. SCOPE:
The system keeps an organized database that helps to manage the Hostels database and to keep it up to date. The system deals with the room maintainance on a regular basis and handles complaints via E-Mails. The system monitors the students attendance on a daily basis. The Systems database can be used to check the room/mess availability when a change is requested by the student. The system deals with all the financial transactions considering the Hostel and Mess payments. The Systems database contains all the details about the working staff, wardens and supervisors. The system allows the data entry operator to update the information about the rooms/mess.

1.3. OVERVIEW:
The SRS will provide a detailed description of the Hostel Management System. This document will provide the outline of the requirements, overview of the characteristics and constraints of the system. 1.3.1. Section 2: This section of the SRS will provide the general factors that affect the product and its requirements. It provides the background for those requirements. The items such as product perspective, product function, user characteristics, constraints, assumptions and dependencies and requirements subsets are described in this section. 1.3.2. Section 3: This section of SRS contains all the software requirements mentioned in section 2 in detail sufficient enough to enable designers to design the system to satisfy the requirements and testers to test if the system satisfies those requirements.

2. OVERALL DESCRIPTIONS: PRODUCT PERSPECTIVE:

The Hostel Management System is a package to be used by the students to get the concise availability of the required rooms/mess slots. It facilitates the students to view the status of the room vacancies. The Supervisors can track the absentees by inputting the daily attendance. The product to be developed has interactions with the users: Students and Supervisors. The product has to interact with other systems like: Database and general input system. The complete overview of the system is as shown in the overview diagram below:

INTERACTION DIAGRAM:

PRODUCT FUNCTION:
The Hostel Management System is a system specially designed to centrally manage Hostels Associations. The system uses one single central database that serves the activities of the whole associations. Technically, it is a multi-tier application running from a central server. Users are using thin clients, connected to the center using phone lines or the Internet and will never need technical support and maintenance (zero client administration). The system was originally designed to deal with the complexity of Youth Hostels Associations and is not a modified hotel system. All administrative functions and application system data has been designed to be kept centrally and unique for the entire organization. The system handles Hostels bed reservations and complex groups as well as standard hotel room reservation.

The Students will be provided with the various options for the hostel selection. The data entry operator is provided with the interfaces to enter the updated information about the rooms and also to add or delete the information about the rooms/mess availability.

USER CHARACTERISTICS: The users of the system are students, administrator and supervisors. The permissions for students to access the database are very limited. Mostly the students are given read-only permissions and only can write when they register. The Supervisors are given mostly read and write permissions over the attendance and for the room cancellation, etc., The Administrators are given every possible permissions over the database. The administrator can create, update and delete new hostels, rooms and mess. CONSTRAINTS: The Hostel Management system must be compatible with the Internet applications. The students can access the database for the availability check from the internet itself. After the rooms are registered, students are asked to print the fee receipt and the amount should be paid in the finance office. The Hostel Management system must be portable so that it should not be specific to any platform.

ASSUMPTIONS AND DEPENDENCIES: The users have sufficient knowledge of computers. The computers (from which they access the system) should have Internet connection and Internet server capabilities. The users know the English language, as the user interface will be provided in English. The product can access the Hostel information database.

WBS:
Hostel Management System Attendance

Hostel Settings

Registration

Fee Management

Allotment Hostel Master Settings Room Settings Category Settings Bed Settings Reservation

Hostel Login(Finger scan/ Card Swiping) Hostel Attendance

Fee Settings

Group Wise Fee Assigning Individual Fee Assigning Fee Collection

Room Transfer

Reports

Reports

3. SPECIFIC REQUIREMENTS:
3-1.FUNCTIONAL REQUIREMENTS: The system shall provide the various options to the user as listed below. Search by Hostel name or Hostel reference NO. Search by Room no. Search by no.of beds available.

The system shall provide validity checks on the inputs as follows. Students name, Registration number and Hostel names Every User has-Username and password

The system shall restrict the type of services provided based on the type of users as listed below. Passenger: The system shall provide the facility for retrieving the room availabilities for the specified input (as given above). The system shall also allow viewing the status of each room/mess. The system shall provide the facility to view the cost of the room allocated. The system shall allow printing the fee receipt, for which the room/mess has been allocated.

 The system shall also provide the facility to go back to the previous page.

Supervisor: The system shall provide the interface to login to the system. The system shall allow updating the information about the attendance, rooms and mess.

Administrator: The system shall provide the interface to login to the system. The system shall allow providing the access rights to other users. The system shall facilitate printing the reports. The system shall provide the administrator to update the total databse.

The system shall provide the output for the specified input as listed below to the users.

INPUT/OPTION
Hostel Number Room no Academics Year Get status Get Fee Chart Username and password Update room/mess info Get printout 3-2.NON-FUNCTIONAL REQUIREMENTS: 3-2-1 Performance: Response Time:

OUTPUT
Rooms available No of slots available Eligible Hostels Status of all hostels Payment for each type for rooms Home page or error message Interface for updating Printout of the material

The Information page should be able to be downloaded within a minute using a 56K modem. The information is refreshed every two minutes. The system shall respond to the user in not less than two seconds from the time of the request submittal. The system shall be allowed to take more time when doing large processing jobs. The processing for printing the page shall be done with in a minute.

 Administrator/Operator Response: The system shall take as less time as possible to provide service to the administrator or the Supervisor. Capacity: The system is capable of handling thousands of users at a time. Resource Utilization: The resources are utilized to the optimum extent.
3-2-2 Usability:

The system shall allow the users to access the system from the Internet using HTML or its derivative technologies. The system uses a web browser as an interface. The interface should be minimally designed, so that it can be accessed by everyone. Since all users are familiar with the general usage of browsers, no specific training is required. The system is user friendly and self-explanatory. The user shall also be provided with the help manual.

3-2-3 Reliability: The system has to be very reliable due to the importance of data and the damages incorrect or incomplete data can do. Availability: The system is available 100% for the user and is used 24 hours a day and 365 days a year. The system shall be operational 24 hours a day and 7 days a week. The system shall provide the factors required to guarantee a defined availability level for the entire system such as checkpoint, recovery and restart. Accuracy: The accuracy of the system is limited by the accuracy of the speed at which the users use the system. The accuracy plays an important role cause, the allocation rooms are limited for each room/mess. 3-2-4 Security: Using certain crypto graphical techniques the inputs are encoded. Passwords are stored in hashed formats. Restricting the communicating facilities between the necessary modules by providing password protected login account facilities.

3-3.INTERFACES:
3-3-1 SOFTWARE INTERFACES: A firewall will be used with the server to prevent unauthorized access to the system. 3-3-2 COMMUNICATION INTERFACES: The Hostel Management System will be connected to the World Wide Web and has a Central Server. 3-3-1 USER INTERFACES: The user-interface of the system shall be designed as shown in the user-interface prototypes.

HOMEPAGE:

LOGIN PAGE:

CONTACT: