INDEX

S.NO DESCRIPTION PAGE NO

1 CERTIFICATE 3

2 ACKNOWLEDGEMENT 4

3 INTRODUCTION 5

4 OBJECTIVES 6

5 PROPOSED SYSTEM 7
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
6 8
PHASES OF SYSTEM DEVELOPMENT LIFE
7 CYCLE 9-15

8 FLOW CHART 16
SOURCE CODE
9 17 - 19

10 OUTPUT 20 - 21

11 TESTING 22 – 23

HARDWARE AND SOFTWARE

12 24
REQUIREMENTS

13 BIBLIOGRAPHY 25

2|Page
 CERTIFICATE

This is to certify that Cadet ____________ CBSE Roll No: ________

has successfully completed the project Work entitled Project Report
on Hostel Management System in the subject Computer Science (083)
laid down in the regulations of CBSE for the purpose of Practical
Examination in Class XII to be held in Narayana School on______.

( )
PRINCIPAL

( )
Lecturer, CS

Signature of External Examiner

Name: _________

Examiner Number: _____

3|Page
 ACKNOWLEDGEMENT
Apart from the efforts of me, the success of any project depends
largely on the encouragement and guidelines of many others. I take
this opportunity to express my gratitude to the people who have been
instrumental in the successful completion of this project.
I express deep sense of gratitude to almighty God for giving me
strength for the successful completion of the project.
I express my heartfelt gratitude to my parents for constant
encouragement while carrying out this project.
I gratefully acknowledge the contribution of the individuals who
contributed in bringing this project up to this level, who continues to
look after me despite my flaws,
I express my deep sense of gratitude to the luminary The Principal,
___________________ Narayana Schools, Newtown who has been
continuously motivating and extending their helping hand to us.
I express my sincere thanks to the academician The Dean, Narayana
Schools, Newtown, for constant encouragement and the guidance
provided during this project
I am overwhelmed to express my thanks to The Administrative
Officer for providing me an infrastructure and moral support while
carrying out this project in the school.
My sincere thanks to______________, Master In-charge, A guide,
Mentor all the above a friend, who critically reviewed my project and
helped in solving each and every problem, occurred during
implementation of the project
The guidance and support received from all the members who
contributed and who are contributing to this project, was vital for the
success of the project. I am grateful for their constant support and
help.

4|Page
5|Page
HOSTEL MANAGEMENT

INTRODUCTION
In our current era of automated systems with it being either software
or hardware, it’s not advisable to be using manual system. Hostels
without a management system are usually done manually.
Registration forms verification to other data saving processes are
done manually and most at times, they are written on paper. Thus, a
lot of repetitions can be avoided with an automated system. The
drawbacks of existing systems lead to the design of a computerised
system that will help reduce a lot of manual inputs. With this system
in place, we can improve the efficiency of the system, thus overcome
the drawbacks of the existing manual system.
This system is designed in favour 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 those ones who had left
the hostel years before. This system gives an idea about how a
student and fee details, room allocation, mess expenditure is
maintained in a better way. The hostel management system will also
contain special features like how many students are in a room,
student’s id and free rooms or space available. The administration
has a unique identity for each member as well as students details.
This information can be stored in the data and can be verified
whenever we want. This computer programme can be used for hostels
schools etc.

6|Page
OBJECTIVES
The main objective of the Hostel Management System is to manage
the details. of Rent, Allottees, Hostel, Rooms, Payments. It manages
all the information about t Rent. Beds, Payments, Rent. The project is
totally built at administrative end and thus only the administrator is
guaranteed the access. The purpose of the project is to build an
application program to reduce the manual work for managing the
Rent, Allottees, Beds, Hostel. It tracks all the details about the Hostel,
Rooms, Payments.
1. Provides the searching facilities based on various factors. Such
as Rent, Hostel, Rooms, Payments.
2. College Management System also sells the employees details
online for students details, employees details, courses.
3. College Management System also sells the employees details
online for students details, employees details, courses.
4. Provide the functionality to make your own bookings
5. Update your web site without the need to get a web designer
involved.
6. It tracks all the information of Allottees, Beds, Rooms etc
7. Manage the information of Allottees.
8. Shows the information and description of the Rent, Hostel
9. To increase efficiency of managing the Rent, Allottees.
10. It deals with monitoring the information and transactions
of Rooms.
11. Manage the information of Rent.

