Class Diagram | OOP and Design Patterns by Oum Saokosal
Download as PPTX, PDF3 likes1,144 views
This document provides an overview of class diagrams, describing the essential components such as classes, attributes, operations, and relationships like dependencies, generalizations, associations, aggregations, and compositions. It emphasizes the importance of visual representation in modeling these concepts, including the use of interfaces and their relationships to classes. The presentation includes examples and diagrams illustrating these modeling techniques and principles.
![Interfaces
An interface is a named set of operations that specifies the
behavior of objects without showing their inner structure. It can
be rendered in the model by a one- or two-compartment
rectangle, with the stereotype <<interface>> above the interface
name.
Interfaces do not get instantiated. They have no attributes or
state. Rather, they specify the services offered by a related class.
This presentation is available to download at: https://www.slideshare.net/oumsaokosal 13
<<interface>>
ControlPanel
getChoices : Choice[]
makeChoice (c : Choice)
getSelection : Selection](https://image.slidesharecdn.com/classdiagram-171115051501/85/Class-Diagram-OOP-and-Design-Patterns-by-Oum-Saokosal-13-320.jpg)
Class Diagram | OOP and Design Patterns by Oum Saokosal
- 1. Class Diagram OUM SAOKOSAL Chief of Faculty of Computer Science, NPIC.edu.kh Master of Engineering in Information Systems, Jeonju University, South Korea 012252752 / 070252752 https://youtube.com/oumsaokosal http://kosalgeek.com
- 2. Class Diagram A class is a description of a set of objects that share the same attributes, operations, relationships, and semantics. Graphically, a class is rendered as a rectangle, usually including its name, attributes, and operations in separate, designated compartments. This presentation is available to download at: https://www.slideshare.net/oumsaokosal 2 ClassName attributes operations
- 3. Class Diagram (cont.) Attributes/Operation can be: + public # protected - private ~ default This presentation is available to download at: https://www.slideshare.net/oumsaokosal 3 Person + name : String # address : Address # birthdate : Date ~ ssn : Integer eat(f:Food) : Void sleep(t:Time) : Duration work() : Void play(sport) : Boolean
- 4. Depicting Classes When drawing a class, you needn’t show attributes and operation in every diagram. This presentation is available to download at: https://www.slideshare.net/oumsaokosal 4 Person name : String birthdate : Date ssn : Int eat() sleep() work() play() Person Person name address birthdate Person eat play Person
- 5. Dependency Relationships A dependency indicates a semantic relationship between two or more elements. The dependency from CourseSchedule to Course exists because Course is used in both the add and remove operations of CourseSchedule. This presentation is available to download at: https://www.slideshare.net/oumsaokosal 5 CourseSchedule add(c : Course) remove(c : Course) Course
- 6. Generalization Relationships A generalization connects a subclass to its superclass. It denotes an inheritance of attributes and behavior from the superclass to the subclass and indicates a specialization in the subclass of the more general superclass. This presentation is available to download at: https://www.slideshare.net/oumsaokosal 6 Person Student Teacher
- 7. Association Relationships If two classes in a model need to communicate with each other, there must be link between them. An association denotes that link. This presentation is available to download at: https://www.slideshare.net/oumsaokosal 7 InstructorStudent
- 8. Association Relationships (Cont.) We can indicate the multiplicity of an association by adding multiplicity adornments to the line denoting the association. The example indicates that a Student has one or more Instructors: This presentation is available to download at: https://www.slideshare.net/oumsaokosal 8 InstructorStudent 1..*
- 9. Association Relationships (Cont.) The example indicates that every Instructor has one or more Students: We can also indicate the behavior of an object in an association (i.e., the role of an object) using rolenames. We can also name the association. This presentation is available to download at: https://www.slideshare.net/oumsaokosal 9 InstructorStudent 1..* InstructorStudent 1..*1..* learns fromteaches TeamStudent membership 1..* 1..*
- 10. Association Relationships (Cont.) We can constrain the association relationship by defining the navigability of the association. Here, a Router object requests services from a DNS object by sending messages to (invoking the operations of) the server. The direction of the association indicates that the server has no knowledge of the Router. This presentation is available to download at: https://www.slideshare.net/oumsaokosal 10 Router DomainNameServer
- 11. Association Relationships: Aggregations and Compositions We can model objects that contain other objects by way of special associations called aggregations and compositions. An aggregation specifies a whole-part relationship between an aggregate (a whole) and a constituent part, where the part can exist independently from the aggregate. Aggregations are denoted by a hollow-diamond adornment on the association. This presentation is available to download at: https://www.slideshare.net/oumsaokosal 11 Car Engine Transmission
- 12. Association Relationships: Aggregations and Compositions (cont.) A composition indicates a strong ownership and coincident lifetime of parts by the whole (i.e., they live and die as a whole). Compositions are denoted by a filled-diamond adornment on the association. This presentation is available to download at: https://www.slideshare.net/oumsaokosal 12 Window Scrollbar Titlebar Menu 1 1 1 1 1 1 .. *
- 13. Interfaces An interface is a named set of operations that specifies the behavior of objects without showing their inner structure. It can be rendered in the model by a one- or two-compartment rectangle, with the stereotype <<interface>> above the interface name. Interfaces do not get instantiated. They have no attributes or state. Rather, they specify the services offered by a related class. This presentation is available to download at: https://www.slideshare.net/oumsaokosal 13 <<interface>> ControlPanel getChoices : Choice[] makeChoice (c : Choice) getSelection : Selection
- 14. Interface Realization Relationship A realization relationship connects a class with an interface that supplies its behavioral specification. It is rendered by a dashed line with a hollow triangle towards the specifier. This presentation is available to download at: https://www.slideshare.net/oumsaokosal 14 <<interface>> ControlPanel VendingMachine specifier implementation
- 15. Depicting Interfaces A class’interface can also be rendered by a circle connected to a class by a solid line. This presentation is available to download at: https://www.slideshare.net/oumsaokosal 15 File outputStream FileWriter {file must not be locked} FileReader {file must exist}