Component DiagramsĬomponent diagrams are used to illustrate how components of a system are wired together at a higher level of abstraction than class diagrams. The object element may also have extra information to model the state of the attributes at a particular time, as in the case of myAccount in the above example. Typically, an object instance is modeled using a simple rectangle without compartments, and with underlined text of the format InstanceName:Class As you would expect, this diagram uses some elements from class diagrams.
Object diagrams provide information about the relationships between instances of classes at a particular point in time.
UML EDITOR PARAMETERIZED CLASS CODE
They used to hold useful information for the diagram, such as explanations or code samples, and can be linked to entities in the diagram. Notes Notes or comments are used across all UML diagrams.
The following example shows a multiple association, between ClassA and ClassB, with an alias given to the link. Direction is expressed using arrows, which may be bi-directional. Sometimes more complex relationships exist between classes, where a third class contains the association information.įigure 7: Account associates the Bank with a Personįor all the above relationships, direction and multiplicity can be expressed, as well as an annotation for the relationship. This is depicted using a hollow triangle at the general side of the relationship.įigure 6: Ford is a more specific type of Car Generalization “…is a…”Also known as inheritance, this indicates that the subtype is a more specific type of the super type. This is depicted using a hollow diamond.Ĭomposition “…is part of.”More specific than aggregation, this indicates a strong life cycle dependency between classes, so when the container is destroyed, so are the contents. The contained classes do not have a life cycle dependency on the container, so when the container is destroyed, the contents are not. RelationshipDescriptionDependency “.uses a…”A weak, usually transient, relationship that illustrates that a class uses another class at some point.įigure 2: ClassA has dependency on ClassBĪssociation “…has a.”Stronger than dependency, the solid line relationship indicates that the class retains a reference to another class over time.Īggregation “…owns a…”More specific than association, this indicates that a class is a container or collection of other classes. Interfaces Interface names and operations are Operations and attributes can have their visibility annotated as follows: + public, # protected, - private, ~ package
0 kommentar(er)