7|Page
PROPOSED SYSTEM
Today one cannot afford to rely on the fallible human beings who
really want to stand against today’s merciless competition where not
to wise saying “to err is human” no longer valid, it’s outdated to
rationalize your mistake. So, to keep pace with time, to bring about
the best result without malfunctioning and greater efficiency so to
replace the unending heaps of flies without malfunctioning and
greater efficiency so to replace the unending heaps of flies with a
much-sophisticated hard disk of the computer.
One has to use the data management software. Software has been as
ascent in atomization various organisations. Many software products
working are now in markets which have helped in making the
organizations work easier and efficiently. Data management initially
had to maintain a lot of ledgers and a lot of paper work has to be done
but now software product on this organization has made their work
faster and easier. Now only this software has to be loaded on the
computer and work can be done.
This prevents a lot of time and money. The work becomes fully
automated and any information regarding the organization can be
obtained by clicking the button. Moreover, now its an age of
computers and automating such an organization gives the better look.

8|Page
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development life cycle is a project management

technique that divides complex projects into smaller, more easily
managed segments or phases. Segmenting projects allows managers
to verify the successful completion of project phases before allocating
resources to subsequent phases.
Software development projects typically include initiation, planning,
design, development, testing, implementation, and maintenance
phases. However, the phases may be divided differently depending on
the organization involved.
For example, initial project activities might be designated as request,
requirements-definition, and planning phases, or initiation, concept-
development, and planning phases. End users of the system under
development should be involved in reviewing the output of each
phase to ensure the system is being built to deliver the needed
functionality.

9|Page
PHASES OF SYSTEM DEVELOPMENT LIFE
CYCLE
INITIATION PHASE
The Initiation Phase begins when a business sponsor identifies a need
or an opportunity.
The purpose of the Initiation Phase is to:
1. Identify and validate an opportunity to improve business
accomplishments of the organization or a deficiency related to a
business need.
2. Identify significant assumptions and constraints on solutions to
that need.
3. Recommend the exploration of alternative concepts and
methods to satisfy the need including questioning the need for
technology, i.e., will a change in the business process offer a
solution?
4. Assure executive business and executive technical sponsorship.
The Sponsor designates a Project Manager and the business
need is documented in a Concept Proposal. The Concept
Proposal includes information about the business process and
the relationship to the Agency/Organization.
5. Infrastructure and the Strategic Plan. A successful Concept
Proposal results in a Project Management Charter which
outlines the authority of the project manager to begin the
project.
Careful oversight is required to ensure projects support strategic
business objectives and resources are effectively implemented into an
organization's enterprise architecture. The initiation phase begins
when an opportunity to add, improve, or correct a system is identified
and formally requested through the presentation of a business case.
The business case should, at a minimum, describe a proposal’s
purpose, identify expected benefits, and explain how the proposed
system supports one of the organization’s business strategies. The
business case should also identify alternative solutions and detail as

10 | P a g e
many informational, functional, and network requirements as
possible.

11 | P a g e
SYSTEM COMCEPT DEVELOPMENT PHASE
The System Concept Development Phase begins after a business need
or opportunity is validated by the Agency/Organization Program
Leadership and the Agency/Organization CIO.
The purpose of the System Concept Development Phase is to:
1. Determine the feasibility and appropriateness of the alternatives.
2. Identify system interfaces.
3. Identify basic functional and data requirements to satisfy the
business need.
4. Establish system boundaries; identify goals, objectives, critical
success factors, and performance measures.
5. Evaluate costs and benefits of alternative approaches to satisfy
the basic functional requirements
6. Assess project risks
7. Identify and initiate risk mitigation actions, and develop high-
level technical architecture, process models, data models, and a
concept of operations. This phase explores potential technical
solutions within the context of the business need.
8. It may include several trade-off decisions such as the decision to
use COTS software products as opposed to developing custom
software or reusing software components, or the decision to use
an incremental delivery versus a complete, onetime deployment.
9. Construction of executable prototypes is encouraged to evaluate
technology to support the business process. The System
Boundary Document serves as an important reference document
to support the Information Technology Project Request (ITPR)
process.
10. The ITPR must be approved by the State CIO before the
project can move forward.
PICTORIAL REPRESENTATION OF SDLC

