Eclipse Community Forums: Papyrus » extending requirement diagram in SysML

Help

Home

Home » Modeling » Papyrus » extending requirement diagram in SysML

Show: Today's Messages :: Show Polls :: Message Navigator

extending requirement diagram in SysML [message #997795]

Tue, 08 January 2013 13:56

Jeni Martin
Messages: 15
Registered: November 2012

Junior Member

Hi,

I just started working with Papyrus and I went through tutorial for making UML profiles (with the example of requirement Model). Now I want to extend the Requirement element in SysML. So I want to choose Requirement as my base metaclass. How can I do that?

Thank you so much in advance for your help.

Report message to a moderator

Re: extending requirement diagram in SysML [message #997852 is a reply to message #997795]

Tue, 08 January 2013 16:47

Christian W. Damus
Messages: 550
Registered: July 2009

Senior Member

Hi, Jeni,

You should be able to import the SysML profile as an imported package
in your profile. In the Model Explorer, select the root package of
your profile and select "Import Registered Package" (not sure of the
exact label) in the context menu. Can you choose the SysML profile in
this dialog? If so, then you'll end up with that profile imported and
its types available to use in generalization relationships,
associations, etc.

However, I'm not sure that the UML2 implementation of "dynamic
profiles" support these kinds of dependencies between profiles very
well. I think it may copy all of the definitions from the referenced
profiles (SysML in your case) into your profile's Ecore definition, so
that at the EMF level you end up with a distinct copy of SysML that
isn't interoperable with the original SysML profile. Perhaps somebody
in this newsgroup knows better than I how this works with dynamic
profiles. I know that dependencies between profiles work well when the
profiles are statically generated.

HTH,

Christian

On 2013-01-08 18:56:19 +0000, Jeni Martin said:

> Hi,
> I just started working with Papyrus and I went through tutorial for
> making UML profiles (with the example of requirement Model). Now I want
> to extend the Requirement element in SysML. So I want to choose
> Requirement as my base metaclass. How can I do that?
>
> Thank you so much in advance for your help.

Report message to a moderator

Re: extending requirement diagram in SysML [message #998727 is a reply to message #997852]

Thu, 10 January 2013 10:11

Camille Letavernier is currently offline

Camille Letavernier
Messages: 224
Registered: February 2011

Senior Member

Hello,

I think the "Import registered package" menu won't work in this case. It is intended for UML Libraries.

However, the "Import registered profile" menu will work fine.

You cannot choose the SysML Requirement as the "Base Metaclass" of your new Stereotype. Instead, you should create a Generalization between your Stereotype and the SysML Requirement.

Regards,
Camille

Report message to a moderator

Re: extending requirement diagram in SysML [message #998732 is a reply to message #998727]

Thu, 10 January 2013 10:19

Christian W. Damus
Messages: 550
Registered: July 2009

Senior Member

Hi, Camille,

Thanks for the correction of the menu action.

Indeed, stereotypes are not metaclasses and thus cannot be extended by
stereotypes. But the Eclipse UML implementation supports
generalization of stereotypes well (though, as I said, I'm not sure
about how practical it is to have generalization relationships to
stereotypes in another profile when the profiles are dynamically
defined).

cW

On 2013-01-10 15:11:59 +0000, Camille Letavernier said:

> Hello,
>
>
> I think the "Import registered package" menu won't work in this case.
> It is intended for UML Libraries.
>
> However, the "Import registered profile" menu will work fine.
>
> You cannot choose the SysML Requirement as the "Base Metaclass" of your
> new Stereotype. Instead, you should create a Generalization between
> your Stereotype and the SysML Requirement.
>
>
> Regards,
> Camille

Report message to a moderator

Re: extending requirement diagram in SysML [message #1000342 is a reply to message #998732]

Mon, 14 January 2013 10:04

Jeni Martin
Messages: 15
Registered: November 2012

Junior Member

Hi,

Thank yuo so much for all replies and helps.

I imported the SysML as standard profile and made a new stereotype (without any new property)which is the specialization of Stereotype Requirement (from SysML). but when I validate it, it says not all members of namespace Profile are distinguishable within it.

What do you think?

Thanks.

Report message to a moderator

Re: extending requirement diagram in SysML [message #1000588 is a reply to message #1000342]

Mon, 14 January 2013 23:00

Christian W. Damus
Messages: 550
Registered: July 2009

Senior Member

Hi, Jeni,

A package import adds members of the imported package (SysML profile)
into the importing namespace (your profile), but only those members
that have names that are distinct from all of the names in the
importing namespace. Thus, a package import shouldn't be able to add
duplicate names, which is what this warning is about.

Which element names are repeated?

cW

On 2013-01-14 15:04:26 +0000, Jeni Martin said:

> Hi,
>
> Thank yuo so much for all replies and helps.
>
> I imported the SysML as standard profile and made a new stereotype
> (without any new property)which is the specialization of Stereotype
> Requirement (from SysML). but when I validate it, it says not all
> members of namespace Profile are distinguishable within it.
>
> What do you think?
>
> Thanks.

Report message to a moderator

Re: extending requirement diagram in SysML [message #1001498 is a reply to message #1000588]

Wed, 16 January 2013 15:41

Jeni Martin
Messages: 15
Registered: November 2012

Junior Member

yeah, Thank you so much. This is the problem. Smile

Report message to a moderator

Previous Topic:	Best way to extend papyrus to add free string for multiplicity
Next Topic:	Help!

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed May 22 03:55:54 EDT 2013