Software Requirements Specification for Hostel Management System
Page i
Software Requirements Specification
for
Hostel Management system
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:
Miss Sundus Munir
Department of Computer Science
Lahore Garrison University
Software Requirements Specification for Hostel Management System
Page ii
Table of Contents
1.Introduction................................................................................................................................1
0.1 Purpose ...............................................................................................................................................
0.2 Document Conventions.......................................................................................................................
1.3 Intended Audience and Reading Suggestions....................................................................................
0.3 Product Scope.....................................................................................................................................
0.4 References...........................................................................................................................................
1
1
1
2
2
1. Overall Description....................................................................................................................2
1.1 Product Perspective.............................................................................................................................
1.2 Product Functions...............................................................................................................................
1.3 User Classes and Characteristics........................................................................................................
1.4 Operating Environment.......................................................................................................................
1.5 Design and Implementation Constraints.............................................................................................
1.6 Assumptions and Dependencies.........................................................................................................
2
3
3
4
4
4
3. External Interface Requirements............................................................................................ 4
3.1 User Interfaces...................................................................................................................................
3.2 Hardware Interfaces...........................................................................................................................
3.3 Software Interfaces............................................................................................................................
3.4 Communications Interfaces................................................................................................................
4
5
5
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...............................................................................................................
5.2 Safety Requirements........................................................................................................................
5.3 Security Requirements.....................................................................................................................
5.4Software Quality Attributes.............................................................................................................
5.6 Business Rules.................................................................................................................................
12
12
12
12
12
List Of Tables
Table 1:Add Students.................................................................................................................... 6
Table 2:Login with database........................................................................................................7
Software Requirements Specification for Hostel Management System
Page iii
Table 3:Create Account number................................................................................................. 7
Table 4:Room Allocation...............................................................................................................7
Table 5:Generate student profile..................................................................................................7
Table 6:Delete Student.................................................................................................................. 7
Table 7:Generate Mess Account...................................................................................................8
Table 8:Change the hostel dues of student.................................................................................. 8
Table 9:Student is Requesting For room.................................................................................... 8
Table 10:Pay Bill............................................................................................................................ 8
Table 11:Check profile.................................................................................................................. 9
Table 12:Check mess bill...............................................................................................................9
Table 13:Search Student In Database..........................................................................................9
Table 14:Mess Bill Calculation..................................................................................................... 9
Table 15:State Attendance.......................................................................................................... 10
Table 16:Check the availability of room....................................................................................10
Table 17:solve the problem......................................................................................................... 10
List of Figures:
Figure 1:Use Case Diagram.................................................... 6
Figure 2:ERD.......................................................... 14
Software Requirements Specification for Hostel Management System
Page iv
Figure 3:Add student Sequence diagram:............................... 15
Figure 4:Sequence Diagram of Delete Student:.................................. 16
Figure 5:Sequence Diagram of Login:..................................................... 16
Figure 6:Generate profile of student:.............................................. 17
Figure 7:Sequence diagram of Room allocation:.......................................17
Figure 8:Sequence Diagram of search Student:........................................18
Figure 9:Sequence Diagram of Check the availability of room...............................19
Figure 10:Sequence Diagram of Mess Bill Calculation Payment...20
Figure 11:Sequence diagram Of State attendance.............................21
Figure 12:Sequence Diagram of request for mess bill..............................................................22
Figure 13:Sequence Diagram Of Check Mess bill.......................... 23
Figure 14:Sequence Diagram of request for room......................................24
Figure 15:Sequence Diagram of Assistant to solve the problem of students:
..................................................................................................................................................25
Figure 16:Zero Level DFD...................................................... 25
Software Requirements Specification for Hostel Management System
Page 1
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.2
Document Conventions
 Main Heading Titles:
 Font: Times
 Face: Bold black
 Size: 18
 Sub Heading Titles:
 Font: Times
 Face: Bold black
 Size: 14
 Main points:
 Font: Times
 Face: bold black underline & displayed with bullets .
 Size: 12
 Other text explanation:
 Font: Times
 Face: Normal black
 Size:12
1.3 Intended Audience and Reading Suggestions
The Software Requirements Specification is primarily intended for all project developers associated
with this project. This Specification is organized into several sections or members that can be read
and referenced as follows
1.Project Manager
2.Software Designer
3.Software Tester
4.Database Administrator
5.Software Analyst
To manages all processes in the project
To design the models and diagrams that helps
the programmer in implementation phase
To test system by using dummy data
To perform database operations
To analyze the requirements of hostel
management system
Software Requirements Specification for Hostel Management System
Page 2
0.3
Product Scope
The software product “Hostel Management System” will be an application that will be used for
maintaining the records in an organized manner and to replace old paper working on the system.
This projects aims at automating the hostel management for smooth working of the hostel by
automating almost all the calculations and accounting work would be accurate.
 Hostel Management System is designed for hostel like (Schools and Universities).
 He checks the attested application form of students obtained from the internet &
