Hostel Management SRS.doc

7/22/2019 Hostel Management SRS.doc

1/17

Software Requirements Specification

Submitted byShahbaz Khan

Pankaj kumar Banshiwal

Ritesh Khandelwal

Jatin Gupta

Prepared for

Software Engineering Lab, CS/IT Department, CTAE

Feb 2013

Software Requirements Specification Page 1


2/17

Revision History

Date Description Author Comments

Document Approval

The following Software Requirements Specification has been accepted and approved by the following:

Signature Printed Name Title Date

Lead Software Eng.



3/17

Table of Contents

REVISION HISTORY................................................................................................................................................................2

DOCUMENT APPROVAL........................................................................................................................................................ 2

1.2 INTENDED AUDIENCEAND READING SUGGESTIONS:........................................................................................................4

Rules for writing the document:1) The SRS should be neatly typed on both side and in A4 size Paper only, leaving a margin of 1

inch on left hand side and 0.5 inch on right hand side and 1 inch at the top and same at the

bottom.

2) Following typing Instructions should be followed.

i. 1.0 line spacing should be used for typing the general text.

ii. The general text shall be justified and typed in the Font style Times New Roman and

Font size 12.iii. Heading shall be typed in the Font style Times New Roman and Font size 14 and bold.

iii. Subheading shall be typed in the Font style Times New Roman and Font size 12 andbold.

iv. Fancy fonts should be avoided for text writing.



4/17

1. Introduction:1.1 Purpose

This system is designed in favor of the hostel management which helps them to save the records

of the students about their rooms and other things. It helps them from the manual work from

which it is very difficult to find the record of the students and the mess bills of the students, andthe information of about the those ones who had left the hostel three years before.

This system automatically calculates all the bills and issued the notifications for those studentswho are against some rules.

1.2 Intended Audience and Reading Suggestions:

This Software Requirements Specification is primarily intended for all project developers

associated with this project. Users, testers, and other parties that have an interest in this projectcan also use this document to gain a better understanding of the software. This Specification is

organized into several sections that can be read and referenced as needed

1.3 Scope:

The proposed system for HOSTEL MANAGEMENT SYSTEM is computerized.Today is the era of computers. This software project solves all the problems discussed above in

the present system. The main objective of developing this project is to save time and money. The

proposed system provides the following features on different tasks.

All the details related to a hosteller could be find in one place like the admission details, fees

details, room details , attendance ,mess details, stipend details etc.

Will make the monitoring of student moment and stock details easy.

The same application could be used by both the account section and the hostel management for

their specific needs and purposes.

1.4 Definitions & Abbreviations:

HMS Hotel management system

User The student who lived in the hostel.

trator The warden of the hostel who manage all the things.



5/17

ID card The card issued bye the hotel which contains the information of the student.

Database the records of every current and old students is saved here.

Account number The issued bye the HMS when the new students becomes the part of thehostel.This number is on the ID card of the student. This is users ID.

Mess status it tells the mess information of the students.

1.5 References:

http://freestudentprojects.com

http://www.bzupages.net/

We take the material from the sites and follow the pattern you have given in the example.

2. General Discription:

2.1 Product Perspective

The Hotel management software is fully independentproduct. Our product is not a part of any other

system.We have user interfaces. Users will be categorized as;Administrator Interfaces

Staff Interfaces

Interfaces for Administrator

List of interfaces are listed as bellow

Account View

In this view user will add, remove new staff in the system. Inadministrator view, administrator will

confirm newly addeddepartment. Administrator will be able to access all information abouthotel staff,

customers and managed them.

2.2 Product Functions

The various functions covered by the REQUIREMENT SPECIFICATION, which follows,are to be provided to meet the requirements of database manager, students and administrator

with role-based updating and viewing rights.

The following general features shall be included:

Student Details are filled by as:

Student Name

Student Fathers Name

Student Branch

Student Year

http://freestudentprojects.com/wp-content/uploads/2011/12/Hostel-Synopsis.dochttp://www.bzupages.net/http://freestudentprojects.com/wp-content/uploads/2011/12/Hostel-Synopsis.dochttp://www.bzupages.net/


6/17

Student Room No.

Student Permanent Address

Following information will be given by Administrator:

Students details

Room Details

Attendence Details

Mess Details per month

Updations by database manager:

update the student details.

update mess item expenditure.

update the attendance details.

Calculations & Report

total mess expenditure per month.

calculate mess fees for each student.

