IDS\ Software_Requiremet_Specificatio.doc
Table of Cotets... Itroductio... 3. Purpose of Documet... 3.2 Goals ad Objective... 3.3 Major Costraits... 3 2 User Requiremet Aalysis... 3 2. User Profiles... 4 2.2 User Requiremets for Exteral User... 4 2.3 User Requiremets for Iteral User... 4 2.4 User Requiremets for Aget... 5 2.5 Aalysis... 5 3 Data Model ad Descriptio... 6 3. Etity Descriptio... 6 3.. Customer... 6 3..2 Aget... 6 3..3 Supplier... 6 3..4 Doctor... 6 3..5 Accout... 6 3..6 Prescriptio... 6 3..7 Drug... 6 3..8 Order... 7 3..9 MedicalHistory... 7 3..0 ShoppigCart... 7 3.2 Etity ad Attributes... 7 3.3 Relatioships... 8 3.4 Complete Data Model... 8 4 Data Model Explaatio... 5 Software Iterface Descriptio... 5. Exteral Machie Iterface... 5.2 Exteral System Iterface... 5.3 Huma Iterface... IDS\ Software_Requiremet_Specificatio.doc 2
Itroductio This documet serves as a prelimiary software requiremet specificatio for Iteratioal Drug Store (IDS) project (Project ID: 44 IDS) developed by Team for 22C:44 Itroductio to Database Systems. It cosists of a overview of IDS missio ad aalysis of customer requiremets from software desig perspective, followed by data model ERD ad desig explaatio. At the ed of this documet, a prelimiary website prototype is give ad costraits of IDS are specified.. Purpose of Documet This documet presets the (SRS) for the IDS Project (Project ID: 44-_IDS). This documet specifies all the deliverable user requiremets from a software system perspective. As IDS Team is aware of the relatively striget developmet time ad huma resources, this documet categorizes user requiremets ito 3 categories: User specified, Bous, Advaced. Each category directly relates to certai priority i IDS implemetatio. For aalysis detail, please go to Sectio 2. The acceptace of this documet by both the customer ad developmet team serves as a iformal agreemet of deliverables betwee the customer ad IDS Team. It s realized that certai software requiremets specified i this documet are subjective to chage durig developmet stage..2 Goals ad Objective The Project ivolves buildig a website for a olie drug store (IDS). IDS is a web-based olie drug store that allows for patiets to order drugs to fill prescriptios, track the status of placed orders, ad offers basic orderig process security. The system also supports iteral use by pharmacists who receive customer iquiries over the phoe for quotes, orders, ad order status iformatio ad who maitai the product ad customer database..3 Major Costraits As it s stated i Sectio., oe of the greatest challege IDS Team is facig is the rather striget developmet time ad resources. Due to this potetial risk, IDS Team will categorize the customer requiremets so that durig the developmet cycle, basic requiremets are completely fulfilled while bous features are implemeted as much as possible. I order to achieve this, IDS data model desig should fulfill all the basic requiremets while remai pretty scalable to icorporate add-i fuctioality. 2 User Requiremet Aalysis This sectio provides a aalysis of all the user requiremets stated i Project Pla Sectio 2.3. It categorizes user requiremets ito 3 categories: User specified, Bous, Advaced. Each category directly relates to certai priority i IDS implemetatio. The priorities of all the requiremets are show i Table. Table Requiremet Priority Ico Requiremet Category Priority US User Specified Customer required, must deliver B Bous Team will try to deliver whe additioal time ad resources are available A Advaced Ulikely to deliver For each requiremet, a ID is assiged to facilitate trackig dow user requiremet to specific desig ad implemetatio detail. IDS\ Software_Requiremet_Specificatio.doc 3
2. User Profiles User Group: This olie facility ca be used by ayoe i the Uited States as well as i Caada, but ot available i ay other coutry. The user group may be divided ito two categories.. Exteral users: customers who are orderig drugs. 2. Iteral users: pharmacists who take customer orders ad iquiries over the phoe. Fially, iteral system users are IT persoel resposible for the maiteace of the database. 3. Aget: This refers to a perso who helps a customer to order ay drugs olie ad thus, get commissio from the order. 2.2 User Requiremets for Exteral User ID Category Descriptio ER US Idetificatio through user id ad password ER2 US To maitai (eter/update/delete) prescriptio ad doctor iformatio for patiets coformatio of prescriptio is doe by the IDS staff offlie ER3 US To maitai patiet iformatio icludig password, phoe, shippig address etc. ER4 US To allow for olie etry of drug orders ad trackig of order shippig status ER5 US To maitai (eter/update/delete) patiet medical ad drug histories. ER6 US To be able to use shoppig cart whe makig orders ER7 US To be able to search for drugs based o partial/complete ame (commo/medical) ER8 US To perform quick browsig usig the first letter of drug ames ER9 US To produce a patiet report listig all the orders/prescriptios they have made over a give timeframe. ER0 US To allow a user to save a shoppig cart ad remember it whe they retur to the site. Oe user should have oe ad oly oe shoppig cart. ER B To allow a user to retrieve their forgotte user id/password usig their e-mail address ER2 B To use previous patiet orders to allow a rapid refill of prescriptios (by usig iformatio from the last order(s)) ad iformatio from the prescriptio ER3 B To implemet credit card processig that allows credit cards to be processed o a web site ER4 A To allow a user to place oe order for multiple people at the same shippig address. ER5 A To oly allow multiple people shippig to the same address be implemeted o a family basis 2.3 User Requiremets for Iteral User ID Category Descriptio IR US Idetificatio through user id ad password IR2 US To maitai iformatio o prescriptio drugs icludig suppliers, prices, descriptio ad recommeded dosages by maually modifyig usig the iterface IR3 US To allow a user to eter patiet iformatio to the database give over the phoe idirectly through Iteral User IR4 US To allow a user to eter patiet order iformatio give over the phoe idirectly through Iteral User IR5 US To allow a user to track order status iformatio requested over the phoe IR6 US To produce a quote o drug prices whe drugs were give over the phoe IR7 US To produce a report o all customers curretly i the system IR8 US To produce a report o all order totals o a daily, weekly, mothly, ad aual basis IR9 B To produce a report o reveues o all orders o a daily, weekly, mothly, ad aual basis IR0 B To save order give over the phoe or by the user o the website so that they may be later ordered IR B To maitai drug iformatio ad prices by automatically updatig data based o data i a text file which is compared to existig data i the database IR2 B To produce a sales report that lists the top sellig drugs IR3 B To produce a sales report that lists the customers that have placed the most orders IDS\ Software_Requiremet_Specificatio.doc 4
IR4 B To track the most popular drugs ad make them easier to order o the web site IR5 A To compare the prices of other competitors ad produce a report IR6 A To produce ay advaced report such as a report breakig dow the orders by customer regio 2.4 User Requiremets for Aget ID Category Descriptio AR A allows for affiliates (marketers) to eter customers, orders, ad status iformatio AR2 A To automatically calculate commissios of affiliates usig iformatio i the database AR3 A To produce reports for affiliates showig customer iformatio, order statistics, ad their commissios AR4 A To produce a report summarizig affiliates order iformatio 2.5 Aalysis The rakig of requiremets are doe through Sectio 2.2 ~ 2.4. Notice that may fuctios required are geerally overlapped as show below ad they will affect the order of actual implemetatio. Figure Requiremets Overlap IDS\ Software_Requiremet_Specificatio.doc 5
3 Data Model ad Descriptio 3. Etity Descriptio 3.. Customer They are the mai users of the olie drug store. To be able to use this system the customer must first register with a user ame ad password olie i.e. fill i all their iformatio about prescriptio, doctor iformatio ad order drugs olie. For the purpose of verificatio they will have to mail i their prescriptio. Customer ca update, delete all their iformatio icludig password, address ad phoe umber, etc. 3..2 Aget This refers to a perso who helps a customer to order ay drugs olie ad thus, get commissio from the order the customer paid. 3..3 Supplier A supplier is a compay who supplies drugs. Oe supplier ca supply more tha oe drug. Ad oe drug ca be supplied by more tha oe compay. 3..4 Doctor Each Customer will have oe or more doctors. A doctor ca give more tha oe prescriptio. All the iformatio about a doctor is very importat because the pharmacy staff have to cofirm with the doctor, that the customer has filled i the right prescriptio ad the right amout of refills. 3..5 Accout This icludes Accout Number, Password ad the Type. Type of accout icludes "Customer", "Aget", "Doctor" ad "Admiistrator". 3..6 Prescriptio This is filled by the customer ad cofirmed by the pharmacy staff. It ca also be filled i by a pharmacy staff over phoe. A prescriptio should have doctor s cofirmatio, the drug ame, refills if ay, ad customer's ame. 3..7 Drug The mai data stored for this table is all the iformatio about the drugs. Some drugs have other medical ames, side effects etc. So before ay customer orders the drug olie he or she ca read all the descriptio that is provided alog with the drug ame. Ay customer ca also fid out about ay drug that is ew i the market. IDS\ Software_Requiremet_Specificatio.doc 6
3..8 Order Each customer ca place a order olie by sigig i or also place a order via a staff member (admiistrator, also kow as iteral user) by phoe. They ca fill i the prescriptio ad order for the required drugs. All the members of a sigle family ca place a sigle order (several orders shipped to oe address). Additioal data stored will iclude Date (o what date it was placed), Trackig umber, which will help the customer to track their orders, Total, Shippig Status, which will be helpful to fid the curret status of the order, Shippig Date (whe it was shipped out ), Shippig Fees, the Address where the order was shipped etc. 3..9 MedicalHistory This will be helpful for the staff to look for ay particular drug, if they kew about a customer s medical backgroud, i.e what drug he was takig or what illess he was sufferig from. Note: the implemetatio detail of this etity is delayed for later stage of developmet, IDS Team- kows more about what should costitute a Medical History. 3..0 ShoppigCart Wheever a customer logs i his accout ad starts to order the drugs, it should be easy for him to remember what all he wats to order. So use of a shoppig cart will make order etry easier for the customer. Note: the shoppig cart referred here is ot a whole buch of drugs that customer bought but ot paid; istead, for every kid of drug the customer bought yet paid, there is a shoppig cart costructed for this particular product cotaiig the exact iformatio about this drug (uit price, quatity) whe the customer added it to the shoppig cart. Each time a customer fiishes with his order, goes to the checkig out page ad makes the paymet, the shoppig cart iformatio is saved i Order ad OrderDetails. 3.2 Etity ad Attributes Etity Attributes Customer cid, cname, sex, birthdate, chome, coffice, ccell, cstreet, ccity, cstate, czip, cemail Aget aid, aname, aphoe, astreet, acity, astate, azip, aemail Supplier sid, sname, sphoe, swebsite, sstreet, scity, sstate, szip, semail Doctor docid, docname, docaffiliatio, docphoe, docstreet, doccity, docstate, doczip, docemail Accout acnumber, acpasswd, actype Prescriptio pid, cid, docid, pdate, pdisease, pcofirm Drug did, upc, dname, dmedname, ddiscriptio, drecdosage, duitprice Order oid, odate, otrack, ototal, oshstatus, oshdate, oshfee, ostreet, ocity, ostate, ozip, oname MedicalHistory mid, mdate, mdisease ShoppigCart dname, oduitprice, odquatity, odsubtotal IDS\ Software_Requiremet_Specificatio.doc 7
3.3 Relatioships There is a relatioship Has betwee Customer ad medical History. A customer s health iformatio is stored i multiple MedicalHistory There is a relatioship Reserve betwee Customer ad Shoppig cart. A customer ca place items i the shoppig cart ad pay for all of them at the ed of shoppig. Notice that as the shoppig cart is implemeted o oe cart per drug level, oe customer might have multiple shoppig carts at the same time. There is a relatioship PreOrder betwee Drug ad Shoppig cart. Each shoppig cart relates to a particular kid of drug ordered by a particular customer ad records the exact iformatio of the drug (ame, uitprice, etc.) at the time whe customer placed it ito shoppig cart. There are two relatioships Write ad Cofirm betwee Doctor ad Prescriptio. Doctor writes prescriptios for a patiet (customer). He specifies what drug to be take, its dosage ad refills if ay. A doctor ca write more tha oe prescriptio. Doctor also eeds to cofirm the prescriptios etered by the customer ad saved i IDS. There is a relatioship Place betwee Customer ad Order. A customer places a order. It ca be more tha oe order for each customer. Order will have order details as well as all shippig details. There is a relatioship Cotai betwee Order ad Drug. A order cotais of multiple drugs. Whe a customer places a order, he fills the drug details i.e which drug he wats to order. Oe order ca cotai may drugs. There is a relatioship Supply betwee Drug ad Supplier. A supplier is a compay that supplies drugs. Oe supplier ca supply may drugs, ad oe drug ca be supplied by may suppliers. There is a relatioship Comprise betwee Prescriptio ad Drug. A prescriptio cotais multiple drugs. Whe a doctor writes prescriptio for a patiet, it cotais drug ad dosage, quatity, refill for that particular drug. Oe prescriptio ca have may drugs while a particular drug may appear i multiple prescriptios as well. There is a relatioship Has betwee Customer ad prescriptio. A customer ca fill i the prescriptio which has all the details about the drug ad the doctor who wrote the prescriptio. There is a relatioship Logi betwee Customer ad Accout, it also exists betwee Aget ad Accout. Each customer/aget ca have a sigle accout to sig i IDS. 3.4 Complete Data Model Figure 2 shows the UML versio of the complete data model. Figure 3 shows the traditioal ER diagram equivalet of the same data model withi IDS. IDS\ Software_Requiremet_Specificatio.doc 8
Total Supplier sid (PK) sname swebsite sphoe saddress sstreet scity sstate szip semail..* Prescriptio pid(pk) pdate pdisease pcofirm? Write Supply? Comprise?.... sdquatity sdprice sdsubtotal pdquatity pddosage pdrefill pdexpire Doctor docid(pk) docname docaffiliatio docphoe docemail docaddress docstreet doccity docstate doczip? Cofirm..*..* ShoppigCart odname oduitprice odquatity odsubtotal Drug did (PK) upc dcomname dmedname ddescriptio duitprice drecdosage? Has Preorder?..? Reserve..*..? Cotai price quatiy.. Customer cid (PK) cname sex birthdate caddress cstreet ccity cstate czip cphoe chome coffice ccell cemail.. Order Place? oid (PK) odate ototal oshfee oaddress oname ostreet ocity ostate ozip oshdate oshstatus otrack Has?.. Logi?.... Figure 2 Data Model (UML) MedicalHistory mid (PK) mdate mdisease Accout acnumber (PK) acpassword actype....?recommed? Logi Aget aid(pk) aname aphoe aemail aaddress astreet acity astate azip 0.. IDS\ Software_Requiremet_Specificatio.doc 9
IDS\ Software_Requiremet_Specificatio.doc 0 Customer Order ShoppigCart MedicalHistory mid cemail acpasswd sname ccity mdate sid cname cid mdisease AcName Has sex birthdate caddress aphoe aname aid pdexpire pdate otrack odate cphoe oid chome coffice ccell cstreet cstate Reserve pid docaffiliatio Price Quatity oname oshfee oshstatus swebsite sphoe Total odsubtotal oshdate odquatity oduitprice odname Place Drug Supplier scity saddress sstreet sstate Supply Cotai pdrefill pddosage pdquatity duitprice drecdosage ddescriptio dmedname did sdsubtotal sdprice sdquatity upc dcomname Aget Recommed pcofirm docphoe docname docid ototal ocity oaddress ostreet ostate Prescriptio Doctor doccity docaddress docstreet docstate Write Comprise Has pdisease m m m Logi czip Accout actype Logi ozip acity aaddress astreet astate azip aemail doczip docemail szip semail caccout aaccout Preorder Figure 3 Data Model (ERD)
4 Data Model Explaatio This sectio icludes all the differet types of trasactios like update, delete, eter some data ad retrieve data usig SQL Queries. We ca achieve these thigs as follows.. List the details of all the customers. I this above statemet we ca see that we eed to retrieve all the iformatio about the customer from the etity Customer. 2. Update or Delete ay prescriptio ad doctor iformatio for patiets. For this we eed to update or delete iformatio from etity Doctor, Prescriptio. So we ca see that there is a relatio betwee doctor ad prescriptio. 3. Eter the details of the ew customer. Isert data ito all fields of the Customer etity. Similarly other thigs ca be etered ito ay of the other tables, like eter ew patiet order iformatio. The eter the details of the ew aget. Eter the details of the ew supplier that may supply ay drug. Eter the details of the ew doctor for a old or ew customer. Eter the details of the ew prescriptio iformatio for customer. 4. Perform searches for drugs based o ame. For gettig the right result we ca see that we have to search i the Drug etity for the give ame or part of the ame. 5. Produce a patiet report listig all the orders/prescriptios they have made over a give timeframe. For this particular query we will have to perform a joi betwee Customer, Order ad Prescriptio. For such queries we will have to relate all three tables together. 6. Produce a quote o drug prices whe drugs were give over the phoe. We should search UitPrice for that drug from the Drug table. Similarly most of the US fuctios specified i Sectio2 ca be doe through the data model created. As further discussio o them would actually go to a more low level desig issue, we delay the detail explaatio of the model ito High Level ad Low Level Desig. 5 Software Iterface Descriptio 5. Exteral Machie Iterface No exteral machie iterface requiremet is available of IDS. 5.2 Exteral System Iterface IDS Team is usig SQL server as back-ed database o idealab5.cs.uiowa.edu. Developmet is coducted maily usig JDBC through coectio with idealab2.cs.uiowa.edu. It s possible to debug locally ad test o idealab2 usig file trasfer. The whole website ca be visited publicly ad fial testig will be doe exterally to achieve maximum efficiecy. 5.3 Huma Iterface A ope-ed prototype of IDS homepage is provided i Figure 2 for better uderstadig of the fial software product. IDS\ Software_Requiremet_Specificatio.doc
Figure 4 IDS Homepage Prototype IDS\ Software_Requiremet_Specificatio.doc 2