Slides Part 2 (OOA, pages 1-128, pdf, 4 slides per page)

More documents

Recommendations

Info

EXAMPLE: BANK Life-Cycle Bank system: Openacc;(Transaction|Query|Openacc) ∗ Openacc = OpenaccNC | OpenaccKC Query = query balance;#current balance Transaction = deposit money | Withdrawal OpenaccNC = open new customer account; (Schufaquery|#customer already known) OpenaccKC = open known customer account; (#account opened|#account not opened) Withdrawal = withdraw money; (#give money|#no cover) Schufaquery = #schufa query; (credit worthiness ok; #account opened) |(credit worthiness not ok; #account not opened) 117 LIFE-CYCLE MODEL AS STATE MACHINE ➠ System operations as events ➠ Output events as actions ➠ Transitions between states: event / action Example: life-cycle of an account 2 1 no account 3 5 no account Schufa queried 1: open_known_customer_account / #account_not_opened 2: open_new_customer_account / #customer_arlready_known 3: open_new_customer_account / #schufa_query 4: open_known_customer_account / #account_opened 5: credit_worthiness_not_ok / #account_not_opened 4 6 119 account without deposit 7 7 8 account with deposit 7: query_balance / #current_balance 8: deposit_money 9: withdraw_money / #give_money 10: withdraw_money / #no_cover 8 6: credit_worthiness_ok / #account_opened 9 10 PROBLEM We can only express that some account must be opened before a transaction or query can take place. We cannot express that before a transaction or query on account X can take place, X must have been opened before. Alternative: Describe life-cycle of specific objects. Example: Lifecycle Account: Open | n Open Open = NewAcc; (query balance;#current balance) ∗ ; deposit money; (Transaction|Query) ∗ n Open = (open new customer account;#schufa query credit worthiness not ok;#account not opened) |(open new customer account;#customer already known) |(open known customer account;#account not opened) NewAcc = open new customer account;#schufa query; credit worthiness ok;#account opened | open known customer account;#account opened LIFE-CYCLE MODEL FOR INSURANCE AGENCY Summary of system operations and their output events: 118 Upd = update product;#product updated EntCDat = enter c data;#c data entered Query = c data present?; (#c data present!|#c not data present!) Offer = prepare offer;#offer prepared Appl = prepare application; (#check application || #application prepared) Acc = application accepted;#contract prepared NAcc = application not accepted;#contract not prepared Chg = change contract;#confirm change ChY = change confirmed;#contract changed ChN = change not confirmed;#contract not changed 120
Canc = cancel contract;#confirm cancellation CanY = cancellation confirmed;#contract canceled CanN = cancellation not confirmed; #contract not canceled HIEv = report HI event;#settle HI event HIOK = HI settlement ok;#HI event settled HINOK = HI settlement not ok;#HI event not settled ALPLEv = report AP/PL event;#authorize expert DelRep = deliver report; #report delivered ALPLOK = settle AP/PL event;#AP/PL event settled ALPLNOK = not settle AP/PL event; #AP/PL event not settled Top-Level-Behavior: 121 V 1 = Query ∗ || Upd + || QuerEnt + V 2 = Offer ∗ || Query ∗ || Upd ∗ || QuerEnt ∗ V 3 = (Appl;NAcc) ∗ || Offer ∗ || Query ∗ || Upd ∗ || QuerEnt ∗ V 4 = (Appl;Acc) + || Offer ∗ || Query ∗ || Upd ∗ || QuerEnt ∗ V 5 = Offer ∗ || Query ∗ || Upd ∗ || QuerEnt ∗ || Contract ∗ || Change ∗ || Cancellation ∗ || Event ∗ Lifecycle Agency: V 1; V 2; V 3; V 4; V 5 123 Definition of “business processes”: QuerEnt = c data present? ; #c data not present! ; EntCDat Contract = Appl ; (Acc | NAcc) Change = Chg ; (ChY | ChN) Cancellation = Canc ; (CanY | CanN) HI Event = HIEv ; (HIOK | HINOK) AL/PL Event = ALPLEv ; DelRep ; (ALPLOK | ALPLNOK) Event = HI Event | AL/PL Event REMARKS 122 • It is always possible to enter client data, to query if client data are present, and to update products (V 1). However, before an offer can be prepared (V 2), at least one update and one entering of client data must take place (V 1). • Moreover, it is possible that applications are prepared which are rejected (V 3). • Before the full functionality of the agency is possible (V 5), at least one application must have been accepted (V 4). • The different business processes may be executed concurrently (operator ||). Note: The life-cycle model should not only consist of life-cycle expressions that reproduce the scenarios, because the scenarios do not contain all possible/ permitted behavior. However, each scenario must be permitted by the life-cycle model. 124
Page 1 and 2: LITERATURE The Fusion Method using
Page 3 and 4: 5. System class model Borderline be
Page 5 and 6: MEANING OF THE CLASS DIAGRAM ➠ Ea
Page 7 and 8: STRUCTURING CLASS MODELS In general
Page 9 and 10: ACTORS ➠ are outside of the syste
Page 11 and 12: ➠ extend-relation extension point
Page 13 and 14: EXAMPLE: OPENING AN ACCOUNT • Nor
Page 15 and 16: PATTERN FOR MODELING “” REMARKS
Page 17 and 18: OBJECT-ORIENTED ANALYSIS ➠ Class
Page 19 and 20: Excursion: Design by Contract What
Page 21 and 22: APPLICATION OF THE DESIGN-BY-CONTRA
Page 23 and 24: SCHUFA QUERY REMARKS sd SchufaQuery
Page 25 and 26: USE CASE “PREPARE APPLICATION/CON
Page 27 and 28: Operation = application not accepte
Page 29: LIFE-CYCLE EXPRESSIONS The Life-Cyc

Slides Part 2 (OOA, pages 1-128, pdf, 4 slides per page)

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?