generate mess bill report.

2.3 Operating Environment:

The HMS is JAVA based application. The user will use this application to maintain the database of

students & the rooms, mess.The application of Hostel Management System has a very user-

friendly interface.The software provides accuracy along with a pleasant interface.Make the

present manual system more interactive, speedy and user friendly.

2.4 User Characteristics:

There are 3 kinds of users for the proposed system

Administrator

Student

Database manager

Administrator

Administrator is the one who monitors all users and user transactions.Admin has tomaintain the data of every student profile in database. When the request given by the user admin

checks the availability of the user account then it forwarded to the student database. Admin

haves the complete information related to every student database and all the information related

to the students. All the data is maintained at the Admin level. Admin is having the rights torestrict any database.



7/17

Student

Every student who have room in hostel have a database and a student account to accesshis Data. these permission shall be showed after administrator approval. Student can check his

data weather its true or need to some changes.Also he can check the monthly reports of their

fines, mess bills and other stuffs.

Database manager

Database manager is the user who have the administrator permission to update the entiredatabase. In this project the Database manager have the permissions to update the student details,

room details, student attendense details,& update mess item expenditure.

2.5 General Constraints:

The developed system should run under any platform i.e. Unix, Linux, Mac, Windows

etc

All mandatory fields should be filled by an individual.

There can be security risks involved.

Details provided by the individual during his sign up should be stored in database.

Student details can update or change by only administrator or database manager.

2.6 Assumptions and Dependencies:

The details related to the student, rooms, mess.

Administrator is created in the database already.

Roles and tasks are predefined.

3. Specific Requirements:

3.1 External Interface Requirment

3.1.1 User Interface:

Since there are 3 types of users, there are 3 types of user interface and those are;

- Administration interface

- Student Interface

- Database manager user interface



8/17


9/17

3.3 Use Cases

Use case diagram is a diagram that shows the interaction between user and system to capture the

users goals.

Use Case #1



10/17

Use Case #2



11/17

3.4 Class Diagram



12/17

3.5 Non-Functional Requirements

3.5.1 Performance

The application shall be based on java and has to be run on any platform.

The application shall take initial load time depending on performance of Operating System.

The performance shall depend upon hardware & software components of the computer.

3.5.2 Reliability & availability

The project shall provide storage of all databases on redundant computers with oracle database.

3.5.3 Security

This project provide a genuine security to all those individuals who are having there account onthe database as they are password protected.

This is very important aspect of the design and should cover areas of hardware reliability, fallback procedures, physical security of data and provision for detection of fraud and abuse.

3.5.5 Maintainability



13/17

Hostel Management System will be maintainable as long as there are no Hardware &

software problems. Also databases should be updated.

3.5.6 Portability

The project is made in java as front end & sql database as back end and will work upon

all OS efficiently.

4. Analysis Models:

4.1 Sequence Diagram



14/17

4.4 Data Flow Diagram

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data

through an Information System. A data flow diagram can also be used for the

visualization of Data Processing. It is common practice for a designer to draw a context-

level DFD first which shows the interaction between the system and outside entities. This

context-level DFD is then "exploded" to show more detail of the system being modeled.

A DFD represents flow of data through a system. Data flow diagrams are

commonly used during problem analysis. It views a system as a function that transforms

the input into desired output. A DFD shows movement of data through the different

transformations or processes in the system.



15/17

Dataflow diagrams can be used to provide the end user with a physical idea of where

the data they input ultimately has an effect upon the structure of the whole system from

order to dispatch to restock how any system is developed can be determined through a

dataflow diagram. The appropriate register saved in database and maintained by

appropriate authorities.

Data Flow Diagram Notation

Function/Process

File/Database

Input/output

Flow

4.3 State-Transition Diagrams (STD)



16/17

5.Conclusion



17/17

Hostel Management System is a Customize and user-friendly software for Hostel.

It has been designed to automate, manage and look after the over-all processing of even

very large hostel. It is capable of managing Enquiry details, Student Details, Payment

Details etc. Hostel Management System is a Customize and user-friendly software for

Hostel which provide hostel information, hostel room information, hostel accountsinformation.

Hostel Management Software System is offering a maximum of stability, cost-

effectiveness and usability. It provides the most flexible and adaptable standards

management system software solutions for hostel.


Date post:	10-Feb-2018
Category:	Documents
Upload:	pankaj-banshiwal
View:	264 times
Download:	1 times

Hostel Management SRS.doc

Documents