Dependency Properties

To view or edit a dependency's properties, double-click its diagram symbol or Browser or list entry. The property sheet tabs and fields listed here are those available by default, before any customization of the interface by you or an administrator.

The General tab contains the following properties:

Property	Description
Name/Code/Comment	Identify the object. The name should clearly convey the object's purpose to non-technical users, while the code, which is used for generating code or scripts, may be abbreviated, and should not normally include spaces. You can optionally add a comment to provide more detailed information about the object. By default the code is generated from the name by applying the naming conventions specified in the model options. To decouple name-code synchronization, click to release the = button to the right of the Code field.
Stereotype	Extends the semantics of the object beyond the core UML definition. You can enter a stereotype directly in this field, or add stereotypes to the list by specifying them in an extension file. The following common stereotypes are provided by default: << Access >> - Public contents of the target package that can by accessed by the source package << Bind >> - Source object that instantiates the target template using the given actual parameters << Call>> - Source operation that invokes the target operation << Derive >> - Source object that can be computed from the target << Extend >> - (Use Case/Class) Target object extends the behavior of the source object at the given extension point << Friend>> - Source object that has special visibility towards the target << Import >> - Everything declared public in the target object becomes visible to the source object, as if it were part of the source object definition << Include >> - (Use Case/Class) Inclusion of the behavior of the first object into the behavior of the client object, under the control of the client object << Instantiate >> - Operations on the source class create instances of the target class << Refine >> - The target object has a greater level of detail than the source object << Trace >> - Historical link between the source object and the target object << Use >> - Semantics of the source object are dependent on the semantics of the public part of the target object << ejb-ref >> - (Java only) Used in Java Generation to create references to EJBs (entity beans and session beans) for generating the deployment descriptor << sameFile >> - (Java only) Used in Java Generation to generate Java classes of visibility protected or private within a file corresponding to a class of visibility public
Influent	Selected use case or actor influences the dependent object. Changes on the influent object affect the dependent object. Click the Properties tool to the right of the field to view the object property sheet
Dependent	Selected use case or actor depends on the influent object. Changes on the dependent object do not affect the influent object. Use the tools to the right of the list to create, browse for, or view the properties of the currently selected object.
Keywords	Provide a way of loosely grouping objects through tagging. To enter multiple keywords, separate them with commas.

If the dependency is created in a use case diagram, you cannot change the objects linked by the dependency. For example, you cannot attach the dependency coming from a use case to a class or an interface.