Dependency Properties

You can modify an object's properties from its property sheet. To open a dependency property sheet, double-click its diagram symbol or its Browser entry in the Dependencies folder.

The General tab contains the following properties:

Property	Description
Name	Specifies the name of the item, which should be clear and meaningful, and should convey the item's purpose to non-technical users.
Code	Specifies the technical name of the object, which is used for generating code or scripts.
Comment	Descriptive comment for the object.
Influent	Selected use case or actor influences the dependent object. Changes on the influent object affect the dependent object. You can click the Properties tool beside this box to display 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. You can use the tools to the right of the list to create an object, browse the complete tree of available objects or view the properties of the currently selected object.
Stereotype	Extends the semantics of the object beyond the core UML definition. 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

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.