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

More documents

Recommendations

Info

ASSOCIATION CLASSES ➠ Associations can also have attributes. ➠ Reasonable, if the attributes cannot be assigned to any of the classes involved in the association. Writes Student Exam Writes mark GENERALIZATION/SPECIALIZATION ➠ Classes correspond to types. ➠ Subclasses correspond to subtypes, not subsets. ➠ Specialization = ”is a” , but ”act as” , ”is a kind of” BachelorCourse MasterCourse subject 21 Course Personnel Student Constraint title name name pers.nr inscription_number salary {complete} specialization 23 Professor TeachingAssistent specialty AGGREGATION AND COMPOSITION are special associations. Room Wall The wall is a part of the room. If a part belongs to only one whole and can only exist with that whole, then this is a composition relation. CONSTRAINTS Window Frame or ➠ Are conditions that must hold. ➠ Are written between “{}”. 22 Window Frame ➠ The example: “{complete}” means that no other subclasses of Course can exist. ➠ Meaning of constraints must be described informally. 24
STRUCTURING CLASS MODELS In general the class model must divided into different diagrams. The following conventions must be obeyed: ➠ Modeling elements with the same name represent the same element. ➠ The set of the attributes of an element is the union of the attributes of all element representations. ➠ Multiplicities are combined by conjunction, i.e., 1..14 and 0..5 yields 1..5. ➠ Role names must be unique. 25 • The contents of an already placed contract only changes if the client wishes for changes and the central office approves of these changes. A client contacts an employee of the agency and informs the employee about the desired changes. The employee notifies the central office about the change request. The central office then decides on accepting the request or not and making changes if necessary. The procedure for canceling contracts proceeds analogously. • The data concerning product changes and launches is adjusted monthly. Here, the central office updates the databases of the agencies for each product. 27 EXAMPLE: INSURANCE AGENCY A software system is to be developed for managing an insurance agency. • The following products are offered: Health insurance- (HI), automobile liability- (AL) and private liability (PL). • An employee prepares offers for individual products. These offers contain the essential data for the respective insurance. The product information must be available in form of a database. Client data must be entered if they are not yet present. • The employee prepares the application together with the client. The application is sent from the agency to the central office. The central office checks the application and records the data in its system. If a contract can be placed, the central office sends this contract to the agency in electronic form. A newly placed contract can only refer to a current product. 26 • In case of an occurrence of event insured, the client has to contact an employee of the agency. In case of AL and PL insured events, the agency authorizes an expert advisor who appraises the damage and sends the corresponding report back to the agency via Internet. In insured events within the scope of HI, no expert advisor is appointed. The central office can decide on assuming the payment for an insured event or not. In cases of AL and PL, the agency determines the settlement of a claim on the basis of the expert advisor’s report. 28
Page 1 and 2: LITERATURE The Fusion Method using
Page 3 and 4: 5. System class model Borderline be
Page 5: MEANING OF THE CLASS DIAGRAM ➠ Ea
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 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?