RUPUML RUP RUP RUP RUP

Size: px

Start display at page:

Download "RUPUML RUP RUP RUP RUP"

派花
7 years ago
Views:

1 (RUP)

2 RUPUML RUP RUP RUP RUP

3 1 UML RUPUML UML,: 1() --,:

4 --,: Actor Use case Use case

5 --,,:. UML8,UML!. \.

$. \.$

6 UML4,, UML4! / \\ 12()

$\\ 12()$

7 UML UML

8 2 UML14,: U SE C A SE

9 6 8. : use case

10 ,.,UML

11 2 UMLRUP ; ;

12 RUP Actor Use case USE CASE Use case, RUP UML

13 1 RUP RUP :. : RUP

14 2 RUP Use Case USE CASE

15 RUP USE CASE

17 ( )( )

19 RUPthe inception phase the elaboration phase the construction phase the transition phase

20 ()

21 --. : ;() --

22 RUP.... : -;

23 objectives

25 ;, /. /.

26 RUP 1,. RUP -- -USE CASE

27 2-3 1) 2) 3) 1) 3) 2)

28 1) : USE CASE actor 4 2) :USE CASE -USE CASE -USE CASE

29 3) -Feature - - Use case -

30 (1) (////),,Feature,.: : item shrinks 100 A 15

31 , : USE CASE Actor USE CASE USE CASE1 USE CASE2 USE CASE3 USE CASE

32 - - Status ( / Priority(e.g.,critical, important, or ancillary)

33 (2), -.: 1 manipulate thing Real-world objects Events

34 : Order date of submission delivery address 1..* payable 1..* Item description picture cost Invoice amount date of submission last date of payment : buyer 1 seller 1 Account balance owner Order, Invoice, Item, and Account,,.

35 2 2 use case.use CASE, use casebusiness processes, actorscustomers. :

36 interior workers business entities work units use caseuse case Business entity : something, use case work unit : workers: use case. :Business entities work unit,use case

37 (3), 1Use-Case 1 Use-Case model Use-Case system * * The Use-Case system denotes the top-level package of the model Actor 2Use-Case Use case - Use-Case actors use cases

38 3 System Analysis Use-case Specifier User-interface designer Architect responsible for responsible for responsible for responsible for use case model Actor Glossary Use case User interface prototype Architecture Description

39 4USE CASE 1:ActorUSE CASE 1: Actor -, actors worker actor actor, actor - actor actor actors Note:actor actor

40 actors,2actors : actor actors actor actors,2actors actor actor actor

41 2:Actors Actors actors, convey, Actors actor

42 : the Buyer, Seller Buyer A Buyer represents a person who is responsible for buying goods or services as described in the business use case Sales: from Order to Delivery. This person may be an individual or someone within a business organization. The Buyer of goods and services need the Billing and Payment System to send order and to pay invoices. Seller A Seller represents a person who sells and delivers goods or services. The Seller uses the system to look for new orders and to send order confirmations, invoices, and payment reminders.

43 3:Use Case --, ;, -- /,

44 --

45 -- complete. (result of value). ( particular actor)

46 :

47 4: 43 UAE CASE Pay Invoice Use Cases The use case Pay Invoice is used by a Buyer to schedule invoice payments. The Pay Invoice use case then effects the payment on the due date.

48 Before this use case can be initiated, the Buyer has already received an invoice (delivered by another use case called Invoice Buyer ) and has also received the goods or services ordered.: 1. The buyer studies the invoice to pay and checks that it is consistent with the original order. 2. The Buyer schedules the invoice for payment by the bank. 3. On the day payment is due, the system checks to see if there is enough money in the Buyer s account. If enough money is available, the transaction is made.

49 1: --[]: --[]

50 2:use case Priority 12 [] Use Case model [outlined] Architect Supplementary Requirements Glossary Prioritized Use Cases Architecture Description [view of the use case model]

51 --: ; --; --,

52 3: Use Case use case actors Use Case model [outlined] Use case Specifier The result is a detailed description of a particular use case in text and diagram. Supplementary Requirements Detail a Use Case Use Case [detailed] Glossary

53 : use case use case use case Flow of Events

55 Paths of the Pay Invoice Use Case Precondition: The buyer has received the goods or services ordered and at least one invoice from the system. The buyer now plans to schedule the invoice(s) for payment. Flow of Events Basic Path 1 The buyer invokes the use case by beginning to browse the invoices received by the system. The system checks that the content of each invoice is consistent with order confirmations received early(as part of the Confirm Order use case) and somehow indicates this to the buyer. The order confirmation describes which items will be delivered, when, where, and at what price.

56 2 The buyer decides to schedule an invoice for payment by the bank, and the system generates a payment request to transfer money to the seller s account. Note that a buyer may not schedule the same invoice for payment twice. 3 later, if there is enough money in the buyer s account, a payment transaction is made on the scheduled date. During the transaction, money is transferred from the buyer s account to the seller s account, as described by the abstract use case Perform Transaction(which is used by Pay Invoice). The buyer and the seller are notified of the result of the transaction. The bank collect a fee for the transaction, which is withdrawn from the buyer s account by the system.

57 4 The use case instance terminates. Alternative Path In Step 2, the buyer may instead ask the system to send an invoice rejection back to the seller.in Step 3, if there is not enough money in the account, the use case will cancel the payment and notify the buyer. Post-condition: The use case instance ends when the invoice has been paid or when the invoice payment was canceled and no money was transferred.

58 1 2 Step 1 3 Step 1-4) 4 Step 4 5 6

59 7 ( Step 2 Step 3), 8 (Step 3),

60 : /

61 use case use case, ;

62 4: use cases use case

63 5 :Use Case : actors use cases, use case use case use case use case use case use caseadditional or optionaluse case

64 Buyer Pay Invoice Seller Perform Transaction Pay Invoice Perform Transaction 2 use case

65 Buyer Pay Invoice extend Perform Transaction Pay Overdraft Fee Seller Pay Invoice Pay Overdraft Fee 2use cases use case use cases include

66 :

67 realization

68 refining []

69 RUP() work to be done result artifacts -List candidate requirements Feature list -Understand system context Business or domain model -Capture functional requirements Use case model -Capture nonfunctional requirements Supplementary requirements or individual use cases (for use case specific req.)

70 use case use case Use-Case Model conditionscapabilities The Use-Case A Use-Case actors use cases 1 Use-Case model Use-Case system * * The Use-Case model and its contents. The Use-Case system denotes the toplevel package of the model Actor Use case

71 use-case use caseuse case use-case - a survey description -a detailed description of each use case. use case use case use-case realization test cases

72 1,,

<4D6963726F736F667420506F776572506F696E74202D20C8EDBCFEBCDCB9B9CAA6D1D0D0DEBDB2D7F92E707074>

<4D6963726F736F667420506F776572506F696E74202D20C8EDBCFEBCDCB9B9CAA6D1D0D0DEBDB2D7F92E707074> 软件架构师研修讲座胡协刚软件架构师 UML/RUP 专家 szjinco@public.szptt.net.cn 中国软件架构师网东软培训中心小故事 : 七人分粥当前软件团队的开发现状和面临的问题软件项目的特点解决之道 : 从瀑布模型到迭代模型解决项