SYSTEM REQUIREMENT SPECIFICATION

ON

“HOSTEL MANAGEMENT SYSTEM”

SUBMITTED TO:- SUBMITTED BY:-

VIJAY MOHAN SHRIMAL Rakesh & Pankaj
(Assistant Professor) (CS-A/2ndyear)
(CSE Deptt.)
 Index

S.NO. PARTCULAR PAGE NO.

1. Project introduction 1-2
1.1 Purpose of document 1
1.2 Scope of developments 1
1.3 Overview 1
1.4 Business context 1-2

2. General Description 2-3

2.1 Product function 2
2.2 User problem statement 2
2.3 User objectives 3
3. System Analysis 4-8
3.1 Functional requirement 4
3.1.1 System requirement 4
3.1.2 Program requirement 5
3.1.3 Stability & speed 5-6
3.2 Feasibility study 6
3.2.1 Operational 6
3.2.2 Technical 7
3.2.3 Economic 8
4. System Design 9-13
4.1 Scope 9
4.2 Database design 9
4.3 Data flow diagram (DFD) 10-12
4.4 Entity relationship diagram(E- 13
R diagram)
4.5 Module description 13

5. Interface requirement 14
5.1 Graphical interface 14
5.2 Command line interface 14
5.3 Hardware interface 14
5.4 Software interface 14
6. Performance requirement 15

7. Non functional attributes 16-17

7.1 Security 16
7.2 Reliability 16
7.3 Maintainability 16
7.4 Portability 16
7.5 Reusability 17
7.6 Resource utilization 17
7.7 Stable and speed efficiency 17

8. Security 18-22
8.1 Description 18
8.2 Technical issues 19
8.3 Cost and schedule 20
8.4 Risk 21-22

9. Reference & Appendices 22

10. Conclusion 22
 Page 1

HOSTEL MANAGEMENT SYSTEM

1. Project Introduction

1.1 Purpose of the document : -

The purpose of this SRS document is to provide a detailed overview of our software
product, its parameters and goals. This document describes the project's target audience
and its user interface, hardware and software requirements. It defines how our client,
team and audience see the product and its functionality.

1.2 Scope of this Document : -

Our project goals are to create a management system for hostels or it centralized
database where the hostel management provides to accessing information through WEB,
research collections and providing high level services and collections to its users.

1.3 Overview : -

In this software we will provide with the “HOSTEL MANAGEMENT SYSTEM” with
the features:

 Content can always be accessible, regardless of time or place, to be read

on PCs or on portable for hosteler.
 Provided with the facility to access information through WEB.

1.4 Business Context : -

Business Requirements constitute a specification of simply what the business
wants. This is usually expressed in terms of broad outcomes the business requires,
 Page 2

rather than specific functions the system may perform. Specific design elements
are usually outside the scope of this document, although design standards may be
referenced. Hostel rooms, investigates the reservation of rooms, and develops
different facilities, principles and potential strategies for further exploration of the
use of facilities.

2.General Description : -

1.1 Product Functions :-

Defining the functionality is the most important part of the whole scenario because
the how the product is going to perform is the foremost matter of concern for any
business solution. It describes general functionality of the SYSTEM as: -.
 Provided the database which allows the user to check all the fortnight
information like quantity of rooms, facilities, number of available rooms
etc.
 Provide user login form & password.
 Provided with the facility to access information through WEB.
 Database security features.
 Other user friendly facilities

1.2 User Problem Statement :-

User may face the restriction on some room reservation to access the
information & downloads its information due to these are for confirmation. User can not
login without User-Id & Password
 Page 3

1.3User Objective :-

The new system will provide the user-friendly environment through GUI
based application, which gives an easy access to software interface for user.
User wants a system which provides the feature to get information from the
system without interrupting the job of others, which also reduces the workload
of the hostelers and information can be gathered more frequently.

1.4General Constraints :-

 User must use User-Id & Password for login in system.

 Maintaining the information of each item
 User must bind with certain time limit until his/her response.
 Page 4

