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; } } }

ReqIF/RIF with scripting

medini_1052758087

Hello Jan,

is it possible to export ReqIF/RIF format using scripting?

Kind regards,
Smitta

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Smitta,

automating ReqIF export is not feasible I'm afraid at the moment.

Jan

All comments

medini_1024169437

Hm, difficult but not impossible. We may expose something the typical "reqif.js" way but it would be a bit fragile and difficult to maintain.

Jan

medini_1023909254

Hi Smitta, what is the use-case behind this?

Eckhardt

medini_1053080245

Hello,

I don't know if it was my request but I request the same thing to Medini support. The use cases are the following:

-->we use classically requirements editing table to edit our requirements within MEDINI. But to be able to get the HW item related to the function for which I have allocated the requirement, I have created a simple script which display that.

(1)We want to use the requIF export feature to get these requirements (and scripting fields) and use it into another tool for system engineering.

(2)It seems that scripting field are declared but data are not exported...

It would be helpful to find a way to get this information into the ReqIF generated by MEDINI

medini_1024169437

Hi Romain,

so the request is not to *trigger* the ReqIF export in a script but to export scripted properties into ReqIF, right? I know that there is exactly the limitation, that derived properties are currently excluded by intention.

I think the argument here is that a scripted property can return arbitrary content and its not fully clear how to type the exported field. However, we have this "Type Hint" in place so we may improve here in the future to at least optionally export scripted fields.

Would that be the desired feature?

Happy Scripting

Jan

medini_1033829014

Perhaps one workaround could be to implement "mirror properties" for all derived profile properties you want to export to the requirements tool. This means string profile attributes with a similar name as the derived profile property you want to export.

Then you create a script that, when manually started, copies a snapshot of the interesting derived properties into the mirror string properties. Of course, if something is not a string by nature (e.g. a reference to another object), you will have to find an appropriate string representation for it, e.g. the ID or name of the referenced components. From there, an export to ReqIF should be possible,

Would this help?

Best regards

Bernhard

medini_1053080245

@Jan Mauersberg: yes this is the desired feature ;-)

@Bernhard Kaiser: I am a not a scripting expert in MEDINI. So I am afraid to not be able to do that by myself... If I understand well, I could create script manually started to make some copy of scripting field into not-scripting field?

medini_1052758087

@ Eckhardt: I am sorry somehow I missed it, the use case was bit different from this conversation.The customer wants to automate the export ReqIF/RIF format using script.

medini_1024169437

Romain,

yes, that was what Bernhard proposed. The scenario would be like this:

You have script aka derived property A which returns a nice result but is ignored by ReqIF
You define a string property B and then a script that takes A and writes the value into B
B is then exported by ReqIF

A bit cumbersome but at least a workaround.

Well, that would raise the question, why we need A in the first place? The script may calculate the value of A and write it into B always.

Jan

medini_1024169437

Smitta,

automating ReqIF export is not feasible I'm afraid at the moment.

Jan

medini_1033829014

Not sure if there are different topics being mingled up at the moment: The Idea I had in mind and that Smitta quoted was not about automating the ReqIF export.

It was about a script that copies values from derived profile properties (which apparently cannot be part of a ReqIF export) into textual attributes that mirror a snapshot of their current values and can be included in the ReqIF export. The script that does this copy action would have to be started by hand, and also the ReqIF export. So there would be two manual actions to be performed in a row.

Best regards

Bernhard

medini_1024169437

Yes, two separate use cases, anyway, no problem to handle both in this article :-)

Jan

medini_1053080245

Thanks all of you for your answers.

If i understand well, two different use cases but leading to the same need for me at the end: Get a REQIF export, where scripting fields are exported. And if i summarize, current status is:

Use case A: choose when doing manual REQIF exporting, if scripting fields should be exported and if Yes is selected then REQIF file will contain it --> not available today. It will be one day? If yes what is the timeline?
Use case B: write a dedicated script (me) to manualy export REQIF data with an intermediate step where scripting fields are copied into string fields --> possible but script still need to be written...

Am I right?

medini_1024169437

Yes and no I would say, the two things are still separated I think.

We separate manual and script triggered export, first is available second is not and difficult at the moment, still *both* ways use the internal ReqIF export function
That function currently ignores features which are scripted and features that are "hidden", there is no timeline but definitely something on the roadmap
Now use case B is the way to cope with all these issues for time being, so a solution that you can use right now
Idea is to - instead of scripting a property - moving that code into a batch script and write the result into a plain string proeprty
then use the normal existing manual ReqIF export

Hope that clarifies this

Jan

medini_1055811001

Hello,

Coming to the question from Romain, I'm not expert in scripts either ...

Could you please give an example about what this script would look like ? (i.e. "a script that takes A and writes the value into B")

Regards,

Thibaut

medini_1024169437

Well, I actually meant something like this:

// find all requirements and aggregate data
finder.findByType(Metamodel.safetygoals.SafetyRequirement).forEach(aggregate);

function aggregate(req) {
 // we calculate any value based on the state of the requirement
 var a = req.identifier + "-" + req.kind + "-" + req.state; // <-- just an example

 // now we write that into a string property b which we prepared beforehand in the profile
 req.user_b = a; 
}

Aggregation of course will be prob. more complex but this should explain the approach.

The value may then for example look like:

B will be then exported in next ReqIF export.

Happy Scripting

Jan

medini_1055811001

Thanks Jan! It works perfectly

I have an extra question..

Currently Medini is configured so that "ID" is the "ReqIF.Name" exported attribute.

Is there a way to make "B" as the "ReqIF.Name" attribute, instead ?

medini_1024169437

Hello Thibaut,

as far as I know, there actually isn't, I'm sorry. The custom mapping support which medini offers for Jama/PTC/DOORS etc. is not there for ReqIF.

Happy Scripting

Jan