The object oriented paradigm has replaced the structured
programming paradigm in modern software development. The following
table empahsizes the
necessary shift in terminlogy required to upgrade
from structured programming to object oriented software development.
|
|
|
|
|
|
|
|
|
|
|
|
1. object architecture
2. operation algorithms |
1. UML class diagrams
2. SAC for algorithms |
|
The following is the best, most concise example I can think of that illustarte all the constructs of object oriented software design.
|
Prototype Architecture for a Geometry Application |
![]() |
| The diamond headed links between classes represent "has-a" relationships. |
|
showing only the distinctive elements for an Expansion of Geometry Application Architecture |
![]() |
| The dashed arrow represents
the "uses-a" relationship between classes.
The triangular arrow represents the "is-a" relationship between classes. Italics represent an "abstract" class that can not be made into a real object. |
|
for the preceding Expansion of Geometry Application Architecture |
![]() |