3. SYSTEM ANALYSIS :-
System analysis and design refers to the process of examining a business situation
with the intent of improving it through better procedures methods. System development
can generally be thought of as having two major component. System Analysis and
System Design.

3.1 Functional Requirements :-

1. The details of the rooms, Price of rooms, and Employee details are to be maintained
and controlled solely by the (Manager) Admin alone.
2. The Employer can change alone the password assigned to him.
3. Also first the employer needed to login first in order to perform the booking actions.
4. Calculations of the charges and the reimbursements are to be implemented by the
application alone as designated by the admin.
5. The details of the rooms and facalities available are to be maintained and can be
updated regularly (of course only by the admin).
6. Enquiry form, Booking form and the pricing list are to be maintained in separate pages.
7. There should be new, update, cancel and search options available.

3.1 .1 System Requirements :-

A condition or capability that must be met or possessed by a system or system
component to satisfy a condition or capability needed by a user to solve a problem.
System requirement usually used as shorthand for "system functional requirement" .The
system’s hardware requirements are really much closer to the actual configuration that we
generally use in the daily life in our homes or offices.

System
 Windows 98, ME, NT4, 2000 or Windows XP
 Page 5

 PC with Intel P-IV, 20 GB hard-disk and 256 MB RAM, CD-ROM Drive,

Color Monitor
 TEXT EDITOR: e.g. Notepad is used for creating coding.
 In order to use print command printers should be installed.

The system should be:-.

 Capable to provide all the information as per the security conditions.
 Capable to provide information’s to users like-
 Quantity of available staff.
 Name of available staff.
 Quantity of available rooms.
 Price of rooms reservation.
 Capable to provide facility for downloading room reservation form.
3.1.2 Program Requirement :-
 Client: Windows95/98/NT
Internet Explorer/Netscape Navigator

 Server: Windows 2000/NT/XP

JDK 1.4.1
Java Web Server/Apache/Tomcat5.0
MS SQL Server/M-S Access
Flash/Macromedia Dream weaver
FireWall

3.1.3 Stability & Speed :-

No concerned issue of stability and issue are likely to entangle. It is expected that
the end result solution would take approximately 3-4 min to get start and once started the
result is not going to take not more then a min as the time for the query and the same still
 Page 6

depends that how compressed our data is in the resources. The response time will be even
less then that.
The product is highly stable and still would made upgraded to the fact that we commit to
provide after sales services, but any feature that the other side wants to embed would may
end up in extra economics, still we commit to get the solution modified and updated each
time we find a need of, or can be minor modified as per the user’s wish within a month of
the purchase of the software.
Stability establish the basis for agreement between the customers and the suppliers on
what the software product is to do.

3.2 Feasibility Study :-

Feasibility is the determination of whether or not a project is worth doing the
process followed and making this determination is called feasibility study. This
determines whether a project can and should be taken. Once it has been determined go
ahead and prepare the project specification which finalizes project requirement.
Generally, feasibility studies are undertaken within right time and normally culminate in
a written and oral feasibility report. The contents and recommendations of such a study
will be used as a sound basis for deciding whether to proceed, postpone or cancel
constraints of the project. Thus, the feasibility study may lead to the commitment of large
resources, it becomes necessary that it should be conducted competently and that no
fundamental errors of judgement are made.

3.2.1 Operational Feasibility:-

It is mainly related to human organizational and political aspects. The points
to be considered are:
 What changes will be brought with them system?
 What organisation structures are distributed?
 What new skills will be required? Do the existing staff members have these skills?
At present stage all the work is done by manual. So, throughout and response time is too
much. Major problem is lack of security check that must to be applied. Finding out the
 Page 7

detail regarding any information was very difficult, because data is stored in different
books and each book at different places. In case of any problem, no one can solve the
problem until the master of this field is not present. I have not changed the structure of
organisation. I have delivered a system that looks like a current structure of organisation.
But, this system removes all the overheads. All the computational work will be done
automatically in our system.

3.2.2 Technical Feasibility:-

