UML Basic Architecture Modeling-associated terminology and concepts (iii)

Other Features

Other features

Plain, unadorned dependencies, generalizations, and associations with names, multiplicities, and roles is the most CO Mmon Features you'll need when creating abstractions. In fact, for the most of the models you build, the basic form of these three relationships'll be is all your need to convey the Most important semantics of your relationships. Sometimes, however, you'll need to visualize or specify other features, such as composite aggregation, navigation, discriminants, association classes, and special kinds of dependencies and Generalizations.these and many other features can is expressed in the UML, But they is treated as advanced concepts.

Unpretentious, unmodified dependencies, generalized relationships, and federated relationships with names, polymorphism, and roles are the most common features you'll need to create abstract things. In fact, most of the models you build, the basic form of these three relationships will be the most important semantics for communicating the relationships that you already have. However, sometimes you need to visualize or describe other features such as composite aggregation, navigation, judgment, association classes, and special categories of dependency and generalization relationships. These and many other features can be expressed in UML, but they belong to a deeper concept.

Dependencies, generalizations, and associations is all static things defined at the level of classes. In the UML, these relationships is usually visualized in class diagrams.

dependencies, generalizations, and unions define static things at the class level. In UML, these relationships are usually drawn in a class diagram.

When you start modeling at the object level, and especially if you start working with dynamic collaborations of Thes e objects,you'll encounter links, which is instances of associations representing connections among OB Jects across which messages may be sent.

When you start modeling at the object layer. Especially when you start to work on the dynamic interactions between these objects, you encounter a lot of connections, which are associated instances that represent connections between objects, which may be the sending of messages.

Drawing Styles

Painting style

Relationships is shown in diagrams by lines from one icon to another. The lines has various adornments, such as arrowheads or diamonds, to distinguish different kinds of relationships. Typically, modelers choose one of the styles for drawing lines:

1. oblique lines at any angle. Use one line segment unless multiple segments is needed to avoid other icons.

2. rectilinear lines drawn parallel to the sides of the page. Unless a lines connects and icons that align, the line must is drawn as a series of line segments connected by right angle S. This is the style mostly used.

The relationship is shown in the diagram as a straight line from one icon to another. These lines have many modifications, such as arrows or diamonds, to distinguish between different categories of relationships. Most typically, the modeling chooses two styles of drawing lines:

1. slash at any angle. Use a line segment unless you want to use multiple segments to avoid other icons.

2. the lines are drawn parallel to the sides of the page. Unless a line is connected to two neatly arranged icons, the line is drawn as a series of segments connected at right angles. This format is the most commonly used in this book.

With care, the most line crossings can avoided. If a line crossing is necessary and there was ambiguity about what the paths is connected, a small arc can used to Indic Ate a line crossing.

Note that most of the lines can be avoided by crossing. If a crossover line is unavoidable, there is ambiguity as to how the path is connected. A small arc is used to indicate a crossover line.

UML Basic Architecture Modeling-associated terminology and concepts (iii)