Gendoc2 uses M2T Acceleo as scripting language inside tags <gendoc>.
In Acceleo or OCL language, "self" is the current element (current element in a
loop, ...)
Inside <gendoc> tag, the first value it takes is the value defined by
<context> tag, where you define the model (in your example ${projectName}.uml
), and the element (by default, it is the model root).
So in your example, "self" refers to the model root.
Best regards,
Anne
De : [email protected]
[mailto:[email protected]] De la part de Topcased user
list where issues are discussed
Envoyé : vendredi 27 janvier 2012 16:40
À : [email protected]
Objet : Re: [Topcased-users] Usage of getRequirementProject(EObject) in the
requirement bundle
Thanks for your patience Anne,
One last question hopefully.
What is 'self' referring to below?
<gendoc>
All Upstream requirements :
[for(req:ttm::Requirement | self.getRequirementProject().
upstreamModel.documents.children.oclAsType(ttm::Requirement))]
[req.ident/]
[/for]
</gendoc>
On Fri, Jan 27, 2012 at 10:19 AM, Topcased user list where issues are discussed
<[email protected]<mailto:[email protected]>>
wrote:
Brad,
The ModelExplorer view is not the place to see requirements.
Two views are dedicated to the management of requirement :
- In "Upstream requirement" view, you will see the upstream
requirements contained in the .requirement model you have associated to your
model
- In "Current requirement" view, you can see the links between
upstream requirements and model elements : the structure corresponds to the
model structure and you see CurrentRequirements under the model elements they
are attached to.
If you have Upstream requirements inside the "Upstream requirement" view, it
means the requirement model is correctly linked to your model.
Best regards,
Anne
De :
[email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
De la part de Topcased user list where issues are discussed
Envoyé : vendredi 27 janvier 2012 16:04
À : [email protected]<mailto:[email protected]>
Objet : Re: [Topcased-users] Usage of getRequirementProject(EObject) in the
requirement bundle
Thanks Anne,
But there is still something I must be overlooking. I attached the requirements
to my model following the procedures in the Requirements Tutorial but I guess I
don't know to what element in my model they have been attached to.
Using the following produced no results.
<config> <drop/>
<param key='projectName' value='JEESG'/><drop/>
<param key='project' value='${workspace_loc}\${projectName}'/><drop/>
<param key='model' value='${project}\Models\${projectName}.uml'/><drop/>
<output path='${project}/Generated/requirements_output.docx'/><drop/>
</config><drop/>
<drop/>
<context model='${model}' importedBundles='gmf;papyrus;requirement'
searchMetamodels='true'/>
<gendoc> <drop/>
All Upstream requirements :
[for(req:ttm::Requirement |
self.getRequirementProject().upstreamModel.documents.children.oclAsType(ttm::Requirement))]
[req.ident/]
[/for]
</gendoc><drop/>
So they are not attached to the topmost Model element. The Model Explorer View
offers no clues as to which element they might be attached to. If I have linked
the requirements to my model properly should this work? Or is there something
I've done wrong linking the requirements to my model?
Thanks for your help.
Brad
On Fri, Jan 27, 2012 at 7:59 AM, Topcased user list where issues are discussed
<[email protected]<mailto:[email protected]>>
wrote:
Hi Brad,
The getRequirementProject() method is called from an element of your UML/SysML
model that has an attached requirement model.
It is used to access the full requirement model : RequirementProject is the top
element of this metamodel, thus you have to know the requirement meta-model in
order to use this method correctly.
For example, from a RequirementProject, you can get full list of Upstream
requirements for the current UML model with the following code :
<gendoc>
All Upstream requirements :
[for(req:ttm::Requirement |
self.getRequirementProject().upstreamModel.documents.children.oclAsType(ttm::Requirement))]
[req.ident/]
[/for]
</gendoc>
Best regards,
Anne
De :
[email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
De la part de Topcased user list where issues are discussed
Envoyé : jeudi 26 janvier 2012 18:59
À : [email protected]<mailto:[email protected]>
Objet : [Topcased-users] Usage of getRequirementProject(EObject) in the
requirement bundle
Two part question really -
1. on what EObject in the model is this method used on? So I have a model in
which I have associated external requirements and I see them in the Upstream
Requirement view. I can drag them to model components or Current Requirements
view and all is well. But I can't really tell from the Model Explorer view (or
any other way) what object in the model the RequirementProject is associated
with so I'm not really sure on what object in my model this call should be made.
2. According to the tutorial this method returns a RequirementProject object.
How does one then make use of this?
Any help would be appreciated. An example that produces upstream requirements
for a model in which they have been associated would be ideal.
Thanks in advance.
Brad
________________________________
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]<mailto:[email protected]>
http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users
_______________________________________________
Topcased-users mailing list
[email protected]<mailto:[email protected]>
http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users
_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users
