|Re: How to organize a new Papyrus model? [message #1732218 is a reply to message #1732166]
||Fri, 13 May 2016 13:36
|| Christian Damus
Registered: July 2009
See some replies in-line, below.
On 2016-05-13 07:51:09 +0000, Harald Kornmayer said:
> Dear Developers
> I'm quite new to Papyrus, but so far I like it very much.
That's good to hear. Glad you like it!
> Starting to consolidate different modeling activities of developers in
> the context of one development project, forced me to think about the
> organisation of a Papyrus Project. What is the best way to organize a
> large modelling project?
The best way is what works for you, according to your requirements.
There are so very many ways to organize model content.
> Please correct me, if I'm wrong with my view.
> A Papyrus Project has one or many models inside. But model elements in
> one model can not be used in another model of the same Papyrus Project.
> So at the end all model
Of course models can reference and re-use elements from other models.
You just need to load those other models into your editor. On any
package in the Model Explorer, you can use the import actions in the
context menu to load content from other models.
> elements reside in one model in one Papyrus Project.
> Is there a better way to structure the model than this 1-1-Korrelation?
As I indicated above, cross-model references are fully supported. You
can optionally create actual PackageImport relationships, but that has
semantics that change the members of the importing namespace, and is
> Thank you for suggestions and discussions.
Powered by FUDForum
. Page generated in 0.01996 seconds