This is concerned with specifying equipment, software and hardware that will
successfully satisfy the user requirement. The technical needs of the system may vary
considerably, but might include:
 The facility to produce output in a given time.
 Response time under certain condition.
 Ability to process a certain volume of transactions at a particular speed.
 Facility to communicate data to distant location.

In examining technical feasibility, configuration of the system is given more

importance than the actual make of hardware.
The configuration should give the complete picture about the system
requirements. What speeds of input and output should be achieved at particular
quality of printing. According to the definition of technical feasibility the
compatibility between front and back-end is very important. In our project the
compatibility of both is very good. The degree of compatibility of visual basic and
PL/SQL is very good. The speed of output is very good when we enter the data
and click button then the response time is very fast and give result very quickset.
I never find difficulty when we use complex query or heavy transaction. The
speed of transaction is always smooth and constant. This software provides
facility to communicate data to distant location.
The designing of front-end of a project is very important. So I have
selected visual basic as front-end due to the following reason:
 Easy implementation of code.
 Well defined interface with database.
 Well defined hand shaking with PL/SQL.
 Easy compiling and running
 Page 8

 At present scenario, a number of back-end tools are available, but I

have selected PL/SQL because of the following reason:
 Able to handle large amount of data.
 Security.
 Robust RDBMS.
 Backup &recovery.

With the help of above support we remove defect of existing software. In future, we can
easily switch over any platform to ensure that system does not halt in case of undesired
situation or events.
3.2.3 Economical Feasibility
Economic analysis is the most frequently used technique for evaluating the
effectiveness of a proposed system. It is commonly known as cost/benefit analysis: The
procedure is to determine the benefit and savings that are expected from a proposed
system and compare them with cost. If benefits outweigh cost, a decision is taken to
design and implement the system. Otherwise, further justification or alternative in the
proposed system will have to be made if it is to have a chance of being approved. This is
an ongoing effort that improves in accuracy at each phase of the system life cycle.

4. SYSTEM DESIGNING:-

4.1 SCOPE:-
1) A person should be able to login the system, change the password.
2) Mail should be send to the concerned person about confirmation of rooms.
3) Login id and password should be send at the email address.
4) The system should automatically show the fare for the corrosponding seat.

4.2 DATABASE DESIGN:-

 Page 9

Database design is the process of producing a detailed data model of a database.

This logical data model contains all the needed logical and physical design choices and
physical storage parameters needed to generate a design in a Data Definition Language,
which can then be used to create a database. A fully attributed data model contains
detailed attributes for each entity.

The term database design can used to describe many different parts of the design of an
overall database system. Principally, and most correctly, it can be thought of as the logical
design of the base data structures used to store the data. In the relational model these are
the tables and views. In an object database the entities and relationships map directly to
object classes and named relationships. However, the term database design could also be
used to apply to the overall process of designing, not just the base data structures, but also
the forms and queries used as part of the overall database application within the database
management system .

The process of doing database design generally consists of a number of steps which will
be carried out by the database designer. Usually, the designer must:

 Determine the relationships between the different data elements.

 Superimpose a logical structure upon the data on the basis of these relationships.

4.3. DATA FLOW DIAGRAM:-

0-LEVEL Diagram
 Page 10

HOSTEL
MANAGEMENT

PAYMENTS BED
MANAGEMENT MANAGEMENT

HOSTEL
MANAGEMENT
SYSTEM
ALLOTES ROOMS
MANAGEMENT MANAGEMENT

RENT
MANAGEMENT

1-Level Diagram
 Page 11

HOSTEL GENRATE
MANAGEMENT HOSTEL REPORT

BED GENRATE
MANAGEMENT BED REPORT

HOSTEL
RENT MANAGEMET GENRATE
MANAGEMENT RENT REPORT
SYSTEM

PAYMENT GENRATE
MANAGEMENT PAYMENT REPORT

ALLOTEES CHECK
Admin Lodin to Check
MANAGEMENT ALLOTEES DETAIL
System Roles of Manage Hostel Details
Access
2-LEVEL DFD
Manage Beds Details
Forget
Passwor
d Manage Rooms Details
Check
Manage
Credentia
Modules Manage Rent Details
ls

