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

More documents

Recommendations

Info

RULES ➠ An operation schema must be set up for each system operation occurring in the scenarios. ➠ The actors given in the sends-clause must be the same as in the scenarios. ➠ The entities in the reads- and changes-clauses must be disjoint. ➠ Preconditions and scenarios must be consistent (number and type of error cases) ➠ The actors are responsible for guaranteeing the precondition of a system operation! The system operation does not check if the precondition is fulfilled, but assumes that it is! Operation = c data present? Description = It is checked if the client exists. Reads = supplied cd : CData 93 client : Client with client.clientData = cd Changes = – Sends = Employee:{c data present!(client.nr), Pre = — c data not present!} Post = exists client : Client with client.clientData = cd ⇒ is sent{c data present!(client.nr)} otherwise: is sent{c data not present!} =⇒ The class Client belongs to the system and has the attributes clientData and nr. 95 Operation schemas for the insurance agency Operation = enter c data Description = Data of a new client is entered. Reads = supplied cd : CData Changes = new client: Client Sends = Employee : {c data entered(cl nr)} Pre = not exists client : Client with client.clientData = cd Post = client.clientData ′ = cd client.nr ′ = cl nr, where cl nr is an new client number is sent{c data entered(cl nr)} 94 96
USE CASE “PREPARE APPLICATION/CONTRACT”, COMBINED FRAGMENTS sd EnterClientData Employee c_data_present? alt [cdp] c_data_present! [else] c_data_not_present! enter_c_data c_data_entered : Agency sd PrepareAppl/Contr Employee ref EnterClientData alt [ok] [else] 97 prepare_application application_prepared contract_prepared contract_not_prepared : Agency Pre = exists client : Client with client.nr = cl nr coregion check_application application_accepted application_not_accepted CentralOffice Post = application.nr ′ = app nr, where app nr new appl. number prod = car ⇒ application.applicationData ′ = generate application(client.clientData, al.productData, al.alData, a data) ForAppl ′ = ForAppl ∪{(application, al)} prod = liability ⇒ application.applicationData ′ = generate application(client.clientData, pl.productData, pl.plData, a data) ForAppl ′ = ForAppl ∪{(application, pl)} 99 Operation = prepare application Description = An application for a known client is prepared. Reads = supplied cl nr : CNr supplied prod : Prod ID supplied a data : applicationData client : Client with client.nr = cl nr hi, al, pl : Product Changes = new application : Application PreparesAppl, ForAppl Sends = Employee: {application prepared(app nr)}, CentralOffice:{check application(prod, application.applicationData ′ , app nr, client.clientData)} prod = health ⇒ 98 application.applicationData ′ = generate application(client.clientData, hi.productData, hi.hiData, a data) ForAppl ′ = ForAppl ∪{(application, hi)} PreparesAppl ′ = PreparesAppl ∪{(client, application)} is sent{application prepared(app nr)} is sent{check application(prod, application.applicationData ′ 100 app nr, client.clientData)}
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: SCHUFA QUERY REMARKS sd SchufaQuery
Page 27 and 28: Operation = application not accepte
Page 29 and 30: LIFE-CYCLE EXPRESSIONS The Life-Cyc
Page 31 and 32: Canc = cancel contract;#confirm can

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

Create successful ePaper yourself

Delete template?

Save as template?