225139 software engineering

Software engineering

Name:-Avishkar Subhash Shelake

Std:- SYBSC-CS
Roll no:-225139
Sub-teacher name:-Vrushali Wadkar Mam
225139 software engineering

Case Study:
SRS (Software Requirement Specification)
HOSTEL MANAGEMENT

(1)INTRODUCTION :-

SRS 2 Hostel Management System

Introduction
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.
We design this system on the request of the hostel management, through this they cannot
require so efficient person to handle and calculate the things.
This system automatically calculates all the bills and issued the notifications for those
students who are against some rules.

(2)Project statement:-
The hostel management needs to create the hostel management system (HMS) to
organize the rooms, mess, students record and the other information about the
students. how many students can live in a room, and the students of the hostel can
be recognized from their ID card number.

1.2.1 Descriptions
This software product the hostel management to improve their services for all
the students of the hostel. This also reduce the manual work of the persons in
admin penal and the bundle of registers that were search when to find the
225139 software engineering

information of a previous student, because through this system you can store the
data of those students who had leaved the hostel three years ago. Through this you
can check the personal profile of all the current students within few minutes the
data base of the system will help you to check a particular one. You can select the
time of the student to use the internet by allocating the specific time to every
student. The system will help you to check the mess bills of every student and the
student’s hostel dues. The students of the hostel will be recognized from the ID
number allocated at the room rental time. This system also attach to the system of
the library and the departments, so that t5hey can access the data of the particular
student. In the last this system will improve the management work in the hostel.

● Hostel Reservation:
When the student login with his/her Login Id and Password then he/ she is asked
about the sours of his/her booking, root, date and time of booking and type of but i. e.
Normal or Ac. This checked for availability in database on proposed time, if the sit is
available then the reservation is done
by taking the e-payment and the sit no. And reservation, date and time of the hostel is
sent to the student along with a blueprint of the ticket. If the reservationis not
available then the student is given all other alternatives. Even if the student completes
his journey, then also administrative staff should not delete his PIN from the system.
So that database about regular student can be maintained and special discount offers
or them can be given.

Process flow
There are four types of flow

Registration flow
To take the membership of the hostel the students should tell the department’s
name to the hostel management system. He/she should fill his/her personal
profile on the profile page. After this the warden issued ID # to him/her. So
that the student can accessed bye his/her ID # in case of any problem or other
thing.

Mess Flow
When a student will use the mess his/her ID card will be scand by the system
user at mess. A student can take only 2 messes at a time.
At the end of the month the hard copy of mess details issued to the student’s
room, which shows the detailed of his/her messes and all the dues of the mess
The student should pay the dues within 10 days after the issued of mess bill.
In case of not paying dues the warning letter is issued against the student.

• Room process flow A room will be allocated when a student is registered in the hostel.
The allocation will be on the basis of the department, semester and the session of the student.
A room is only for the two students. The dues of the hostel is only for 1 semester and after
225139 software engineering

the end of the semester the student should pay the next semester’s dues. The student will pay
the dues within 10 days after next semester. In case of not paying the dues of the hostel at the
announced date a warning is send to the student. In case of the unavailability of a room the
students will be entered in a waiting list when the room will be free the student will be told
by the management of the hostel.

2.1 General Business Rules & Constraints 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 approve 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 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 uses warden of the hostel.
• The Hostel id card is necessary to use mess.
• Barcode is used to read the id of the student.
• Time constraint 2.2 General Assumptions.
The following details any high level assumptions regarding the proposed changes including
any restrictions regarding scope of the project. It also details any functionality limitations or
environment or design limitation that may impact the design or delivery of the change.
Details are also provided on any assumptions that may impact the requestor/customer/user.

4.0 Product descriptions

2.1 General Business Rules & Constraints 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 approve 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 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 uses warden of the hostel.
• The Hostel id card is necessary to use mess.
• Barcode is used to read the id of the student.
• Time constrain
225139 software engineering

● Software Quality Attributes:

○ Maintainability:
Back Up : The system shall provide the capability to back-up the Data
Errors: The system shall keep a log of all the errors.
● Reliability:
Availability :The system shall be available all the time

4.References:
Agarwala, R. (2005), From Work to Welfare: the State and Informal Workers’ Organizations in
India, Center for migration and development, working paper series, Princeton University
Available, http://cmd.princeton.edu/papers/wp0407.pdf, Last accessed 1 February
2007
Anjaria, J. S. (2006), Street Hawkers and Public Space in Mumbai, Economic and Political
Weekly, May 27, pp 2140-2146
Appadurai, A.(2000), Spectral housing and urban cleansing: notes on millennial Mumbai, Public
Culture, Vol 12, no 3, 627–651
Burrell, J. (forthcoming), Problematic Empowerment: West African Internet Scams as Strategic
Misrepresentation, Information Technology and International Development.

