1

2






3



4



5 • .

6 •   •   •   .

7 •   •    •  .

8 • • • .

9 • • • • .

10 • • •    .

11 Requirements definition Requirements checking Domain understanding Prioritisation Requirements specification Conflict resolution Requirements collection Classification .

12 •        .

13 •        .

14 •     .

15 •     .

16 •      .

17 • • • .

18 • • .

19 • • • • • • • Review : Software Specification Review (SSR) • Prototyping : executable model of the system/software .

20 •    •      .

21 • • • • .

22 • • Processes Data Behavior .

23 Process Specificatio Data Flown (PSPEC) Diagram (DFD) Data Object Description ER Diagram Data Dictionary State Transition Diagram (STD) Control Specificatio n (CSPEC) .

|…] : selection / or () : optional “ “ : literal * * : comment/description Vend product (partly) : Name Element Type object [coin | slug](product) data product [ice cream | coffee | candy] data coins 0{[quarter | nickel | dime]}8 data product available [TRUE | FALSE] control [“YES” | “NO”] quarter *25 cents US currency* coin return request [TRUE | FALSE] control .24 Representasi Simbol : = : composed of + : and {} : iterations of [….

25 • • • • •    .

26 •    Customer •     data    control • .

27 •    1 Proses A •    •   data X .

28 • • •    •   .

29 object returned coins 0* Customer customer selection slug coin return request Vend product Customer product product available .

30 object slug coin return request coins 1* Get customer payment payment sufficient payment coin detected price table 5* Dispense change 2p Get product price returned coins change due 3p Validate payment price valid selection customer selection product product available 4p Get valid selection 6p Dispense product valid selection product available products product dispensed .

31 coin return request product available change due 5.2p Get payment coin coins payment payment coins .1p Get change coin returned coins change coins 5.

32 • Inputs : payment (data in) • price (data in) • Outputs : change due (data out) • sufficient payment (control out) • Body : • IF payment >= price THEN • change due = payment – price • sufficient payment = TRUE • ELSE • change due = 0 • sufficient payment = FALSE • END IF .

33 coin return request product available get change coin get payment coin TRUE TRUE 1 0 D/C FALSE 0 1 .

34 • • • • .

35 • • • • •   .

36 Enter object Customer Select product Get return coins .

If the selected product is available but there isn’t enough number to order. x”. Alternative flows 1. the system will display a message “Your selected product is not available”. max. If the selected product is not available. 2.37 Flow of events for the Select product use-case Objective Allow customer to select a certain product to dispense Actors Customer Pre-condition Coin detected and valid Main flow 1. Post-condition The selected product dispensed as the number needed . 2. The customer selects a button product. X is the existing number of the product. The system displays an entry prompt of number of product to order. the system will display a message “The number isn’t enough.

38 •     •    .

39 .

40 • • •     .

41 .

Sign up to vote on this title
UsefulNot useful