Академический Документы
Профессиональный Документы
Культура Документы
<Hostel Management>
Submitted by
Shahbaz Khan
Pankaj kumar Banshiwal
Ritesh Khandelwal
Jatin Gupta
Prepared for
Software Engineering Lab, CS/IT Department, CTAE
Feb 2013
Revision History
Document Approval
The following Software Requirements Specification has been accepted and approved by the following:
Signature Printed Name Title Date
<Your Name> Lead Software Eng.
Table of Contents
REVISION HISTORY................................................................................................................................................................2
DOCUMENT APPROVAL........................................................................................................................................................ 2
1.2 INTENDED AUDIENCE AND READING SUGGESTIONS:........................................................................................................4
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, and
the 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 students
who are against some rules.
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 project
can 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:
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 the
hostel.
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:
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
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.
Administrator
Administrator is the one who monitors all users and user transactions.Admin has to
maintain 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 to
restrict any database.
Student
Every student who have room in hostel have a database and a student account to access
his 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 entire
database. In this project the Database manager have the permissions to update the student details,
room details, student attendense details,& update mess item expenditure.
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.
3. Specific Requirements:
- Administration interface
- Student Interface
These interfaces will be variated according to Hostel & Student detail requirements. However
they will have some common properties such as:
- A customizable window
- Menus
- Detail fields
Hardware interfaces exist in computing systems between many of the components such as
the various storage devices, other I/O devices, etc. these are following for this project.
The software is developed with all the basic controls and class
provided in java & sql .Windows XP or above installed on the system.
Application Package must be installed.
Use Case #2
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.
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 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.
3.5.5 Maintainability
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
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.
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.
Function/Process
File/Database
Input/output
Flow
5.Conclusion