UML Basic Architecture Modeling-Considerations for modeling common mechanisms



When you adorn a model with notes,

l Use notes with those requirements, observations, reviews, and explanations that can ' T Express simply or meaningfully using existing features of the UML.

l Use notes as a kind of electronic sticky note, to keep track of your work in progress.

When you're decorating a model with notes,

l only when you are on those needs ﹑ observed ﹑ review and explain the use of notes when you cannot simply express or use UML's existing functionality.

l use notes as electronic notes to keep track of your work progress.

When you draw notes,

l Don ' T clutter your models with large blocks of comments. Rather, if you really need a long comment, use notes as a placeholder to link to or embed a document that contains the FUL L comment.

When you are drawing notes,

l don't use a large paragraph of annotations to make your model look cluttered. Conversely, if you really need to have a large paragraph of comments, use a note as a dot, link or embed a file that contains a full comment.

When you extend a model with stereotypes, tagged values, or constraints,

l standardize on a small set of stereotypes, tagged values, and constraints to use the your project, and avoid letting in Dividual developers create lots of new extensions.

l chose short, meaningful names for your stereotypes and tagged values.

l Where Precision can is relaxed, use free-form text for specifying constraints. If you need rigor, use the OCL to write constraint expressions.

when you use the layout ﹑ when a tag value or constraint extends the model,

l The spec uses a small amount of layout on your project ﹑ tag values and constraints, and prevent individual developers from creating more new extensions.

l choose a short and meaningful name for your layout and label values.

l in places where accuracy is not high, free-form text is used for the specified constraint. If you require strict, use the object constraint language to write the constraint expression.

When you draw a stereotype, tagged value, or constraints,

l use Graphical stereotypes sparingly. Can totally change the basic notation of the UML with stereotypes, but in so doing ' ll Make it Impossible for anyone else to understand your models.

l consider using simple-color or shading for graphical stereotypes, as-well as more complicated icons. Simple notations is generally the best, and even the most subtle visual cues can go a long-in communicating meaning.< /c2>

when you draw the layout ﹑ Tag Value or constraint,

l use a graphical layout carefully. With typography you can completely change the basic markup of UML, but the result is that others will find it hard to understand your pattern.

l consider using simple colors or shadows, and more complex icons for a graphical layout. Simple markers are generally the best, even more ingenious visual cues that can go a long way in expressing intentions.

UML Basic Architecture Modeling-Considerations for modeling common mechanisms