Show Posts
1
Uml Process / How to model attribute dependency inside one class in class diagram
« on: April 24, 2019, 12:06:46 am »
I think you mixed more things together. Dependency can be seen almost everywhere for instance, if an attribute has a type you can say that this attribute depends on its type. Dependency is the most general metaclass used usually to say: I won't to specify it more precious which doesn't mean it is wrong.
On the other hand, flow means that a piece of data flows from source to target. It doesn't say anything else such as who starts the transfer. Secondly, information flow is not from UML point of view a specialization of dependency.
Last but not least, multiplicity has nothing to do with dependency neither with information flow.
To sum it up: if you use information flow, there is no need to use dependency. Using multiplicity with dependency or information flow is against UML 2 standard. I would definitely delete the dependency if there is an information flow.
On the other hand, flow means that a piece of data flows from source to target. It doesn't say anything else such as who starts the transfer. Secondly, information flow is not from UML point of view a specialization of dependency.
Last but not least, multiplicity has nothing to do with dependency neither with information flow.
To sum it up: if you use information flow, there is no need to use dependency. Using multiplicity with dependency or information flow is against UML 2 standard. I would definitely delete the dependency if there is an information flow.