Chapter 10 Tutorial-style Review and Reinforcement

Transcription

1 MACIASZEK, L.A. (2007): Requirements Analysis and System Design, 3 rd ed. Addison Wesley, Harlow England ISBN Chapter 10 Tutorial-style Review and Reinforcement Pearson Education Limited 2007

2 Topics 1. Use case modeling 2. Activity modeling 3. Class modeling 4. Interaction modeling 5. Statechart modeling 6. Implementation models 7. Object collaboration design 8. Window navigation design 9. Database design Chapter 10 (Maciaszek - RASD 3/e) 2

3 Tutorial OnLine Shopping Buying computers over Internet using the manufacturer s web page. Computers classified into servers, desktops and portables. Customer can select standard configuration or can configure his/her own configuration. For each new configuration, the system can calculate price. To place order, the customer must fill out the shipment and payment information. The system sends a confirmation message to the customer with details of the order. Customer can check the order status online at any time. Moreover, the system needs to verify the customer s credentials and payment method, request the ordered configuration from the warehouse, print an invoice, and request the warehouse to ship the computer to the customer. Chapter 10 (Maciaszek - RASD 3/e) 3

4 1. Use case modeling

5 Use case modeling - actors Consider the following requirements: 3. The customer may choose to order a computer online or may request that the salesperson contact him/her to explain order details, negotiate the price, etc. before the order is actually placed. 7. The warehouse obtains the invoice from the salesperson and ships the computer to the customer. Customer Salesperson Warehouse Chapter 10 (Maciaszek - RASD 3/e) 5

6 Use case modeling use cases Consider the following requirements: 3. The customer may choose to order a computer online or may request that the salesperson contact him/her to explain order details, negotiate the price, etc. before the order is actually placed. 7. The warehouse obtains the invoice from the salesperson and ships the computer to the customer. Order Configured Computer Request Salesperson Contact Print Invoice Chapter 10 (Maciaszek - RASD 3/e) 6

7 Display Standard Computer Configuration Build Computer Configuration Use case Order Configured Computer diagram Verify and Accept Customer Payment Customer <<extend>> Display Order Status Print Invoice Request Salesperson Contact Warehouse Inform Warehouse about Order Salesperson Chapter 10 (Maciaszek - RASD 3/e) 7

8 Documenting use cases Use case Brief description Actors Preconditions Main flow Alternative flows Postconditions Order configured computer Customer Order Configured Computer This use case allows a Customer to enter a purchase order. This includes providing a shipment and invoice address as well as payment details. Customer points Internet browser to the computer manufacturer s order entry web page. The page displays the details of a configured computer together with its price. The use case begins when the Customer decides to order... The system requests that the Customer enters... The Customer chooses the Purchase function... The system assigns a unique order number... The system s the order number and... The Customer activates the Purchase function before... The Customer chooses the Reset function to revert to... If the use case was successful, the purchase order is recorded in the system s database. Otherwise, the system s state is unchanged. Chapter 10 (Maciaszek - RASD 3/e) 8

9 2. Activity modeling

10 Actions 3 The Customer chooses the Purchase (or similarly named) function to send the order to the manufacturer. Order Configured Computer Get Purchase Details 4 5 The system assigns a unique order number and a customer account number to the purchase order and it stores the order information in the database. The system s to the Customer the order number and the customer number, together with all order details, as the confirmation of the order s acceptance. Store Order Order Details Get Purchase Details Store Order Order Details Chapter 10 (Maciaszek - RASD 3/e) 10

11 Activity diagram Order Configured Computer Display Current Computer Get Order Request [ timeout ] Display Purchase Form Store Order [ incomplete ] [ OK ] Get Purchase Details Order Details Chapter 10 (Maciaszek - RASD 3/e) 11

12 3. Class modeling

13 Classes 6 7 The details of the transaction, including an order number and a customer account number, are ed to the customer, so that the customer can check the status of the order online. The warehouse obtains the invoice from the salesperson and ships the computer to the customer. Order, Customer, (OrderStatus) Invoice, (Salesperson), (Shipment),Computer, Customer Order Customer Invoice Computer OrderStatus Shipment?? Do we need the Shipment class if we know that the shipment is the warehouse responsibility and it is therefore out of the scope? Is OrderStatus a class or an attribute of Order? Is Salesperson a class or an attribute of Order and Invoice? Chapter 10 (Maciaszek - RASD 3/e) 13

