D.A.V.

Public School, Dudhichua

Projec t Repor t On :

Hospit al Manag ement System

Name : Pankaj Kumar Shah

Roll No. : 31

Subjec t : Comp uter Science (083)

Class : 12 (A}

Projec t Guide : Mr. Rajesh Mishra

 Certificate

This is to certify that Cadet : Pankaj Kumar Shah

Roll No. - ....... Has successfully Completed the project

work entitled hospital management system in the

subject computer science (083) laid down in the

regulation of C.B.S.E. for the purpose of practical

examination in class XII to be held in D.A.V. Public

School Dudhichua on ........ .
 TAB LE OF CO NTE NT§ J[_T O C J

I SER DES CRI PT ION ! IP.i\ 'G E INO

j \ I
I .,

'\ .
\. -\C t,NO \ \ '._E:'GE~•iE \!T I 04
'
I
I
0: INT ROD UCT ION 'OS

OBJ ECT!\ ES OF T HE PRO JEC T :1

-o0·"' -OS I

11

04 PRO POS ED SYS TEl \ l

06

'
I
05 SYS TEf vl DEV ELO Pl\l ENT LIFE C't CLE ~SD L C)
07

06 PHA SES OF SYS TEM DEV ELO PM ENT LIFE CYC

LE 08

07 FLO W CHA RT
15
 /\CKNOWLEDGEMENT

Apa, I from the c.fforts of me, tile succer.s of ~nv proiect depends laroely on
th'"• cnoouragcmcnl and gu1del11ws or many others. I t.ike lhl', opportunity lo e.'press
-,, r atrtud~ to 1110 people who have been instrument;:il in :he successful completron
ol a,I~ ProJect.

I e>.:pr~s deej) sense of gratrtude to almighty God for gIvIng me strength for
the· success~u l completion of the project.

I express my heartfelt gratitude to my parents for constant encourag ement

while ca, rymg out lhis project.

I g1atefully acknov.ledge the contribution of lhe individuals who contributed in

bringing this project up to this level, who con tinues to look after me despite my fiaws,

I exp1ess my deep sense of gratitude to the luminary The Pnnc1pal, D.AV

Public School , Dudhichua who has been continuously motivating and extending their
help111g nand 10 us.

I exp1c.">ss ITI}' sincere \hanks lo the academician The Vice Principal DAV
Pub 1c School , Duchichua for constant 1?ncouragemenl and the guidance provided
cur ng this pro;ect

I em O\ Pf,,,,, el med to expres~ my thanks to The Administmt,vt• OtrllE'I tor

pi ov,1fo 19 rntJ an nf, a~truc1ur e anu moral ~uppon while cm ryIn~1 out thi~ pI0Ject In the
school

