Login | Register
My pages Projects Community openCollabNet

Discussions > users > RE: [argouml-users] Interface association

argouml
Discussion topic

Back to topic list

RE: [argouml-users] Interface association

Author "Arapakis, Lake TCX11" <Lake dot Arapakis at pdo dot co dot om>
Full name "Arapakis, Lake TCX11" <Lake dot Arapakis at pdo dot co dot om>
Date 2001-07-23 20:40:59 PDT
Message Hi Fernando/Markus,

Why would you pass an interface as an argument??

I would have thought a class inherited from an abstract class would be more
prudent. Perhaps the abstract class could then implement the interface.
Afterall, an interface does not contain any fields or methods other than
method definitions (prototypes).

But maybe I am missing the point....

Regards,

Lake

-----Original Message-----
From: Markus Klink [mailto:mkl at baba9 dot com]
Sent: Wednesday July 18, 2001 12:34 PM
To: users at argouml dot tigris dot org
Subject: Re: [argouml-users] Interface association


Hi Fernando,

nice that you had a look into the specs. So far, ArgoUML still looks
pretty much compliant to me.
You can have an association from a class to an interface (even in Argo).
However, we were discussing also two other cases:
association between two interfaces (clearly not possible), and how one
would model something like

class something {
void foo(MyInterface x)
}

Thierry suggested that the deployment diagram would be the correct place
here and I tend to agree. If you want to make it more clear in the class
diagram, I would add a note.

Markus



Fernando Vaquero wrote:

> UML Semantics
>
> 2.5.3.21 Interface
>
> Interfaces may not have Attributes, Associations, or Methods. An
> Interface may
>
> participate in an Association provided the Interface cannot see the
> Association; that is,
>
> a Classifier (other than an Interface) may have an Association to an
> Interface that is
>
> navigable from the Classifier but not from the Interface.
>
> [1] An Interface can only contain Operations.
>
> self.allFeatures->forAll(f |
>
> f.oclIsKindOf(Operation) or f.oclIsKindOf(Reception))
>
> [2] An Interface cannot contain any ModelElements.
>
> self.allContents->isEmpty
>
> [3] All Features defined in an Interface are public.
>
> self.allFeatures->forAll ( f | f.visibility = #public )
>
> So any Classifier, even a Class, may has an Association with an Interface.
>
> Regards,
>
> Fernando
>
>
> --------------------​--------------------​--------------------​------------
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@ar​gouml.tigris.org For
> additional commands, e-mail: users-help at argouml dot tigris dot org



--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@ar​gouml.tigris.org
For additional commands, e-mail: users-help at argouml dot tigris dot org

--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@ar​gouml.tigris.org
For additional commands, e-mail: users-help at argouml dot tigris dot org

« Previous message in topic | 1 of 2 | Next message in topic »

Messages

Show all messages in topic

RE: [argouml-users] Interface association "Arapakis, Lake TCX11" <Lake dot Arapakis at pdo dot co dot om> "Arapakis, Lake TCX11" <Lake dot Arapakis at pdo dot co dot om> 2001-07-23 20:40:59 PDT
     Re: [argouml-users] Interface association mkl_foo Markus Klink 2001-07-23 20:50:15 PDT
Messages per page: