Eclipse Community Forums: Papyrus » copy classes from one model to another

Help

Home

Home » Modeling » Papyrus » copy classes from one model to another

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

copy classes from one model to another [message #1807042]

Tue, 21 May 2019 16:39

nimo mayr

Messages: 22
Registered: April 2019

Junior Member

I have a project and a 2 models (model a, model b) within.

As my first class diagram grows, I want to split this class diagram into two and want to copy a subset of some classes within a new class diagram in model b.

However, I cannot find the appropriate option for that?

Is this possible or do I have to create all new nodes again in model 2?

Report message to a moderator

Re: copy classes from one model to another [message #1807045 is a reply to message #1807042]

Tue, 21 May 2019 17:13

nimo mayr

Messages: 22
Registered: April 2019

Junior Member

Ok, I found solution: https://wiki.eclipse.org/Papyrus/UserGuide/Submodel

Report message to a moderator

Re: copy classes from one model to another [message #1849465 is a reply to message #1807045]

Thu, 20 January 2022 19:27

Lars Wilmer Thomas

Messages: 7
Registered: January 2022

Junior Member

That page is apparently outdated
Could someone please provide your solution to the task? :)

I find it odd that there is no better and comprehensive documentation and examples to be found on making the case for Papyrus to compete with proprietary tolls suites
I feel like I'm bound to keep paying my way to the top :P

Report message to a moderator

Re: copy classes from one model to another [message #1849490 is a reply to message #1849465]

Fri, 21 January 2022 13:55

Carsten Pitz

Messages: 479
Registered: May 2015
Location: Germany

Senior Member

Hi Lars,

first there is the Eclipse Papyrus Youtube channel
https://www.youtube.com/c/PapyrusEclipseUML/videos

I for myself prefer the OMG's specifications as manuals for Eclipse Papyrus. Papyrus works exactly like specified.

To compare Papyrus with other tools:

Papyrus is neither a drawing tool with repository nor a state machine to source code translator with UML/SysML diagramming added. Papyrus is a modeling tool originally (I refer to TopCased here) to support the systems engineering of highly safety critical technical systems in big organisations.

This has some implications:
* like i.e. SAP, Eclipse Papyrus is ment to be tailored to optimally fit a given SE process
* the SE process and tool usage is backed with trainings
* Papyrus focussed on formal correctness rather than on ease of use

Just my inofficial 2 cents,
Carsten

Report message to a moderator