Hostel Management System SRS

Document Sample
Hostel Management System SRS Powered By Docstoc
					    Hostel Management System

Software Requirements Specification

                    Hostel Management System Software Requirements Specifications

1   Introduction
This document fully and formally describes the requirements of the proposed said project system.
It sets out the functional and non-functional requirements and includes a description of the user
interface and documentation and training requirements.

1.1 Purpose
The purpose of Software Requirements Specification (SRS) document is to describe the
external behavior of the Hostel Management System (HMS). Requirements Specification
defines and describes the operations, interfaces, performance, and quality assurance
requirements of the Hostel Management System (HMS). The document also describes the
nonfunctional requirements such as the user interfaces. It also describes the design
constraints that are to be considered when the system is to be designed, and other factors
necessary to provide a complete and comprehensive description of the requirements for
the software. The Software Requirements Specification (SRS) captures the complete
software requirements for the system, or a portion of the system. Requirements described
in this document are derived from the Vision Document prepared for the Hostel
Management System (HMS).

1.2 Scope
The Software Requirements Specification captures all the requirements in a single
document. 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.The Hostel Management System (HMS) is supposed to have the
following features.

       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, Student attendance, leave and other details
       Hostel facility related bills and receipts and essential reports are available.
       Hostel Mess panel

1.3 Definitions, Acronyms, and Abbreviations.

        HMS - Hostel management system

        User - The student who lived in the hostel.

        Administrator - The warden of the hostel who manage all the things.
                    Hostel Management System Software Requirements Specifications

        Student Profile - information of the student.

        Mess status - it tells the mess information of the students.

        User’s profile - It contain the student’s personal information. e.g.. his name,
        father’s name, his full address etc.

1.4     Overview
        The SRS will provide a detailed description of the Hostel Management System
        (HMS). This document will provide the outline of the requirements, overview of
        the characteristics and constraints of the system.
        1.5.1 Section 2: This section of the SRS will provide the general factors that
        affect the product and its requirements. It provides the background for those
        requirements. The items such as product perspective, product function, user
        characteristics, constraints, assumptions and dependencies and requirements
        subsets are described in this section.
        1.5.2 Section 3: This section of SRS contains all the software requirements
        mentioned in section 2 in detail sufficient enough to enable designers to design
        the system to satisfy the requirements and testers to test if the system satisfies
        those requirements.

2     The Overall Description
Describes the general factors that affect the product and its requirements. This section
does not state specific requirements. Instead it provides a background for those
requirements, which are defined in section 3, and makes them easier to understand.

2.1 Product Perspective
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 number.

2.1.1 Hardware Interfaces
    The existing Local Area Network (LAN) will be used for collecting data from the
    Different Pc’s and also for updating the Hostel Records.

2.1.2 Software Interfaces
        Client on PC:            Operating System (any latest windowns)
    Data Base Server:            SQL Server 2008
    Development End:             Visual Studio 2008 (VB.Net).
                     Hostel Management System Software Requirements Specifications

2.2   Product Functions
Admission details and type of admission to the hostel.

Student Management
Student attendance, leave and other details like late entry, mess

Bills and Collection
Hostel facility related bills and receipts and essential reports are available.

2.3 User Characteristics

Every user should be comfortable of working with computer. He must have basic
knowledge of English too.

2.4 Assumptions and Dependencies
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

 Area                         Descriptions

Hostel                        All other hostel related functionality and/or processes will
processes                     remain intact. The
                              process and logic the system executes to manage the hostel
                              user accounts will
                              remain the same as the process before automation.

Databases                     The underlying database to be used for this system is already
                              in place as part of
                              the standard infrastructure.
Administrator                  Only the warden will administer the system. All other hostel
                              employees will
                              only have access permissions like any other users.
                        Hostel Management System Software Requirements Specifications

3    Specific Requirements
This section describes in detail all the functional requirements.

3.1 External Interfaces
The Hostel Management System will use the standard input/output devices for a personal
computer. This includes the following:
    Keyboard
    Mouse
    Monitor
    Printer

