A Project Report On

HOSTEL MANEGEMENT SYSTEM

In partial fulfillment of requirements for the degree of

Bachelor of Engineering In Computer Science and Engineering

SUBMITTED BY:

1. Name of the student 1 2. Name of the student 2

Under the Guidance of

Prof. Name

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING AJAY KUMAR GARG ENGINEERING COLLEGE GHAZIABAD 201302. 2011 - 2012

CERTIFICATE
This is to certify that the project entitled HOSTEL MANEGEMENT SYSTEM has been carried out by the team under my guidance in partial fulfillment of the degree of Bachelor of Engineering in Computer Science and Engineering of Ajay Kumar Garg Engineering College, Ghaziabad during the academic year 2011-2012 (Semester-VIII) .
Team:

1. Name of the student 1 2. Name of the student 2

Date: Place:

Guide (Name of Guide)

Head, Computer Department (Mr. U. B. Pawar)

ACKNOWLEDGEMENT
In completing this graduate project I have been fortunate to have help, support and encouragement from many people. I would like to acknowledge them for their cooperation. First, I would like to thank Mr Sandeep Kumar Aggarwal, HOD (MCA), BIT,Meerut for guiding me with knowledge and support. I would also like to thank Mrs Rimmi Anand, Asst. Professor, BIT,Meerut for guiding me through each and every step of the process. I would also like to thank Mr Saurabh Verma, External Project Supervisor, Team Leader at Wizard InfoSolutions Private Limited, who showed immense patience and understanding throughout the project and provided suggestions

1. Name of the student 1 2. Name of the student 2

PAGE INDEX
Topic ABSTRACT 1. TITLE OF CHAPTER ONE 1.1 HEADING 1.2 HEADING Page No.

2.

TITLE OF CHAPTER TWO 2.1 HEADING 2.2 HEADING

: : : : : N-1 N.

CONCLUSION BIBLIOGRAPHY APPENDIX A USER MANUAL APPENDIX B SNAP SHOTS OF GUI/RESULT APPENDIX C

ABSTRACT
As the name specifies HOSTEL MANAGEMENT SYSTEM is a software developed for managing various activities in the hostel. For the past few years the number of educational institutions are increasing rapidly. Thereby the number of hostels are also increasing for the accommodation of the students studying in this institution. And hence there is a lot of strain on the person who are running the hostel and softwares are not usually used in this context. This particular project deals with the problems on managing a hostel and avoids the problems which occur when carried manually. Identification of the drawbacks of the existing system leads to the designing of computerized system that will be compatible to the existing system with the system Which is more user friendly and more GUI oriented. We can improve the efficiency of the system, thus overcome the drawbacks of the existing system. Less human error Strength and strain of manual labour can be reduced High security Data redundancy can be avoided to some extent Data consistency Easy to handle Easy data updating Easy record keeping Backup data can be easily generated

1. INTRODUCTION
1.1 PROBLEM STATEMENT
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. All the hostels at present are managed manually by the hostel office. The Registration form verification to the different data processing are done manually. Thus there are a lot of repetitions which can be easily avoided. And hence there is a lot of strain on the person who are running the hostel and softwares are not usually used in this context. This particular project deals with the problems on managing a hostel and avoids the problems which occur when carried manually Identification of the drawbacks of the existing system leads to the designing of computerized system that will be compatible to the existing system with the system which is more user friendly . We can improve the efficiency of the system, thus overcome the drawbacks of the existing system. We design this system of the hostel management especially for the college hostel, 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.

1.2 OBJECTIVES OF PROJECT

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 information of a previous student, because through this system you can store the data of those students who had left the hostel . 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. The system will help you to check the mess bills of every student and the students hostel dues. The students of the hostel will be recognized from the ID number allocated at the room rental time. In the last this system will improve the management work in the hostel.

1.3

TO THE PROBLEM
Hostel management gives on idea about how the students details, room

allocation, mess expenditure are maintained in the particular concern. The hostel management system also includes some special features. The administration has the unique identity for each members as well as students details. The stock management has also held by mess expenditure, the mess expenditure 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.

Visual Basic6.0 is used as the front end tool and Oracle is used as a backend tool. Visual Basic is one of the driven programming languages. The application wizards, menu editor and data reports etc is very much useful for creating very good professional software.

