Hello Yannick, Thanks for your focus on this point.
This is a very important topic and there are tricky things when working with sub models, especially concerning the links between sub models. We still need to improve collaborative working and would be very pleased if we can get feedback from Topcased community and publish the most representative scenarios. We already have test cases on collaborative work but I think we need more. So I wait for a few days and I will organize a webex with all interested users on that topic. Regards raphaël Topcased team De : [email protected] [mailto:[email protected]] De la part de Topcased user list where issues are discussed Envoyé : jeudi 21 mars 2013 20:17 À : [email protected] Objet : [Topcased-users] Collaborative work with Topcased : guidelines for splitting models Hello, all, I've read with much interest the tutorial about collaborative work with Topcased using the "control" command. However, we are facing a significant model with several layers on the physical level (system and then several components, maybe with several levels of breakdown), and on the process level (requirements and then design). Each of these steps may require several people to work on the model. So, we need to split the overall model in a number of sub-models all more or less related to one another. When we started extracting more than one or two sub-models out of our overall model, we encountered problems like blocks or associations without any data available and "crossed". I guess this is because of the order in which we split the model (an already extracted sub-model isn't "aware" that part of the model elements it references are extracted somewhere else afterwards). So, I suppose that other Topcased users have encountered this type of need, and might be willing to share their experience and maybe guidelines to prevent breaking the model when splitting it. With best regards, Yannick. ________________________________ Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
_______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users
