Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Papyrus » Multi model or submodel approach ?
Multi model or submodel approach ? [message #1692567] Thu, 16 April 2015 14:22 Go to next message
Lola Masson is currently offline Lola MassonFriend
Messages: 27
Registered: March 2015
Junior Member
Hello,
I want to design a system with papyrus and I want to implement the collaborative work with SVN. I see that in papyrus tutorials they explain how to create and share submodels, but what is the interest of this approach instead of create different models for every subsystem as every submodel create a new file in the view project explorer. Having every diagrams for the whole design in a same model is it interesting to make for example verifications or validations in te model, or is it just to keep the architecture of a system composed of subsystems ?
Thank you,
Lola
Re: Multi model or submodel approach ? [message #1692714 is a reply to message #1692567] Fri, 17 April 2015 12:36 Go to previous messageGo to next message
Lola Masson is currently offline Lola MassonFriend
Messages: 27
Registered: March 2015
Junior Member
What is your opinion about this ?
Re: Multi model or submodel approach ? [message #1692905 is a reply to message #1692714] Mon, 20 April 2015 14:00 Go to previous messageGo to next message
Charles Rivet is currently offline Charles RivetFriend
Messages: 219
Registered: May 2014
Location: Canada
Senior Member

Hi Lola,

I'm not sure exactly what you are asking, but let me try an answer. I am also unsure whether this is directly related to Papyrus as it appears to be more of a system/SCM architecture question.

When working on large systems, it is often a good idea to separate the model into multiple files ("modules"). this typically helps minimize (but not necessarily eliminate, conflicts when contributions ("check ins", "pushes", etc.) are made by the developers.

The way the model is segmented will depend on many things: architecture of the complete system, hierarchy of the components/modules, development team organization, platforms targeted, etc. The goals are typically to minimize dependencies in general and eliminate cross-dependencies (e.g., module A depends on module B that depends on Module C that depends on Module A) and to minimize conflicts when developers "check in" their changes. The dependencies, would be represented both as UML dependencies and relationships, but also as model imports (so that the module's elements are visible in the importing model). Note that a module should never have dependencies (import) to a module that is higher in the hierarchy.

Typically, each module will have their own diagrams. Modules that "contain" other modules will also have diagrams that show how they use the "sub-modules".

There would also be a single, "system" model that would show the dependencies at the highest level of the architecture.

Does that help?


/Charles Rivet
Re: Multi model or submodel approach ? [message #1692921 is a reply to message #1692905] Mon, 20 April 2015 15:13 Go to previous messageGo to next message
Lola Masson is currently offline Lola MassonFriend
Messages: 27
Registered: March 2015
Junior Member
Thank you,
I think I will keep the "sub-models" approach so the architecture is easier to understand.
Re: Multi model or submodel approach ? [message #1693060 is a reply to message #1692921] Tue, 21 April 2015 13:33 Go to previous messageGo to next message
Charles Rivet is currently offline Charles RivetFriend
Messages: 219
Registered: May 2014
Location: Canada
Senior Member

Hi Lola,

The sub-model approach in Papyrus just facilitates and automates some of the concepts I discussed in my previous answer, mainly the creation of the files associated with the sub-models. In my answer, you could easily substitute "sub-models" for "modules".

However, some aspects, like the management of dependencies across the hierarchy, cross-dependencies, and parallel development on models/sub-models, are still manual.

Good luck and have fun!


/Charles Rivet
Re: Multi model or submodel approach ? [message #1693076 is a reply to message #1693060] Tue, 21 April 2015 14:29 Go to previous messageGo to next message
Lola Masson is currently offline Lola MassonFriend
Messages: 27
Registered: March 2015
Junior Member
Thank you for the answer !
Re: Multi model or submodel approach ? [message #1693300 is a reply to message #1692905] Thu, 23 April 2015 04:17 Go to previous messageGo to next message
Tomas Sandkvist is currently offline Tomas SandkvistFriend
Messages: 149
Registered: October 2013
Senior Member
Charles Rivet wrote on Mon, 20 April 2015 10:00
Hi Lola,

I'm not sure exactly what you are asking, but let me try an answer. I am also unsure whether this is directly related to Papyrus as it appears to be more of a system/SCM architecture question.

When working on large systems, it is often a good idea to separate the model into multiple files ("modules"). this typically helps minimize (but not necessarily eliminate, conflicts when contributions ("check ins", "pushes", etc.) are made by the developers.

The way the model is segmented will depend on many things: architecture of the complete system, hierarchy of the components/modules, development team organization, platforms targeted, etc. The goals are typically to minimize dependencies in general and eliminate cross-dependencies (e.g., module A depends on module B that depends on Module C that depends on Module A) and to minimize conflicts when developers "check in" their changes. The dependencies, would be represented both as UML dependencies and relationships, but also as model imports (so that the module's elements are visible in the importing model). Note that a module should never have dependencies (import) to a module that is higher in the hierarchy.

Typically, each module will have their own diagrams. Modules that "contain" other modules will also have diagrams that show how they use the "sub-modules".

There would also be a single, "system" model that would show the dependencies at the highest level of the architecture.

Does that help?


Hi Charles!

Interesting discussion, since I have, while trying to figure out what is wrong with my imports tried to visualize how my models needs to be interconnected. See the attached image. Actually this image is not exactly how things are at the moment, but rather a concept of a future structure, but still shows the principals of design.

index.php/fa/21614/0/

BaseCS is a skeleton control system that my company adapts or refines for a specific customer by adding customer specific function or when necessary, modifying those already in the skeleton system.

Would you say the way it is modeled could be improved in any way?

Regards,
Tomas Sandkvist

[Updated on: Thu, 23 April 2015 04:21]

Report message to a moderator

Re: Multi model or submodel approach ? [message #1693506 is a reply to message #1693300] Fri, 24 April 2015 15:29 Go to previous message
Charles Rivet is currently offline Charles RivetFriend
Messages: 219
Registered: May 2014
Location: Canada
Senior Member

Hi Tomas,

Assuming that all elements are public within their namespaces (packages), this looks fine.


/Charles Rivet
Previous Topic:Hide type of the blocks
Next Topic:Diagram Deployment
Goto Forum:
  


Current Time: Thu May 28 05:47:17 GMT 2020

Powered by FUDForum. Page generated in 0.02192 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top