eclipse-capella / capella-requirements-vp

This add-on allows importing a set of requirements from a ReqIF file
Eclipse Public License 2.0
18 stars 15 forks source link

[ReqIF] Spec object attribute not imported depending on the long name of the attribute definition #161

Closed nercisse closed 2 years ago

nercisse commented 2 years ago

Hello everyone,

II have been doing some test with the capella requirement viewpoint on Capella 5.2 with a ReqIF file I found as part of the test suite of this repo in capella-requirements-vp/tests/org.polarsys.capella.vp.requirements.ju/model/inputs/Sample1.reqif

Taken as is, it seems to work fine

test_puid

I then just modified the long name of the attribute definition from IE PUID to IE UUID in the the SPEC-OBJECT-TYPE as shown in the diff of the two files:

test_diff

Weirdly enough, the spec object type "Requirement Type" is correctly imported, but the attribute in the object type is not imported any more. Yet the OBJECT-TYPE has not changed, it still references the same OBJECT-TYPE-SPEC and has an ATTRIBUTE-VALUE-XHTML that references the ATTRIBUTE-DEFINITION-XHTML

test_uuid

I did further tests with ATTRIBUTE-DEFINITION-STRING objects instead of ATTRIBUTE-DEFINITION-XHTML and saw the same behaviour. The long name seem to have an impact on the import result and I don't understand why that is.

nercisse commented 2 years ago

Nevermind, I just realised that the import is based on the preferences

pref

That explains why some stuff is not being imported, though I don't quite get where does the ReqIF attributes list come from... (leaving RMF aside).

As far as I know, the reqIf standard does not specify any attribute in particular (e.g. ReqIF.ForeignID, ReqIF.ChapterName, etc...)

Am I missing something?

Cheers

nercisse commented 2 years ago

For those who like me didn't know, the attribute names come from a convension (not the standard). More info here:

https://www.prostep.org/fileadmin/downloads/prostep-ivip_ImplementationGuide_ReqIF_V1-8.pdf

I'll close this issue.