| dependency and allocation [message #477008] |
Fri, 29 February 2008 16:32  |
Eclipse User |
|
|
|
Hi,
I create a profile to model association between application and architecture
of a System On Chip.
I want to associate data to memory (I have a stereotype called Memory) but I
can not create dependency between ports and the component stereotyped
Memory.
Does UML allow this?
And if it is not possible to link port to a component, how can I associate
data that flows through ports with the component stereotyped Memory?
thanks a lot
Asma
|
|
|
|
|
|
|
|
| Re: dependency and allocation [message #626115 is a reply to message #477008] |
Fri, 29 February 2008 11:57  |
| Eclipse User |
|
|
|
Hi Charfi,
I'm not certain what exactly you mean by "..but I cannot create dependency
between ports and the component ....".
You say that you want to somehow "link port to a component".
A Component is an EncapsulatedClassifier and thereby has an ownedPorts
collection (ports are owned by composition).
I would need some clarification on what you are trying to accomplish.
- James.
"charfi asma" <asma@charfi.com> wrote in message
news:fq8u1f$pr$2@build.eclipse.org...
> Hi,
>
> I create a profile to model association between application and
> architecture of a System On Chip.
> I want to associate data to memory (I have a stereotype called Memory) but
> I can not create dependency between ports and the component stereotyped
> Memory.
> Does UML allow this?
> And if it is not possible to link port to a component, how can I associate
> data that flows through ports with the component stereotyped Memory?
>
> thanks a lot
>
> Asma
>
|
|
|
| Re: dependency and allocation [message #626116 is a reply to message #477011] |
Fri, 29 February 2008 12:06 |
| Eclipse User |
|
|
|
.... You are perhaps trying to associate ports on different Components in
which case you use a Dependency or possibly an InformationFlow or possibly
Connector if you are using the component with the context of some
StructuredClassifier...
I would need more info.
- James.
"James Bruck" <jbruck@ca.ibm.com> wrote in message
news:fq9dig$9lv$2@build.eclipse.org...
> Hi Charfi,
>
> I'm not certain what exactly you mean by "..but I cannot create dependency
> between ports and the component ....".
> You say that you want to somehow "link port to a component".
>
>
> A Component is an EncapsulatedClassifier and thereby has an ownedPorts
> collection (ports are owned by composition).
>
> I would need some clarification on what you are trying to accomplish.
>
> - James.
>
>
> "charfi asma" <asma@charfi.com> wrote in message
> news:fq8u1f$pr$2@build.eclipse.org...
>> Hi,
>>
>> I create a profile to model association between application and
>> architecture of a System On Chip.
>> I want to associate data to memory (I have a stereotype called Memory)
>> but I can not create dependency between ports and the component
>> stereotyped Memory.
>> Does UML allow this?
>> And if it is not possible to link port to a component, how can I
>> associate data that flows through ports with the component stereotyped
>> Memory?
>>
>> thanks a lot
>>
>> Asma
>>
>
>
|
|
|
| Re: dependency and allocation [message #626117 is a reply to message #477012] |
Mon, 03 March 2008 16:39 |
| Eclipse User |
|
|
|
hi james,
that exacteley what I want to do , associate one port (of a component
stereotyped "applicationcomponent") with a component stereotyped "Memory" to
say that datas that flows from the port are stocked in the memory.
I want to stereotype my dependancy "dataallocation".
My question is, can we use dependancy to link a port to a component.
Is this conform to the UML spec.
thanks
"James Bruck" <jbruck@ca.ibm.com> a
|
|
|
| Re: dependency and allocation [message #626124 is a reply to message #477013] |
Mon, 03 March 2008 17:18 |
| Eclipse User |
|
|
|
Hi Charfi,
Yes absolutely, you can use a dependency for that.
You can draw a dependency between any NamedElement ( just about anything in
UML ).
The UML superstructure spec has examples where a dependency is drawn between
various required/provided interfaces on ports and drawing dependency between
port and component is fine.
From the spec:
A dependency is a relationship that signifies that a single or a set of
model elements requires other model elements for their specification or
implementation. This means that the complete semantics of the depending
elements is either semantically or structurally dependent on the definition
of the supplier element(s).
Cheers,
- James.
"charfi asma" <asma@charfi.com> wrote in message
news:fqgrhp$4pk$2@build.eclipse.org...
> hi james,
> that exacteley what I want to do , associate one port (of a component
> stereotyped "applicationcomponent") with a component stereotyped "Memory"
> to say that datas that flows from the port are stocked in the memory.
> I want to stereotype my dependancy "dataallocation".
> My question is, can we use dependancy to link a port to a component.
> Is this conform to the UML spec.
> thanks
> "James Bruck" <jbruck@ca.ibm.com> a
|
|
|
|
Powered by
FUDForum. Page generated in 0.46345 seconds
Home