Object-oriented modeling Class/Object Diagrams. Karolina Muszyńska. Based on : http://www.csun.edu/~dn58412/IS431/IS431_SP13.html S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”. Object Modeling – class/object diagrams. Static view - class/object diagrams
Based on: http://www.csun.edu/~dn58412/IS431/IS431_SP13.html
S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Class diagrams – kind of UML diagrams showing the static view of the system, constituting the basis for the future object-oriented database. Class diagrams depict the system’s object structure and show object classes that the system is composed of as well as the relationships between classes.
Object diagrams - they are similar to class diagrams but instead of depicting object classes they model actual object instances, showing the structure of the systems in a given moment of time.
Conceptual diagram – class diagram including basic elements, using class, attributes and behavior names, which are clear and understandable for the user.
Implementation diagram – class diagram enriched by additional elements like data types, visibility, association classes, generalization relationships, or realizations.
Object – anything that is or is capable of being seen, touched, or otherwise sensed, and about which users store data and associate behavior(which is important in the considered domain)
Attributes - data that represents characteristics of interest about an object (everything what is known about an object is represented by the attributes)
Behavior/Methods - refers to things that the object can do and that correspond to functions that act on the object’s data (or its attributes)
Class - a set of objects sharing a common structure – attributes and behavior, and common relationships and meaning.
Attributes with data types
Methods with output data types
Values of the attributes
An object/classrelationship is an association that exists between one or more objects/classes. It is defined by business rules and/or common practices. There are four types of relationships among classes: association, generalization, dependency and realization.
Association - main type of relationship describing the possible set of associations among objects of the associated classes.
Navigation is the defined direction of communication between classes; if not defined the default navigation is bi-directional.
Multiplicity defines how many instances of one class can be associated with one instance of another class.
Association with Multiplicity
works for one
and only one
Zero or one
An employee has
either one or no
A customer can
make no payment
up to many
One or more
offers at least 1
course up to
A team has either
7, 8, or 9 games
OrderClass/object diagrams – basic concepts
“is a part of” relationships
(part-objects may be shared by many whole-objects)
“is made of” relationships
(all part-objects make up and live in the whole-object)
AuctionClass/object diagrams – advanced concepts
Multiple association – a situation when associated classes can play different roles to each other and so there are multiple associations between them. Each association should be named or characterized.
Reflexive association – a situation when there is an association between different objects of the same class (an association binding the class with itself).
Generalization relationship - indicates that one of the two related classes - the subclass (child) is considered to be a specialized form of the other - the superclass (parent) and superclass is considered as ‘generalization'of subclass. In other words the child class is a specific type of the parent class and assumes all the characteristics of its parent class.
The generalization relationship is also known as the inheritance relationship.
The parent class can be either a real class or an abstract class. The abstract class has no real object instances, it is only a generalization of real objects which are specified as child classes.
Realizationrelationship - denotes the implementation of the functionality defined in one class by another class (interface). Relationship in which one model element (the client) realizes (implements or executes) the behavior that the other model element (the supplier) specifies. A realization relationship between classes and interfaces shows that the class realizes the operations offered by the interface.
Realizations can only be shown on class or component diagrams.
Find the potential objects (the best way is to review each use case to find nouns that correspond to business entities or events).
Select the proposed objects (clean the list of all potential business objects from: synonyms, nouns outside the scope of system, nouns that are roles without unique behavior or are external roles, unclear nouns that need focus and nouns that are really actions or attributes).
Identify attributes and operations of the classes.
Identify associations and multiplicity (to help insure that all possible relationships are identified we can create a class matrix).
Identify generalization relationships (we should look for all one-to-one multiplicity relationships between objects because they may be generalization relationships, as well as for classes that have common attributes and behaviors).
Identify aggregation relationships (we must remember that aggregation relationships do not imply inheritance but they propagate behavior).
The first step should be to identify related classes and build class diagrams for each particular use case and next build an integrated class diagram for the whole system.