RUP(1)

(RUP)2009.12RUPUMLRUPRUPRUPRUPRUPUML1UMLUML,:1()--“”,:ActorUsecaseUsecase--,:--,,:“”“”.UML8,UML””!.\.UML4,,UML4””!“/”\\12()UMLUML2UML14,:USECASE68.:usecase,.,UML2UMLRUP;;,RUPUML“”ActorUsecaseUSECASEUsecaseRUPRUP1RUP:“”.:--“”--RUP----2RUPUseCaseUSECASEUSECASERUP()()RUPtheinceptionphasetheelaborationphasetheconstructionphasethetransitionphase()--------“”.--:;()RUP.:“”-;...objectives.“”.----.--.;,/./.RUP1,.RUP---USECASE2-31)2)3)1)2)3)1):USECASEactor42):USECASE-USECASE-USECASE3)-Feature--Usecase-usecases(1)(////),,Feature,.::itemshrinks100A15,:USECASEUSECASE1USECASEUSECASE2USECASE3USECASEActor--Status(/Priority(e.g.,critical,important,orancillary)(2),-.:1manipulatethingReal-worldobjectsEventsOrderdateofsubmissiondeliveryaddressItemdescriptionpicturecostInvoiceamountdateofsubmissionlastdateofpaymentAccountbalanceowner1..*payable1..*buyer1seller1:Order,Invoice,Item,andAccount,,.:22•usecase.USECASE,usecasebusinessprocesses,actorscustomers.:•interiorworkersbusinessentitiesworkunitsusecaseusecaseBusinessentity:something,usecaseworkunit:workers:usecase.:Businessentitiesworkunit,usecase(3),1Use-Case2Use-Case-Use-CaseactorsusecasesUse-CasesystemUse-CasemodelActorUsecase**1TheUse-Casesystemdenotesthetop-levelpackageofthemodel3SystemAnalysisresponsibleforUse-caseSpecifierresponsibleforUser-interfacedesignerresponsibleforArchitectresponsibleforusecasemodelActorGlossaryUsecaseUserinterfaceprototypeArchitectureDescription4USECASE1:ActorUSECASE1:Actor-,actors•workeractor•actor,actor-actoractoractorsNote:actoractoractors,2actors:actoractorsactor“”actors,2actorsactor“”actor“”actor2:ActorsActorsactors,“”convey,Actorsactor:theBuyer,SellerBuyerABuyerrepresentsapersonwhoisresponsibleforbuyinggoodsorservicesasdescribedinthebusinessusecaseSales:fromOrdertoDelivery.Thispersonmaybeanindividualorsomeonewithinabusinessorganization.TheBuyerofgoodsandservicesneedtheBillingandPaymentSystemtosendorderandtopayinvoices.SellerASellerrepresentsapersonwhosellsanddeliversgoodsorservices.TheSellerusesthesystemtolookfornewordersandtosendorderconfirmations,invoices,andpaymentreminders.--,“”“”;,--/,3:UseCase--••••--complete.(resultofvalue).(particularactor):“”4:43UAECASE“PayInvoiceUseCases“TheusecasePayInvoiceisusedbyaBuyertoscheduleinvoicepayments.ThePayInvoiceusecasetheneffectsthepaymentontheduedate.”“Beforethisusecasecanbeinitiated,theBuyerhasalreadyreceivedaninvoice(deliveredbyanotherusecasecalledInvoiceBuyer)andhasalsoreceivedthegoodsorservicesordered.:1.Thebuyerstudiestheinvoicetopayandchecksthatitisconsistentwiththeoriginalorder.2.TheBuyerschedulestheinvoiceforpaymentbythebank.3.Onthedaypaymentisdue,thesystemcheckstoseeifthereisenoughmoneyintheBuyer’saccount.Ifenoughmoneyisavailable,thetransactionismade.”1:--[]:--[]2:usecasePriority12[]ArchitectUseCasemodel[outlined]SupplementaryRequirementsGlossaryArchitectureDescription[viewoftheusecasemodel]PrioritizedUseCases--:;--;--,3:UseCaseusecaseactorsUsecaseSpecifierUseCasemodel[outlined]SupplementaryRequirementsGlossaryUseCase[detailed]DetailaUseCaseTheresultisadetaileddescriptionofaparticularusecaseintextanddiagram.:usecaseusecaseusecaseFlowofEvents“PathsofthePayInvoiceUseCasePrecondition:Thebuyerhasreceivedthegoodsorservicesorderedandatleastoneinvoicefromthesystem.Thebuyernowplanstoscheduletheinvoice(s)forpayment.FlowofEventsBasicPath1Thebuyerinvokestheusecasebybeginningtobrowsetheinvoicesreceivedbythesystem.Thesystemchecksthatthecontentofeachinvoiceisconsistentwithorderconfirmationsreceivedearly(aspartoftheConfirmOrderusecase)andsomehowindicatesthistothebuyer.Theorderconfirmationdescribeswhichitemswillbedelivered,when,where,andatwhatprice.2Thebuyerdecidestoscheduleaninvoiceforpaymentbythebank,andthesystemgeneratesapaymentrequesttotransfermoneytotheseller’saccount.Notethatabuyermaynotschedulethesameinvoiceforpaymenttwice.3later,ifthereisenoughmoneyinthebuyer’saccount,apaymenttransactionismadeonthescheduleddate.Duringthetransaction,moneyistransferredfromthebuyer’saccounttotheseller’saccount,asdescribedbytheabstractusecasePerformTransaction(whichisusedbyPayInvoice).Thebuyerandthesellerarenotifiedoftheresultofthetransaction.Thebankcollectafeeforthetransaction,whichiswithdrawnfromthebuyer’saccountbythesystem.4Theusecaseinstanceterminates.AlternativePathInStep2,thebuyermayinsteadaskthesystemtosendaninvoicerejectionbacktotheseller.InStep3,ifthereisnotenoughmoneyintheaccount,theusecasewillcancelthepaymentandnotifythebuyer.Post-condition:Theusecaseinstanceendswhentheinvoicehasbeenpaidorwhentheinvoicepaymentwascanceledandnomoneywastransferred.”12Step13Step1-4)4Step4567(Step2Step3),8(Step3),:/usecaseusecase,———;—4:usecasesusecase5:UseCase:actorsusecases,usecaseusecaseusecase•usecaseusecase•usecaseadditionaloroptionalusecaseBuyerSellerPayInvoicePayInvoicePerformTransaction2usecasePerformTransactionBuyerSellerPayInvoicePayInvoicePayOverdraftFee2usecasesextendPerformTransactionPayOverdraftFeeusecaseusecasesinclude:realizationrefining[]RUP()worktobedonere