PROJECT REPORT

HOSTEL MANAGEMENT SYSTEM

The Minor Project report submitted to

Rajiv Gandhi Proudyogiki Vishwavidyalaya, Bhopal

towards partial fulfillment of the Degree of

Bachelor of Engineering

in

Computer Science

Guided by: Submitted by:

Prof. Gourav shrivastav Mr.Ankit singh
Mr.Shubham nagar
Mr.Hemant baluni

Computer Science Engineering Department

Mahakal Institute of Technology & Management, Ujjain (M.P.)

1
 2018-19

MAHAKAL INSTITUTE OF TECHNOLOGY &

MANAGEMENT, UJJAIN

RECOMMENDATION

This is to certify that Mr.Ankit singh,Mr.Shubham nagar,Mr.Hemant baluni student of third year
B.E. (CSE) in the year 2018-19 of Computer Science Engineering Department of this institute has
completed their work on “HOSTEL MANAGEMENT SYSTEM” for Major/Minor project based on
syllabus and has submitted a satisfactory account of their work in this report which is
recommended for the partial fulfillment of the degree of Bachelor of Engineering in Computer
Science.

PROJECT GUIDE, HOD,

CSE DEPT. GOURAV SHRIVASTAV CSE DEPT. DEEPALI KELKAR

M.I.T.M. Ujjain M.I.T.M. Ujjain

2
 MAHAKAL INSTITUTE OF TECHNOLOGY &
MANAGEMENT, UJJAIN

CERTIFICATE

This is to certify that the Major/Minor Project report entitled “Hostel Management

System” submitted by Mr.Ankit Singh, Mr.Shubham Nagar, Mr.Hemant Baluni of B.E.

VI semester, Computer Science Engineering department in the year 2018-19, is a

satisfactory account of their work based on syllabus which is accepted in partial

fulfillment of degree of Bachelor of Engineering in Computer Science .

INTERNAL EXAMINER EXTERNAL EXAMINER

Date: Date:

3
 ACKNOWLEDGEMENT

It is always a pleasure to remind the great people in the MIT College for their sincere
guidance I received to uphold my practical as well as my theoretical skills.
First of all I would like to thanks to Prof. Mrs. Deepali Kelkar Mam for giving us
guidance and support.

Second, I also want to express my deepest thanks to Prof. Vaishali mam as an advisor for
a project that has helped me a lot in dealing with project. She had supported to me by
showing different method of Information collection. She helped all the time when I
needed and she gave right direction towards completion of project.

And I would like to thanks Prof.Gourav shrivastav Sir (our guide) for extending their
friendly nature towards me and as a person in charge of our project who has helped to
manage our project on HOSTEL MANAGEMENT SYSTEM.

4
 ABSTRACT
HOSTEL MANAGEMENT SYSTEM
The Existing Hostel Management System By Manual Way Is A Tadious Process Since It
Involves Workload And Time Consumption As Well As Chances Of Mismanagement Are
Greater Since It Involves Various Section Like Fees Submition, Room Allocation .

In This Project We Can Easily Manage Room Allocation , Mess Expenditure ,Hostel Details
,Room Details Also Keeping Track Of The Student Records. As It Provide Us Edge Over
Each Manual System And Also Easier To Manage And Decrease Workload And Time
Consumption.

The Different Process Involves Are

-To Maintain Hostel Mess Bills Monthly

-To Maintain Provisions
-To Maintain Room Status As Well Details
- To Maintain Student Records Individually

The technology used in this project is java as the front end back end is visualbasics.

This Project Is Made By—

Mr. Ankit Singh Sisodiya
Mr. Hemant Baluni
Mr. Shubham Nagar

5
 TABLE OF CONTENTS

CHAPTER 1.......................................................................................................................5
INTRODUCTION.............................................................................................................5
1.1 EXISTING APPLICATION......................................................................................5
1.2 PROPOSED APPLICATION....................................................................................5
1.2.1 Features Of Proposed Application.............................................................................7
1.2.2 User Requirements....................................................................................................8
1.3 FEASIBILITY ........................................................................................................8
1.3.1 Technical Feasibility………………………………………………………………..8
1.3.2 Operational Feasibility..….…………………………………………………..……..8
1.3.3 Economical Feasibility…….………………………………………………………..8