1.4. TO THE SOFTWARE TOOL The visual part refers to the method used to create the graphical user interface (GUI). Rather than writing numerous lines of code to describe the appearance and location of interface elements, you simply drag and drop prebuilt objects into place on screen. If youve ever used a drawing program such

as paint, you already have most of the skills necessary to create an effective user interface. It revolves around ready-made objects and it is event-driven that is all the activities in a program are triggered by one event or another. Each object has its own properties, determining its position, size, color, appearance and nature of its text and much more. Each object also has its own event-handling procedures. Visual basic knows what a button is and how it works? It also works how to handle images, menus, dialog boxes, drive and directory list and much else. The programmer does not have to write code to trap these events the system does that automatically because the program code runs in response to events. The flow of execution is not as fixed in a traditional program. Operations do not have to follow a set of sequence and can be easily interrupted, suspended or abandoned. The process of program design reflects the nature of the system. You begin by the screen layout events and then any necessary code to co-ordinate the whole program.

2. OVERALL DIAGRAM
2.1 Use Case Diagram:
Use case diagram is a diagram that shows the interaction between user and system to capture the users goals.

2.2 Class Diagram:

Class diagram is a collection of static elements such as classes and their relationships connected as a graph to each other.

2.3 Sequence Diagram

Sequence diagram shows an interaction arranged in a time sequence . it is an alternate way to understand the overall flow of the control of the system program.

2.4 State Diagram:

State diagram are a familiar technique to describe the behaviour of a system. They describe all of the possible states that a particular object can get into and hoe the objects state changes as a result of events that reach the object.

2.5 Activity Diagram:

It describes the sequence of activity it support for the conditional and parallel behaviour . It is a variant of a state diagram in which most of the states are activity states.

Use Case Diagram

collect& store the student details

store the availability of hostel& room details

generate & update the attendance details

calculate& generate report for mess expenditure detail for ... aadministrator db manager calculate & generate report for mess expenditure detail for ...

request for mess bill report

check and verify mess bill report

mess bill calculation

update the payment details

display the mess bill report to the student

payment of mess bill student

Class Diagram

Sequence Diagram

student

Administrator give details

DB manager

enter student details update

enter mess item & eexpenditure details update

calculate(total mess expenditure)

enter attedance details update

request for mess bill expenditure

calculate(total mess item expenditure/total no of student)

publish

mess fees details

pay the fees

enter the payment details

update

State Diagram:

get details

CHeking

all details correct

processing update details

some details missing details obtained mess details details verified update

Waiting missing details obtained

calculating calculate mess expenditure

mess bill

Reporting generated report stop

Activity Diagram

start

Login

enter student details

enter room details

enter mess details

calculate mess expenditure& mess bill

generate report

Update details

stop

3. METHODOLOGY
It contains four modules in it. They are given below Student details Attendance details Room details Mess modules

3.1.Students details:
This module consists of the details of the student such as roll number, name, date of birth, address, phone number, year, degree, room no, department name nad etc. here the details are entered and are updated. 3.1.1.Use Case Diagram Use case diagram is a diagram that shows the interaction between user and system to capture the users goals.

enter student details

edit details

adminis delete details

db manager

view details

details updated

3.1.2.Class Diagram:
Class diagram is a collection of static elements such as classes and their relationships connected as a graph to each other.

3.1.3.Sequence Diagram: Sequence diagram shows an interaction arranged in a time sequence . it is an alternate way to understand the overall flow of the control of the system program.

Administrator

db Manager

enter student details

edit details

details are updated

update details details updated

delete details details updated

view details by giving rollno

3.1.4.State Diagram: State diagram are a familiar technique to describe the behaviour of a system. They describe all of the possible states that a particular object can get into and hoe the objects state changes as a result of events that reach the object.
start

checking

all details connect

processing update details

mess details some details missing details obtained details verified updated

waiting missing details obtained

calculating calculate mess mess bill

reporting generated report

stop

3.1.5.Activity Diagram: It describes the sequence of activity it support for the conditional and parallel behaviour . It is a variant of a state diagram in which most of the states are activity states

start

enter student details

enter student rollno

inv alid update details

v alid

edit

delete

v iew

update

stop

3.2.Attendance details:
In this module,attendance details are maintained. Hence the upto date

