RE: Dependencies and associations



Date view Thread view Subject view Author view

Joaquin Miller (miller@joaquin.net)
Mon, 25 Jun 2001 10:42:29 -0700


Gonzalo, thanks for the texts. Two questions, at >>> At 04:59 AM 6/25/2001, Gonzalo Génova wrote: >Daniel, > >I know you don't like the definitions of dependency in the Standard. Anyway, >here there are some quotations from v1.4 (draft): > >- A dependency states that the implementation or functioning of one or more >elements requires the presence of one or more other elements [UML 2-37]. >- A dependency specifies that the semantics of a set of model elements >requires the presence of another set of model elements. This implies that if >the source is somehow modified, the dependents probably must be modified >[UML 2-78]. >- A relationship between two modeling elements, in which a change to one >modeling element (the independent element) will affect the other modeling >element (the dependent element) [UML B-6]. > >First definition deals with the idea of the required "presence"; in my understanding, if class A has a navigable association to class B, then class A requires the presence of class B to function, and so I say that A is dependent on B (for example, you cannot reuse A without reusing B; the inverse is not true). >>> And there are many, many other ways that it might come to pass that implementation or functioning of one or more elements requires the presence of one or more other elements, right? >Regarding the second definition, if, for example, an operation's name changes in class B, then class A will have to be modified accordingly (if it invokes this operation): this matches your "code text dependence", but I think this applies too at a higher level. >Finally, I agree the third defintion is too vague to be useful. >>> So, if i may ask, what does 'dependency' mean in UmlOne? (Don't answer if this question is off topic.)


Date view Thread view Subject view Author view