verify it with student database.
 If the students are found eligible then they allotted to the hostel room.
 Objectives and Goals:
 Objectives:
HMS activities.
The basic HMS objectives as follows
 Room Allocation
 Bill Generation
 Maintaining Student’s Records
 Provide to student’s Complaints
 Maintaining Employee Records
 Goals:
The goals of the system are to accept these problems in an effective and optimal
manner by:
 Centralizing the database and thus providing consistent data to all the employees in
the Hostel.
 Make the system more user friendly by providing an intensive user interface.
 Easy access through reports.
 Restricted data access to employees thus providing additional security to data.
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
1.1
Product Perspective
The HMS is fully independent product. Our product is not a part of any other system. We
have user interfaces. User interfaces will be divided like
 Administrator Interfaces
 Staff Interfaces
Software Requirements Specification for Hostel Management System
Page 3
 Interfaces for Administrator:
List of interfaces are listed as bellow
 Account View:
In this view User will add remove, new staff in the system. In administrator view,
administrator will confirm newly added department. Administrator will be able to
access all information about hostel staff, students & managed them.
 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.
1.2
Product Functions
“Hostel Management system” is an attempt to simulate the basic management system. The system
enables to perform the following functions
 Maintaining the resident information.
 Maintaining room information.
 Maintaining fee information.
 Maintaining employee information.
 Searching, sorting and retrieval of data.
The various other functions covered by the requirement specifications which follows are
provided to meet the requirements of database administrator students and administrator with
role based updating and viewing rights.
The following general features will be included:
 The student details are filled by as:
 Student Name
 Student father’s Name
 Student year
 Room No
 Following information given by the administrator:
 Student details
 Room details
 Attendance details
 Mess details
 Mess details per month
 Updating by database administrator:
Updates the
 Student details
 Mess item expenditure
 Attendance details
1.3
User Classes and Characteristics
User Characteristics:
 Educational Level:
Software Requirements Specification for Hostel Management System
Page 4
 At least user of the system should be comfortable with English language.
 Technical Expertise:
 User should be comfortable using general purpose applications on the system.
User Classes with Functionality:
 Administrator:
The administrator can
 Allot different student to different hostels.
 Vacate the Students for the hostels.
 Control the status of the fee payment.
 Edit the details of the students and modify the student record.
 Students:
Every student who have room in hostel have a database and a student account to access
his/her data. These permition shall be showed after administrator approval. Student can
check his or her data weather its true or need to some changes. Also he or she can check the
monthly reports of their fines, mess bills other stuffs.
 Database Manager:
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.
1.4
Operating Environment
The user will use this application to maintain the database of students and the rooms mess. The
application of HMS has a very user friendly interface. The software provides accuracy along with a
pleasant interface. Make the present manual system more interactive, speedy & user friendly.
1.5
Design and Implementation Constraints






1.6
The developed system should run under any platform i.e. Unix, Linux, windows etc.
There can be any security risk involved.
Details provided by individual during his sign up should be stored in database.
Student details can update or change by only administrator or database manager.
The Hostel Id card is necessary to use mess.
Time constraint
Assumptions and Dependencies
 The details related to the students, room, mess.
 Administrator is created in the database already
 Roles and tasks are predefined.
3. External Interface Requirements
3.1 User Interfaces
There are three types of user Interfaces like
Software Requirements Specification for Hostel Management System
Page 5
 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.
