SystemAnalysisandDesign

Assignment1

s2954932
MatthewOwenJones

TableofContents
Introduction....3
Background....3
UseCases.........4
UseCaseDiagram.......6
ActivityDiagram....8
UseCaseDescription......9
DomainModelClassDiagram.........10
SystemSequenceDiagram.........11
Conclusion...12

Introduction:
ThisreportdeeplyanalysestheQBSstoresystemsandanalysesalloftheprocessesandalltheactivitiesthatthesystem
performs.Furthermore,thisreportprovidesdetailedexamplesofalloftheusecasesandactivitiesperformedbythesystem.
Also,thisreportprovidesadetaileddesignofthesystemincludingusecasediagrams,anactivitydiagram,systemsequence
diagramandadomainmodelaclassdiagram.Finallythisreportgoesintogreatdetailontheusecasecustomerbuysitems
andthengoesintomoredetailonthesameusecasebutspecifiedforcontractedcustomers.

Background:
TheQBSstoreshavetwokindsofcustomers:generalpublicandcontractors.Thegeneralpubliccustomersmustsupplycredit
cardinformationinordertopurchaseanyitems.Theirname,phonenumberandemailaddressarealsostoredfor
warranty/refundpurposes.Inaddition,contractorshaveanaccountcreatedbyaQBSclerksothattheycangetaspecific
discount.Eachaccountthuscreatedhasauniqueidentifierandalsostoresthecontractorscompanyname(ifany),thecurrent
creditlimitandthelastpurchasedateandamount.Thetransactionsforgeneralpublicandforthecontractorsareaccomplished
byaQBSclerkwhoscanseachitemandaddsthemtothepurchase.Itemsthatcannotbesuccessfullyscannedareaddedto
thepurchasebyhand.

Ifoneormoreitemsarenotpresentontheshelfandasearchrevealsthatthestockleveliszero,theyareaddedonanorder
thatiscreatedbytheQBSclerkonbehalfofthecustomer(eithergeneralpublicorcontractor).Eachorderthuscreatedhasa
uniqueidentifierandstoresordercreationdate,totalamountandstatus(e.g.pending,closed...).

Thename,priceandstockleveloftheitemsstockedbyQBSarerecordedinthesystemofinteresttogetherwiththeitemtype.
Itemsareproducedbyandsourcedfromamanufacturer,whosenameandcountryarerecordedinthesystem.Thedateofthe
lastpayment,theopenbalanceandthedateofthenextshipmentofitemsarealsorecordedforeachmanufacturer.Notethat
themanufacturerhasnodirectaccesstothesystemofinterest.Also,atthisstagethegeneralpublicandcontractorscan
searchitemsonlinebutcanonlypurchasetheminstore.

Thestocklevelsofeachitemarechangedbythesystemwitheachpurchase.Howevertheselevelsneedtobemanually
updatedbyaclerkincertaincasessuchasshipmentsofitemsfrommanufacturers,refunds,exchanges,etc.

Section1UseCases:
UseCase

Description

Searchforitem

Customersearchesforitemeitheronlineorinstore

Gethelplookingforitem

CustomergetshelpfromQBStofinditem,ifnoitemsfound
andorderismade

SupplyCreditCardInformation

Thisusecaseisforthegeneralpublic.Thegeneralpublic
havetosupplytheircreditcardinformationpriorto
purchasinganyitems.

StoreCustomerDetails

Thisusecaseisforallcustomers(generalpublicand
contractors).Itstoresthecustomersname,phonenumber
andemailaddressforwarrantyorrefundpurposes.

Createaccount

Thisusecaseisforcontractors.TheQBSclerkcreatesan
accountforthecontractor.Theaccountconsistsofaunique
identifier,thecontractor'scompanyname,thecurrentcredit
limitandthelastpurchasedateandamount.

Additemstopurchase

TheQBSclerkaddsitemstothepurchasebyeither
scanningthemormanuallyaddingthem.

Buyitems

Whenitemsarebought,thedetailsofthatitemarestoredto
thesystem,thisincludestheitemname,priceandquantity.
Also,thisusecaseinvolvestheQBSclerkscanningitems,
eithergatheringthegeneralpublicsinformationandcredit
cardinformationorscanningtheuniqueidentifierofthe
contractorsaccount.Whenthecontractorscardisscanned,
numerouschecksaremadebythesystemtocheckthe
accountdetails,toupdatetheaccountandtoprovidea
discountfortheitems.Also,thestocklevelsofeachitemare
changedwitheachpurchase.Finally,thecustomerpaysfor
theitems.

UpdateAccount