Burrell, J and Anderson, K. (2008) "I have great desires to look beyond my world: trajectories of
information
and communication technology use among Ghanaians living abroad”, New Media and Society,
Vol 10 no2 pp 203-224.

Best, L.M and Macaulay C (2002), “Community Internet Access in Rural Areas: Solving the
Economic Sustainability Puzzle”, Sustainable Access in Rural India, SARI- TRR-2002
Available: http://edev.media.mit.edu/SARI/papers/gitrr2002_ch08.pdf), Last accessed 19 March
2009

Chatterji, R. (2005), Plans, habitation and slum redevelopment: The production of community in
Dharavi, Contributions to Indian Sociology, Vol 39 pp197-218
225139 software engineering

Case Study:
Use - Case Diagram
HOSTEL MANAGEMENT

The use case diagram in software engineering shows the sample adaptive behavior
of the hostel management system. It encapsulates the project’s functionality by
incorporating use cases, actors, and their interactions.

Moreover, the diagram assists you in defining and organizing project requirements.
This also provides a clear picture of the user and system relationships. Therefore,
this diagram depicts the high-level functionality of a system including how the user
interacts with it.

Diagram:
225139 software engineering

Hostel management by manual way is tedious process, since it involves

work load and time consumption. In this system, we can easily manage the
hostel details, room details, student records, calculation, easy way of room
allocation and hostel attendance.
The main feature of this project is easy to allocate for the student and also
easy to calculate mess bill.
This project is carried out using Java as front end and back end Language.

Java is used as the front end tool and "racle is used as a backend tool. Java is one
of the driven programming languages. The application wi#ards, menu editor and data
reports etc is very much useful for creating very good professional software.
225139 software engineering

Class Diagram
HOSTEL MANAGEMENT
Class Diagram:

Hostel management gives on idea about how the students details, room allocation,
mess ependiture are maintained in the particular concern. The hostel management
system also includes some special features. The administration has the uni!ue identity
for
each members as well as students details. The stock management has also held by mess
ependiture, the mess ependiture that used to calculate the mess bills of each of the
students. The modules of this project are student details, attendance details, room
details,
mess modules.
225139 software engineering

Sequence diagram
#HOSTEL MANAGEMENT#

Here are the important information about the hostel management system
before you design a sequence diagram for it. You should have a deep
analyzation about its core functions before jumping into its blueprints. This
technique will help you avoid unnecessary repetitions to show the
interaction.

Hostel administration system helps hostel administrators in efficiently

managing the hostel records. This project keeps track of student records,
hostel rooms, and other hostel-related items.

The project hostel management system offers various functionalities that

allow personnel from the housing office to do things like assign students to
different hostels, reserve rooms for students, track the status of rental
payments, and update details of student data.

As you can see through the illustration, the conditions and interactions are
emphasized. These interactions are essential for the Hostel Management
System development.

The series of messages are shown and labeled to guide you in building an
Hostel Management System. You can modify the design if you have more
ideas. You can also add more features to this design and use it as your
project blueprint.

You’ll be able to understand and educate yourself on how the Hostel

Management System works by creating a sequence diagram. Because it
determines the needed objects, actors and messages and their
interactions.
225139 software engineering

Sequence Diagram:

The Hostel Management System is a sort of interaction sequence diagram that

shows how a group of items interacts and in what order. Software engineers and
business experts use these diagrams to understand the requirements of the system
or to describe an existing process.

The Hostel Management System must have a designed diagram to define event
sequences that will result in a desired outcome. The flow of communication that
appears is more important than the message itself. Though the majority of sequence
diagrams will show what messages are transmitted and in what order they usually
occur.

And that completes our discussion fellas! I hope that this article about for Hostel
Management System will help you a lot.
225139 software engineering
225139 software engineering

Conclusion:
Our project “HOSTEL MANAGEMENT SYSTEM” is a very helpful and important project
thatwill manage various activities in the hostel like accommodation, rents, student records
and many other things that are very useful for a well-managed hostel. The scope of this
project is to provide the facility of the living to the student of rural areas, who are unable to
study further in their area.
They will be able to have an affordable rates of living in hostel and they will be fully
provided the environment which they need for their studies. Another benefit of this project is
that all the hostel managing works can be done easily through it by saving our time and also
by saving the human efforts.
This management system will be an errorless or bugs free management system
and will be able to show the records of even years without any confliction.