3.2 Hardware Interfaces
Hardware Interfaces exist in computing systems between many of the components
such as various storages devices, other i/o devices these are following for project
Processor:
Intel core 2duo or higher
RAM:
3GB
Monitor:
15 color monitor
Mouse & Keyboard
Hard
Hard disk
3.3 Software Interfaces
The software is developed with all the basic controls and class provided in java and SQL,
Windows xp or above installed on the system. Application package must be installed.
Operating system
:
windows xp, vista ,7.8, Linux, Tec.
Developing tool
:
Command prompt, SQLyog
3.4 Communications Interfaces
The system shall be a standalone product that does not require any communication interfaces.
Software Requirements Specification for Hostel Management System
Page 6
4.System Features
Use case Diagram Of System:
1.Request for room
Mess bill calculation
Search student
2.Pay the Bill
Request for Mess bill
3.Checks profile
Student
State addentence
Check the availablity of
room
4.Check mess Bill
Database Administrator
5.Add student
6.Login
<<extend>>
7.Create account no
8.Room Allocation
Administrator
9.Delete Student
Keydestribution and solve problems
Assistent
10.Generate Mess Account
11.Generate std profile
Figure 1:Use Case Diagram
4.1Use Cases and Scenarios of Administrator:
Table 1:Add Students
Name
Description
Actor
Precondition
Successful
Completion
Add Students
The scenario describes the process to add the student .
Administrator/Student/Database Administrator
To add the student in Database record of hostel.
1.The administrator login with database.
2.If the Login successful then he checks the availability of room in
Software Requirements Specification for Hostel Management System
Page 7
hostel.
3.The administrator add the student in database.
4.The student will receive the room number.
Post Condition
The student has added in database of hostel.
Table 2:Login with database
Name
Description
Actor
Precondition
Successful completion
Post condition
Login with database
The scenario describes the process of login with database.
Administrator/Student/Database Administrator/system
To login with system or database of hostel.
1.The user boot the system.
2.The user enter password.
3.If the password is valid the user login with database.
4.The user perform his/her tasks.
The user has logged with database or system.
Table 3:Create Account number
Name
Description
Actor
Precondition
Successful completion
Post condition
Create Account number
The scenario describes the process of create account.
Administrator/Student
To create a student account number.
1.The administrator login with database.
2.If login successful then create account number.
3.The account number is allocated to student as id card.
The account has created & allocated to the student
Table 4:Room Allocation
Name
Description
Actor
Precondition
Successful completion
Room Allocation
The scenario describes the process of room allocation.
Administrator
To allocate the room to students.
1.The administrator login with database.
2.If login successful then check the availability of room.
3.If the room is available then allocate the room and room number to
the student.
4.Successfuly room has allocated to the student.
Post condition
The room has allocated to the student.
Table 5:Generate student profile
Name
Description
Actor
Precondition
Successful completion
Generate student profile
The scenario describes the process of generation of student profile.
Administrator/Database administrator
To generate the student profile.
1.The administrator login with database and click on profile page.
2.Display a profile page.
3.The administrator enter the student name, address, ph. no, room
number & account number.
4.The profile has created of student.
Post condition
The student profile has successfully created
allocated to the student.
Table 6:Delete Student
Name
Delete Student
and password is
Software Requirements Specification for Hostel Management System
Page 8
Description
Actor
Precondition
Successful completion
Post condition
The scenario describes the process of delete the student from
database.
Administrator/Database Administrator
To delete the student from database or hostel
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.
The student has deleted from hostel.
Table 7:Generate Mess Account
Name
Description
Actor
Precondition
Successful completion
Post condition
Generate Mess Account
The scenario describes the creation of mess account.
Administrator/Database administrator
To create mess account of student.
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.
The mess account has created or not based above procedure.
Table 8:Change the hostel dues of student.
Name
Description
Actor
Precondition
Successful completion
Post condition
Change the hostel dues of student.
The scenario describes the changing of hostel dues of student
Administrator/Database Administrator
To Change the hostel dues of students if the student pay his/her
payment.
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.
The dues of student has changed or updated by administrator.
4.2Use Cases and scenarios of student:
Table 9:Student is Requesting For room.
Name
Description
Actor
Precondition
Successful completion
Post condition
Student is Requesting For room.
This scenario describes the process for requesting the room.
Student /Administrator
To request for room allocation.
1.The student request for room to the administrator.
2.The administrator open the room detail.
3.If the room is available then the request is full filled.
The request has been submitted.
Table 10:Pay Bill
Name
Description
Actor
Pay Bill
This scenario describes the process of bill payment of hostel room.
Student/database administrator.
Software Requirements Specification for Hostel Management System
Page 9
Precondition
Successful completion
The student wants to pay the bill of hostel room.
1.The student for bill payment.
2.The database administrator search the student and open the
student profile.
3.The database administrator enters the fee bill payment detail.
4.the student pays the bill.
Post condition
The student had paid the bill successfully.
Table 11:Check profile
Name
Description
Actor
Precondition
Successful completion
Post condition
Check profile
This scenario describes the checking of profile of student.
Student
The student wants to check the profile.
1.The student will enter his/her password for login.
2.The student login with profile. The profile page will open.
3.The student checks his /her profile. And also long out it.
The student has checked his/her profile.
Table 12:Check mess bill
Name
Description
Actor
Precondition
Successful
completion
Post condition
Check mess bill
The scenario describes that the student wants to checks his mess bill.
Student
The student wants to check his/her mess bill.
1.The student open the profile page.
2.The student enters password and login his/her profile.
3.The student checks his/her mess bill.
4.The student long out his profile
The student has been checked his mess bill.
4.3Use cases and scenarios of database administrator:
Table 13:Search Student In Database
Name
Description
Actor
Precondition
Successful
completion
Post condition
Search Student In Database
The scenario describes that the DB administrator wants to search the
student.
Database Administrator
The administrator wants to search the student.
1.The Administrator login with database.
2.the administrator open the profile page.
3.The administrator search the student in database.
4.If the student found in the database then he performed his required
task.
5.The administrator long out the database
The student has been searched successfully.
Table 14:Mess Bill Calculation
Name
Description
Mess Bill Calculation
The Scenario describes the process of mess bill calculation.
Software Requirements Specification for Hostel Management System
Page 10
Actor
Precondition
Successful completion
Post condition
Database Administrator
The database administrator calculates the mess bill.
1.The database administrator open the student profile.
2.He checks the mess bill detail.
3.The DB administrator calculates the mess bill.
The mess bill has been calculated successfully.
Table 15:State Attendance
Name
Description
Actor
Precondition
Successful completion
Post condition
State Attendance
The scenario describes that the database administrator wants to
check the current state of attendance of the students.
Database administrator
The database administrator wants to state the attendance of the
students.
1.The Database administrator login with student profile.
2.He opens the attendance sheet and checks the attendance.
3.After the completion of his task he will long out the database.
The database administrator has been checked the state of the student
attendance successfully.
Table 16:Check the availability of room
Name
Description
Actor
Precondition
Successful completion
Post condition
Check the availability of room
The scenario describes the process of checking the availability of
room.
Database Administrator
The database administrator wants to checks the availability of room.
1.The database administrator log in with database.
2.Open the room detail.
3.Checks the availability of room.
4.The database administrator long out the database
The database administrator has been check the availability of room
successfully.
4.4Use cases and scenarios of Assistant
Table 17:solve the problem
Name
Description
Actor
Precondition
Successful completion
Post condition
solve the problem
The scenario describes the process of solving the problems of the
students.
Student /Assistant
The student tells the problems to the database administrator and he
solves the student problems.
1.The student tell his/her problem with detail.
2.The database administrator take some action and solve the
problems.
The problem has solved by assistant.
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
 Student _detail ()
