Hello, Boris,
This is really a key issue for a "real life" project. I have recently posted a subject about guidelines for collaborative work, and Rafaël (one of the authors of the Tutorial) was aware of the need and willing to work on this subject. As far as I know, there is no way to "import" one model into another one, which would be another way of breaking down a model, instead of splitting a huge one with "control". It would be especially useful when you want to reuse existing models (i.e. of standard components). We have a similar need, but with ClearCase. We intended to access the sub-model through the top-level one, while preventing changes to other parts of the model by check-outing only the sub-model's files. This way, we expected that new common elements created in the top-level model, or even other sub-models could be referenced in the modified sub-model. However, we encountered cases where Papyrus asked to remove the read-only flag on other parts of the model, when saving, although we modified or created things only in the (checked-out) sub-model. I suspect Papyrus doesn't bother about read-only files when editing the model, and might need to record data in model elements outside of the modified sub-model. So this strategy seems flawed. Moreover, it seems that when one sub-model has references to another one, controlling can lead to unresolved references (items shown with an "X" and no properties). So, it's probably better to "control" empty packages and fill them afterwards. Now, we're stuck and desperately need help in order to set up a working collaborative environment. With best regards, Yannick. De : [email protected] [mailto:[email protected]] De la part de Topcased user list where issues are discussed Envoyé : jeudi 4 avril 2013 15:34 À : [email protected] Objet : [Topcased-users] Papyrus Collaboration - cross-referencing elements across submodels? Hi there! :-) I followed ATOS' istructions from the latest Collaborative Work tutorial ( http://gforge.enseeiht.fr/docman/view.php/7/4803/TPC_5.3.0_UML%26SysML_withPapyrus_features_tutorial.pdf ) to create a Papyrus model with several "Control"led resources to share the work with co-workers via SVN. We imported some Requirements and created a top-level diagram (SysML) as a starting point. Now I would like to use some elements (Blocks, Requirements) from the top-level diagram in diagrams from other files (Submodels). To me this looks impossible, because the Model Explorer shows always only the elements of the current Submodel. Did I miss anything? Generally, is it possible to reference elements across multiple submodel-sets (*.di, *.notation, *.uml, *.requirement) ? Thanks for your help, best regards Boris Budweg -- Dipl.-Inform. (FH) Boris Budweg Projektleitung F&T und Demonstratoren Diehl Aerospace GmbH An der Sandelmühle 13 D-60439 Frankfurt Tel: +49-69-5805-1478 . Der Inhalt dieser E-Mail ist für den Absender rechtlich nicht verbindlich. Informieren Sie uns bitte, wenn Sie diese E-Mail fälschlicherweise erhalten haben (Fax: +49-7551-891-4001). Bitte löschen Sie in diesem Fall die Nachricht. Jede Form der weiteren Benutzung ist untersagt. . The content of this e-mail is not legally binding upon the sender. If this e-mail was transmitted to you by error, then please inform us accordingly (Fax: +49-7551-891-4001). In such case you are requested to erase the message. Any use of such e-mail message is strictly prohibited.
_______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users
