Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

How to enable link constraints to support satisfied by or satisfies across components in RDNG project

 When we are trying to link an artifact in one component with satisfied by with artifact present in another component for example: 


Component 1 has System Requirements artifacts and Component 2 has Software Requirements artifacts. 
Now artifact in System Requirements component needs to link to artifact in Software Requirements with Satisfied by or Satisfies link constraints. 

When we tried to link as above we are getting error saying: 

"The Satisfied By link can not be created to Software Requirements component in (project (RM))" 

Above link type is working perfectly for the artifacts within System Requirements component, problem occurring when we tried to link artifact from Software Requirements component. 

And on similar line, we are not able to add Validated By link under link constraints similar to above requirement even with in same component. 

Here we are looking for ability to add System Requirements/Software Requirements with Validated By to Implementation Proxy artifact types.

Thanks & Regards,
Pradeep

0 votes

Comments

The oslc_qm:validatesRequirement link is owned by a test case in ETM and runs from that test case to a requirement. See https://docs.oasis-open-projects.org/oslc-op/qm/v2.1/os/quality-management-shapes.html#TestCaseShape.
"Validated by" is the inverse label for that relationship.

 Hi David Honey,

Thanks for the inputs on validated by and validates.

Could you please share the instructions how to enable the configuration for linking artifacts with satisfied by or satisfies between different components within RM project?

Thanks & Regards,
Pradeep

When you say "constraint" do you mean "link constraint"? Docs for link constraints are here https://www.ibm.com/docs/en/elms/elm/7.0.2?topic=properties-link-constraints - important to note a) that once you define any link constraint all linking has to meet specified link constraints, and b) if linking between components then exact same link types and constraints have to be defined in each component. It's a very good idea to have URIs on all link types; these are already on system-defined link types you should ensure identical link types have the same URI in each component.


Links can be created from either end but are always stored at the 'from' end - so your user must have permission to modify the 'from' end of the link, e.g. at the Software Requirement end which would read like 'Software Requirement Satisfies System Requirement'.

The system-defined link type Validated By is an OSLC link type and can only be created from ETM to RM, i.e. can't be used RM->RM. You can create your own custom link type for the purpose you want - but don't call it Validates/Validated By



One answer

Permanent link

Could you please share the instructions how to enable the configuration for linking artifacts with satisfied by or satisfies between different components within RM project?


0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 6,131

Question asked: Apr 18 '23, 5:03 a.m.

Question was seen: 1,038 times

Last updated: Apr 21 '23, 4:03 a.m.

Confirmation Cancel Confirm