-
To enter the details of the students
 Room details ()
-
To enter the details of hostel rooms
 Attendances details ()
-
Maintain the student attendance detail.
 Mess _details
-
To keep the record of challan of mess bill.
 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.
 Mess account: A mess account also will generate.
 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:
 Request for room: The student will request for room.
 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.Other Non-functional Requirements
There are the following non-functional requirements of hostel management system
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.
5.2 Safety Requirements
The database may get crashed any certain time due to the virus or operating system failure.
Therefore, it is required to take the backup of database.
5.3 Security Requirements
This project provides a genuine security to all those
individuals who are having their account on the database as they are password protected. This is
very important aspect of the design and should cover areas of hardware reliability fall, back
procedures, physical security of data and provision for detection of fraud and abuse.
5.4Software Quality Attributes
 Reliability and Availability:
The project shall provide storage of all database on redundant computer with
oracle database.
 Maintainability:
The system shall provide the capability to back up the database.
 Portability:
The Hostel Management System shall run on any Microsoft Windows environment.
 Flexibility:
Ability to add new features to the system and handle them conveniently.
 Reusability:
What is ability to use the available components of the system in other.
 Efficiency:
How much less number of resources and time are required to achieve a particular
task through the system.
5.6 Business Rules
The system is desired to handle all the activities of the students as well as the administrative
level. The system will have the ability to search the student’s information about his/her room
mess and all the other things. Once the current and previous record is entered then the
database will be updated for the new students automatically.
This system is for hostel so that the primary users of the system are the students and the
administrative penal. The main constraint is the system registration is valid if the department
has been approving that student is valid for the department. The constrains are the amount of
the hostel dues and the mess dues that are calculated in the system. These dues should be
Software Requirements Specification for Hostel Management System
Page 13
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:
 SRS
System Requirement Specification
 DFD
Data Flow Diagram
 ERD
Entity Relationship Diagram
 HMS
Hostel Management System
 User
The student who lived in Hostel
 Database
The records of every old and currant students is saved here
 Mess Status
It tells the mess information of the student
 Account Number
