Hostel Accomodation System

Project Document

Hostel Room Allocation System

[pic 1][pic 2][pic 3]

[pic 4]

BTech

Computer Science and      Engineering

School of Computer Science &Engineering

[pic 5][pic 6]

Table of Contents

• Abstract

• Process model

• Scheduling diagrams

• SRS

1. Introduction

1. Purpose

1. Scope

1. Overall Description

1. Product Perspective

1. Product Functions

1. Operating Environment

1. External Interface Requirements

1. User Interface

1. Hardware Interface

1. Software Interface

1. Functional Requirements

1. Non Functional Requirements

1. Performance Requirements

1. Logical Database Requirements

1. Design constraints

1. Standard compliance

1. Reliability

1. Availability

1. Security

1. Use case Diagram

1. Use case Descriptions

• SDS

1    Introduction

1. Purpose

1. Scope

1. Objective

1. System Overview

1. Product Perspective

2.1.1 Design Method

2.1.2 User Interfaces

2.1.3 Hardware Interfaces

2.1.4 Software Interfaces

2.1.5 Memory Constraints

2.1.6 Operations

2.1.7 Site Adaptation Requirements

1. Product Functions

1. User Characteristics

1. Constraints

1. Assumptions and dependencies

1. Design Consideration

1.  Operating Environment

2 Fault Tolerance

1. Design Conventions

            4 Architectural Designs

              5 Architectural Diagrams

               6 User Interface

4  System Architecture

4.1 View of Product Classes

1. Individual Classes of Systems

5   Diagrams

1. Data Flow Diagram

1. Activity Diagram

1. Use Cases

4   Sequential Diagram

1. Collaboration Diagram

1. State Chart Diagram

6   Restrictions, Limitations and Constraints

1. Testing Issues

• Test cases

• User Interface

• Conclusion

ABSTRACT:

With every passing year, the intake of students in colleges increased drastically. This inevitably raises the question of hostel room allocation as many students leave their hometowns. Viewing a similar scenario on a much smaller scale, say A and B are two students in need of room and both willing to pay the fees required. However, only one desired room with all facilities is available. Either A or B can be given the room. The other student needs to be allocated a room of lower value. This problem can be overcome by sorting students based on their academic performances (cgpa). This provides the student with numerically smaller rank with a choice of rooms available to pick from.

In the backend we have database of students which contain personal information like name, reg no, branch, cgpa etc. In the frontend we have the available rooms list for each student and by taking the cgpa of student from backend. Based on this room is allocated. Cgpa’s are obtained according to first come first serve basis. Room once allotted can’t be changed.

In this project we will be working with Jsp which contains database of student’s personal details along with their cgpa and on the other hand in the frontend which contains the available rooms list. Rooms are allotted based on their cgpa’s and each student will be given a NCGPA rank based on their cgpa and branch. The student with less rank has a choice of selecting the room first than the person with higher rank. The next person chooses from the remaining rooms left. It is basically done based on the rooms available to each student at the time of their counselling. Here we are following first rank first serve. Student with higher rank has fewer available room options than the student with low rank. Our project tells that a better cgpa gives a better rank and a better room too. Room allocation is directly dependent on the student’s academic performance.

PROCESS MODEL:

The model which we have opted to follow for our project is the Waterfall model.

JUSTIFICATION:

• First we will create database of students which includes their cgpa and personal data.
• The requirements are well defined and clear.
• The rooms are allotted to the students based on cgpa.
• Once the room is allotted it can’t be changed again. For this rule Waterfall model supports us.
• Since it is a sequential approach it allows us to do step by step process.

SCHEDULING DIAGRAMS:

Work-breakdown Structure:[pic 7]

Gantt chart:

[pic 8]

Timeline Chart:

[pic 9]

SRS:

1. Introduction

The following subsections of the Software Requirements Specifications (SRS) document provide an overview of the entire SRS.

1.1 Purpose

The Software Requirements Specification (SRS) will provide a detailed description of the requirements for the Hostel room allocation system. This SRS will allow for a complete understanding of what is to be expected of the system to be constructed. The clear understanding of this and its functionality will allow for the correct software to be developed for the end user and will be used for the development of the future stages of the project. This SRS will provide the foundation for the project. From this SRS, the system can be designed, constructed, and finally tested.