Hi Cédric, Before going to far on Gendoc2 advanced context capabilities, have you seen that you have a lot of facilities to access requirements and model elements are provided in services from "requirement" external bundles (all methods are described slide 25 of Gendoc2 tutorial) ? Ex : get all requirements attached to a model element, get all Upstream requirements attached to a CurrentRequirement, etc...
If that is what you want to get, just refer to your .uml model in the context, add "requirement" to the list of importedBundles, and you can use these methods. If not, could you send us your document template (or at least the part containing this access to both requirement model and uml model), because the best solution depends on the result you want to obtain. Regards, Anne -----Message d'origine----- De : [email protected] [mailto:[email protected]] De la part de Topcased user list where issues are discussed Envoyé : mardi 15 mars 2011 15:29 À : [email protected] Objet : Re: [Topcased-users] [Gendoc2] requirement questions Hi Tristan Again, thank you for your quick help I'm closer, but I still cannot manage to do it. As the requirement model uses references to the model itself, I have big troubles to set the correct content element... Example : <Model>M/<Package>P In requirement model I see : <RequirementProject>RP/<Model>M/<Package>P But I have : <RequirementProject>RP/<HierachicalElement>.element=<Model>M .children=<HierachicalElement>.element=<Package>P So, I tried : 'identifier=”RP”/{1} : no error 'identifier=”RP”/element="M" : error 'identifier=”RP”/element.name="M" : error ... So I can't manage to get it work Would you have a sample of a proper requirement element tag for context ? For this day, I earned a good headache but no requirement doc. Kind regards _______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users ________________________________ 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 Origin ne pourra être recherché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 recherché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 Origin group liability cannot be triggered for the message content. Although the sender endeavours 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/mailman/listinfo/topcased-users
