Professional Documents
Culture Documents
Software Requirements Specification For Hostel Management System
Software Requirements Specification For Hostel Management System
Page i
Date 14-05-2018
Submitted by:
Afifa Akram (MCS 2nd Semester Roll No#003)
Hira Akram (MCS 2nd Semester Roll No#004)
Amta Ahmer (MCS 2nd Semester Roll No#021)
Submitted to:
Table of Contents
1.Introduction................................................................................................................................1
0.1 Purpose ............................................................................................................................................... 1
0.2 Document Conventions....................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions.................................................................................... 1
0.3 Product Scope..................................................................................................................................... 2
0.4 References........................................................................................................................................... 2
1. Overall Description....................................................................................................................2
1.1 Product Perspective............................................................................................................................. 2
1.2 Product Functions............................................................................................................................... 3
1.3 User Classes and Characteristics........................................................................................................ 3
1.4 Operating Environment....................................................................................................................... 4
1.5 Design and Implementation Constraints............................................................................................. 4
1.6 Assumptions and Dependencies......................................................................................................... 4
3. External Interface Requirements............................................................................................ 4
3.1 User Interfaces................................................................................................................................... 4
3.2 Hardware Interfaces........................................................................................................................... 5
3.3 Software Interfaces............................................................................................................................ 5
3.4 Communications Interfaces................................................................................................................ 5
4.System Features......................................................................................................................... 6
4.1Use Cases and Scenarios of Administrator:........................................................................................ 6
4.2Use Cases and scenarios of student:................................................................................................... 8
4.3Use cases and scenarios of database administrator:............................................................................ 9
4.4Use cases and scenarios of Assistant................................................................................................ 10
4.5System Feature 1............................................................................................................................... 10
5.Other Non-functional Requirements......................................................................................12
5.1Performance Requirements............................................................................................................... 12
5.2 Safety Requirements........................................................................................................................ 12
5.3 Security Requirements..................................................................................................................... 12
5.4Software Quality Attributes............................................................................................................. 12
5.6 Business Rules................................................................................................................................. 12
List Of Tables
Table 1:Add Students.................................................................................................................... 6
Table 2:Login with database........................................................................................................7
Software Requirements Specification for Hostel Management System
Page iii
List of Figures:
Figure 1:Use Case Diagram.................................................... 6
Figure 2:ERD.......................................................... 14
Software Requirements Specification for Hostel Management System
Page iv
1.Introduction
0.1 Purpose
The purpose of this project to make an automated system to carry out different operations of a
hostel. The system will provide the ease, comfort of use to the staff of the hostel by performing all
work on computer system rather than following a paper pen approach. This approach helps
improving the reliability of data maintained and provides a fast and efficient for users of the
software.
Hostel Management System is a customize and user friendly software for hostel which provide
Hostel information, Hostel room information and Hostel accounts information. It helps admin to
manage Student record, staff record & generating report of students etc.
0.4 References
http//freestudentprojects.com
http//bzupages.net//
www.iitm.ipu.ac.in
www.du.ac.in
http://en.wikipedia.org/wiki/secondry_data
http//www.slidshare.net/fahadchishti/hostel-management-system
www.student projectguide.com
http://t4tataurials.com//srs
1. Overall Description
Administrator Interfaces
Staff Interfaces
Software Requirements Specification for Hostel Management System
Page 3
Staff Interfaces:
At the start there will be a login screen where the user has to enter its login
name & password to authenticate himself or herself.
After the login a homepage will be displayed showing all the information and
operations provided by Hostel Management System.
A report will be generated for each student containing fee information, fines
dues & check in or check out information’s.
Database manager is the user who have the administrator permition to update the entire
database. In this project the database manager has the permition to update the student
details, room details, student’s attendance details & update item expenditure.
Administration Interface
Student Interface
Database Manager Interface
Communication Interface
Administrator:
An administrator is one who monitors all users and user tractions. Admin has to
maintain data of every student profile in database. When the request is given by user admin
checks the availability of 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 data is maintained at the admin level.
Student:
Every student who have room in hostel have a database and a student account to
access his data. these permissions shall be showed after administrator approval. Student can
check his or her data. Also he/she can check the monthly reports of their fines, mess bills
and other staff.
Database Manager:
Database manager is a user who have the administrator permission to update the entire
database. In this project the database manager has the permission to update the student
update details, room details, student attendance details & update of mess.
4.System Features
Use case Diagram Of System:
5.Add student
6.Login
8.Room Allocation
Keydestribution and solve problems
hostel.
3.The administrator add the student in database.
4.The student will receive the room number.
Post condition The student profile has successfully created and password is
allocated to the student.
Table 6:Delete Student
Description The scenario describes the process of delete the student from
database.
Actor Administrator/Database Administrator
Precondition To delete the student from database or hostel
Successful completion 1.The administrator login with database.
2.If the login is successful then database administrator searches the
student.
3.If the record of student is appears then checks his/her dues.
4.The database administrator delete the student from system or
database.
Post condition The student has deleted from hostel.
Table 7:Generate Mess Account
Name Generate Mess Account
Description The scenario describes the creation of mess account.
Actor Administrator/Database administrator
Precondition To create mess account of student.
Successful completion 1.The administrator login with database.
2.If the login is successful then generate the mess account of
student.
3.If the login not successful then check the system.
Post condition The mess account has created or not based above procedure.
Table 8:Change the hostel dues of student.
Name Change the hostel dues of student.
Description The scenario describes the changing of hostel dues of student
Actor Administrator/Database Administrator
Precondition To Change the hostel dues of students if the student pay his/her
payment.
Successful completion 1.The Administrator login to system or database for changing of
hostel dues of student.
2.If the login is successful then the administrator checks the profile
and hostel dues report & dues current status.
3.If the student has payed the bill or payment then the dues will
updated.
Post condition The dues of student has changed or updated by administrator.
4.5System Feature 1
Functional Requirements
Software Requirements Specification for Hostel Management System
Page 11
The functions which are used in this project and their functioning
Administrator:
Add students: The HMS allows the administrator to add new student in to the database.
Create Account Number: The HMS generate an account number that is allocated to student
as his /her id card.
Room Allocation: The HMS will allocate a room to student. The room no will store in user
profile.
User Profile: The HMS shall generate the user’s profile containing the following
information, student account number, student full name, student address, phone number,
room number etc.
Delete Student: The HMS allows the administrator to remove the student.
Dues status: Student dues status will be changed according to student pay dues.
Database Administrator:
Search Student: The HMS shall allow the students to search from database according to
different criteria
Mess Bill calculation: The database administrator can calculate the student mess bill.
State Attendance: The HMS shall allow to the database administrator to state the student
attendance.
Check the availability of Room: The HMS allows to the database administrator to check the
availability of room,
Student:
Pay the Bill: The student will pay the bill to the manager.
Check its Profile: The registered student will see his or her profile.
Check Mess Bill Report: The student will see the mess report.
Software Requirements Specification for Hostel Management System
Page 12
5.1Performance Requirements
The application shall be based on java and has to be run on any platform. the
application shall task initial load time depending on performance of operating system. The
performance shall depend upon hardware and software components of the computer.
paid within 10 days. If anyone could not do the payment for some reason the system will
notify the name of the student.
• System will use warden of the hostel.
• The Hostel id card is necessary to use mess.
• Time constraint
Appendix A: Glossary
Abbreviations & Definitions:
Database The records of every old and currant students is saved here
Account Number The issued by HMS when the new student becomes the part of the
hostel
id
Login_user
_name Pass oword
Login_id
Login
User_id
Mess_Deta il
Manage
Paument_i
d
H _n a
m
Has
e
Hostle Payment
o
tle
s
l ita e
m _d e
ta
d_tn e myaP
il
Rooms
R
p
Bed_no
Has Beds
Figure 2:ERD
Software Requirements Specification for Hostel Management System
Page 15
1.Open
3.Verifying Password
5.Login sucessful
6.Check availability
7.Add student
DB
Administr
Student Administr
ator
ator
Search student
Updating aDetail s
Delete student
Verifying
Send me ssege
1.Give Detail
3.Update
4.Generate Profile
Verify
5.Update
Updat e
Che cking
Allot Room No
Administr Login
Database
ator Page
Enter User name
Enter password
Validate
Valide user
Notify User
Seaching complete
Datadbase
Administrator Database Room
Room
Checke it self
Return the detail of room
DB
Student Administrator
Administrator
Calculate
DB
Student Administrator
Administrator
Publish
Enter Mess Bill &item deatail
Acknowlegment
Calculate
Publish
Acknowlegment
Database
Administrator
Administrator
Update detais
Updated
Data base
Student Administrator
:addministrato
Student
Student :receptionist :DB
r
Calculate
(total mees
expenditure)
Calculate
(total mess item expenditure
/total no of students
Room avaiable
Create resernation
Total price
Advise student
Accept Terms
Request credit
Reserve Room
Student Assistent
Complain to assitent
Take action
Problem solved