3.1.1 User Interfaces
Hostel Management System is a Customize and user-friendly software for Hostel. It has
been designed to automate, manage and look after the over-all processing of even very
large Institutes. It is capable of managing Enquiry details, Student Details, Faculty
Details, Payment Details etc.

It also Provides Very helpful report for managing the hostels in easy and accurate way

1. Hostel Information panel

2. Admin panel

3. Hostel Account panel

4. Student panel

5. Hostel Mess panel
                    Hostel Management System Software Requirements Specifications

3.1.2 Software Interfaces
The system shall interface with an SQL Server 2008.
3.1.3 Hardware Interfaces
The system shall run on a Microsoft Windows based system.
3.1.4 Communication Interfaces
The system shall be a standalone product that does not require any communication

3.2 Functional Requirements

     Add Students
      The Hostel Management System shall allow the warden to add new students to the
      system’s database.

     ID Number
      The HMS shall generate an account number. This number will be the students’s
      ID number.

     Students’s Profile
      The HMS shall generate the students’s profile containing the following
      information: student’s account number, student’s full name, student’s address,
    phone number, email ID, student’s room # and mess account #.

     Room Allocation
      The HMS will allocate a room to student according to the session or class. The
      room no. will store in the student’s profile.

     Mess A/C
      A mess account will also generate. This account having the mess status of the
      whole month. On the base of this account monthly charges of mess of a student
      will be defined.

     Profile Security
      Profile of each student will be created before operating HMS including guardian
      to maximize the HMS security. Student dues status and mass A/C status can be
      accessed here.

     Dues Status
      Student dues status will be changed in database according to dues pay or not.

     Mess Status
                   Hostel Management System Software Requirements Specifications

       HMS will also having the detail of mess of a student and stored in database.

     Room Reservation
      The HMS will allow staff to put a hold on a room if any room is not available at
      the moment

    Database Entities
      The HMS has entities users, students, room, mess A/C. The HMS will have in the
      room profile the following information: room no, type and capacity.

     Student Search
      The HMS shall allow the users to search the students from the database according
      to different criteria such as by name, id or phone number.

     User Search
       The HMS shall allow the users to search the user from the database according to
      different criteria such as by name, id or phone number.

     Profile’s Update
      The HMS will allow the warden to access and update any student’s, room, and
      HMS student’s profile information.

     Room at leaving
      When a student will leave its room. Room will checkout and changes the status of
      room from room profile and student’s registration will be cancelled.

Registration Options

     Room Renewal
      The HMS will allow renewing the student’s registration every year.

     Cancel Registration
       The HMS will allow the guardian to cancel registration from the system’s
      database who will leave room.
                    Hostel Management System Software Requirements Specifications

3.3 Nonfunctional Requirements
     Performance
      The system shall support up to 2 students per room.

     ID Number
      The system requires the user to identify by using an ID Number at the checkout

     Access Permission
      The HMS shall have several types of access permissions. For instance, the
      warden is recognized as the system’s administrator, thus, the warden shall be able
      to perform any type of activities on the system and both the user’s and student
      profiles. At the same time, the other hostel staff members shall have restricted
      access to both the users’ and student profiles.

3.3.1 Performance Requirements
Performance requirements define acceptable response times for system functionality.
     The load time for user interface screens shall take no longer than two seconds.
     The log in information shall be verified within five seconds.
     Queries shall return results within five seconds.

3.3.2 Design Constraints
The Hostel Management System shall be a stand-alone system running in a Windows

3.3.3 Standards Compliance
There shall be consistency in variable names within the system. The graphical user
interface shall have a consistent look and feel.

3.3.4 Reliability
The system shall be available 99.9% of the time.
3.3.5 Maintainability
The system shall provide the capability to backup the database.
3.3.6 Portability
The Hostel Management System shall run in any Microsoft Windows environment that
contains VB.NET Programming and the Microsoft SQL Server Database.

Other constrains
      The system supports for Email Features.
Hostel Management System Software Requirements Specifications

Description: Hostel Management System project SRS is uploaded in this document