Manage allotees Details

Send
Email to
User Manage payments Profiles

Manage hostel facility Report

Manage System Admins Manage Roles of User Manage User Permission

 Page 12

4.4 ER DIAGRAM :-

DEPARTMENT NAME
NUMBE
R

BELON DEPARTMENT
GS

BIRTHDAT OFFERR
E D

SE REGISTE
X STUDENT R

STUDENT ID

STUDENT’S
NAME
 Page 13

COURSE

LIVIN
G COURSE
NAME

HOSTEL NUMBER
OF
CREDIT

HOSTEL
ID
HOSTEL NAME
COURSE NO

NUMBER
OF
SEATS

5. INTERFACE REQUIREMENT:-

5.1 GRAPHICAL USER INTERFAE:-

There are no such specific requirements for the system solution still the
requirement applicable only pertain to the area of GUI of CLI. The GUI is surely
applicable and the interface and the design, we are going to make you have feel how
before implementing the same.

5.2 COMMAND LINE INTERFACE:-

Command line interface available on most networking devices to permit a
network manager to view statistic, make configuration changes and perform other
administrative functions. An old traditional technique yet the most effective and the most
reliable one is this. We are surely going to have it embedded in our project with a user
friendly alias name rather with a name that you suggest us, for the cause, its really very
difficult to remember the complete path name and the word jargons for the same.

5.3 HARDWARE INTERFACE:-

 Page 14

 Website server
 Database server
 Client machine with internet connection

5.4 SOFTWARE INTERFACE:-

JDK 1.4.1
Java Web Server/Apache/Tomcat5.0
Ms-Excess.

6. Performance Requirement: -

The website must be able to provide a user-friendly interface to search, select and
sell various items from the shop along with proper navigational controls. Design scheme
should be aesthetic and uniform

The performance requirement for WEB is: -

 Internet speed
 Proper security and communication for password and premium submission.
 Page 15

7. NON FUNCTIONAL ATTRIBUTES:-

7.1 SECURITY:-
The authorization mechanism of the system will block the unwanted attempts to
the server and also let the system decide on which privileges may the user have. The
system has different types of users so there are different levels of authorization. There
will be also a firewall installed on the server so the incoming transactions can be filtered.
Data integrity for critical variables will also be checked.

7.2 REALIBILITY:-
The system shall operate 95% of the time. The number of defect should not
exceed 10 per function. In addition, before the submission of the final release the
calendar must be tested in case of the defects over 10 per function.

7.3 MANTAINABILITY:-
The requirements, modules that are explained in this document are enough to
satisfy the customer needs and wants. In case of a change or addition demand after
 Page 16

completing the system or in development process of the system, a new agreement shall be
done between the acquirer and FERSOFT Dev Group. The maintainability shall be easily
done by integrating new modules new offering new software solutions for the system.

7.4 PORTABILITY:-
The OBTRS is online service. So, anyone can use the service. One and only the
server of the system must have the required software including MYSQL, Apache.

7.5 REUSABILITY:-
Software development, have made many observations about the theories of software
reuse and what will actually work in practice. Key among these observations lies the fact
that to successfully introduce a formal reuse program into an organization, management
must support reuse both with words and with the necessary resources.
(1) we point out that reuse allows the manager to continue to avoid cost over the entire
life of the product. in our environment, we have centralized support for our reusable
components. so if reusable software has a bug, reusers can have it fixed for free (not
counting the hassle). although we can estimate maintenance costs many ways, we happen
to do it by multiplying our known historical error rates by what it costs us to fix those
errors.

7.6. RESOURCE UTILIZATION:-

Resource utilization relates generally to computer executable workflow management and
control systems and more particularly to computer system executable methods for use in
an automated workflow system.

7.7. STABLE AND SPEED EFFICIENCY:-

Stability and Speed establish the basis for agreement between the customers and the
suppliers on what the software product is to do. The complete description of the functions
to be performed by the software specified in the SRS will assist the potential users to
 Page 17

determine if the software specified meets their needs or how the software must be
modified to meet their need.