I.~,, t nr,..;r , 11:lanl 5 to Mr. l{.iJu!,h M1•,l11 n Nl.i'ilt•1 II I r h.11 ~Jf'. A ~1u1cle,
l.,,rento1 all ti 1? auo .,. a f11111d, •:,t1 r1 un1cc1lly ,ovmwfHI r11y pr OJ('l t (1ml helped in
solv11,g each and w.i,.,>' prnl>lorn , occ,u11, ti dLJ1111u I111pl, r11 0 11lnt10 11 uf tile plOJt'cl

4
 The guidance and support rcce1vod from ::ill th,; tnr:rnb,:r•, 11h11 'hrll.li, J♦'; ';
and who are contributing lo this project, wa':, vital for th<: 'AJ<,<.V/, <A tl11; r,r',)':'A I :; ' f
grateful for their constant support and help.

PROJECT ON CYBER CAFE MANAGEMENT SYSTEM

INTRODUCTION

The cyber cafe management system is developed with 8 v1r; 11 rA r,r,, ,,,; r ') :;:

better experience for customers in modern cyber cafes. It cln,ar•,, 1h r: d'J'J~,t,, ,,f 11 r;

customers and helps the owner of the cyber cafe in maintaining a ':.'Jlid r<:</,rd r;f 1r,1:

customers and ensuring the paying of bills. It also helps in providing for:,Jb~r,r•, r,f

our cyber cafe. This is a project which helps us to understand thr:: 1rnr/Jrt;jnr,r: ,Jf

computers in our daily life because without them there would have br;r:n nrJ ',Jt,<:r

cafes.

OBJECTIVES OF THE PROJECT

The objective of this project is to let the students apply the prCl]r:3rr-rr r 'J

knowledge into a real- world situation/problem and expo5ed the cturfonl', hr, :1

programming skills helps in developing a good software.

1. Write programs utilizing modern software tools.

2. Apply object oriented programming principles effectively when de 1ebping

small to medium sized projects.

3. Write effective procedural code to solve small lo medium sized problems.

4. Students will demonslrato a breadth of knowledge in computer sc..ienw, as

exemplified in the areas of systems, theory and software development.

5
 ~ Stuli,'nb will cll'111onst1t1lo ah1lily to conducl H research or :1prhcd Computer

Sr1enrL' p10Ject. 1cqu111119 w, 1lrng and p1cscnlat1on skills which exempltfy

scholarly style in compute, science .

PROPOSED SYSTEM

Today one cannot afford lo rely on the fallible human beings of be really wants

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 with a much sophisticated hard disk of the

computer.

One has to use the data management software. Software has been an 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 tho organization can be obtained by clicking the

button. Moroover, now it's nn ngc of computers of and aulomc1ting such an

organization gives the bollor look.

6
 SYS TEM DEV ELO PME NT LIFE CYC LE {SDL C)

1 Pla nni ng ~
r------
_ n_ a_ly_·s_•_·s_, ~
._A / Des ign I
U Imp lem ent atio n
n
I Sup por t I
I

-~~-=--=--=== (Co11!-i~lcd o f thre e it<!rution..i: on

D10~ r cnl hnrclw on.• plntfo rnu•)

mana geme nt techn ique that

The syste ms deve lopm ent fife cycle is a proje ct
ged segm ents or phas es.
divid es comp lex proje cts into smal ler, more easil y mana
the succe ssful completion of proje ct
Segm entin g proJects allow s mana gers to verify
nt phas es.
phas es befor e alloc ating resou rces to subs eque
initiation, plann ing, desig n,
Softw are deve lopm ent proje cts typic ally inclu de
tenan ce phas es. Howe ver, the
di; 1eloprnent. testin g, imple ment ation , and main
the organ izatio n invol ved.
phas e~ rnay be d1v1ded differ ently depe nding on
be dcsig nnted os reque st,
For f;/arn plc, 1nrt1al proJcct activ ities migh t
or 1nrtic1t1on, c:onccpt deve lopm ent,
requ1rnrnr;nt~-de;f,r11t1on, and plnnn rng phns cs,
rn uncJor tlcvc loprn ent shou ld be
and planr nng plm•, ,:f,. I nd u•,or•, of tliu r.ysto

7
involved in rcvtC'Wlllfl tlH' output of <';1r.l1 phnso lo 1111•,1111• tho ~,y•,torn i•, brJrng built to
dC'h\'l'I thl' needed functio11.1hly

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:

• Identify and validate an opportunity to improve business accomplishments of

the organization or a deficiency related to a business need.
• Identify significant assumptions and constraints on solutions to that need.

• 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?
• 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 andthe relationship to the Agency/Organization.

• 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 arc effectively implemented into an organization's
enterprise architecture. The initiation phase begins when an opportunity to add,

8
improve, or correct a system is 1dcntif1ed and formally requc:;ted through the

presentation of a business case The business case should, al 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 many informational, functional,
and network requirements as possible.

SYSTEM CONCEPT 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:

• Determine the feasibility and appropriateness of the alternatives.

• Identify system interfaces.

• Identify basic functional and data requirements to satisfy the business need.

• Establish system boundaries; identify goals, objectives, critical success

factors, and performance measures.

• Evaluate costs and benefits of alternative approaches to satisfy the basic

functional requirements

• Assess project risks

• Identify and initiate risk mitigation actions, andDevelop 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.

• It may include several trade-off decisions such as the decision lo 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
 • Const, uct1011 of executable prototypes Is encouraged to evaluate technolr,g/
to surport the busmC'5S process The System Boundary Documont 5/JNes m;
an important reference document to support the Information Technology
Project Request (ITPR) p1ocess.
• The ITPR must be approved by the State CIO before the pro;ect can move
fomard.

PICTORIAL REPRESENTATION OF SDLC:

PLANNING PHASE

The planning phase is the most critical step in completing development,

acqu1&1t1on, and maintenance projects. Cmoful planning, port1cuk11 ly in the eJrly
~\ages of a project, lfi necessary to coordinnte octivilios nnd mnnage project risks
r.:ffr:c.t,vely f ho depth nnd for111nllty of pr ojocl plnns ~houlcl bP commonsrnate with
thC: cha,ach:11I•,tIc,b and rt&k& of fl g1von p1 ojm:t P1ojoct pkrns reline the information

10
 g..1lhcrcd du11ng the initiation phase by further identifying the specific activities and
resources required lo complete a project.

A critical part of a project manager' sjob 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 terms of data, system performance,
security, and maintainability requirements for the system. The requirements are
defined in this phase to alevel 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 a re captured in the Test and Evaluation MasterPlan.

The purposes of this phase are to:

• Further define and refine the functional and data requirements and document
them in the Requirements Document,
• 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 docs the information go, and who
processes it),