CHAPTER 2.....................................................................................................................62
SOFTWARE DEVELOPMENT LIFE CYCLE.......………………………………...20
2.1 System Development Life Cycle…………...……………………………………...20
2.1.1 Benefits of the SDLC Process.................................................................................20
2.2 Iterative Model…...…………….…………...……………………………………...20
2.2.1 Iterative Model Design............................................................................................20
2.2.2 Iterative Model Application.....................................................................................20
2.2.3 Iterative Model Pros and Cons……………………………………………………..20

CHAPTER 3....................................................................................................................20
ANALYSIS.......................................................................................................................20
3.1 REQUIREMENT ANALYSIS.................................................................................20
3.1.1 Requirement Gathering...........................................................................................20
3.1.2 Analysis of Gathered Requirement..........................................................................20
3.2 SOFTWARE REQUIREMENT SPECIFICATON...............................................21
3.2.1 Non Functional Requirements.................................................................................21
3.2.2 Functional Requirements.........................................................................................21
3.3 USE CASE ANALYSIS............................................................................................24
3.3.1 Use case Diagram .................................................................................................24
3.3.2 Use case Description...............................................................................................24
3.4 ACTIVITY DIAGRAMS.........................................................................................27

6
CHAPTER 4.....................................................................................................................30
DESIGN............................................................................................................................30
4.1 SYSTEM FLOW DIAGRAM..................................................................................30
4.1.1. Data Flow Diagrm..................................................................................................31
4.3 CLASS DIAGRAM..................................................................................................39
4.3.1 Admin......................................................................................................................39
4.3.2 User..........................................................................................................................40
4.3.3 Products...................................................................................................................43
4.3.4 Payment...................................................................................................................43
4.3.5 Cart..........................................................................................................................44
4.4 SEQUENCE DIAGRAMS.......................................................................................44

CHAPTER 5.....................................................................................................................52
IMPLEMENTATION......................................................................................................52
5.1 PLATFORM USED..................................................................................................52
5.2 IMPLEMENTATION LEVEL DETAILS..............................................................52
5.2.1 Manifest xml............................................................................................................52
5.2.2 JAVA class...............................................................................................................53
5.2.3 xml file.....................................................................................................................53
5.2 TESTING …….........................................................................................................52

CHAPTER 6.....................................................................................................................62
CONCLUSION................................................................................................................62

APPENDIX.......................................................................................................................66
SCREEN SHOT 1: SPLASHSCREEN.........................................................................66
SCREEN SHOT 2:LOGIN PAGE................................................................................67
SCREEN SHOT 3 :SIGNUP PAGE..............................................................................68
SCREEN SHOT 4 :NAVIGATION DRAWER ……………………………………..68

7
 TABLE OF FIGURES

Figures

Figure 2.2: Iterative Model.............................................................................................24

8
 CHAPTER 1
INTRODUCTION
“Hostel Management System”
Hostel Management system is the system that manages the student data, Room
data students admission process and create receipt for the fees paid by the student who
stay in the hostel and also help in maintaining visitors messages .

9
 CHAPTER-2
SOFTWARE
DEVELOPMENT LIFE
CYCLE

10
2.1 SOFTWARE DEVELOPMENT LIFE CYCLE

One of the basic notions of the software development process is SDLC models which
stand for Software Development Life Cycle models. SDLC – is a continuous
process, which starts from the moment, when it’s made a decision to launch the project,
and it ends at the moment of its full remove from the exploitation.
A software development life cycle (SDLC) model is a conceptual framework describing
all activities in a software development project from planning to maintenance. This
process is associated with several models, each including a variety of tasks and activities.

2.1.1 Benefits of SDLC Process

Software development involves the participation of people with different roles, including
business stakeholders, project managers, developers, testers, and members of the support
team. These people may be geographically distributed, there will be turnover, and there is
the relentless advance of tools and methodologies being used.

For these reasons, it is important to follow a common methodology which basically

defines who does what, when, and how. The software development lifecycle (SDLC)
serves this purpose. Consider the SDLC a script that these actors follow, but it’s a script
that they can agree to change as needed.

2.2 PROTOTYPING MODEL

2.2.1 PROTOTYPING MODEL DESIGN

Prototyping is defined as the process of developing a working replication of a product or

system that has to be engineered. It offers a small scale facsimile of the end product and
is used for obtaining customer feedback as described below:

