finalreporthmsadiallutapn.docx

8/18/2019 FinalReportHMSAdiAlluTapn.docx

1/33

HOSPITAL MANAGEMENT SYSTEM

The Industrial Training Project report submitted to Rajiv Gandhi Proudyogiki Vishwavidyalaya, Bhopal

towards partial ul!llment o the "egree o Bachelor o #ngineering

in$omputer %cience and #ngineering

Guided by Submitted byProf. Gaurav Shrivastava Aditi Trivedi

Anand PandeyTapan Jain

Computer Science DepartmentMaha a! In"titute o# Techno!o$y % Mana$ement& '((ain)M*P*+

,-./0,-.1


2/33

MAHA2AL INSTIT'TE O3 TECHNOLOGY%MANAGEMENT& '44AIN

5ECOMMENDATION

This is to certify that Miss. Aditi Trivedi, Mr. Anand Pandey and Mr. Tapan Jain, students

of fourth year B.E., in the year 201 !1" of #o$puter Science and En%ineerin% &epart$ent

of this institute has co$p'eted their (or) on * HOSPITAL MANAGEMENT SYSTEM + for

ndustria' Trainin% pro-ect ased on sy''a us and has su $itted a satisfactory account of

their (or) in this report (hich is reco$$ended for the partia' fu'fi''$ent of the de%ree of

Bache'or of En%ineerin% in #o$puter Science.

HOD& Pro(ect Guide&

Computer Science Computer ScienceEn$ineerin$ Department En$ineerin$ DepartmentM*I*T*M* '((ain M*I*T*M* '((ain

Director&M*I*T*M* '((ain


3/33


4/33

Date7 Date7

A8ST5ACT

ur pro-ect Patient ecord Syste$ inc'udes re%istration of patients, storin% their detai' into

the syste$. ur soft(are has faci'ity to %ive a uni3ue id for every patient and stores the detai's

of every patient and the staff auto$atica''y. t inc'udes a search faci'ity to )no( the current

status of each roo$. 4ser can search avai'a i'ity of a doctor and the detai's of the patient usin%

the id.

This patient record syste$ can e entered usin% a userna$e and pass(ord. t is accessi 'e

either y an ad$inistrator or receptionist. n'y they can add data into the data ase. The data

can e retrieved easi'y. The data are (e'' protected for persona' use and $a)es the data

processin% very fast.

5eepin% trac) of a'' the activities and their records on paper is very cu$ erso$e and error

prone. t a'so is very inefficient and a ti$e!consu$in% process servin% the continuous

increase in popu'ation and nu$ er of peop'e visitin% the hospita'.

The $ain ai$ of our pro-ect is to provide a paper!'ess hospita' up to 607. t a'so ai$s at

providin% 'o(!cost re'ia 'e auto$ation of the e8istin% syste$s. The syste$ a'so provides

e8ce''ent security of data at every 'eve' of user!syste$ interaction and a'so provides ro ust

9 re'ia 'e stora%e and ac)up faci'ities.


5/33

TA8LE O3 CONTENTS&' Introduction '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

'''''''''''''''''''''''&

1.1 E8istin% Syste$................................................................................................1 1.1.1 :i$itations of E8istin% syste$;;;;;;;;;;;;;;..;;.....11.2 -ective of Proposed Syste$;;;;;;;;;;;;;;;;;;..2

2. Soft(are &eve'op$ent :ife #yc'e;;;;;;;;;;;;;.;;;;;.<2.1 S&:# Mode' used;;;;;;;;;;;;;;;;;.;;...;;....<


6/33

@. eferences;;;;;;;;;;;;;;;;;;;;;;;;.............


7/33

needs to e co$puteriDed.

.*, Ob(ecti:e" o# Propo"ed Sy"temThe $ain o -ectives of the proposed syste$ can e enu$erated as fo''o(s

• Patients are easi'y a''ocated to the doctors.

• &octorFs search is possi 'e.

• TodayFs patient 'ists he'p doctors to search their patients.

#hapter 2Soft(are deve'op$ent :ife #yc'e

The syste$s deve'op$ent 'ife cyc'e S&:#H, a'so referred to as the app'icationdeve'op$ent 'ife!cyc'e, is a ter$ used in syste$s en%ineerin%, infor$ation syste$s andsoft(are en%ineerin% to descri e a process for p'annin%, creatin%, testin%, and dep'oyin%an infor$ation syste$. The syste$s deve'op$ent 'ife!cyc'e concept app'ies to a ran%e of hard(are and soft(are confi%urations, as a syste$ can e co$posed of hard(are on'y,soft(are on'y, or a co$ ination of oth.

An iterative 'ife cyc'e $ode' does not atte$pt to start (ith a fu'' specification of re3uire$ents. nstead, deve'op$ent e%ins y specifyin% and i$p'e$entin% -ust part of thesoft(are, (hich can then e revie(ed in order to identify further re3uire$ents. This

process is then repeated, producin% a ne( version of the soft(are for each cyc'e of the$ode'.

,*. SDLC Mode! u"ed in our product;Iterati:e Mode!<

terative 'ife cyc'e $ode' does not atte$pt to start (ith a fu'' specification of re3uire$ents. nstead, deve'op$ent e%ins y specifyin% and i$p'e$entin% -ust part of thesoft(are, (hich is then revie(ed in order to identify further re3uire$ents. This process isthen repeated, producin% a ne( version of the soft(are at the end of each iteration of the$ode'.


8/33

Iterati:e Mode! de"i$n

terative process starts (ith a si$p'e i$p'e$entation of a su set of the soft(arere3uire$ents and iterative'y enhances the evo'vin% versions unti' the fu'' syste$ isi$p'e$ented. At each iteration, desi%n $odifications are $ade and ne( functiona'capa i'ities are added. The asic idea ehind this $ethod is to deve'op a syste$ throu%hrepeated cyc'es iterativeH and in s$a''er portions at a ti$e incre$enta'H.

terative and ncre$enta' deve'op$ent is a co$ ination of oth iterative desi%n or iterative $ethod and incre$enta' ui'd $ode' for deve'op$ent. &urin% soft(aredeve'op$ent, $ore than one iteration of the soft(are deve'op$ent cyc'e $ay e in

pro%ress at the sa$e ti$e. and This process $ay e descri ed as an evo'utionaryac3uisition or incre$enta' ui'd approach.

n incre$enta' $ode' the (ho'e re3uire$ent is divided into various ui'ds. &urin% eachiteration, the deve'op$ent $odu'e %oes throu%h the re3uire$ents, desi%n, i$p'e$entationand testin% phases. Each su se3uent re'ease of the $odu'e adds function to the previousre'ease. The process continues ti'' the co$p'ete syste$ is ready as per the re3uire$ent.The )ey to successfu' use of an iterative soft(are deve'op$ent 'ifecyc'e is ri%orousva'idation of re3uire$ents, and verification 9 testin% of each version of the soft(area%ainst those re3uire$ents (ithin each cyc'e of the $ode'. As the soft(are evo'vesthrou%h successive cyc'es, tests have to e repeated and e8tended to verify each version of the soft(are.

Ad:anta$e" o# Iterati:e mode!

n iterative $ode' (e can on'y create a hi%h!'eve' desi%n of the app'ication efore (eactua''y e%in to ui'd the product and define the desi%n so'ution for the entire product.:ater on (e can desi%n and ui't a s)e'eton version of that, and then evo'ved the desi%n

ased on (hat had een ui't.n iterative $ode' (e are ui'din% and i$provin% the product step y step. ence (e can

trac) the defects at ear'y sta%es. This avoids the do(n(ard f'o( of the defects.

n iterative $ode' (e can %et the re'ia 'e user feed ac). Chen presentin% s)etches and 'ueprints of the product to users for their feed ac), (e are effective'y as)in% the$ toi$a%ine ho( the product (i'' (or).

n iterative $ode' 'ess ti$e is spent on docu$entin% and $ore ti$e is %iven for desi%nin%.


9/33

Di"ad:anta$e" o# Iterati:e mode!

• Each phase of iteration is ri%id (ith no over'aps.• #ost'y syste$ architecture or desi%n issues $ay arise ecause not a'' re3uire$ents

are %athered up front for the entire 'ifecyc'e.

#hapter <Ana'ysis

=*. 5e>uirement Ana!y"i"e3uire$ents ana'ysis in syste$s en%ineerin% and soft(are en%ineerin% , enco$passes

those tas)s that %o into deter$inin% the needs or conditions to $eet for a ne( or a'tered product or pro-ect, ta)in% account of the possi 'y conf'ictin% re3uire$ents of thevarious sta)eho'ders , ana'yDin%, docu$entin%, va'idatin% and $ana%in% soft(are or syste$ re3uire$ents.

e3uire$ents ana'ysis is critica' to the success of a syste$s or soft(are pro-ect. There3uire$ents shou'd e docu$ented, actiona 'e, $easura 'e, testa 'e, tracea 'e, re'ated toidentified usiness needs or opportunities, and defined to a 'eve' of detai' sufficient for syste$ desi%n.

e3uire$ents ana'ysis inc'udes three types of activities

• E'icitin% re3uire$ents e.%. the pro-ect charter or definitionH, usiness processdocu$entation, and sta)eho'der intervie(s. This is so$eti$es a'so ca''edre3uire$ents %atherin%.

• Ana'yDin% re3uire$ents deter$inin% (hether the stated re3uire$ents are c'ear,co$p'ete, consistent and una$ i%uous, and reso'vin% any apparent conf'icts.

• ecordin% re3uire$ents e3uire$ents $ay e docu$ented in various for$s,usua''y inc'udin% a su$$ary 'ist and $ay inc'ude natura'!'an%ua%e docu$ents, usecases , user stories , or process specifications.

=*, 5e>uirement Speci#ication"

=*,*. 3unctiona! 5e>uirement"A functiona' re3uire$ent defines a function of a syste$ and its co$ponents. A function isdescri ed as a set of inputs, the ehavior, and outputs.

http://en.wikipedia.org/wiki/Use_casehttp://en.wikipedia.org/wiki/Use_casehttp://en.wikipedia.org/wiki/Use_casehttp://en.wikipedia.org/wiki/User_storyhttp://en.wikipedia.org/wiki/User_storyhttp://en.wikipedia.org/wiki/User_storyhttp://en.wikipedia.org/wiki/Use_casehttp://en.wikipedia.org/wiki/Use_case


10/33

=unctiona' re3uire$ents $ay e ca'cu'ations, technica' detai's, data $anipu'ation and processin% and other specific functiona'ity that define (hat a syste$ is supposed toacco$p'ish.

ur soft(are product (i'' provide the fo''o(in% services

1. #o''ectI nput &ata, i.e., %et data into the Soft(are App'ication2. Mana%e &ata, i.e., receive data, verify data, store data, send datauirementA non!functiona' re3uire$ent is a re3uire$ent that specifies criteria that can e used to

-ud%e the operation of a syste$, rather than specific ehaviors. This shou'd e contrasted(ith functiona' re3uire$ents that define specific ehavior or functions. The p'an for i$p'e$entin% functiona' re3uire$ents is detai'ed in the syste$ desi%n. The p'an for i$p'e$entin% non!functiona' re3uire$ents is detai'ed in the syste$ architecture.

A "o#t?are re>uirement" "peci#ication S SH is a description of a soft(are syste$ to edeve'oped, 'ayin% out functiona' and non!functiona' re3uire$ents , and $ay inc'ude a setof use cases that descri e interactions the users (i'' have (ith the soft(are.

Soft(are re3uire$ents specification esta 'ishes the asis for an a%ree$ent et(eencusto$ers and contractors or supp'iers in $ar)et!driven pro-ects, these ro'es $ay e

p'ayed y the $ar)etin% and deve'op$ent divisionsH on (hat the soft(are product is to doas (e'' as (hat it is not e8pected to do. Soft(are re3uire$ents specification per$its ari%orous assess$ent of re3uire$ents efore desi%n can e%in and reduces 'ater redesi%n. tshou'd a'so provide a rea'istic asis for esti$atin% product costs, ris)s, and schedu'es.

The soft(are re3uire$ents specification docu$ent en'ists enou%h and necessaryre3uire$ents that are re3uired for the pro-ect deve'op$ent. To derive the re3uire$ents (eneed to have c'ear and thorou%h understandin% of the products to e deve'oped or ein%deve'oped. This is achieved and refined (ith detai'ed and continuous co$$unications(ith the pro-ect tea$ and custo$er ti'' the co$p'etion of the soft(are.

=*= '"e ca"e Ana!y"i"


11/33

=*=*. '"e ca"e De"cription

To $ode' a syste$ the $ost i$portant aspect is to capture the dyna$ic ehavior. Toc'arify a it in detai's, dyna$ic ehavior $eans the ehavior of the syste$ (hen it isrunnin% Ioperatin%. So on'y static ehavior is not sufficient to $ode' a syste$ rather dyna$ic ehavior is $ore i$portant than static ehavior. n 4M: there are five dia%ra$savai'a 'e to $ode' dyna$ic nature and use case dia%ra$ is one of the$. >o( as (e haveto discuss that the use case dia%ra$ is dyna$ic in nature there shou'd e so$e interna' or e8terna' factors for $a)in% the interaction. These interna' and e8terna' a%ents are )no(nas actors. So use case dia%ra$s are consists of actors, use cases and their re'ationships.The dia%ra$ is used to $ode' the syste$Isu syste$ of an app'ication. A sin%'e use casedia%ra$ captures a particu'ar functiona'ity of a syste$. 4se case dia%ra$s are used to%ather the re3uire$ents of a syste$ inc'udin% interna' and e8terna' inf'uences. Thesere3uire$ents are $ost'y desi%n re3uire$ents. So (hen a syste$ is ana'yDed to %ather itsfunctiona'ities use cases are prepared and actors are identified.

The purposes of use case dia%ra$s can e as fo''o(s1. 4sed to %ather re3uire$ents of a syste$.2. 4sed to %et an outside vie( of a syste$.


12/33

=i%ure


13/33

=i%ure


14/33


15/33


16/33

Loginusernamepassword

Login()

BillRoomBillNoDischargeIDBillingDateNoOfDaysRoomChargesTotalRoomChargesSer iceChargesTotalCharges!aymenet"ode!ayment"odeDetails

#ill()generateBill()

discharge!atientID $dmitIDDischargeDateD!%Remar&s

discharge!atient()

'ard

wardNamewardTypeNoOfBedsCharges

'ard()

RoomroomNo

roomTyperoomChargesroomStatus

allotment()chec&$ alia#ility()

Bill'ard#illNodischarge#illingDate

noOfDaystotalBedChargeser iceChargestotalChargespayment"odepayment"odeDetailscharges!aiddueCharges

addBill'ard()a aila#iltiy()

includes

depends on

doctor DoctorIDDoctorName

+atherName $ddressContctNo,mail-ualificationSpeciali.ation/ender Blood/roupDateOf0oining

doctor()

admit!atient $dmitIDpatientIDdiseaseRoomNo $dmitDateDoctorID $!%Remar&

admit!atient()

patientRegistrationpatientID!atientName+atherName $ddressContactNo,mail $ge/ender B/Remar&s

patientRegistration()

includes

((includes))

=i%ure ." #'ass &ia%ra$

/*/ Databa"e De"i$n7

Databa"e de"i$n is the process of producin% a detai'ed data $ode' of a data ase .This 'o%ica' data $ode' contains a'' the needed 'o%ica' and physica' desi%n choices and

physica' stora%e para$eters needed to %enerate a desi%n in a data definition 'an%ua%e ,(hich can then e used to create a data ase. A fu''y attri uted data $ode' contains detai'edattri utes for each entity.

E05 Dia$ram7&ata ase desi%ns a'so inc'ude E entity!re'ationship $ode'H dia%ra$s. An E dia%ra$ isa dia%ra$ that he'ps to desi%n data ases in an efficient (ay.


17/33

Attri utes in E dia%ra$s are usua''y $ode'ed as an ova' (ith the na$e of the attri ute,'in)ed to the entity or re'ationship that contains the attri ute.

Cithin the re'ationa' $ode' the fina' step can %enera''y e ro)en do(n into t(o further steps, that of deter$inin% the %roupin% of infor$ation (ithin the syste$, %enera''y

deter$inin% (hat are the asic o -ects a out (hich infor$ation is ein% stored, and thendeter$inin% the re'ationships et(een these %roups of infor$ation, or o -ects. This step isnot necessary (ith an -ect data ase.

=i%ure .? E! &ia%ra$

/*1 Modu!e" identi#ied

Patient 5e$i"tration7

This $odu'e records asic patient re'ated infor$ation, (hich is co''ected Chen the patient visits the hospita' for the first ti$e. Each patient is a''ocated a uni3ue patient identification nu$ ers.Patient id, patient na$e, address, ad$itted date, doctor na$e, roo$ nu$ er areentered in a for$ and stored for future reference. A'so particu'ar patient detai's can evie(ed in the ta 'e usin% a separate for$ (ith a attri ute patient id.


18/33


19/33

MySK: is a popu'ar choice of data ase for use in (e app'ications, and is a centra'co$ponent of the (ide'y used :AMP open source (e app'ication soft(are stac) andother LAMPL stac)sH. :AMP is an acrony$ for :inu8, Apache,MySK:, Per' IP PI Python . =ree!soft(are!open source pro-ects that re3uire a fu''!featured data ase $ana%e$ent syste$ often use MySK:.

MySK: can e ui't and insta''ed $anua''y fro$ source code, ut this can e tedious so itis $ore co$$on'y insta''ed fro$ a inary pac)a%e un'ess specia' custo$iDations arere3uired. n $ost :inu8 distri utions the pac)a%e $ana%e$ent syste$ can do(n'oad andinsta'' MySK: (ith $ini$a' effort, thou%h further confi%uration is often re3uired to ad-ustsecurity and opti$iDation settin%s.

Thou%h MySK: e%an as a 'o(!end a'ternative to $ore po(erfu' proprietary data ases, ithas %radua''y evo'ved to support hi%her!sca'e needs as (e''. t is sti'' $ost co$$on'y usedin s$a'' to $ediu$ sca'e sin%'e!server dep'oy$ents, either as a co$ponent in a :AMP!

ased (e app'ication or as a standa'one data ase server. Much of MySK:Ls appea'ori%inates in its re'ative si$p'icity and ease of use, (hich is ena 'ed y an ecosyste$ of open source too's such as phpMyAd$in. n the $ediu$ ran%e, MySK: can e sca'ed ydep'oyin% it on $ore po(erfu' hard(are, such as a $u'ti!processor server (ith %i%a ytesof $e$ory.

There are ho(ever 'i$its to ho( far perfor$ance can sca'e on a sin%'e server Lsca'in%upLH, so on 'ar%er sca'es, $u'ti!server MySK: Lsca'in% outLH dep'oy$ents are re3uired to

provide i$proved perfor$ance and re'ia i'ity. A typica' hi%h!end confi%uration caninc'ude a po(erfu' $aster data ase (hich hand'es data (rite operations and

is rep'icated to $u'tip'e s'aves that hand'e a'' read operations. The $aster server synchroniDes continua''y (ith its s'aves so in the event of fai'ure a s'ave can e pro$otedto eco$e the ne( $aster, $ini$iDin% do(nti$e. =urther i$prove$ents in perfor$ancecan e achieved y cachin% the resu'ts fro$ data ase 3ueries in $e$oryusin% $e$cached, or rea)in% do(n a data ase into s$a''er chun)s ca''ed shards (hichcan e spread across a nu$ er of distri uted server c'usters.

4a:a7

Java is a set of severa' co$puter soft(are and specifications deve'oped y SunMicrosyste$s, 'ater ac3uired y rac'e #orporation that provides a syste$ for deve'opin%app'ication soft(are and dep'oyin% it in a cross!p'atfor$ co$putin% environ$ent. Java isused in a (ide variety of co$putin% p'atfor$s fro$ e$ edded devices and $o i'e phonesto enterprise servers and superco$puters. Chi'e 'ess co$$on, Java app'ets run in secure,sand o8ed environ$ents to provide $any features of native app'ications and can ee$ edded in TM: pa%es.

http://en.wikipedia.org/wiki/Perlhttp://en.wikipedia.org/wiki/Perlhttp://en.wikipedia.org/wiki/Python_(programming_language)http://en.wikipedia.org/wiki/Perlhttp://en.wikipedia.org/wiki/Python_(programming_language)


20/33


21/33

N /ersionin%N Physica' ndependenceN :o%ica' ndependenceN nte%rity constraint independenceN /ie( 4pdatin%

N &ata &escriptionN #o$prehensive data su 'an%ua%eN nsert and update ru'eN &istri ution

1*.*. Hard?are recommended

Processor nte' # E i"Syste$ Type ? it .S.Me$ory #apa i'ity 2 GB

ard &is) #apa i'ity 20 GBMonitor Ma)e &E::

1*.*, So#t?are recommended

peratin% Syste$ Cindo(s @&ata ase My SK: Server .Pro%ra$$in% :an%ua%e Java

1*, Imp!ementation !e:e! Detai!"

1*,*. Sy"tem Modu!e" De"criptionThey are sa$e descri ed ear'ier in section ." OModu'es dentifiedF.

1*,*, Screen"hot"ere, so$e screenshots of that $odu'e are presented.

'"er !o$in ?indo?7


22/33

Patient re$i"tration ?indo?7

Ne? ?ard entry ?indo?7


23/33

5oom boo in$ ?indo?7

Main menu ?indo?7


24/33

@ard boy entry detai!" @indo?7

Patient in#o ?indo?7


25/33

1*,*= Samp!e Source CodePatient 5e$i"tration

private void eset H

t8tPatient &.setTe8t H t8tPatient>a$e.setTe8t H

t8t=atherna$e.setTe8t H t8t#ontact>o.setTe8t H t8tAddress.setTe8t H t8tA%e.setTe8t H t8tE$ai' &.setTe8t H t8t e$ar)s.setTe8t H c$ B'oodGroup.setSe'ected nde8 !1H c$ Gender.setSe'ected nde8 !1H tnSave.setEna 'ed trueH tn4pdate.setEna 'ed fa'seH tn&e'ete.setEna 'ed fa'seH

t8tPatient &.re3uest&efau't=ocus HQ

Lo$in7


26/33

pu 'ic :o%in H init#o$ponents Hset:ocation e'ativeTo nu''H Q

private void init#o$ponents H

-Menu te$1 R ne( -ava8.s(in%.JMenu te$ H fi''er1 R ne( -ava8.s(in%.Bo8.=i''er ne( -ava.a(t.&i$ension 0, 0H, ne(

-ava.a(t.&i$ension 0, 0H, ne( -ava.a(t.&i$ension a$e R ne( -ava8.s(in%.JTe8t=ie'd Ht8tPass(ord R ne( -ava8.s(in%.JPass(ord=ie'd H

tn 5 R ne( -ava8.s(in%.JButton H

tn#ance' R ne( -ava8.s(in%.JButton H fi''er2 R ne( -ava8.s(in%.Bo8.=i''er ne( -ava.a(t.&i$ension 0, 0H, ne( -ava.a(t.&i$ension 0, 0H, ne( -ava.a(t.&i$ension #: SEHsetTit'e :o%in =or$ Hset esiDa 'e fa'seHaddCindo(:istener ne( -ava.a(t.event.Cindo(Adapter H

pu 'ic void (indo( pened -ava.a(t.event.Cindo(EventevtH for$Cindo( pened evtH Q QH

-:a e'1.setTe8t 4ser >a$e H

-:a e'2.setTe8t Pass(ord H

t8t4ser>a$e.addMouse:istener ne( -ava.a(t.event.MouseAdapter H pu 'ic void $ouse#'ic)ed -ava.a(t.event.MouseEventevtH t8t4ser>a$eMouse#'ic)ed evtH Q QHt8t4ser>a$e.addAction:istener ne( -ava.a(t.event.Action:istener H

pu 'ic void actionPerfor$ed -ava.a(t.event.ActionEventevtH t8t4ser>a$eActionPerfor$ed evtH Q QH


27/33

t8tPass(ord.add5ey:istener ne( -ava.a(t.event.5eyAdapter H pu 'ic void )eyPressed -ava.a(t.event.5eyEventevtH t8tPass(ord5eyPressed evtH Q QH

tn 5.setTe8t 5 H tn 5.addMouse:istener ne( -ava.a(t.event.MouseAdapter H pu 'ic void $ouse#'ic)ed -ava.a(t.event.MouseEventevtH tn 5Mouse#'ic)ed evtH Q QH

tn 5.addAction:istener ne( -ava.a(t.event.Action:istener H pu 'ic void actionPerfor$ed -ava.a(t.event.ActionEventevtH tn 5ActionPerfor$ed evtH Q

QH tn#ance'.setTe8t #ance' H tn#ance'.addAction:istener ne( -ava.a(t.event.Action:istener H pu 'ic void actionPerfor$ed -ava.a(t.event.ActionEventevtH tn#ance'ActionPerfor$ed evtH Q QH

-ava8.s(in%.Group:ayout 'ayout R ne( -ava8.s(in%.Group:ayout %et#ontentPane HH%et#ontentPane H.set:ayout 'ayoutH'ayout.set oriDonta'Group'ayout.createPara''e'Group -ava8.s(in%.Group:ayout.A'i%n$ent.:EA& >GH .addGroup 'ayout.createSe3uentia'Group H .addGroup 'ayout.createPara''e'Group -ava8.s(in%.Group:ayout.A'i%n$ent.:EA& >GH .addGroup 'ayout.createSe3uentia'Group H .addGap 6, 6, 6H .add#o$ponent fi''er2, -ava8.s(in%.Group:ayout.P E=E E& S UE, ?,

-ava8.s(in%.Group:ayout.P E=E E& S UEHH .addGroup 'ayout.createSe3uentia'Group H .addGap


28/33

.add#o$ponent tn 5, -ava8.s(in%.Group:ayout.P E=E E& S UE, -ava8.s(in%.Group:ayout.P E=E E& S UEH .addPreferredGap -ava8.s(in%.:ayoutSty'e.#o$ponentP'ace$ent. E:ATE&, -ava8.s(in%.Group:ayout.&E=A4:T S UE, Short.MA /A:4EH

.add#o$ponent tn#ance'HH .add#o$ponent t8tPass(ord, -ava8.s(in%.Group:ayout.P E=E E& S UE, -ava8.s(in%.Group:ayout.P E=E E& S UEHHH .addGroup 'ayout.createSe3uentia'Group H .add#o$ponent -:a e'1H .addGap 26, 26, 26H .add#o$ponent t8t4ser>a$e,

-ava8.s(in%.Group:ayout.P E=E E& S UE, -ava8.s(in%.Group:ayout.P E=E E& S UEHHHHH .add#ontainerGap EH .add#o$ponent -:a e'1H .add#o$ponent t8t4ser>a$e,

-ava8.s(in%.Group:ayout.P E=E E& S UE, -ava8.s(in%.Group:ayout.&E=A4:T S UE, -ava8.s(in%.Group:ayout.P E=E E& S UEHH .addGap 2?, 2?, 2?H .addGroup 'ayout.createPara''e'Group -ava8.s(in%.Group:ayout.A'i%n$ent.BASE: >EH .add#o$ponent -:a e'2, -ava8.s(in%.Group:ayout.P E=E E& S UE,

-ava8.s(in%.Group:ayout.P E=E E& S UEH .add#o$ponent t8tPass(ordHH .addGap 2?, 2?, 2?H .addGroup 'ayout.createPara''e'Group -ava8.s(in%.Group:ayout.A'i%n$ent.BASE: >EH .add#o$ponent tn 5H .add#o$ponent tn#ance'HH .addPreferredGap -ava8.s(in%.:ayoutSty'e.#o$ponentP'ace$ent. E:ATE&,

-ava8.s(in%.Group:ayout.&E=A4:T S UE, Short.MA /A:4EH .add#o$ponent fi''er2, -ava8.s(in%.Group:ayout.P E=E E& S UE,

-ava8.s(in%.Group:ayout.P E=E E& S UEH .addGap 20, 20, 20HH H

pac) H


29/33

Q

private void t8t4ser>a$eMouse#'ic)ed -ava.a(t.event.MouseEventevtH Q

private void tn 5Mouse#'ic)ed -ava.a(t.event.MouseEventevtH

if t8t4ser>a$e.%etTe8t H.e3ua's HH J ptionPane.sho(Messa%e&ia'o% this, P'ease enter user na$e , Error ,J ptionPane.E MESSAGEHreturn Q Strin% Pass(ordR Strin%.va'ue f t8tPass(ord.%etPass(ord HHif Pass(ord.e3ua's HH J ptionPane.sho(Messa%e&ia'o% this, P'ease enter pass(ord , Error ,J ptionPane.E MESSAGEHreturn

QconR#onnect.#onnect&B H Strin% s3'R se'ect V fro$ users (here 4ser>a$eR L t8t4ser>a$e.%etTe8t H L anduser Pass(ord RL t8tPass(ord.%etTe8t H Ltry

pstRcon.prepareState$ent s3'HrsR pst.e8ecuteKuery Hif rs.ne8t HHthis.hide HMainMenufr$Rne( MainMenu Hfr$.set/isi 'e trueH Qe'se

J ptionPane.sho(Messa%e&ia'o% nu'', :o%in =ai'ed..Trya%ain W , Accessdenied ,J ptionPane.E MESSAGEH QQcatch SK:E8ception X ead'essE8ception eHJ ptionPane.sho(Messa%e&ia'o% nu'', eH

QQ

private void tn#ance'ActionPerfor$ed -ava.a(t.event.ActionEventevtH Syste$.e8it 0H Q

private void for$Cindo( pened -ava.a(t.event.Cindo(EventevtH


30/33

Q

private void t8t4ser>a$eActionPerfor$ed -ava.a(t.event.ActionEventevtH II T & add your hand'in% code here Q

private void t8tPass(ord5eyPressed -ava.a(t.event.5eyEventevtH if evt.%et5ey#ode HRR5eyEvent./5 E>TE HconR#onnect.#onnect&B H Strin% s3'R se'ect V fro$ users (here 4ser>a$eR L t8t4ser>a$e.%etTe8t H L anduser Pass(ord RL t8tPass(ord.%etTe8t H Ltry

pstRcon.prepareState$ent s3'HrsR pst.e8ecuteKuery Hif rs.ne8t HHthis.hide H

MainMenufr$Rne( MainMenu Hfr$.set/isi 'e trueH Qe'se

J ptionPane.sho(Messa%e&ia'o% nu'', :o%in =ai'ed..Trya%ain W , Accessdenied ,J ptionPane.E MESSAGEHt8t4ser>a$e.setTe8t Ht8tPass(ord.setTe8t Ht8t4ser>a$e.re3uest&efau't=ocus H QQcatch SK:E8ception X ead'essE8ception eH J ptionPane.sho(Messa%e&ia'o% nu'', eH Q Q Q

1*= Te"tin$


31/33

Testin% is the process of eva'uatin% a syste$ or its co$ponent sH (ith the intent to findthat (hether it satisfies the specified re3uire$ents or not. This activity resu'ts in theactua', e8pected and difference et(een their resu'ts. n si$p'e (ords testin% is e8ecutin%a syste$ in order to identify any %aps, errors or $issin% re3uire$ents in contrary to theactua' desire or re3uire$ents.

Accordin% to A>S I EEE 10"6 standard, Testin% can e defined as *A process of ana'yDin% a soft(are ite$ to detect the differences et(een e8istin% and re3uiredconditions that is defectsIerrorsI u%sH and to eva'uate the features of the soft(are ite$+.

t invo'ves the e8ecution of a soft(are co$ponent or syste$ co$ponent to eva'uate one or $ore properties of interest. n %enera', these properties indicate the e8tent to (hich theco$ponent or syste$ under test

• $eets the re3uire$ents that %uided its desi%n and deve'op$ent,

• responds correct'y to a'' )inds of inputs,

• perfor$s its functions (ithin an accepta 'e ti$e,

• is sufficient'y usa 'e,

• can e insta''ed and run in its intended environ$ents, and

• Achieves the %enera' resu't its sta)eho'ders desire.

Syste$ Testin% is an i$portant sta%e in any syste$ deve'op$ent 'ifecyc'e. Testin% is a process of e8ecutin% a pro%ra$ (ith the intention of findin% errors. The i$portance of soft(are testin% and its i$p'ications (ith respect to soft(are 3ua'ity cannot eovere$phasiDed. Soft(are testin% is a critica' e'e$ent of soft(are 3ua'ity assurance andrepresents the u'ti$ate revie( of specification, desi%n and codin%. A %ood test case is onethat has a hi%h pro a i'ity of findin% a yet undiscovered error. Testin% is the set of activities that can e p'anned in advance and conducted syste$atica''y. &ifferent testconditions shou'd e thorou%h'y chec)ed and the u%s detected shou'd e fi8ed. Thetestin% strate%ies for$ed y the user are perfor$ed to prove that the soft(are is free andc'ear fro$ errors. To do this, there are $any (ays of testin% the syste$Fs re'ia i'ity,co$p'eteness and $aintaina i'ity.

1*=*. Te"tin$ Techni>ue" Per#ormed

'nit Te"tin$7n the unit testin% the ana'yst tests the pro%ra$ $a)in% up a syste$. The soft(are units in

a syste$ are the $odu'es and routines that are asse$ 'ed and inte%rated to perfor$ aspecific function. n a 'ar%e syste$, $any $odu'es on different 'eve's are needed. 4nittestin% can e perfor$ed fro$ the otto$ up startin% (ith the s$a''est and 'o(est 'eve'


32/33

$odu'es and proceedin% one at a ti$e. =or each $odu'e in a otto$!up testin%, a short pro%ra$ e8ecutes the $odu'e and provides the needed data.

Inte$ration Te"tin$7

nte%ration testin% is a syste$atic techni3ue for constructin% the pro%ra$ structure (hi'econductin% test to uncover errors associate (ith interfacin%. -ectives are used to ta)eunit test $odu'es and ui't pro%ra$ structure that has een directed y desi%n. Theinte%ration testin% is perfor$ed for this Patient ecord Syste$ (hen a'' the $odu'es(here to $a)e it a co$p'ete syste$. After inte%ration the pro-ect (or)s successfu''y.

a!idation Te"tin$7Tests (ere perfor$ed to find confor$ity (ith the re3uire$ents. P'ans and procedures(ere desi%ned to ensure that a'' functiona' re3uire$ents are satisfied. The soft(are (asa'pha!tested. There are t(o %oa's in preparin% test p'ans. =irst'y, a proper'y detai'ed test

p'an de$onstrates that the pro%ra$ specifications are understood co$p'ete'y. Second'y,

the test p'an is used durin% pro%ra$ testin% to prove the correctness of the pro%ra$.1*=*, Te"t Ca"e"7CeF'' co$e up (ith our o(n re3uire$ent set for the 'o%in screen. CeF'' (rite the scenario

ased4serna$e shou'd contain 'etter, nu$ er and period.

• 4serna$e shou'd not e 'eft 'an).• 4serna$e shou'd not start (ith or contain any sy$ o's.

'"er Inter#aceere are so$e of the 3uestions that can he'p you for$ test cases.

•

Chere is the cursor focus in te8t area (hen you 'oad the pa%eY• &oes enter )ey (or)s as a su stitute for the si%n in utton actionY• &oes userna$e and pass(ord te8t fie'd appears in orderY• &oes re$e$ er $e chec) o8 se'ected y defau'tY• &oes the 'o%in pa%e has re%ister 'in) for ne( usersY• &oes the user interface 'oo) as per the desi%n specificationY

Po"iti:e te"t ca"e"7• Enter va'id userna$e and pass(ord.• #'ic) on re%ister 'in) and fi'' out the for$ and re%ister userna$e and pass(ord.•

4se enter utton after typin% correct userna$e and pass(ord.• 4se ta to navi%ate fro$ userna$e te8t o8 to pass(ord te8t o8 and then to 'o%in

utton.

Ne$ati:e te"t ca"e"7 Enter va'id userna$e and inva'id pass(ord. Enter va'id pass(ord ut inva'id userna$e. 5eep oth fie'd 'an) and hit enter or c'ic) 'o%in utton.


33/33

5eep userna$e 'an) and enter pass(ord. 5eep pass(ord 'an) and enter userna$e. Enter userna$e and pass(ord (ron%.

#hapter ?#onc'usionThe pro-ect Patient 5ecord Sy"tem is for co$puteriDin% the (or)in% in a hospita'. Thesoft(are ta)es care of a'' the re3uire$ents of an avera%e hospita' and is capa 'e to provideeasy and effective stora%e of infor$ation re'ated to patients that co$e up to the hospita' .F*. Important 3eature7

#an e used in any ospita', #'inic 'a s for $aintainin% patient detai's and their testresu'ts.

F*, Limitation"The siDe of the data ase increases day! y!day, increasin% the 'oad on the data ase

ac) up and data $aintenance activity.

Trainin% for si$p'e co$puter operations is necessary for the users (or)in% on thesyste$.

F*= 3uture ?or • There can e $any i$prove$ents possi 'e in any ne( or o'd syste$.• t cou'd e $ade on'ine on internet (hich e8pands its service to (ho'e (or'd.•

A'so (e (i'' )eep trac)s of u%s found (hi'e testin%.

5e#erence"7.* (((.%oo%'e.co$2. (((.s'ideshare.co$

finalreporthmsadiallutapn.docx

Documents