nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Separate requirements export in different chapter

medini_1056077241

Hi,

i'm currently working to create a template to export requirements from a project.

The requirements are organized as depicted in this image:

So there can be one or more requirement diagram (CF001, CF002, etc..)that organize the overall requirements.

A requirement is included in at least one diagram.

I'd like to export a separate chapter for each requirement diagrams, containing image diagram and the description of the included requirements.

now i'm using an OCLData set with the following query:

SafetyRequirement.allInstances()

with this query i can extract all requirements and i can filter them for example using the kinf of requirement as key, to create "static" subchapters.

I'd like to create a flexible way to separate requirements according to the requirements diagram structure. i don't know at prior the requirement diagram number.

Thanks

Samuele

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1056077241

Problem solved. It can be closed.

medini_1024169437

Hi Samuele, although this was nicely "self resolved" by you, could you post how you solved the problem?

Thanks

Jan

medini_1056077241

hi,

basically starting from OCLData source i've created a DataSet with this query:

PJDiagram.allInstances()->select(dia : PJDiagram | dia.mediniGetTracedElements(safetygoals::SafetyGoal)->isEmpty())

and i've added the computed column with this expression:

var visibleElements = "";

function getVisibleElements(parent) {
 var children = parent.getChildren();
 for (var i = 0; i < children.size(); i++) {
 var child = children.get(i);
 try {

 	visibleElements += child.getElement().getMediniIdentifier() + " ";
 	getVisibleElements(child);
 } catch (e) {
 	// catch empty
 }
 } 
 }

getVisibleElements(row["diagram"].getObject());
visibleElements;

So now i have, for all diagrams, the Medini Identifier of each contained object. This contained object are the requirements if the diagram is a diagram requirement.

Now i've created a list that uses the Architecture image data set and inside this list there is a nested list that uses the requirements dataset (that contain all requirements of the model). Now i've simply applied the filter:

BirtStr.search(row["Medini Identifier"],row._outer["ElementsOnDiagram"])==-1 is False

and for some reason the row._outer select the current istance of the diagram. So the result is a list of diagrams and for each diagram is appended a list of requirements thare are contained in that particular diagram, thanks to the filter.

Samuele

medini_1024169437

Thanks for posting. Note that the OCL query could be improved.

If you have PJDiagram as Context Type the engine queries all instances of that class for you so using

PJDiagram.allInstances()

is overkill. You may reduce to:

self->select(dia : PJDiagram | dia.mediniGetTracedElements(safetygoals::SafetyGoal)->isEmpty())

Thanks for posting!

Jan

medini_1056077241

Hi Jan,

we are using PJDiagram.allinstances instead of self ->…

because we have seen that using self. requires to define the path "platform:/resource/XXX/.project.medini" in the OCLDataSource. Where XXX is the project folder name.

See image:

Instead using PJDiagram.allistances for some reason that i don't know it extracts the report of the currently selected project.

This is usefull for us because we are building templates to be used for various projects.

Am i missing something?

Thanks

Samuele

medini_1024169437

That sounds very odd... are you referring to the "Preview" section of the OCL Data Source dialog?

I assume to. In that case it would be very strange that they work differently. I HAVE to check :-)

Thanks for the hint... but please confirm/deny my understanding

Jan

medini_1056077241

Hi Jan,

i'm referring to both:

-the "Preview Results" section of all the data set that uses the OCLDataSource.

-the actual export content of the custom exports.

If i specify self…… in the data set query, it extracts in the Preview Results all the time the content from the project that is specify in the DataSource (see may previous post image). And also the export that uses that template uses the contents of the poject specified in the DataSource, not the project selected during the export process.

Using PJDiagram.allistances this doesn't happen (however the Preview Results) doesn't work, but i can live with that.

Samuele

medini_1024169437

This sounds weird. The preview pane indeed only works with the project that is defined in the data source. Since there is no medini project selected at this time. However, self and allInstances should work the same - and do in my case.

When running report generation via Report -> Custom Report or via Report -> <Report From Project> in any case the data should come from the project itself, again independent on self or allInstances().

Jan