The Prototyping Model is one of the most popularly used Software Development Life
Cycle Models (SDLC models).This model is used when the customers do not know the

11
exact project requirements beforehand. In this model, a prototype of the end product is
first developed, tested and refined as per customer feedback repeatedly till a final
acceptable prototype is achieved which forms the basis for developing the final product.

In this process model, the system is partially implemented before or during the analysis
phase thereby giving the customers an opportunity to see the product early in the life
cycle. The process starts by interviewing the customers and developing the incomplete
high-level paper model. This document is used to build the initial prototype supporting
only the basic functionality as desired by the customer. Once the customer figures out the
problems, the prototype is further refined to eliminate them. The process continues till the
user approves the prototype and finds the working model to be satisfactory.

There are 2 approaches for this model:

1. Rapid Throwaway Prototyping –

This technique offers a useful method of exploring ideas and getting customer
feedback for each of them. In this method, a developed prototype need not
necessarily be a part of the ultimately accepted prototype. Customer feedback helps
in preventing unnecessary design faults and hence, the final prototype developed is
of a better quality.

2. Evolutionary Prototyping –
In this method, the prototype developed initially is incrementally refined on the
basis of customer feedback till it finally gets accepted. In comparison to Rapid
Throwaway Prototyping, it offers a better approach which saves time as well as
effort. This is because developing a prototype from scratch for iteration of the
process can sometimes be very frustrating for the developers.

2.2.2 PROTOTYPING MODEL – APPLICATION

The prototyping model should be used when the requirements of the product are not
clearly understood or are unstable. It can also be used if requirements are changing
quickly. This model can successfully use for developing user interfaces, high technology

12
software-intensive and very good choice to demonstrate the technical feasibility of the
product. And hence it is opted for very same reason that the project needs a lot of testing
during development phase hence prototyping is best suited for game development.

Advantages –
 The customers get to see the partial product early in the life cycle. This ensures a
greater level of customer satisfaction and comfort.
 New requirements can be easily accommodated as there is scope for refinement.
 Missing functionalities can be easily figured out.
 Errors can be detected much earlier thereby saving a lot of effort and cost, besides
enhancing the quality of the software.
 The developed prototype can be reused by the developer for more complicated
projects in the future.
 Flexibility in design.
Disadvantages –
 Costly w.r.t time as well as money.
 There may be too much variation in requirements each time the prototype is
evaluated by the customer.
 Poor Documentation due to continuously changing customer requirements.
 It is very difficult for the developers to accommodate all the changes demanded
by the customer.
 There is uncertainty in determining the number of iterations that would be
required before the prototype is finally accepted by the customer.
 After seeing an early prototype, the customers sometimes demand the actual
product to be delivered soon.
 Developers in a hurry to build prototypes may end up with sub-optimal solutions.
 The customer might lose interest in the product if he/she is not satisfied with the
initial prototype.

13
 CHAPTER 3
ANALYSIS

Application analysis is the process of gathering and interpreting facts, diagnosing

problems and using the information to recommend improvements on the
application. Application analysis is a problem solving activity that requires intensive
communication between the application users and application developers.

3.1 REQUIREMENT ANALYSIS

Before starting to design a software product, it is extremely important to understand the
precise requirements of the customer and to document them properly. Improper
documented requirements increase the number of iterative changes required during the life
cycle phases. Therefore, requirement analysis and specification is considered to be a very
important phase of software development and has to be undertaken with utmost care.

Web Application development differs from Desktop Application Development in terms of

requirement analysis, since every Web Application is different completely to other and not
developed on the basis of what users’ needs but on the basis of what they will like.
Basically the whole concept of a Application may be decided by a team of developer or
individual member which users’ should considering when picking a new Web Application.
This comes from the fact that the users’ of Web Application is not decided perfectly at the
time of developing a Web application.

The requirement analysis and specification phase starts once the idea behind the Web
Application and study phase is complete and the Web Application is supposed to be
holding up in between others title in market and technically feasible.

3.1.1 Requirement Gathering.

For requirement gathering for the proposed idea “Hostel Management System” I
have used the following requirement gathering techniques technique: -

 Reviewing: - Reviewing reviews of different users on the similar type of

Application to my projects idea. By which I have acquired their basic needs
and what they expect from the kind of Web Page I am developing.

14
 Studying and Research: - Since the proposed idea for the Web Page is
derived two different genre of the Web Application.

15