| composition | sufficient names to make the association clear and unambiguous | legitimate only if its links will survive beyond the execution of any particular operation | a model unless it is relevant to the application - it will be needed to implement some requirement | aggregation | 5.6 - More Advanced Features of Class Diagrams | The rooms of a building cannot exist without the building | the pieces of data that describe some entity, so that programmers can manipulate that data as a unit | a relationship that will exist between instances at run time | the details of data | "has" if it has neither an association name nor a role name | a class possesses, controls, is connected to, is related to, is a part of, has as parts, is a member of, or has as members, some class in your model | instance variables in Java: you divide each two-way association into two one-way associations - so each associated class has an instance variable | role name | several ways in Java | A strong kind of aggregation in which if the aggregate is destroyed, then the parts are destroyed as well | a programmer to cope with the complexity of data | 'part-whole' relationships | a solid (filled-in) diamond in a UML diagram | how two classes are related to each other |
Object Oriented Software Engineering View all facts Glossary Help
