Legacy Issue Number: 15435
Source: ProSTEP iViP Association ( Bertil Muth [X] (Inactive))
In the RFC, a "RelationGroup" element is associated to "specRelations".
However, in contrast to prior versions of the Requirements Interchange Format,
the ReqIF RFC does not account for the fact that grouped relations should either link
requirements of two specifications (e.g. Customer Requirements Specification and
System Requirements Specification) or requirements within one specification.
Thus, two associations should be added to "RelationGroup", called "sourceSpecification" and
"targetSpecification" to point out the specifications in which the
source "SpecObject" elements and the target "SpecObject" elements connected by
the "specRelations" are located.
Note that having these associations in place would also greatly increase performance of ReqIF tool
An additional constraint should be added to the RelationGroup section that defines that the "specObject" elements
connected by the "specRelations" must be referenced by a (SpecHierarchy element) of the respective specification.
Reported: ReqIF 1.0.1 — Fri, 27 Aug 2010 04:00 GMT
Disposition: Resolved — ReqIF 1.1
Update the textual description and the diagrams shown in the specification, the
machine-readable file reqif.cmof and the XML schema file reqif.xsd to reflect the
change as described in the issue.
Also, update the textual description of SpecRelationType to clarify the distinction
Updated: Fri, 6 Mar 2015 23:15 GMT
REQIF11 — Associate RelationGroup to source specification and target specification
- Key: REQIF11-1
- OMG Task Force: Requirements Interchange Format V1.1 (ReqIF) RTF