attendance of the each students are maintained. 3.2.1.Use Case Diagram: Use case diagram is a diagram that shows the interaction between user and system to capture the users goals.

enter the rollno

enter the attendence P/A adminis DBmanager

update details

updated successfully

3.2.2.Class Diagram: Class diagram is a collection of static elements such as classes and their relationships connected as a graph to each other.

3.2.3.Sequence Diagram: Sequence diagram shows an interaction arranged in a time sequence . it is an alternate way to understand the overall flow of the control of the system program.

administrator enter rollno

db manager

enter attendence details

update

details

updated

3.2.4.State Diagram: State diagram are a familiar technique to describe the behaviour of a system. They describe all of the possible states that a particular object can get into and hoe the objects state changes as a result of events that reach the object .

start

entering enter attendence details

details entered

updating update details

some details are missed get details

all details are connected

waiting

3.2.5.Activity diagram: It describes the sequence of activity it support for the conditional and parallel behaviour . It is a variant of a state diagram in which most of the states are activity states.

start enter rollno

valid

enter the attendence absent present

invalid

UPDATE details

stop

3.3.Room details:
In this module, the room number for the hostel student is allocated and the details of the each students are maintained and updated regularly. 3.3.1Use Case Diagram: Use case diagram is a diagram that shows the interaction between user and system to capture the users goals.

enter room details

update details

view details

enter the hostelno

adminis check free room

DBmanager

check for availability in other hostel no

enter the other hostelno allocate room

display free rooms request room

student

room details displayed

3.3.2.Class Diagram: Class diagram is a collection of static elements such as classes and their relationships connected as a graph to each other.

3.3.3. Sequence Diagram:

Sequence diagram shows an interaction arranged in a time sequence . it is an alternate way to understand the overall flow of the control of the system program.

student

administrator enter room details

db manager

update request for room av ailability

checking

enter room no to v iew details

allot room no

display the room details

3.3.4.State Diagram: State diagram are a familiar technique to describe the behaviour of a system. They describe all of the possible states that a particular object can get into and hoe the objects state changes as a result of events that reach the object.

CHECKIN G

all details correct

processing update details

room details some details missing details verified details obtained waiting missing details obtained view details update

3.3.5.Activity Diagram: It describes the sequence of activity it support for the conditional and parallel behaviour . It is a variant of a state diagram in which most of the states are activity states.

start room details

enter room details

request for room availability enter room no

UPDATE Details

check room availability

request room details

display room availability details

view room details

exit

stop

3.4.Mess Modules:
In this module, the mess item expenditure for each student in the hostel is calculated for each month and the mess bill for each student in calculated and displayed.

3.4.1.Use Case Diagram: Use case diagram is a diagram that shows the interaction between user and system to capture the users goals.

enter mess expenditure

calculate expenditure for veg

calculate expenditure for non-veg

ADMINISTRATOR

DBmanager calculate mess expenditure details per day

mess bill calculation acknowledgement for messbill calculate mess expenditure details per month

display mess bill report

request for messbill report

student

3.4.2.Class Diagram:
Class diagram is a collection of static elements such as classes and their relationships connected as a graph to each other.

3.4.3.Sequence Diagram:

Sequence diagram shows an interaction arranged in a time sequence . it is an alternate way to understand the overall flow of the control of the system program.

student

administrator

db manager

enter mess item & expenditure detail(veg,nonveg)

calculate totalmess expenditure(veg,nonveg) request for mess fees calculation

calculate

publish

mess fees details

acknowlegement

enter the payment details

3.4.4.State Diagram: State diagram are a familiar technique to describe the behaviour of a system. They describe all of the possible states that a particular object can get into and hoe the objects state changes as a result of events that reach the object.

get details Checking all details correct Processing Update details

mess details some details missing details obtained Waiting missing details obtained details verified Calculate calculate mess expenditure update

mess bill

Report Generator report

3.4.5.Activity Diagram: It describes the sequence of activity it support for the conditional and parallel behaviour .It is a variant of a state diagram in which most of the states are activity states.

start

enter mess item details(veg,nonveg)

enter payment details

Update

UPdate

calculate mess bill expenditure per day

calculate mess bill expenditure per month

display the mess expenditure(veg,nonveg)

Display the m ess expenditure (veg,non veg)