14 Attributes Customer customername : String customeraddress : String phonenumber : String address : String Order ordernumber : String orderdate : Date ship Ad dress : String ordertotal : float orderstatus : String salespersonname : String Invoice invoicenumber : String invoicedate : Date invoicetotal : float Computer computername : String standardprice : float Chapter 10 (Maciaszek - RASD 3/e) 14

15 Associations Customer Computer 1 0..n ConfigurationItem Order n Payment Invoice 1..n ConfiguredComputer Chapter 10 (Maciaszek - RASD 3/e) 15

16 Aggregations Computer Customer 1 1..n 0..n Order n ConfigurationItem 1..n 1..n Payment Invoice ConfiguredComputer Chapter 10 (Maciaszek - RASD 3/e) 16

17 Class diagram Customer customername : String customeraddress : String phonenumber : String address : String n Order ordernumber : String orderdate : Date shipaddress : String ordertotal : float orderstatus : String salespersonname : String n Invoice invoicenumber : String invoicedate : Date invoicetotal : float 1..n ConfigurationItem itemtype : String itemdescr : String 1..n Computer computername : String Payment paymentmethod : String datereceived : Date amountreceived : float ConfiguredComputer configuredprice : float S tand ardcomputer standardprice : float Chapter 10 (Maciaszek - RASD 3/e) 17

18 4. Interaction modeling

19 Custom computer configuration webpage Chapter 10 (Maciaszek - RASD 3/e) 19

20 Configuration summary webpage Chapter 10 (Maciaszek - RASD 3/e) 20

21 Sequence diagram Display Current Configuration : P CustomConfiguration : EComputer : EConfigurationItem 1. submit() 1.1. getcurrentconf() getcomputername() getitemdescr() getprice() 1.2. new(currentconf) : PConfigurationSummary display() Chapter 10 (Maciaszek - RASD 3/e) 21

22 Communication diagram Display Current Configuration 1. submit() getcomputername() getprice() 1.1. getcurrentconf() : PCustomConfiguration : EComputer 1.2. new(currentconf) display() getitemdescr() : PConfigurationSummary : EConfigurationItem Chapter 10 (Maciaszek - RASD 3/e) 22

23 Class methods PCustomConfiguration submit() E Config ura tionitem itemtype : String itemdescr : String getitemdescr() 1..n PConfigurationSummary PConfigurationSummary(currentConf) display() EComputer computername : String getcurrentconf() getcomputername() getprice() EStandardComputer co nfigured Price : floa t EConfiguredComputer standardprice : float Chapter 10 (Maciaszek - RASD 3/e) 23

24 5. State machine modeling

25 States and transitions E Invoice Unpaid partial payment Partly Paid final payment final payment Fully Paid Chapter 10 (Maciaszek - RASD 3/e) 25

26 Statechart diagram EOrder Pending New Order stock not available Back Order stock available[ ship date in future ] Future Order stock available[ ship date in future ] [ canceled ] stock available[ ship date now ] / configurecomputer Canceled [ canceled ] Ready to Ship ship[ accepted ] Filled Chapter 10 (Maciaszek - RASD 3/e) 26

27 6. Implementation models

28 Subsystems id Subsystems Presentation Control Bean Mediator Entity Resource Chapter 10 (Maciaszek - RASD 3/e) 28

29 Packages (1 of 2) Chapter 10 (Maciaszek - RASD 3/e) 29

30 Packages (2 of 2) Chapter 10 (Maciaszek - RASD 3/e) 30

31 Components id Components ProductDisplay ProductList Configuration Purchase OrderTracking Chapter 10 (Maciaszek - RASD 3/e) 31

32 Nodes deployment diagram dd Deployment Model Client Browser HTTP Web Server JDBC, SQLJ Database Server Chapter 10 (Maciaszek - RASD 3/e) 32

