In all cases, must be two-way communication tables or feature classes?

There is a connection:

Aggregation-Composition3.png

Here, aggregation, and composition. All the given classes have to be stored back links encompassing class (a doubly linked list)?
The Professor can exist without the Department and the University, and the Department without the University.
July 2nd 19 at 17:02
1 answer
July 2nd 19 at 17:04
All the given classes have to be stored back links encompassing class (a doubly linked list)?
No, in many cases, unilateral enough.

The most popular form of communication just - one-sided many-to-one.
And if I need to have communication from Professor to Department? However, I don't want to keep the Professor a link to the Department or pass a loop through all the Departments, in search of the Professor. - Ofelia72 commented on July 2nd 19 at 17:07
> And if I need to have communication from Professor to Department?
> However, I don't want to keep the Professor a link to the Department...
Some paragraphs are mutually exclusive... - Giles_Luettgen18 commented on July 2nd 19 at 17:10

Find more questions by tags OOPDatabasesProgramming