generate mess bill & payment report stop

3. REQUIREMENT ENGINEERING
Systematic requirements analysis is also known as requirements engineering. It is sometimes referred to loosely by names such as requirements gathering, requirements capture, or requirements specification. The

term requirements analysis can also be applied specifically to the analysis proper, as opposed to elicitation or documentation of the requirements, for instance. Requirements Engineering can be divided into discrete chronological steps:

Requirements elicitation, Requirements analysis and negotiation, Requirements specification, System modeling, Requirements validation, Requirements management. Requirement engineering according to Laplante (2007) is "a subdiscipline

of systems engineering and software engineering that is concerned with determining the goals, functions, and constraints of hardware and software systems. In some life cycle models, the requirement engineering process begins with a feasibility study activity, which leads to a feasibility report. If the feasibility study suggests that the product should be developed, then requirement analysis can begin. The requirement engineering provides the appropriate mechanisam for understanding what customer wants. 2.1FeasibilityStudy Feasibility study conducted once the problem is clearly understood.Feasibility study is a high level capsule version of the entire system-analysis and design

process.The objective is to determine quickly and at the minimum expense how to solve the problem and to determine the problem is solved. .

2.2 Requirement Analysis

Requirements Analysis is the process of understanding the customer needs and expectations from a proposed system or application and is a well-defined stage in the Software Development Life Cycle model. Requirements are a description of how a system should behave or a description of system properties or attributes. It can alternatively be a statement of what an application is expected to do.Given the multiple levels of interaction between users, business processes and devices in global corporations today, there are simultaneous and complex requirements from a single application, from various levels within an organization and outside it as well.The Software Requirements Analysis Process covers the complex task of eliciting and documenting the requirements of all these users, modeling and analyzing these requirements and documenting them as a basis for system design. Software Requirements Analysis and Documentation Processes are critical to software project success. Requirements Engineering is an emerging field which deals with the systematic handling of requirements.

2.3 Proposed System

The drawback of the existing system is that it is very difficult to retrieve data from records. It is difficult to handle the whole system manually and it is less accurate and to keep the data in records for future reference because it may get destroyed . Moreover it is very difficult to retrieve data. Redundancy of data may occur and this may lead to the inconsistency. The manual system is so time-consuming. The proposed system is very easy to operate. Speed and accuracy are the main advantages of proposed system. There is no redundancy of data. The data are stored in the computer secondary memories like hard disk,

etc. it can be easily receive and used at any time. The proposed system will easily handle all the data and the work done by the existing systems. The proposed systems eliminate the drawbacks of the existing system to a great extent and it provides tight security to data.

4. REQUIREMENT AND SPECIFICATION

4.1.System Requirement
This project mainly aims to deal the operations of college hostel It consist of 2 modules. User module Administrator module User Module Consist Of User login View notice board

Adminstrator Module Consist Of Admin login Registration Allocation Vocate Hostelbill 4.1.1 User Panel
4.1.1.1 User Login

1. It allows the different users to access the registration forms. 2. User can view the details of notice boards.

4.1.1.1.1 Notice Board

Any change in the Hostel fee, mess fee will be shown in this. It can be also used for different notifications. 4.1.1.2 Admin Panel
4.1.1.2.1 Administrator Login
4.2.1.1 Home

The Administrator can : 1. Allot students to the hostel. 2. Vacate the students form the hostel. 3. Control the status of the fee payement. 4. Edit the details of the students & modify the student records.

4.2.1.2 Registration Form 4.2.1.3 Allocating the rooms 4.2.1.4Vacating the rooms

As the students course is over they will vacate their rooms. So it is required for the administrator to remove their records from the database tables. This section includes the option for the room vacation and the deletion of the particular record from the database

4.2.REQUIREMENTS
4.2.1 Software Configuration Front end Backend : C#.NET : Microsoft SQL Server 2005

Operating System : Windows XP Language : C#

Frame work : Visual studio 2005 framework 2.0

3.2.2 Hardware Configuration Processor RAM Monitor Keyboard Mouse CD-ROM Floppy Drive Hard Drive Mother Board : Pentium III,1.13GHz :128 Mb SD RAM : SVGA, samtron 56v : Samsung Keyboard 105 keys : Logitech 3-Button : Samsung 52X : 1.44Mb[3 ] sony : 40GB HDD : Pentium 810

