Please enable JavaScript.
Coggle requires JavaScript to display documents.
Object-Oriented Modeling - Coggle Diagram
Object-Oriented Modeling
-
-
Goals
- Construct & refine
MODELS of all the objects.
- Entity Objects
(from problem space)
- Control Objects
(receive events & coordinate actions)
- Boundary Objects
(connect to services outside the system)
-
-
-
Four Design Principles
-
-
-
Example: Food if abstracted, then it's nutritional value,
and not it's cost would be part of it's
simplified description
Good abstraction emphasizes on the essentials
need for the concept and removes details
which are not essential
-
-
Abstraction should define attributes of of the concept.
Example: for Student concept, attributes could be:
Grade, courses, university etc
an abstraction should describe a concept's basic behaviors. For a student, those behaviors would be studying, doing assignments, and attending lectures.
If the purpose of your system or the problem changes, don't be afraid to update your abstractions accordingly. Abstractions are not a fixed creation, but are a direct result of the problem for which you created them
encapsulation forms a self-contained object by bundling the data and functions it requires to work, exposes an interface whereby other objects can access and use it, and restricts access to certain inside details