Pharmacy Management System (Desktop Application)
Requirement Analysis Document Prepa Pre par red By: By : 1. Belew Godano 2.Bezuwork Jemaneh 3.Fentahun Assnakew 4.Habitamu Asimare 5.Hareg Gebrebrhan Gebrebrhan Submitted to: Ins. Betsegaw Lemma [1]
Table of content
page
1.
Intr Introd oduc ucti tion on… ………… ………………… ……………… ……… ………… ……………… ………………… ……………… ……… ………… ……………… ………………… ……………. …...
3
1.1.
Purpose …… ……………………………………………………………………………………….
3
1.2.
Scope…………………………………………………………………………………………
4
1.3.
Objective……………………………………………………………………………………..
4
1.4 1.4.
Defin efinit itiion, on, acr acrony onyms, ms, and and bbre bbrevi viaation tionss……………………………………………………
!
1.!.
"eference nce……………………………………………………………………………………..
#
1.#.
Overv ervie$………………………………………………………………………………………
#
2.
%urr %urren entt syst system em…… ………… ……… ………… ……………… ………………… ……………… ……… ………… ……………… ………………… ……………… ……… ………… ………
#
3.
Prop Propos osed ed syst system em…… ……… ………… ……………… ………………… ……………… ……… ………… ……………… ………………… ……………… ……… ………… ………….
&
3.1.
Overv ervie$………………………………………………………………………………………
'
3.2. 3.2.
(unct unctio iona na)) "e*ui "e*uirm rmen ents ts…… ……… ………… ………………… ……………… ……… ………… ……………… ………………… ……………… ……… ………
'
3.3 3.3.
+onfun nfuncctio tiona) na) re*u re*uir ireement ents…… s…………………………………………………………………..
3.4. 3.4.
3.3.1. 3.3.1.
-sabi -sabi)it )ity… y……… ………… ………… ………… ………… ………… ………… ………… ………… ……... ...... ...... ..... ..... ...... ...... ...... ...... ...... ...... ...... ..... ..... ...... ...... ...
3.3. 3.3.2. 2.
"e)i "e)iab abi) i)it ity y………… …………… …………… ……………… ……… ………… ……………… ………………… ……………… ……… ………… ……………. …….
3.3. 3.3.3. 3.
Perf Perfor orma manc nce… e…… ………… ……………… ……………… ………………… ……………… ……… ………… ……………… ………………… ……………. …...
3.3.4. 3.3.4.
Suppor Supportab tabi)i i)ity… ty……… ………… ………… ………… ………… ………… ………… ………… ……... ...... ...... ...... ..... ..... ...... ...... ...... ...... ...... ...... ...... ..... ..... ...... ..... ..
1
3.3. 3.3.!. !.
Imp)e mp)eme ment ntat atio ion… n……… ……… ………… ………………… ……………… ……… ………… ……………… ………………… ……………… ……… …….
1
3.3.#. 3.3.#.
Interf Interface ace…… ………… ………… ………… ………… ………… ………… ………… ………… ………. ….... ...... ...... ...... ..... ..... ...... ...... ...... ...... ...... ...... ...... ..... ..... ...... .....
1
Syst System em mode mode)s )s…… ………… ………… ………… ………… ………… ………… ………… ………… …….. .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ..
1
[]
Table of content
page
1.
Intr Introd oduc ucti tion on… ………… ………………… ……………… ……… ………… ……………… ………………… ……………… ……… ………… ……………… ………………… ……………. …...
3
1.1.
Purpose …… ……………………………………………………………………………………….
3
1.2.
Scope…………………………………………………………………………………………
4
1.3.
Objective……………………………………………………………………………………..
4
1.4 1.4.
Defin efinit itiion, on, acr acrony onyms, ms, and and bbre bbrevi viaation tionss……………………………………………………
!
1.!.
"eference nce……………………………………………………………………………………..
#
1.#.
Overv ervie$………………………………………………………………………………………
#
2.
%urr %urren entt syst system em…… ………… ……… ………… ……………… ………………… ……………… ……… ………… ……………… ………………… ……………… ……… ………… ………
#
3.
Prop Propos osed ed syst system em…… ……… ………… ……………… ………………… ……………… ……… ………… ……………… ………………… ……………… ……… ………… ………….
&
3.1.
Overv ervie$………………………………………………………………………………………
'
3.2. 3.2.
(unct unctio iona na)) "e*ui "e*uirm rmen ents ts…… ……… ………… ………………… ……………… ……… ………… ……………… ………………… ……………… ……… ………
'
3.3 3.3.
+onfun nfuncctio tiona) na) re*u re*uir ireement ents…… s…………………………………………………………………..
3.4. 3.4.
3.3.1. 3.3.1.
-sabi -sabi)it )ity… y……… ………… ………… ………… ………… ………… ………… ………… ………… ……... ...... ...... ..... ..... ...... ...... ...... ...... ...... ...... ...... ..... ..... ...... ...... ...
3.3. 3.3.2. 2.
"e)i "e)iab abi) i)it ity y………… …………… …………… ……………… ……… ………… ……………… ………………… ……………… ……… ………… ……………. …….
3.3. 3.3.3. 3.
Perf Perfor orma manc nce… e…… ………… ……………… ……………… ………………… ……………… ……… ………… ……………… ………………… ……………. …...
3.3.4. 3.3.4.
Suppor Supportab tabi)i i)ity… ty……… ………… ………… ………… ………… ………… ………… ………… ……... ...... ...... ...... ..... ..... ...... ...... ...... ...... ...... ...... ...... ..... ..... ...... ..... ..
1
3.3. 3.3.!. !.
Imp)e mp)eme ment ntat atio ion… n……… ……… ………… ………………… ……………… ……… ………… ……………… ………………… ……………… ……… …….
1
3.3.#. 3.3.#.
Interf Interface ace…… ………… ………… ………… ………… ………… ………… ………… ………… ………. ….... ...... ...... ...... ..... ..... ...... ...... ...... ...... ...... ...... ...... ..... ..... ...... .....
1
Syst System em mode mode)s )s…… ………… ………… ………… ………… ………… ………… ………… ………… …….. .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ..
1
[]
4.
3.4.1. 3.4.1.
Scena Scenari rios… os……… ………… ………… ………… ………… ………… ………… ………… ………. ….... ...... ...... ..... ..... ...... ...... ...... ..... ..... ...... ...... ...... ...... ...... ...... ...... ...
11
3.4. 3.4.2. 2.
-se -se case case mode mode)… )…… ………… ………………… ……………… ……… ………… ……………… ………………… ……………… ……… ………… ………
14
3.4 3.4.3. .3.
Object ject /ode ode)…… )…………………………………………………………………………..
24
3.4.3.1.
Data dictionary……………………………………………………………..
2!
3.4.3.2.
%)ass dia0ram……………………………………………………………….
2#
3.4. 3.4.4. 4.
Dyna Dynami micc mode mode)… )……… ………… ……… …………… ……………… ……… ……... …...…… ……… ………… ………………… ……………… ……… …
2#
3.4. 3.4.!. !.
-ser -ser inte interf rfac aces es…… ……… …………… ……………… ……… ………… ……………… ………………… ……………… ……… ………… ……………
3#
)os )ossary sary… ……………………………………………………………………………………………….
1.
3&
Introduction
+o$ a days Information and communication tecno)o0y I%56 p)ays a 0reat ro)e in different fie)ds or areas amon0 tus 7ea)t care system be)on0s to tis. 5is )eads to various studies and researces bein0 conducted to se)ected ea)t care faci)ities. It is necessary to ensure a tecno)o0ica))y appropriate, e*uitab)e, affordab)e, efficient, and environmenta))y adaptab)e and consumer friend)y system, desi0ned to fu))y uti)i8e te I%5 for te ma9imum benefit in te ea)t care industry. 7ere computers ave 0reat re)evant on storin0 datas secure)y secure)y and ease access on tem in sort period of time. In order to e9p)oit te I%5 in ea)t care system, Parmacy mana0ement system is bein0 bui)d. Parmacy mana0ement system is robust, inte0rated tecno)o0y. tecno)o0y. Parmacy mana0e mana0emen mentt system system dea)s dea)s $it $it te mainte maintenan nance ce of dru0s dru0s and consum consumab) ab)es es in te parmacy unit. 5e set:up of tis parmacy mana0ement system $i)) ensure avai)abi)ity of sufficient *uantity of dru0s and consumab)e materia)s for te patient. 5is $i)) enance te efficiency of c)inica) $or; and ease patients convenience, bearin0 in mind tat in
[!]
resources, easy data access of te medicine, security on data input and data access by removin0 a)most manua) based system.
1.1 Purpose 5e parmacy mana0ement system is bui)t for te sa;e of ensurin0 effective and c)ear data savin0 and manipu)atin0 as $e)) as neat $or; on te parmacy medica) products. 5is refers te parmacy mana0ement system project i0)y minimi8e time and resource by $ic, searcin0 te medicine data you can 0et te data in *uic;est time. nd a)most te resources are $ise used since most actions are done on te parmacy system. Some of te resources minimi8ed inc)ude paper, manpo$er and re)ated tin0s. 5e oter tin0 is for storin0 datas in secure $ay. summari8ed )ist of dru0s dispensed to patient can be vie$ed for monitorin0 purposes. )so P/S $i)) be ab)e to 0enerate report on te )ist of dru0s dispensed in te po)yc)inic for a 0iven time period. nd tere is a messa0e a)ert for te user if te stoc; o)din0 *uantity reaces a )o$ )eve). 5us, te parmacist $i)) need to rep)enis te dru0s.
1.2 Scope =it te deve)opment of specific and potent syntetic dru0s, te empasis of te parmacists responsibi)ity as moved substantia))y to$ards te uti)i8ation of scientific ;no$)ed0e in te proper use of modern medicines and te protection of te pub)ic a0ainst dan0ers tat are inerent in teir use. Parmacists are emp)oyed in re0u)atory contro) and dru0 mana0ement, community parmacy, ospita) parmacy, te parmaceutica) industry, academic activities, trainin0 of oter ea)t $or;ers, and researc. In a)) tese fie)ds, teir aim is to ensure optimum dru0 terapy, bot by contributin0 to te preparation, supp)y and contro) of medicines and associated products, and by providin0 information and advice to tose $o prescribe or use parmaceutica) products.
1.3 Objecties It is te user friend)y app)ication for Parmacist $ic reduces te burden and e)ps to mana0e a)) sections of Parmacy )i;e /edicine mana0ement and >i))in0 etc., $ic improve te processin0 efficiency. It dea)s $it te automatin0 tas;s of maintainin0 of >i))s. In Parmacy, >i))in0 mana0ement is te ;ey process. Inc)udin0 safe data store ["]
about medicine as $e)) as fast searcin0, de)ete and update of medicines. 5e parmacy mana0ement system is easy for use so te user can do parmacy actions $itout ambi0uities. 5e main Objectives of te P/S is ma;in0 te parmacy or0ani8ations computeri8ed by creatin0 neat $or; trou0 minimi8in0 or e)iminatin0 $astin0 of time as $e)) as removin0 te resources suc as papers for data savin0 since ;no$ a days is paper based, decrease ma)functioned $or;s on te medica) usa0e by 0ivin0 correct information on eac medicine.
1.! "efinitions# $cronyms and abbreiation "efinitions
-ser:friend)y? Is te $ay tat te bui)t system is not ambi0uous $ic is c)ear for usin0 te created soft$are interface for manipu)atin0 actions or tas;s. In te oter $ay te proposed system is desi0ned for uman )i;ab)e components in co)or, font and oter re)ated tin0s.
/anua) based system? 5e system tat uses $as paper based and arran0ed on te se)f trou0 functiona)ity of documents.
Parmacist? 5e profession $o ave ;no$)ed0e on te medicine usa0e, instruction for use tose medicines for te particu)ar diseases and oter re)ated tin0s.
/ana0ement system? system in $ic mana0e, or0ani8e, formu)ate datas trou0 a tecnica) data structure arran0ement
>i))in0? 5e $ay in $ic 0eneratin0 paper $ic store information about some specific data containin0 detai)s e9p)anation.
[#]
$cronyms and abbreiations PMS% parmacy mana0ement system I"&% inte0rated deve)opment environment
1.' (eference : Prentice Object Oriented Soft$are
1.) Oerie* 5e parmacy mana0ement system is bui)t in order to rep)ace manua) based system to computeri8e. 7ere system is e9pected to be efficient, usefu) and affordab)e on imp)ementin0 tas;s tat is order by te parmacy mana0er.
2 current system 5e current Parmacy system $ere manua))y base system $ic is a)most a)) $or;s on te parmacy or0ani8ation is accomp)ised by papers. mon0 tus /edicine data searc in order to buy, audit, and oter re)ated $or;s. nd te oter one is data security, te datas can be accessed anyone $o entered to te parmacy ouse as friends, oter 7umans $itout te vo)unteer of te parmacist. 5e parmacists $or; in tedious situation because of te upper reasons. +ot efficient on arran0e medicine on te se)f meanin0 arran0ement metod is difficu)t to ta;e in mind. In current system a)most a)) parmacies do not use computeri8ed system but use computer for 0ivin0 bi))s on)y for te so)d medicine to te user. nd use manua)
[$]
searcin0 of medicine on se)f because of manua) based system and tere is notin0 $ic 0ives a)arm for te finised or so)d medicine. )so tere is a difficu)ty on store te data $ic $astes resources as $e)) as time to retrieve te necessary data from te manua))y based data system. So 0enera))y te current system does not arran0e medicine in systematic $ay, does not store te medicine appropriate data, security for te data is )o$, does not indicate o$ muc medicine is needed and so)d *uic;)y and efficient)y. 5e parmacy system $i)) imp)ement by te parmacy unit of te or0ani8ation. t present, manua) system is bein0 uti)i8ed. 5is system re*uires te parmacist to manua))y monitor eac dru0 tat is avai)ab)e in te parmacy se)f. 5is invo)ves manua))y entry up on arriva) of batces of dru0s and upon dru0s movement out of te unit, for e9amp)e, dispensin0 to patients or product reca)) or )oan to oter c)inicsBospita)s. -pon a certain period suc as mont, te parmacist is re*uired to 0enerate reports on te movement of dru0s. 5is is to monitor te justification of orderin0 in order to rep)enis te a)ready diminisin0 stoc;s. In addition, orderin0 of dru0s is a)so bein0 done manua))y. Si0nificant amount of time is a))ocated for $ritin0 order as one needs to 0o trou0 te stoc;s ba)ance and rou0 estimate of te amount to order. 5is usua))y )ed to mista;es as one /ay over or under:order. 5us, in tis aspect, te $or;)oad of a parmacist increases. s a resu)t, sometimes, patient care, in terms of counse)in0, is compromised due to time constraints.
3 Proposed System 5e parmacy mana0ement system is desi0n based on computer science students in order to i))uminate te prob)em of te current system $ic provided by te system invo)ved a)) te parmaceutica) emp)oyees of te parmacy. 5is accessibi)ity of te information $i)) be 0reat advanta0e as it reduced furter medica) errors associated $it pysicians and nurses. 5e system and)es a)) aspects of te inventory contro) function. It a))o$s te parmacist to receive ne$ batces of dru0s, de)ete obso)ete dru0s and modify te current dosa0e and identification of dru0 in te database. (urtermore, te system eases te process of stoc; rep)enisment. On te oter and, P/S enab)es dispensation process. It stores a)) te pysicians prescription of te patients. summari8ed )ist of dru0s dispensed to te patient can be vie$ed for monitorin0 purposes. [%]
=it te proposed system, te parmacist $i)) be ab)e to monitor te movement of te dru0s $it ease. 5e system is desi0n to trac; te entry of refres batces of dru0s, be it upon orders from manufacture or )oan from te ospita)Bc)inics. It a)so monitors te dru0s movement istory, tus )eads to better inventory mana0ement of money a))ocated for te purcase of dru0s. %ompared to te current manua) system, te imp)ementation of Parmacy mana0ement system $i)) reduced te time spent for paper$or;, )eadin0 to concentration on improvin0 parmaceutica) care of patients, especia))y empasis on patients counse)in0 and patient medication monitorin0. It $i)) be 0reat)y embraced by te parmacy profession as it is one 0iant )eap to$ards parmaceutica) care of patients.
3.1 Oerie* 5e parmacy mana0ement system provides functions on identify medication usa0es instruction, minimi8e uman errors in medication safety, faci)itate accessibi)ity of dru0s information and information mana0ement amon0 emp)oyees, providin0 optima) dru0s movement in parmacy unit, enab)e reports $it in si0nificant)y sort period of time, despite simu)taneous usa0e of database for te purpose stated above. 5e system $i)) so)ve te prob)em of te current system by minimi8in0 time $asta0e and reduce resources $ic simp)y can0e manua) based system to computeri8ed system. 3.2
+unctional (e,uirments
5ere are functions done by te system suc as? store te necessary information of dru0s, prepare bi)) for te medicine, 0ive $ee; reports, easi)y searcin0 of medicine, $or;in0 in t$o )an0ua0es, -pdate, de)ete and save datas of medicine.
-enerate report te parmacy mana0ement system 0enerates report $ea;)y on information about te dru0s and it e9ports te information as output document.
Store the necessary information of the drugs : 5e PS parmacy system6 stores te detai) information about eac medicine inc)udin0 ctua) name, formu)a of medicine and o$ it is importance and for $ic diseases is re*uired. Since te information for eac dru0 $ere re*uired in some cases )i;e te use of dru0s, $en use dru0s and for $om is 0iven.
[&]
Searching Medicine and other Data’s : 5e
PS as
easi)y searcin0 of medicine $ic so$s in $ic se)f is put and te beavior of te medicine. 5e searcin0 process is based on te name of te 0ive data or te identification of te item. 7ere $en te user searc te item on searc bar te re)ated tin0s $ere disp)ayed in te screen and can se)ect te actua) item tat te user needs.
Alerting pharmacy Data’s in the system : %an0in0 medicines to anoter because of medicine outdated, modifyin0 te saved medicine data for incorrect data, de)etin0 of datas of te parmacy can be done on te system.
Support multi languages : 'e sstem supposed wo*k on p*ima*il in +nglis and Ama*ic. So te use* can use one o, tese languages. te pu*pose o, te languages we*e wen te use* is un,amilia* ,o* te sstem e-se ma cange te language tat e-se unde*stood simpl it se*/e as a t*anslato*. 'e ,unction wat te sstem do is
Sto*e 0edicine datas Sea*c 0edicine data e2ecti/el 3pdate delete and +dit medicine in,o*mation 4ene*ate *epo*t on medicine 5*epa*e bill ,o* te medicine 4i/es na/igation o* in,o*mation ,o* pa*mac o*gani6ation 4i/e ale*t ,o* te use* wen medicine item is low 7anging login passwo*d 8a/e te sstem document ow to use te sstem
3.3 /on functional (e,uirments 5is parmacy mana0ement system is ab)e to operate in te fo))o$in0 caracteristics.
Usability : Any fami)iar in usin0 $indo$s operation can operate te system since it ave user friend)y user interface. =ic ave te instruction menus o$ to use it $ic se)f directive app)ication ten can be used te system $itout ambi0uity.
Reliability : The parmacy system is avai)ab)e based on te
user needs, can
$or; proper)y, and do transactions efficient)y inc)udin0 safe data mana0ement of te parmacy. (or inva)id and ma)functioned operation te system $i)) restart in order to [9]
prevent data )oose as $e)) as safe operation $itin ! seconds. 5e parmacy system is pass$ord protected to can0e tin0s on te system. 7ere te parmacist mana0er contro) over te system by )o0in to te parmacy system. ny user cant use te system but te 0uest user can see on 0enera) properties of te parmacy and medicines $itout pass$ord. s resu)t data is protected and contro))ed by on)y te administrator .
Performance :
5e parmacy mana0ement system operates its function in
sma)) amount of time $ic is )ess tan t$o seconds and can be accessed by one user at a time or concurrent)y. 5o access te user must first )o0in to te system $ic must ave te parmacy system privi)e0ed and a)so te system can store data up to 4 > data. =en te system may be busy due to ma)function operation it may $ait up to one minute oter $ays te parmacy system restarts.
User interface:
te use* inte*,ace is ,*iendl wic is
eas to use. And a/ing att*acti/e ,*ame st*uctu*e wic is p*epa*ed in assumption wit ote* *elated sstems. Also te use* can cange im-e* use* ,a/o*ite inte*,aces tat Is a/ailable in te sstem.
peration:
te pa*mac management sstem is ope*ated
and cont*olled b te pa*mac manage* ,o* sa,e wo*k.
Supportability: 'is parmacy mana0ement system operates in any version of $indo$s operatin0 system. Suc as $indo$s 9p, $indo$s 23, $indo$s &, $indo$s ' and oter re)ated versions. 5e system can be easi)y maintained by te mana0er of te parmacy system by usin0 te prepared documents of te system for easy maintenance. Oter $ays it is maintained by te system deve)opers for corrective and oter eavy prob)ems.
!mplementation :5e
system is imp)emented in Inte)"6 %ore5/6 i3
processor $it 2 > "/,32 bit computer. nd it is imp)emented trou0 testin0 on bot >)ac; and =ite testin0. 5e )an0ua0e $e use imp)ement te system is +etbeans ID<, ADC, /SE@ database.
"#$ system Models 5e parmacy mana0ement system is based different mode) vie$ to represent te system in understandab)e $ay suc as in scenarios, use case mode)s, object mode)s, ctivity dia0rams, and se*uence dia0rams.
1.1.1.
Scenarios [1]
5e parmacy mana0ement system re0isters medicine, store on te database a0ain accessed $en needed, remove $en obso)ete, modified $en additiona) information is e9ist, <9port reports for $ee;)y so)d medicine, a)terin0 $en medicine items are )o$, bi))in0 for so)d medicine.
Scenario 1? 5e parmacy mana0er and te customer can 0et information on te parmacy by navi0atin0 te parmacy mana0ement system. (rom te system pa0e can see about te /edicine se)) on te parmacy, about te or0ani8ation of te parmacy inc)udin0 basic information. 5rou0 tis te parmacy mana0ement system can disp)ay different information about te or0ani8ation effective)y and efficient)y in sort period of time.
Scenario 2? 5e parmacy mana0er can contro) over te system suc as record medicine information store on te system and a0ain retrieve for data see, de)ete, update, and print a)so te parmacy system contro))er can see reports on te medicine in $ee;)y, and mont)y as te user needs tis is a)) about te function done by te system and do te parmacy mana0er. 5e fo))o$in0 is a scenarios e9p)ain more.
Scenario name etInformationboutParmacy $ctors
%Parmacy mana0er, %ustomer
+lo* of &ent
1. 5e parmacy mana0er initiates te system. [11]
5e system disp)ays te first pa0e. 5e first pa0e consists of menus /edicine , and bout parmacy 5e customer or te parmacy mana0er enters /edicine menu System disp)ays te medicine avai)ab)e on te parmacy $it cost and purpose. ). 5e customer or te parmacy mana0er enters bout parmacy 0. System disp)ays about te or0ani8ation services and estab)isment. 2. 3. !. '.
Scenario1? et information for parmacy scenario for P/S
Scenario name can0e/edicineData $ctors
%Parmacy mana0er
+lo* of &ent 1. 5e parmacy mana0er initiates te system. 2. 5e system disp)ays te first pa0e. 3. 5e first pa0e consists of menus /edicine , and bout parmacy and )o0in /enus !. te parmacy mana0er enters )o0in menu '. te system disp)ays )o0in form to enter te username and pass$ord. ). 5e parmacy mana0er prompts username and pass$ord on avai)ab)e fie)ds tat te system disp)ays. 0. 5e system disp)ays /ain admin pa0e. . o on te settin0s and can0e /edicine Data . Save te can0es
Scenario2? %an0e /edicine Data scenario for P/S
Scenario name 0et+otificationOn/edicine $ctors
%Parmacy mana0er
+lo* of &ent 1. 5e parmacy mana0er initiates te system. 2. 5e system disp)ays te first pa0e.
[1]
3. 5e first pa0e consists of menus /edicine , and bout parmacy and )o0in /enus !. te parmacy mana0er enters )o0in menu '. te system disp)ays )o0in form to enter te username and pass$ord. ). 5e parmacy mana0er prompts username and pass$ord on avai)ab)e fie)ds tat te system disp)ays. 0. If tere is )o$ medicine items te system disp)ays a)ert
Scenario3? 0et+otificationOn/edicine scenario for P/S
Scenario name %an0e@o0inPass$ord $ctors
%Parmacy mana0er
+lo* of &ent 1. 5e parmacy mana0er initiates te system. 2. 5e system disp)ays te first pa0e. 3. 5e first pa0e consists of menus /edicine , and bout parmacy and )o0in /enus !. te parmacy mana0er enters )o0in menu '. te system disp)ays )o0in form to enter te username and pass$ord. ). 5e parmacy mana0er prompts username and pass$ord on avai)ab)e fie)ds tat te system disp)ays. 0. 5e parmacy mana0er 0o on settin0s .
Scenario4? 0et+otificationOn/edicine scenario for P/S
[1!]
3.4.2 -se case mode)
[1"]
[1#]
%# Use case description for &ogin To System Use case name
Login to Sstem
Summary
Sstem /alidates te use*
Actor
te 5a*mac 0anage*
Precondition
te login page must be displaed
Main sequence: 1. 'e pa*mac manage* going to te login menu and click on it. . Sstem p*ompts te use* ,o* use*name and passwo*d !. 'e pa*mac manage* inse*ts use*name and passwo*d to te ;elds. ". Sstem cecks te use*name and passwo*d. #. I, te input we*e /alid /alue ten sstem will displa gene*al sstem o, te pa*mac sstem.
Alternative sequence: Step #: i, te use*name o* passwo*d is not co**ect te Sstem displas an +**o* message. And p*ompts ,o* te co**ect use*name and passwo*d. Step #: i, te use* t*ies to inse*t use*name and 5asswo*d t*ee times
Use case name Add>ew0edicineData Summery success,ull *eco*d new medicine data Actor 5a*mac 0anage* Dependency include login into te sstem Flowof event 1. 'e pa*mac manage* login into te sstem. . 4o to te sstem settings and menus. !. Select on new medicine *eco*d option. ". 'e sstem displa *eco*d ,o*m #. 'en te pa*mac manage* ;lls te ,o*m tat te medicine data as. $. 'en sa/e te medicine tat ;lls in step #. %. Sstem cecks te data ente*ed wete* co**ect o* not &. I, te datas input we*e co**ect ten sstem sa/ed it into te disks.
Alternative sequence Step %: I, te input ,o*m a/e e**o* te sstem displas @Sa/ing e**o* message Step 1=%: i, te use* ente*s cancel te pa*mac management sstem will Stop te ope*ation. Entry condition
'e pa*mac manage* sstem must Be on p*ocess and
login to te sstem.
Exit condition
# 'e pa*mac manage* making t*ansaction could not
be p*ocessed.
uality !equirements .'e t*ansaction must be p*ocess less tan two seconds.
".
4se case description for 4pdate Medicine "ata [1&]
Use case name 3pdate0edicineData Summery success,ull updated medicine data Actor 5a*mac 0anage* Dependency include login into te sstem Flowof event 1. 'e pa*mac manage* login into te sstem. . 4o to te sstem settings and menus. !. Select on medicine *eco*ds option. ". 'e sstem displa te a/ailable medicines tat is *eco*ded be,o*e #. 'en te pa*mac manage* selects te medicine tat e-se wants update. $. 'en p*ess te update ,*om a/ailable options. %. 'e sstem displas te medicine data tat is *eco*ded be,o*e. &. 'e pa*mac manage* cange te data tat displaed in te ,o*m 9. Sa/e te updated ;ll ,o*m. 1. Sstem cecks te data ente*ed wete* co**ect o* not 11. I, te datas input is co**ect ten sstem sa/ed it into te disks.
Alternative sequence Step 1: I, te input ,o*m a/e e**o* te sstem displas @3pdating e**o* message Step 1=1: i, te use* ente*s cancel te pa*mac management sstem will Stop te ope*ation. Entry condition
'e pa*mac manage* sstem must be on p*ocess and
login to te sstem.
Exit condition
# 'e pa*mac manage* making t*ansaction could not
be p*ocessed.
uality !equirements .'e t*ansaction must be p*ocess less tan two seconds. #.
4se case description for "elete Medicine "ata Use case name Summery
Delete0edicineData success,ull updated medicine data [19]
Actor 5a*mac 0anage* Dependency include login into te sstem Flowof event 1. 'e pa*mac manage* login into te sstem. . 4o to te sstem settings and menus. !. Select on medicine *eco*ds option. ". 'e sstem displa te a/ailable medicines tat is *eco*ded be,o*e #. 'en te pa*mac manage* selects te medicine tat e-se wants to delete. $. 'en p*ess te delete ,*om a/ailable options. %. I, te sstem can success,ull delete ten displas te message @success,ull deleted. &. 'e sstem *emo/es te medicine data ,o*m disk.
Alternative sequence Step %: I, te sstem cannot success,ull delete te medicine ten sstem displas @not delete message Step 1=%: i, te use* ente*s cancel te pa*mac management sstem will Stop te ope*ation. Entry condition
'e pa*mac manage* sstem must Be on p*ocess and
login to te sstem.
Exit condition
# 'e pa*mac manage* making t*ansaction could not
be p*ocessed.
uality !equirements .'e t*ansaction must be p*ocess less tan two seconds.
$.
4se case description for (eceie notification Use case name Summery Actor Dependency
ecei/e>oti;cationCo*+ac0edicineData 4i/ing ale*t ,o* low medicines in time 5a*mac 0anage* include login into te sstem []
Flowof event 1. 'e pa*mac manage* login into te sstem. . Sstem cecks ,o* te medicine items !. I, medicine items a*e less tan # ten sstem displas te message b indicating 'e medicine @0edicine >ame is unning out please add.
Alternative sequence Step !: I, te sstem silent no message ,o* te use*
%.
4se case description for change login pass*ord Use case name Summery Actor Dependency (lo)of e*ent 1. 2. 3. !. '. ). 0.
7angeLogin cange passwo*d ,o* sstem success,ull. 5a*mac 0anage* include login to te sstem
Inc)ude )o0in to te system 5e parmacy mana0er navi0ate settin0s te parmacy mana0er se)ect can0e pass$ord
te system disp)ays can0e pass$ord form.
enter te o)d pass$ord enter te ne$ pass$ord re:enter te ne$ pass$ord &. 5en press te can0e )o0in pass$ord option.
9. If o)d pass$ord and ne$ pass$ord entry $ere va)id ten system can0es te )o0in pass$ord.
Alternative sequence Step 9: I, te input old passwo*d is not co**ect ten sstem displas @+**o* in canging passwo*d message Step 9: i, te input ,o* new passwo*d did not matc ten sstem displas @+**o* in canging passwo*d message Step 1=&: i, te use* ente*s cancel te pa*mac management sstem will stop te ope*ation.
[1]
+nt* condition
pa*mac manage* sstem must be login to te
sstem. +Eit condition
.'e pa*mac manage* making t*ans=action could
not be p*ocessed. Fualit
.'e t*ansaction must be p*ocessed less 'an two
seconds.
&.
4se case description for prepare bill for medicine
Use case name
5*epa*eBill
Summery
4i/e Bill ,o* sold medicine
Actor
5a*mac 0anage*
"ependency
include login into te sstem
Flowof event 1. . !. ". #. $. %. &.
'e pa*mac manage* login 'e pa*mac manage* use option p*epa*e bill. 'e sstem displas bill ,o*m 'e pa*mac manage* ;ll te ,o*m 'e pa*mac manage* use option eite* sa/es o* p*ints. I, te pa*mac manage* p*ess on tese options Sstem cecks weate* te input data we*e co**ect o* not I, it is co**ect te sstem sa/es into te disks i, te bill make* p*ess on option sa/es and sends to p*inte* i, bill make* we*e use option p*int
bill. 9. 'e sstem closes te bill ,o*m.
Alternative sequence: Step %: I, te input data is not co**ect ten sstem displas @+**o* in p*epa*ing bill message Step 1=&: i, te use* ente*s cancel te pa*mac management sstem will stop te ope*ation. []
Entry condition
'e pa*mac manage* sstem must be on p*ocess and
login to te sstem.
Exit condition
# 'e pa*mac manage* making t*ans=action could
not be p*ocessed.
uality e!uirements .'e t*ansaction must be p*ocessed less tan two seconds.
9.
4se case description Search Medicine "ata
Use case name
5*epa*eBill
Summery
Displa te sea*ced medicine data eGcientl
Actor "ependency
5a*mac 0anage* include login into te sstem
Flowof event Flowof event 1. 'e pa*mac manage* login to te sstem . 'e pa*mac manage* use option o, te sea*c medicine. !. 7lick on sea*c medicine. ". 5*ompt te name o, te medicine o* te identi;cation o, te medicine. #. 5*ess 4H button to see te data o, medicine $. I, eEist it displa on te sc*een
Alternative sequence: Step $: I, te medicine data is not a/ailable ten sstem displas @>ot eEist message Step 1=&: i, te use* ente*s cancel te pa*mac management sstem will stop te ope*ation.
[!]
Entry condition
'e pa*mac manage* sstem must be on p*ocess and
login to te sstem.
Exit condition
# 'e pa*mac manage* making t*ans=action could
not be p*ocessed.
uality e!uirements .'e t*ansaction must be p*ocessed less tan two seconds.
1.
4se case description Sea 5o* to use the system
Use case name
See8ow'o3se'eSstem
Summery
4i/e b*ie, Document ,o* te use*
Actor "ependency
5a*mac 0anage* include login into te sstem
Flow of event 1. 'e pa*mac manage* login to te sstem . 'e pa*mac manage* use option o, te @about ten @8elp. !. 7lick on wat te use* to know ow to use te sstem. ". 'e sstem displas te manual ,o* te use*.
Entry condition
'e pa*mac manage* sstem must be on p*ocess and
login to te sstem.
Exit condition
# 'e pa*mac manage* making t*ans=action could
not be p*ocessed.
uality e!uirements .'e t*ansaction must be p*ocessed less tan two seconds.
["]
11.
4se case description get report on medicine
Use case name
4etepo*tHn0edicine
Summery
gi/es summa*i6ed *epo*t about sold medicine in te
week end.
Actor
5a*mac 0anage*
"ependency
include login into te sstem
Flow of event 1. 'e pa*mac manage* login to te sstem . 'e pa*mac manage* use option o, te @*epo*t. ! p*ess on *epo*ts. ". 'e sstem displas te summa*i6ed document.
Entry condition
'e pa*mac manage* sstem must be on p*ocess and
login to te sstem.
Exit condition
'e pa*mac manage* making t*ans=action could not be
p*ocessed.
uality e!uirements .'e t*ansaction must be p*ocessed less tan two seconds.
"#$#"# b+ect Model 'e pa*mac management sstem desc*ibed in metodolog o, Data dictiona* and class diag*am. In wic di2e*ent collection o, datas p*oduce we*e supposed to const*uct tis pa*mac management sstem and te *elationsip o, classes tat compose te sstem.
[#]
"#$#$# Data Dictionary #a$le: wor%ing glossary for P&armacy management system' (eeping trac% of important terms and t&eir de)nitions ensures consistency in t&e speci)cation and ensures t&at developers use t&e language of t&e client'
Medicine
/edicine is an entity in $ic recorded, de)eted, updated in te Parmacy mana0ement system and fina))y saved into te system Dis; for re:access te data $at done.
Pharmacy Manager
te user of te system tat ave i0er privi)e0e to contro) over it. "ecord, de)ete, update, and 0et report and oter actions tat Imp)emented by te system is done by te parmacy mana0er.
Patient
te customers in parmacy $o buy medicine from te doctor Prescription. nd 0et bi)) for tat medicine.
(eport
te 0enerated document for medicines $ic store or inc)ude +ecessary information about te medicine tat is so)d in te $ee;
6ill
te piece of paper $ic store information about sin0)e medicine In $ic printed or saved into te system
/otification
n a)ertin0 messa0e $ic notify to te user to ta;e action for -navai)ab)e or )o$ medicine in items.
[$]
"#"#$#%#
3.!.
,lass Diagram
"ynamic Model 3.4.2. Se*uence Dia0ram. [%]
1. Se*uence dia0ram for @o0in into te system
[&]
2. dd ne$ medicine data.
[9]
3. -pdate medicine data.
[!]
4. %an0e )o0in pass$ord
!. enerate "eport [!1]
#. et Information about parmacy [!]
&. "eceive notification
[!!]
'. Searc /edicine
[!"]
. Prepare bi)) for medicine
1. See System instruction.
[!#]
11. De)ete medicine
[!$]
3.4.!.
Supposed user interface 1. +avi0ation Pa0e [!%]
2. @o0in form
!. Admin 0ain 5age
[!&]