12 | P a g e
 PLANNING PHASE
The planning phase is the most critical step in completing
development, acquisition, and maintenance projects. Careful
planning, particularly in the early stages of a project, is necessary to
coordinate activities and manage project risks effectively. The depth
and formality of project plans should be commensurate with the
characteristics and risks of a given project. Project plans refine the
information gathered during the initiation phase by further identifying
the specific activities and resources required to complete a project.
A critical part of a project manager’ job is to coordinate discussions
between user, audit, security, design, development, and network
personnel to identify and document as many functional, security, and
network requirements as possible. During this phase, a plan is
developed that documents the approach to be used and includes a
discussion of methods, tools, tasks, resources, project schedules, and
user input. Personnel assignments, costs, project schedule, and target
dates are established.
A Project Management Plan is created with components related to
acquisition planning, configuration management planning, quality
assurance planning, concept of operations, system security,
verification and validation, and systems engineering management
planning.

REQUIREMENTS ANALYSIS PHASE

This phase formally defines the detailed functional user requirements
using high-level requirements identified in the Initiation, System
Concept, and Planning phases. It also delineates the requirements in

13 | P a g e
terms of data, system performance, security, and maintainability
requirements for the system. The requirements are defined in this
phase to a level of detail sufficient for systems design to proceed.
They need to be measurable, testable, and relate to the business need
or opportunity identified in the Initiation Phase. The requirements that
will be used to determine acceptance of the system are captured in the
Test and Evaluation Masterplan.
The purposes of this phase are to:
1. Further define and refine the functional and data requirements
and document them in the Requirements Document.
2. Complete business process reengineering of the functions to be
supported (i.e., verify what information drives the business
process, what information is generated, who generates it, where
does the information go, and who processes it).
3. Develop detailed data and process models (system inputs,
outputs, and the process.
4. Develop the test and evaluation requirements that will be used
to determine acceptable system performance.

DESIGN PHASE
The design phase involves converting the informational, functional,
and network requirements identified during the initiation and planning
phases into unified design specifications that developers use to script
programs during the development phase. Program designs are
constructed in various ways. Using a top-down approach, designers
first identify and link major program components and interfaces, then
expand design layouts as they identify and link smaller subsystems
and connections. Using a bottom-up approach, designers first identify
and link minor program components and interfaces, then expand
design layouts as they identify and link larger systems and
connections. Contemporary design techniques often use prototyping
tools that build mock-up designs of items such as application screens,
database layouts, and system architectures. End users, designers,
developers, database managers, and network administrators should
review and refine the prototyped designs in an iterative process until
they agree on an acceptable design. Audit, security, and quality

14 | P a g e
assurance personnel should be involved in the review and approval
process. During this phase, the system is designed to satisfy the
functional requirements identified in the previous phase. Since
problems in the design phase could be very expensive to solve in the
later stage of the software development, a variety of elements are
considered in the design to mitigate risk.
These include:
1. Identifying potential risks and defining mitigating design
features.
2. Performing a security risk assessment.
3. Developing a conversion plan to migrate current data to the new
system.
4. Determining the operating environment.
5. Defining major subsystems and their inputs and outputs.
6. Allocating processes to resources.
7. Preparing detailed logic specifications for each software
module. The result is a draft System Design Document which
captures the preliminary design for the system.
8. Everything requiring user input or approval is documented and
reviewed by the user. Once these documents have been
approved by the Agency CIO and Business Sponsor, the final
System Design Document is created to serve as the
Critical/Detailed Design for the system.
9. This document receives a rigorous review by Agency technical
and functional representatives to ensure that it satisfies the
business requirements. Concurrent with the development of the
system design, the Agency Project Manager begins development
of the Implementation Plan, Operations and Maintenance
Manual, and the Training Plan.

DEVELOPMENT PHASE
The development phase involves converting design specifications into
executable programs. Effective development standards include
requirements that programmers and other project participants discuss
design specifications before programming begins. The procedures
15 | P a g e
help ensure programmers clearly understand program designs and
functional requirements. Programmers use various techniques to
develop computer programs. The large transaction-oriented programs
associated with financial institutions have traditionally been
developed using procedural programming techniques. Procedural
programming involves the line-by-line scripting of logical instructions
that are combined to form a program. Effective completion of the
previous stages is a key factor in the success of the Development
phase. The Development phase consists of:
1. Translating the detailed requirements and design into system
components.
2. Testing individual elements (units) for usability.
3. Preparing for integration and testing of the IT system.

INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance testing is
conducted during the integration and test phase. The user, with those
responsible for quality assurance, validates that the functional
requirements, as defined in the functional requirements document, are
satisfied by the developed or modified system. OIT Security staff
assess the system security and issue a security certification and
accreditation prior to installation/implementation.

Multiple levels of testing are performed, including:

 Testing at the development facility by the contractor and
possibly supported by end users
 Testing as a deployed system with end users working together
with contract personnel

Operational testing by the end user alone performing all functions.

Requirements are traced throughout testing; a final Independent
Verification & Validation evaluation is performed and all
documentation is reviewed and accepted prior to acceptance of the
system.

16 | P a g e
 IMPLEMENTATION PHASE
This phase is initiated after the system has been tested and accepted
by the user. In this phase, the system is installed to support the
intended business functions. System performance is compared to
performance objectives established during the planning phase.
Implementation includes user notification, user training, installation
of hardware, installation of software onto production computers, and
integration of the system into daily work processes. This phase
continues until the system is operating in production in accordance
with the defined user requirements.

OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for
continued performance in accordance with user requirements and
needed system modifications are incorporated. Operations continue as
long as the system can be effectively adapted to respond to the
organization’s needs. When modifications or changes are identified,
the system may re-enter the planning phase.
The purpose of this phase is to:
1. Operate, maintain, and enhance the system.
2. Certify that the system can process sensitive information.
3. Conduct periodic assessments of the system to ensure the
functional requirements continue to be satisfied.
Determine when the system needs to be modernized, replaced, or
retired.

FLOW CHART

17 | P a g e
18 | P a g e
SOURCE CODE
import mysql.connector as sql
conn=sql.connect(host='localhost', user='root', passwd='admin@123',
database='hostel_management')
conn.autocommit=True
if conn.is_connected():
print ('connected successfully')
else:
print ('not connected')
c1=conn.cursor()
#c1.execute("create table hostel_management(roll_no int primary key,
name varchar(20), address varchar(100), room_no int, dept
varchar(15), fees int, bal int)
print(" WELCOME TO HOSTEL MANAGEMENT ")
print(" 1.ADMISSION FORM")
print(" 2.FEE CHECKING")
print(" 3.MODIFY DATA")
print(" 4.EXIT")
choice=int(input('ENTER YOUR CHOICE'))
if choice==1:
v_roll=input("ENTER YOUR ROLL NUMBER")
v_name=input("ENTER YOUR NAME")
v_add=input("ENTER YOUR ADDRESS")
v_room_no=input("ENTER YOUR ROOM NUMBER")
v_dept=input("ENTER YOUR DEPARTMENT")
v_fees=input("ENTER YOUR FEES")
v_bal=input("ENTER YOUR BALANCE")