8. SECURITY:-

8.1. DESCRIPTION:-
The security part is yet the best part that would make our product ahead of the rest crew.
A part of the security concern is being taken under the research work. We do not commit
that this part would be fulfilled surely, still our efforts will always soar high holding the
reigns of success and while being on ground.
Some hostels are creating individual user accounts totrack which titles an individual has
checked out, and to create "HOSTEL MANAGEMENT" type features.

8.2. TECHNICAL ISSUES:-

 As far as the technical issues related to this project from security
point of view, there is no chance of steal the data until either we
want or if there is any problem in the coding section.

The technology that we are going to use in order to implement this security
solution is that of the hostel management system embedded with our
 Page 18

software solution that can really help us out in sending bus information and
confirmation through reservation. In case any transaction is being made from
an account the user will receive a information notice regarding his each and
every transaction. Hopefully we are going to implement this technology
through hostel management service.
 Page 19

8.3. Preliminary schedule: -

Now looking at the time limit of 53 days and working for 3 hours and work to do
we can divide our work in following parts:

JOB DAYS TIME

Project selection and formation of team 1 day 1x3=3hrs
Scheduling & Analyzing the project 2 days 2x3=6hrs
Discussing and allotment of job 2 days 2x3=6hrs
Planning of system 10 days 10x3=30hrs
Preparation of reservation detail 3 days 3x3=9hrs
Study on hostel management office 3 days 3x3=9hrs
Working on form design 10 days 10x3=30hrs
Analysis of WEB module 2 days 2x3=6hrs
Working on WEB module 5 days 2x5=10hrs
Working for connectivity to DB 2 days 2x3=6hrs
Testing 8 days 8x3=24hrs
Implementing & integrating 2 days 2x3=6hrs
Documentation 3 days 3x3=9hrs
TOTAL 53 days 159hrs

Preliminary Budget or cost estimation: -

Merely we think of the cost estimation on the basis of the following points:

Static IP for WEB ---- Rs. 1,000 to Rs. 2,000

Paper work & reports ---- Rs. 500
 Page 20

Labour costs ---- Rs. 3,000

Other expanses ---- Rs. 200

We estimated a

Minimum cost of Rs. 4,700

Maximum cost of Rs. 5,700

8.4 RISK:-
The complete RISK ANALYSIS is given below in the table :-

S.NO. RISK ITEMS. RISK MANAGEMENT TECHNIQUES.

1. Personnel Our Team comprises of the persons who are ignorant or
Shortfalls novice in the security issues and also in the technology that
we are going to use for the implementation of the same.
2. Unrealistic The term/ time span allotted is very short, quite insufficient
Schedule and and the things are really next to impossible to be in such a
Budget short span of time, with the same working hours per day.
3. Developing the Mission Analysis is strong but what if a person or more gets
wrong s/ w diverted from.
functions
4. User interface For the user interface developed , even after getting it
sanctioned from the opposite side if it denies to accept the
existing user interface.

5. Continuation What if the user side even after signing the contract are
stream of continuously asking for the changes and modification an undue
requirement problem would be there in the development of the software and
changes. undue time would be utilized for the same which can ultimately
result in a delay in the project.
6. Short Falls in Again a new Bulgarian problem to face.
furnished product
 Page 21

7. Real time This involves Instrument tuning failure, simulation.

performance short
fall

Risk may occur with the WEB is

 Internet speed
 Proper security and communication for password and premium
submission.

We have to take certain important measures to not face these risks to

occur.

9. Reference & Appendices :-

 www.google.com

10.Conclusion
 Page 22

The Integrated Hostel Management System, an online wide area networking

system, had poor networking, operating, application and database security features and
was hence vulnerable to unauthorised access and data/source code modification. These
deficiencies had security
implications in the absence of audit trails, system logs. Unauthorised
business rule having bearing on the revenues of the Corporation was
incorporated in the software. The database was not designed to capture
critical data for grant of various concessions and validation checks were
inadequate.
There is an urgent need to improve networking, operating, application
and data base security features of the system.