UML Weekend Crash Course™ - To Parent Directory

322
Appendix A
7. The pattern defines the materials needed to solve the problem and how to make
them work together. But the implementation may be tailored to the specific type
of application and the technology used for the implementation, not to mention
the preferences of the developer for the peculiar needs of the application.
8. The pattern notation would indicate to everyone using the model that you have
chosen to apply a standardized solution rather than a homegrown solution that
would take more time to evaluate and approve because it has not been tested to
the degree that a pattern has been tested.
9. The roles define the behavior of the participating objects much like job description
or task assignments help clarify how members of a team will coordinate their
efforts to finish the project.
10. The Class diagram models rules, but the Object diagram models facts. The facts may
prove or disprove the accuracy of the rules, so the Object diagram is valuable for
determining what the rules should be and whether the existing rules are accurate.
11. The object name may be similar to the name of an object of another type.
Including the class name prevents misinterpretation of the diagram.
12. The Class diagram declares the rules that constrain the values that you can use in
the attribute. The Object diagram records the actual value. The Class diagram
defines all the rules about the information, whereas the Object diagram is used to
model real examples or test cases.
13. An association defines the rules about how objects may be related to one another.
Links identify how objects are related to one another. A link is to an association as
an object is to a class.
14. Operations are only the declared part of behavior. The declaration would be the
same for all objects of the same class, so including them in the Object diagram
would be redundant.
15. Logical processes include workflows, Use Cases, and operations. The workflow
describes when and how people will use the features of the system. The Use Case
logic explains how the actors will interact with the system to accomplish one specific
goal. Each operation describes the logic required to implement the behavior
that the operation offers.
16. The diamond is used for decisions and as a merge point. The bar is used for initiating
multiple threads or processes and for synchronizing multiple threads or
processes.
17. Place a guard condition on the transition using text enclosed in square brackets [ ].
18. No. You can have multiple transitions out of an activity, each labeled with a guard
condition to show the direction to take based on the outcome of the activity.
19. False. An Activity diagram has one start but may have many end points.
20. There should be one end point for every termination option. But you can use a
single end point for many transitions (that is, you can have many transition
arrows point to the same end point).
21. If the completion of the activity results in criteria needed to make the decision,
then use the activity itself. If the criteria are an explicit decision by the actor, or
the accumulation of information from many previous activities, then use a decision
diamond.