UML Weekend Crash Course™ - To Parent Directory

PART
III #
Saturday Afternoon
Part Review
1. Describe two key characteristics of aggregation.
2. Describe the distinguishing characteristic of composition.
3. How can multiplicity give you a clue as to whether the association should be
aggregation or composition
4. What is the difference between specialization and generalization
5. What is the effect on the application when you choose between 0..1 and
1..1 multiplicity
6. What is the benefit of using qualified associations
7. If a design pattern is not code, how does it help you solve a problem
8. How would the pattern notation help in a development project
9. How does the role notation aid in the description of the pattern in the Class
diagram
10. If the Class diagram models all the rules for creating and using objects, why do you
need to use an Object diagram
11. Why does the object name notation have both the object name and the class
name
12. How do the attribute descriptions differ between the Class and Object diagrams,
and why
13. How is a link different from an association
14. Why aren’t the operations shown in an Object diagram
15. The Activity diagram is used primarily for modeling logic. But when in the development
process would you encounter the need to model logic
16. Two of the Activity diagram symbols are used for dual purposes. Can you describe
them
17. How do you indicate that a transition may occur only if a condition has been
satisfied