19 | P a g e
 abc=("insert into hostel_management values ("+v_roll+",
'"+v_name+"', '"+v_add+"', "+v_room_no+", '"+v_dept+" ',
"+v_fees+", "+v_bal+")")
print(abc)
c1.execute(abc)
conn.commit()
elif choice==3:
roll_no=int(input("enter your roll number"))
mysql="select * from hostel_management where roll_no
=’{}’” .format (roll_no)
c1.execute(mysql)
data = c1.fetchall()
print("roll_no:",data[0][0])
print("name:",data[0][1])
print("address:",data[0][2])
print("room_no:",data[0][3])
print("dept:",data[0][4])
print("fees:",data[0][5])
print("bal:",data[0][6])
elif choice==2:
print("AVAILABLE DEPARTMENTS AS FOLLOWS")
print("1.COMPUTER")
print("2.BIO")
print("3.TECH")
print("4.PHYSICS")
print("5.ECO")
print("6.ENG")
department=input("ENTER YOUR DEPARTMENT")
mysql="select*from fees where department ='{}'.format
(department)
c1.execute(mysql)
data=c1.fetchall()
print("your fees is:", data[0][1])

20 | P a g e
else:
print("QUITTING!!!!!!!!!")

21 | P a g e
OUTPUT

22 | P a g e
23 | P a g e
TESTING
Software Testing is an empirical investigation conducted to provide
stakeholders with information about the quality of the product or
service under test [1], with respect to the context in which it is
intended to operate. Software Testing also provides an objective,
independent view of the software to allow the business to appreciate
and understand the risks at implementation of the software. Test
techniques include, but are not limited to, the process of executing a
program or application with the intent of finding software bugs.
It can also be stated as the process of validating and verifying that a
software program/application/product meets the business and
technical requirements that guided its design and development, so that
it works as expected and can be implemented with the same
characteristics. Software Testing, depending on the testing method
employed, can be implemented at any time in the development
process, however the most test effort is employed after the
requirements have been defined and coding process has been
completed.
TESTING METHODS
Software testing methods are traditionally divided into black box
testing and white box testing. These two approaches are used to
describe the point of view that a test engineer takes when designing
test cases.
BLACK BOX TESTING
Black box testing treats the software as a "black box," without any
knowledge of internal implementation. Black box testing methods
include: equivalence partitioning, boundary value analysis, all-pairs
testing, fuzz testing, model-based testing, traceability matrix,
exploratory testing and specification-based testing.
SPECIFICATION-BASED TESTING
Specification-based testing aims to test the functionality of software
according to the applicable requirements.[16] Thus, the tester inputs
24 | P a g e
data into, and only sees the output from, the test object. This level of
testing usually requires thorough test cases to be provided to the
tester, who then can simply verify that for a given input, the output
value (or behaviour), either "is" or "is not" the same as the expected
value specified in the test case. Specification-based testing is
necessary, but it is insufficient to guard against certain risks.
WHITE BOX TESTING
White box testing, by contrast to black box testing, is when the tester
has access to the internal data structures and algorithms (and the code
that implement these).
Types of white box testing-
The following types of white box testing exist:
1. api testing - Testing of the application using Public and Private
APIs.
2. Code coverage - creating tests to satisfy some criteria of code
coverage. For example, the test designer can create tests to cause
all statements in the program to be executed at least once.
3. fault injection methods.
4. mutation testing methods.
5. static testing - White box testing includes all static testing.

25 | P a g e
HARDWARE AND SOFTWARE REQUIREMENTS
 Operating System: WINDOWS 7 AND ABOVE
 Processor: PENTIUM (ANY) OR
AMDATHALON(3800+- 4200+ DUALCORE)
 Motherboard: 1.845 OR 915,995 FOR PENTIUM 0R
MSI K9MM-V VIAK8M800+8237R PLUS CHIPSET FOR
AMD ATHALON
 RAM: 512MB+
 Hard disk: SATA 40 GB OR ABOVE
 CD/DVD r/w multi drive combo: (If back up required)
 FLOPPY DRIVE 1.44 MB: (If Backup required)
 MONITOR 14.1 or 15 -17 inch
 Key board and mouse
 Printer : (if print is required – [Hard copy])
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python

26 | P a g e
BIBLIOGRAPHY
1. Computer science With Python - Class XII By : SumitaArora
2. A Project Report on Blood Bank Management System (BBMS)
By: Praveen M Jigajinni
3. Website: https://www.w3resource.com

27 | P a g e