1.

1 PURPOSE:
The purpose of this document is to describe the requirements for an automation
system for a college grievance cell to register the complaints online from valid users
and maintain all related information. It also describes the interface, platform and
other constraints.
1.2 SCOPE:
This document is the only one that describes the requirements of the system. It is
meant for the use by the developers and will be the basis for validating the final
delivered system. Any change made to the requirements in the future will have to go
through a formal approval process. The developer is responsible for asking
clarification, where necessary, and will not make any alteration without the
permission of the client.
1.3 DEFINITIONS AND ABBREVIATIONS:
1. OGC- Online Grievance Cell
2. Grievance-A grievance is the subject of a complaint filed by a student, which is to
be resolved by procedures provided in the college. It is any issue causing problem to
the students, which need to be relevant. Ex. Issues related to ragging, food, faculty
etc. Grievance is sometimes referred to as complaint.
3. Student- Any student of SDMCET belonging to any of the semesters from 1st to
8th of any branch.
4. Authority- The Dean academic for academic and Dean Student welfare for non
academic grievances, who are responsible for resolving the grievances of students.
5. Database Administrator- One who manages and maintains the database, i.e
adding/ deleting of users of the software.
6. Abbreviations* Fi: Functional requirement number i.
* ti: Test case number i.
1.4 REFERENCES:
Elmasri and Navathe, Fundamentals of Database Systems, 5th Edition,

Addison- Wesley, 2007.

Database management systems by Raghu Ramakrishnan and gehrke...
2 4.
3
4 SOFTWARE REQUIREMENTS SPECIFICATIONSPreface
5 This section contains the Software Requirements Specification (SRS) Document for
the HostelManagements System (HMS). The main aim is to enable online room application
and allocation to thestudents.
6 4.1.
7
8 Introduction
9 The following subsections are an overview of the entire Software Requirements Specification
(SRS)document.
10 4.2.
11
12 Purpose
13 This SRS section describes the design decisions and the detailed design needed to implement
the system.It defines the product functions, user characteristics, constraints under which it
must operate, how thesystem will react to external stimuli, and specific requirements of the
system. The document is intendedfor the users and the developers of the system.
14 4.3.
15
16 Scope
17 HMS has the main aim of managing room application and allocation in a Web-based
environment. Theoverall system will consist of HMS Database System and HMS Web
Interface. The HMS database systemwill supply the fundamental database structure of the
entire system whereas its Web Interface will providea secure Web interface between the users
and the database. HMS aims towards establishing a
18 paperlessoffice rath
19 er than using a manual system.The objectives of the project are: To enable online room
application and allocation in a timely manner, toenable the students update their details
online, to eliminate duplicate data, and to enable a smoothcommunication channel between
the system administrator and its users,
20 4.4.
21
22 ABBREVIATIONS, DEFINITIONS AND ACRONYMS
23 DFD
24
25 Data Flow DiagramERD
26
27 Entity Relationship DiagramSRS
28
29 Software Requirements SpecificationsHMS
30
31 Hostel Management SystemPHP
32

33 Hypertext Processor
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

13 |
P a g e
HTML5

Hyper Text Markup Language 5MYSQL

Open source database applicationSQL

Structured Query LanguageUsers

The people who will be actually using the system

4.5.
References

IEEE Standards 1016-1998, Recommended Practice for Software Design Descriptions

4.6.
Overview
This document is prepared in accordance with the IEEE Standards 830-1998, IEEE
RecommendedPractice for Software Requirements Specifications.Section 5.0 of this
document gives a general description of HMS. It also provides product perspectives, product
functions, user characteristics, general constraints, and assumptions and dependencies of
thesystem.Section 6.0 contains additional design details. It will contain functional and
performance requirements,design constraints, attributes and external interface requirements
for the HMS.

Introduction
1 Purpose
The purpose of this document is to present a detailed description of the project. It will explain the
purpose and the different features of the system, the interfaces of the system, what the system will
do, the constraints under which it must operate and how the system will react to external stimuli.
3 Document Conventions

Every requirement is having its own priority .Higher priority requirement is marked with a higher
number and then goes to lower number as the priority decreases.
5 Intended Audience and Reading Suggestions
The document is intended for developers, project managers, testers and documentation writers. The
rest of this SRS contains the overall description of the project followed by features, interfaces and
some non functional requirements.