http://argouml.tigris.org/issues/show_bug.cgi?id=6290
------- Additional comments from [email protected] Wed Aug 31 04:41:33 -0700 2011 -------
Hello Laurent,
thank you very much for this patch.
>use case can be owned by several classifiers/Subjects
A use case can be owned by 0..1 subject. It's an other association with "*..*"
In fact I mismatched the two associations; I should have say "use case can be
ATTACHED/APPLIED to several classifiers/Subjects", i.e. I was thinking about
this association in the figure 16.2 in UML2.4 norm: "(0..*)usecase--subject
(0..*)".
So, maybe (certainly...) I am misinterpreting your patch but it seems to me
that the association you used is the association "ownedUsecase", not the
association "(0..*)usecase--subject(0..*)".
My interpretation is that this association "ownedUseCase" is representing the
fact that a use case is owned by one (and only one) 'container'.
The subject relationship instead should be the "(0..*)usecase--subject(0..*)",
where a use case can be linked to several classifiers, several subjects.
When I try to play with the example model opened in the patched ArgoUML, if I
drag and drop a use case, that is already into a class/subject, into another
class/subject, the use case appears (in properties) in the list of owned use
cases of the two, but it should not, in my current understanding.
A separate list "list of use cases for this subject" should be managed, while
only one classifier should have the use case in its list of owned use cases.
With UML2 framework, this means to use the "getUseCases()" and associated
functions, not the "getOwnedUseCases()" functions (as I wrongly thought before).
(see http://www.linuxtopia.org/online_books/eclipse_documentation/
eclipse_uml2_development_guide/topic/org.eclipse.uml2.doc/references/javadoc/
org/eclipse/uml2/uml/eclipse_uml2_Classifier.html#getUseCases() )
best regards
JGN
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=448&dsMessageId=2833310
To unsubscribe from this list, e-mail: [[email protected]].
Please do not reply to this mail. Instead, add your comments in the issue.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.