Thisusecaseisforcontractors.Onceapurchasehasbeen
made,thepurchasedateandamountarestoredtotheir
account.

Refund

Thisusecaseisresponsibleforrefundingthecustomerfora
product.

Exchange

Thisusecaseisresponsibleforhandlingexchangesof
productswiththecustomer.

ProduceOrder

ThisusecaseisconductedbytheQBSclerkonbehalfofa
customer.Theclerksearchesthestocklevels,ifthereisno
stockleftofthatitem/sanorderisproducedcontaininga
uniqueidentifier,theordercreationdate,itemdetails,total
amountandstatus.

UpdateStockLevels

Thisusecasechecksthestocklevelsandcreatesordersto
manufacturesinthesystemfortheitems.Also,theclerk
addsitemsreceivedfromshipment,exchangeorrefundto
thesystem.

UpdateManufacturers

Store/Updatemanufacturesinsystem.Thisusecase
recordsthedateofthelastpayment,theopenbalanceand
thedateofthenextshipment.

Section2UseCaseDiagram:

Section3Activitydiagramforacontractorcustomerbuysitems:

Section4UseCaseDescription
:

Usecasename:

Buyitems.

Scenario:

Contractorcustomerbuysitems.

Triggeringevent:

Customerwantstopayforitems.

Briefdescription:

Clerkscansitems,storeitemdetails,updatestocklevels,scancontractorsaccountcard,
verifyaccount,checkdetails,producediscount,calculatebill,contractorpaysforitems,
storepaymentdetailsandupdatecontractorsaccount.

Actors:

QBSClerk,contractor.

Relatedusecases:

None.

Stakeholders:

Shipping,Manufacturers,Clerk,QBSstaff,contractors.

Preconditions:

Customermusthaveanaccountandtheiruniqueidentifierforthataccount,Accountmust
bevalid,accountlimitmustnothavebeenreachedandmustbewithinrangeofthis
purchase.

Postconditions:

Customersaccountisupdatedwiththecostsofthepurchaseandthedate,limitis
updated.Thestocklevelsofitemsareupdate.

Flowofactivity:

Actor
1.Customerwantstopayforitems.

2.Clerkscanscontractorscard.

3.Customerpaysforitems.

System
1.1.Clerkaddsitemstopurchase.
1.2.Systemupdatesstocklevels.

2.1.Systemverifiesaccountdetails.
2.2.Systemchecksaccountdetails.
2.3.Systemproducesdiscount.
2.4.Systemcalculatesbill.

3.1Systemrecordscustomerspurchase
details.
3.2Systemupdatescustomeraccount
details.

Exceptionconditions:

1.2.Iftheitemisdamaged,getanewitemfromstock,ifnostockleftplaceanorder.
2.1.Noaccountfound,chargefullfee(nodiscount)andgetcreditcardinfoandpersonal
details.
2.2.Accountlimitreached,canceltransactionandrestorestocklevels.
3.Customerdoesnthaveenoughmoney,canceltransactionandrestorestocklevels.

Section5DomainmodelclassdiagramforContractorcustomer
buysitems
:

Section6SystemsequencediagramforContractorcustomerbuys
items:

Conclusion:
ThisreportdeeplyanalysedtheQBSstoresandprovidedmanydiagramstodisplayalloftheactivitiesandfunctionsofthe
system.Alloftheusecasesweredefinedanddescribedinsection1(page4),thenfromsection2(page6)thisreportfocused
ontheusecasecustomerbuysitem.Section2providedtwousecasediagramsforacustomerbuyingitemsfromtheQBS
store,theinteractionwiththesystemanddifferentstakeholders.Fromsection3(page8)thisreportfocusedonthescenarioa
contractorbuysitems.Section3providedadetaileddiagramofalltheactivitiesperformedbythesystemandstakeholdersand
howtheyinteractwiththesystem.Section4(page9)providedafullydevelopedusecasediagramforthescenarioa
contractedcustomerbuysitems.Thissectiondisplayedeveryfactorinvolvedwiththatscenario.Section5(page10)provideda
fullydevelopeddomainmodelclassdiagramforthesamescenario.Thedomainmodeldisplayedalloftheclasses,allofthe
functionsandhowtheclassesareinvolvedwitheachother.Section6(page11)displaysasystemsequencediagramofthe
samescenario.Thesystemsequencediagramdisplayedtheinteractionwiththeclerkandthesystemwhenacontracted
customerwantstobuyitems.Thediagramshowedallofthefunctionsandprocessesoftheclerkandthesystemforthatactivity
andthelifecycleoftheactivity.ThisreportdeeplyanalysedtheQBSstoresandprovidedmanydiagramstodisplaythe
functionalityofthesystem.