11
 • Develop detailed data and process models (system inputs, outputs, and the
process.

• 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

nehvork requirements identified during the initiation and planning phases into unified
design specifications that developers use to scriptprograms during the development
phase. Program designs are c onstructed in various ways. Using a top-down
approach, designers first identify and link majorprogram 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 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:

, Identifying potential risks and defining mitigating design features.

• Performing a security risk assessment.

• Developing a conversion plan to migrate current data to the new system.

, Determining the operating environment.

• Defining major subsystems and their Inputs and outputs.

• Allocating processes to resources.

12
I

• Preparing deta iled logic specifications

for each software module. The result
is
a draf t System Design Documen t whic
h captures the preliminary design for
the system.

• Everything requiring use r input or app

roval is documented and reviewed by
the use r. Onc e these documents hav
e been approved by the Agency CIO and
Business Spo nso r, the final System Des
ign Document is created to serve as
the Critical/Detailed Design for the syst
em.
• This document receives a rigorous revie
w byAgency technical and functional
representatives to ensure that it
satisfies the business requirements
.
Concurrent with the development of
the system design, the Agency Project
Manage r begins development of the
Implementation Plan, Operations and
Maintenance Manual, and the Training
Plan .

DEVELOPMENT PHASE

The development phase involves conv

erting design specifications into
executable programs. Effective developm
ent standards include requirements that
programmers and other project participa
nts discuss design specifications befo
re
programming begins. The procedur
es help ensure programmers clea
rly
understand program designs and func
tional requirements . Programmers use
various techniques to develop compute
r programs. The large transaction orien
ted
programs associated with financial insti
tutions have traditionally been develope
d
using procedural programming techniqu
es. Procedural programming involves the
line- by-line scripting of logical instr
uctions that are combined to form
a
program .Effective completion of the prev
ious stages is a key factor in the success
of the Development phase. The Develop
ment phase consists of:

• Translating the detailed requirements and

design into system components.
• Testing individual elements (units) for usab
ility.
• Preparing for integration and testing of
the IT system.

13
INTEGRATION AND TEST PHASE

rity, and use r acceptance testing is

• Subsystem integration, system, secu
test phase. The use r, with those
conducted during the integration and
ates that the functional requirements,
responsible for quality assu rance, valid
ents document, are satisfied by the
as defined in the functional requirem
urity staff assess the system security
developed or modified system. OIT Sec
and accreditation prio r to
and issue a security certification

installation/implementation .

including:
Mul liple leve ls of test ing are performed,

contract or and possibly supported

• Testing at the development facility by the
by end users

users working together with contract

• Testing as a deployed system with end
personne l

e performing all functions .

• Operational testing by the end user alon
ng.a final Independent Verification &
Requirements are traced throughout testi
all documentation is reviewedand
Validation evaluatio n is performed and
em.
accepted prior to acceptance of the syst

IMPLEMENTATION PHASE

has been tested and accepted by the

This phase is initiated after tlie system
ness
insta lled to support the intended busi
user. In this phase, the system is
blished
pared to performance objectives esta
functions. Sys tem performance is com
ing,
on includes user notification, user train
during the planning phase. Impleme ntati
and
software onto production computers,
installation of hardware, installation of
the
processes. This phnse con tinues until
integration of tho system Into daily work
.
rdance with tho defined userrequirements
system is operating In production in acco

14
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 id,entified, the system may re enter the planning phase.

The purpose of this phase is to:

• Operate, maintain, and enhance the system.

• Certify that the system can process sensitive information.
• 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.

FLOWCHART

I PVTHON-MYSQL CONNECTING

i--
SOFTVvARE LOGIN WITH USERNAME&PASSWORD

ASl<S USER TO ENTER HIS CHO!CE

il

V
YOUR NEED WILL BE FULFILLED PVTHO~ BY

INTERACTING WITH IViYSQL

·.e register'ng-s~ored ·n datab ase

ge~fi g informatiori-get &rori da:abase

AGAIN FIRST PAGE WILL BE OPENED TO FULFILL THE

NEED OF USER
' -