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

Operation = application not accepted
Description = An application is rejected by the central office.
Reads = supplied app nr : Appl nr
client : Client with (client, application) ∈ PreparesAppl
product : Product with (application, product) ∈ ForAppl
Changes = delete application : Application with
application.nr = app nr
PreparesAppl, ForAppl
Sends = Employee: {contract not prepared(app nr)}
Pre = exists application : Application with application.nr = app nr
Post = ForAppl ′ = ForAppl \{(application, product)}
THE SYSTEM CLASS MODEL
PreparesAppl ′ = PreparesAppl \{(client, application)}
is sent{contract not prepared(app nr)}
105
➠ Shows the classes to be implemented.
➠ Is developed from a part of the class model.
➠ Is delineated by a dashed line.
➠ Actors and non-implementable classes (e.g., persons who do not directly
interact with the system) do not belong to the system class model.
➠ The interpretation of a class can change from “real object” to “data
representation”.
➠ Classes on the system border may be divided into internal and external
classes.
107
OBJECT-ORIENTED ANALYSIS
➠ Class model =⇒ Static aspects
➠ Interface model =⇒ Dynamic aspects
• Use case model
• Scenarios
• Operation model
• System class model
• Life-Cycle model
➠ Usually, additions to the class model are necessary by:
106
• attributes that are introduced when setting up the operation model
• “communication classes” for actors, i.e., classes that receive the system
operations (see OOD)
➠ The system class model is a well-formed class model, i.e., an association
only belongs to it if all concerned classes are inside the system.
108