5.DESIGN
5.1 Input Design
The system design is divided in to two portions. The Administrator section and the User(students) section. 5.1.1 Administrator 1. The Administrator can allot students to the hostel. 2.He can vacate the students form the hostel. 3.He can control the status of the fee payement. 4.He can edit the details of the students.He can change their rooms, edit and delete the student records. A process of converting user originated inputs to a computer-based format. Input design is an important part of development process since inaccurate input data are the most common cause of errors in data processing. Erroneous entries can be controlled by input design. It consists of developing specifications and procedures for entering data into a system and must be in simple format. The goal of input data design is to make data entrybas easy, logical and free from errors as possible. In input data design, we design the source document that capture the data and then select the media used to enter them into the computer. There are two major approaches for entering data in to the computer. They are Menus. Dialog Boxes.
5.1.1.1.Menus

A menu is a selection list that simplifies computer data access or entry. Instead of remembering what to enter, the user chooses from a list of options. A

menu limits a user choice of response but reduce the chances for error in data entry.

5.1.1.2.Dialog Box

Dialog boxes are windows and these windows are mainly popup, which appear in response to certain conditions that occur when a program is run. It allows the display of bitmaps and pictures. It can have various controls like buttons, text boxes, list boxes and combo boxes. Using these controls we can make a dialog with the program.

5.2 OUTPUT DESIGN

Designing computer output should proceed in an organized, well throughout manner; the right output element is designed so that people will find the system whether or executed. When we design an output we must identify the specific output that is needed to meet the system. The usefulness of the new system is evaluated on the basis of their output.Once the output requirements are determined, the system designer can decide what to include in the system and how to structure it so that the require output can be produced. For the proposed software, it is necessary that the output reports be compatible in format with the existing reports. The output must be concerned to the overall performance and the systems working, as it should. It consists of developing specifications and procedures for data preparation, those steps necessary to put the inputs and the desired output, ie maximum user friendly. Proper messages and appropriate directions can control errors committed by users. The output design is the key to the success of any system. Output is the key between the user and the sensor. The output must be concerned to the systems working, as it should. Output design consists of displaying specifications and procedures as data presentation.

User never left with the confusion as to what is happening without appropriate error and acknowledges message being received.

5.3 DATABASE DESIGN The data in the system has to be stored and retrieved from database. Designing the database is part of system design. Data elements and data structures to be stored have been identified at analysis stage. They are structured and put together to design the data storage and retrieval system. A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and efficiently. The general objective is to make database access easy, quick, inexpensive and flexible for the user. Relationships are established between the data items and unnecessary data items are removed. Normalization is done to get an internal consistency of data and to have minimum redundancy and maximum stability. This ensures minimizing data storage required, minimizing chances of data inconsistencies and optimizing for updates.

5.4 ARCHITECTURAL DESIGN

Architectural design represents the data structure and program components that are required to build the computer based system. It consider the structures and properties Of the components that constitute the system and relationship that exist between all architectural components of the system.

5.5 PROCESS DESIGN

Process design plays an important role in project development. In order to understand the working procedure, process design is necessary. Data Flow Diagram is the tool used for process design. Data Flow Diagram is the logical representation of the data flow of the project. The DFD is drawn using various

symbols. It has a source and a destination. The process is represented using circlesand source and destination are represented using squares. The data flow is represented using arrows. One reader can easily get the idea about the project through Data Flow Diagram.

6. SYSTEM TESTING
System testing is the stage of implementation, which is aimed at ensuring that the system works accurately and efficiently before live operation commences. Testing is the process of executing the program with the intent of finding errors and missing operations and also a complete verification to determine whether the objectives are met and the user requirements are satisfied. The ultimate aim is quality assurance. Tests are carried out and the results are compared with the expected document. In the case of erroneous results, debugging is done. Using detailed testing strategies a test plan is carried out on each module. The various tests performed in Network Backup System are unit testing, integration testing and user acceptance testing.

6.1 Unit Testing

The software units in a system are modules and routines that are assembled and integrated to perform a specific function. Unit testing focuses first on modules, independently of one another, to locate errors. This enables, to detect errors in coding and logic that are contained within each module. This testing includes entering data and ascertaining if the value matches to the type and size supported by java. The various controls are tested to ensure that each performs its action as required.

