|Re: Requirements links created after initial reqif import break after reimport [message #1830238 is a reply to message #1829396]
||Tue, 21 July 2020 16:49
| Karl Gruber
Registered: July 2020
I used EOLE_SSS.reqif for testing and added xml-elements for defining relation-types and one relation (with the LONG-NAME-attribute added), see attached file EOLE_SSS_modified_with_relations.diff.
First I imported the reqif-file, than I create a SAB-diagram added the two requirements which are referred as source or target by the defined reqif-relation, and created two internal links between both reqiurements and the system-component, see file: Capture1.PNG.
Second I started a reimport of the same reqif-file, see file: Capture2.PNG
The Diff-Merge-editor marked req-links between the requirements, which had been either source or target of the reqif-relation, and the system-components for removal.
Completing the merge resulted in an updated SAB-diagram, see file: Capture4.PNG
All links between requirements and architectural elements (components, functions) remained, ONLY when the requirement had NOT been referenced as source or target within a reqif-relation.
I would consider that behavior as bug.
Is the site https://github.com/eclipse/capella-requirements-vp/issues the correct place to raise a bug towards req-viewpoint development?
Powered by FUDForum
. Page generated in 0.02040 seconds