hostel
The issued by HMS when the new student becomes the part of the
Appendix B: Analysis Models
Software Requirements Specification for Hostel Management System
Page 14
id
Generates
profile
Adminis trator
Login_id
Login_user
_name
Pass oword
Login
User_id
User
Has
Has
Mess_id
Mess_Deta il
H _n
tle
s
o
a
e
m
Manage
m _d
p
R
ta
e
il
Has
Paument_i
d
Hostle
Payment
l ita e
d_tn e myaP
Rooms
Bed_no
Has
Beds
Figure 2:ERD
Software Requirements Specification for Hostel Management System
Page 15
Sequence diagrams of Administrator:
Student
Administrat
or
Login page
Verifier
1.Open
2.Enter login Detail
3.Verifying Password
5.Login sucessful
6.Check availability
7.Add student
8.View details to the student
Student has added in database or hostel record
Figure 3:Add student Sequence diagram:
Room
Database
Software Requirements Specification for Hostel Management System
Page 16
Student
Administr
ator
DB
Administr
ator
Request For Leaving Hostal
Search student
Updating aDetail s
Delete student
Update del eted l ist of student
Figure 4:Sequence Diagram of Delete Student:
Adm inist
rator
Login
Page
Authenti
cate
Enter ogin Detail
Send detail for authentication
Verifying
Send me ssege
Login successfully or not
Figure 5:Sequence Diagram of Login:
Software Requirements Specification for Hostel Management System
Page 17
Administrator
Student
DB Administrator
1.Give Detail
2.Enter Student Details
3.Update
4.Generate Profile
Verify
5.Update
Display details of creating profile
Figure 6:Generate profile of student:
Student
Adm inistr at
or
DB manager
1.Enter Room Detai l
Updat e
Reque st For Room Avai la bi lity
Che cking
Ente r Room No to vi ew De ati l
Allot Room No
Display Room Det ai l
Figure 7:Sequence diagram of Room allocation:
Software Requirements Specification for Hostel Management System
Page 18
Sequence Diagrams of Database Administrator:
Administr
ator
Login
Page
Database
Enter User name
Enter password
Enter user detail
Validate
Valide user
Search the student
Check availability of student
Notify User
Seaching complete
Figure 8:Sequence Diagram of search Student:
Software Requirements Specification for Hostel Management System
Page 19
Datadbase
Administrator
Database
Room
Room
Administrator wants to check the availability of room
Request for log in
Ckeck the authencation of log inner
Generate a message to admin
Enter password & user name
Check the availability of the room
Checke it self
Return the detail of room
Figure 9:Sequence Diagram of Check the availability of room
Software Requirements Specification for Hostel Management System
Page 20
DB
Administrator
Administrator
Student
Enter Mess Bill &item deatail
Calculate Total mess bill expenditure
Request Mess Fee Caclulation
Calculate
DB
Administrator
Administrator
Student
Publish
Enter Mess Bill &item deatail
Mess fee details.
Calculate Total mes s bill expenditure
Request Mess Fee Caclulation
Acknowlegment
Calculate
Publish
Mess fee details.
Enter thepayment Detail
Acknowlegment
Enter thepayment Detail
Figure 10:Sequence Diagram of Mess Bill Calculation Payment
Software Requirements Specification for Hostel Management System
Page 21
Database
Administrator
Administrator
Enter Roll number
Enter attendence detail
Update detais
Check the status of attendence
Updated
Figure 11:Sequence diagram Of State attendance
Software Requirements Specification for Hostel Management System
Page 22
Sequence Diagrams of Student:
Data base
Administrator
Student
Request mess bill
Check mess bill
Return Mess Bill
Figure 12:Sequence Diagram of request for mess bill
Software Requirements Specification for Hostel Management System
Page 23
:addministrato
:receptionist
r
Student
Student
:DB
check mess details
Enter mess item and expenditure details
Calculate
(total mees
expenditure)
Request for mess bill expenditure
Calculate
(total mess item expenditure
/total no of students
Mess fee details
View mess bill
Figure 13:Sequence Diagram Of Check Mess bill
Software Requirements Specification for Hostel Management System
Page 24
Student
:reception
Database
Query for available room
check room availablity
Room avaiable
provisionally book room
Create resernation
Total price
Advise student
Accept Terms
Request credit
Provide credit card
Reserve Room
Figure 14:Sequence Diagram of request for room
Software Requirements Specification for Hostel Management System
Page 25
Student
Assistent
Complain to assitent
Take action
Problem solved
Figure 15:Sequence Diagram of Assistant to solve the problem of students:
Figure 16:Zero Level DFD
Software Requirements Specification for Hostel Management System
Page 26