It's all about the answers!

Ask a question

How to export Module Views through ReqIF?

Taly Hotimsky (2713957) | asked Aug 25 '15, 12:32 p.m.
edited Aug 26 '15, 9:22 a.m.
 Despite seeing the option to export Shared Module Views in the ReqIF Views menu, we couldn't make this work. 

We first created a ReqIF definition just with the View definition and tried importing it into another project.
Then we tried a ReqIF definition containing both a Module and the View and importing.

In both cases the import report indicates the view was imported successfully, but it didn't show in the target projects neither on existing modules nor on brand new modules..

Is there any additional step to make this work that we're missing?

(Tried both on 5.0 and 5.0.2 servers)

Donald Nong commented Aug 26 '15, 3:36 a.m.

It's new to me too. For me the module view only appear in the module that gets imported from the ReqIF file.

Taly Hotimsky commented Aug 26 '15, 9:19 a.m.

 Hi Donald.

In our case, not even that worked (considering our attempt with a ReqIF definition with both the Module and the Shared Module View).

I couldn't find any defects on about this and since it's a feature that's been around for a while I'm thinking a defect would've been filed by now if it was as broken as it seems to us.
That's why I'm thinking there must be an additional step. We just couldn't figure out what it'd be.

Accepted answer

permanent link
Donald Nong (14.4k314) | answered Aug 27 '15, 5:14 a.m.
After some testing and reading, I believe that we just misunderstood how the view in the ReqIF definition should work.

First of all, let's keep in mind that "view filtering information" cannot be exported using ReqIF. It's disappointing but it's clearly documented.

So what is left? Well, view column information.

When you export the view only, without any modules, the view in the ReqIF file actually contains, nothing, not even the column information! When you import such ReqIF file, the nothingness goes on. The successfully imported view (you can find a nice URL in the report), contains nothing as well. Technically speaking, it contains "something" - see blow.
<rdf:RDF xmlns:rdf="" xmlns:dcterms="" xmlns:rm="" xmlns:owl="">
  <rm:AttributeType rdf:about="">
    <rm:valueType rdf:resource=""/>
    <owl:sameAs rdf:resource=""/>
When you export the view with a module, the view column information is exported into the ReqIF file. And when importing such file, the view _should_ be created against the module as long as you can see the same view in the original module.

I hope it is clear enough now.
Taly Hotimsky selected this answer as the correct answer

Taly Hotimsky commented Aug 27 '15, 9:31 a.m.

 Hi Donald.

Thanks for the response.
Based on it I see room for an enhancement request (ie. I don't think the ReqIF should allow "nothing" to be exported) and a PMR (as even exporting the module and the view in the same ReqIF we couldn't get the view to be imported).
I'll add the enhancement link here once I've opened it.

Your answer

Register or to post your answer.