33 7. Object collaboration design

34 Use case document Chapter 10 (Maciaszek - RASD 3/e) 34

35 Requirements management in a CASE tool Chapter 10 (Maciaszek - RASD 3/e) 35

36 GUI prototype Chapter 10 (Maciaszek - RASD 3/e) 36

37 Sequence diagram Chapter 10 (Maciaszek - RASD 3/e) 37

38 Design-level class diagram Chapter 10 (Maciaszek - RASD 3/e) 38

39 8. Window navigation design

40 User experience (UX) elements <<screen>> Computer Order * * <<input form>> Order Entry <<compartment>> Command Button <<screen>> Order Confirmation <<compartment>> Database Exception <<input form>> Incomplete Order Entry Chapter 10 (Maciaszek - RASD 3/e) 40

41 Behavioral UX collaboration Chapter 10 (Maciaszek - RASD 3/e) 41

42 Structural UX collaboration <<screen>> Computer Order * 1 <<input form>> Order Entry +contact details +explanations +invoice address +order summary +payment method +salesperson name +shipment items +title +$display explanations() +$display order summary() +$navigate to() +enter contact details() +enter invoice address() +enter payment method() +enter salesperson name() +enter shipment items() +$navigate to() <<compartment>> Command Button +cancel +submit 2 +press cancel() +press submit() <<input form>> Incomplete Order Entry +invitation to complete +missing items +$navigate to() 0..1 <<screen>> Order Confirmation +confirmation message +$navigate to() <<compartment>> Database Exception +exception message * +$navigate to() Chapter 10 (Maciaszek - RASD 3/e) 42

43 9. Database design

44 DB schema StandardComputer ConfiguredComputer computer_id computer_name standard_price CHAR(15) VARCHAR2(50) NUMBER <pk> computer_id computer_name configured_price CHAR(15) VARCHAR2(100) NUMBER <pk> computer_id = computer_id 0..* computer_id = computer_id 0..* ConfItemToStdComp ConfItemToConfComp computer_id item_id CHAR(15) INTEGER <pk,fk1> <pk,fk2> computer_id item_id CHAR(15) INTEGER <pk,fk1> <pk,fk2> 0..* item_id = item_id 0..* item_id = item_id ConfigurationItem item_id item_type item_descr INTEGER VARCHAR2(60) VARCHAR(200) <pk> Chapter 10 (Maciaszek - RASD 3/e) 44

45 DB schema with referential integrity constraints StandardComputer ConfiguredComputer computer_id computer_name standard_price CHAR(15) VARCHAR2(50) NUMBER <pk> computer_id computer_name configured_price CHAR(15) VARCHAR2(100) NUMBER <pk> Upd(R); Del(C);cpa Upd(R); Del(C);cpa 0..* 0..* ConfItemToStdComp ConfItemToConfComp computer_id item_id CHAR(15) INTEGER <pk,fk1> <pk,fk2> computer_id item_id CHAR(15) INTEGER <pk,fk1> <pk,fk2> 0..* Upd(R); Del(C) 0..* Upd(R); Del(C);cpa ConfigurationItem item_id item_type item_descr INTEGER VARCHAR2(60) VARCHAR(200) <pk> Chapter 10 (Maciaszek - RASD 3/e) 45

46 Referential integrity design payment_id payment_method date_received amount_received Payment CHAR(12) VARCHAR(40) DEC NUMBER(8,2) <pk> invoice_number invoice_date invoice_total Invoice CHAR(12) DATE NUMBER <pk> Upd(R); Del(R) Upd(R); Del(N) Order order_number customer_number status_id payment_id invoice_number order_date ship_address order_total salesperson_name CHAR(12) CHAR(15) CHAR(2) CHAR(12) CHAR(12) DATE VARCHAR2(120) NUMBER VARCHAR2(30) <pk> <fk1> <fk2> <fk3> <fk4> null null null Chapter 10 (Maciaszek - RASD 3/e) 46

47 Summary use case modeling activity modeling class modeling interaction modeling statechart modeling implementation models object collaboration design window navigation design database design Chapter 10 (Maciaszek - RASD 3/e) 47