6.2 Integration Testing

Data can be lost across any interface, one module can have an adverse effect on another, sub functions when combined, may not produce the desired major functions. Integration testing is a systematic testing to discover errors associated within the interface. The objective is to take unit tested modules and build a program structure. All the modules are combined and tested as a whole. Here the Server module and Client module options are integrated and tested. This testing provides the assurance that the application is well integrated functional unit with smooth transition of data.

6.3 User Acceptance Testing

User acceptance of a system is the key factor for the success of any system. The system under consideration is tested for user acceptance by constantly keeping in touch with the system users at time of developing and making changes whenever required.

7. IMPLEMENTATION
Implementation is the stage in the project where the theoretical design is turned into a working system and is giving confidence on the new system for the users that it will work efficiently and effectively. It involves careful planning, investigation of the current system and its constraints on implementation, design of methods to achieve the change over, an evaluation of change over methods. Apart from planning major task of preparing the implementation are education and training of users. The implementation process begins with preparing a plan for the implementation of the system. According to this plan, the activities are to be carried out, discussions made regarding the equipment and resources and the additional equipment has to be acquired to implement the new system. In network backup system no additional resources are needed. Implementation is the final and the most important phase. The most critical stage in achieving a successful new system is giving the users confidence that the new system will work and be effective. The system can be implemented only after thorough testing is done and if it is found to be working according to the specification. This method also offers the greatest security since the old system can take over if the errors are found or inability to handle certain type of transactions while using the new system.

7.1 User Training

After the system is implemented successfully, training of the user is one of the most important subtasks of the developer. For this purpose user manuals are prepared and handled over to the user to operate the developed system. Thus the users are trained to operate the developed system. Both the hardware and software securities are made to run the developed systems successfully in future. In order to put new application system into use, the following activities were taken care of:

 Preparation of user and system documentation . Conducting user training with demo and hands on Test run for some period to ensure smooth switching over the system

The users are trained to use the newly developed functions. User manuals describing the procedures for using the functions listed on menu are circulated to all the users. It is confirmed that the system is implemented up to users need and expectations.

7.2 Security and Maintenance

Maintenance involves the software industry captive, typing up system resources .It means restoring something to its original condition. Maintenance follows conversion to the extend that changes are necessary to maintain satisfactory operations relative to changes in the users environment. Maintenance often includes minor enhancements or corrections to problems that surface in the systems operation. Maintenance is also done based on fixing the problems reported, changing the interface with other software or hardware enhancing the software.Any system developed should be secured and protected against possible hazards. Security measures are provided to prevent unauthorized access of the database at various levels. An uninterrupted power supply should be so that the power failure or voltage fluctuations will not erase the data in the files. Password protection and simple procedures to prevent the unauthorized access are provided to the users .The system allows the user to enter the system only through proper user name and password.

1.LOGIN
FIELD NAME DATA TYPE

Username

Varchar

Password

Varchar

2.STUDENTDETAILS
FIELD NAME id name Pname address age dob lname lrelation ladderss occupation doj Resno Mobno sem branch batch Roomno status DATA TYPE Int Varchar Varchar Varchar Int Date time Varchar Varchar Varchar Varchar Date time Int Int Varchar Varchar Int Int Varchar

3.ROOMDETAILS
FIELD NAME id roomno Noofstudent Vacancy Roomrent DATA TYPE Int Iny Int Int Int

4.MESSDETAILS
FIELD NAME DATA TYPE

id

Int

food

Varchar

vegrate

Int

Nonvagrate

Int

Amount

Int

5.ATTENDENCE DETAILS
FIELD NAME id name thumb DATA TYPE Int Varchar Int

6.VOCATE
FIELD NAME id name branch sem batch roomno status DATA TYPE Int Varchar Varchar Varchar Decimal Int Varchar

7.ACCOUNT DETAILS
FIELD NAME Id Cautionfee Registerfee Room rent Mess bill Fine Totalfee Refund Paid or not paid DATA TYPE Int Decimal Decimal Decimal Decimal Decimal Decimal Decimal Varchar

Level 0

LOGIN
USER HOSTEL MANAGEMENT

DETAILS

Level 1

USER

USER ID/PASSWO RD

LOGIN

VERIFY

LOGIN

Level 2