لطفا منتظر باشید ...
Hints and Tips
When you create a diagram,
- Remember that the purpose of a diagram in the UML is not to draw pretty pictures but to visualize, specify, construct, and document. Diagrams are a means to the end of deploying an executable system.
- Not all diagrams are meant to be preserved. Consider building up diagrams on the fly by querying the elements in your models, and use these diagrams to reason about your system as it is being built. Many of these kinds of diagrams can be thrown away after they have served their purpose (but the semantics upon which they were created will remain as a part of the model).
- Avoid extraneous or redundant diagrams. They clutter your models.
- Reveal only enough detail in each diagram to address the issues for which it was intended. Extraneous information can distract the reader from the key point you re trying to make.
- On the other hand, don't make your diagrams minimalist unless you really need to present something at a very high level of abstraction. Oversimplification can hide details that are important to reasoning about your models.
- Keep a balance between the structural and behavioral diagrams in your system. Very few systems are totally static or totally dynamic.
- Don't make your diagrams too big (ones that run more than one printed page are hard to understand) or too small (consider joining several trivial diagrams into one).
- Give each diagram a meaningful name that clearly expresses its intent.
- Keep your diagrams organized. Group them into packages according to view.
- Don't obsess over the format of a diagram. Let tools help you.
A well-structured diagram
- Is focused on communicating one aspect of a system's view.
- Contains only those elements that are essential to understanding that aspect.
- Provides detail consistent with its level of abstraction (expose only those adornments that are essential to understanding).
- Is not so minimalist that it misinforms the reader about semantics that are important.
When you draw a diagram,
- Give it a name that communicates its purpose.
- Lay out its elements to minimize lines that cross.
- Organize its elements spatially so that things that are semantically close are laid out physically close.
- Use notes and color as visual cues to draw attention to important features of your diagram. Use color with care, however, because many people are color blind; color should only be used as a highlight, not to convey essential information.
