Why I am allowed to define two parents of an Artifact in RRC
RRC 4.0.2
Why I am allowed to define two parents of an Artifact. I would expect to be restricted like in RTC to one parent
The definition is:
If I allow multiple parent, I allow people to build a meshed net and not really a hierarchy.
Did I miss something. A special setup?
Thanks
erwin
Why I am allowed to define two parents of an Artifact. I would expect to be restricted like in RTC to one parent
The definition is:
| Decomposition | Parent Of / Child Of | (System-defined) Captures part-whole relationships between Requirements Management artifacts. These types of links are typically used to represent artifact hierarchies. |
If I allow multiple parent, I allow people to build a meshed net and not really a hierarchy.
Did I miss something. A special setup?
Thanks
erwin
Accepted answer
The link type system in RRC does not have process definition to control when or who can create link types between artifact. Only a preference on the defaults.
That said in Requirements it is possible that the requirement has multiple parents, for example I am product of both a male and female, or I am both Human and a Citizen of a country, or a Car has 4 wheels, so do other vehicles.
So once process control becomes part of the solution you will be able to automatically control link creation, until then it is a manual process.
That said in Requirements it is possible that the requirement has multiple parents, for example I am product of both a male and female, or I am both Human and a Citizen of a country, or a Car has 4 wheels, so do other vehicles.
So once process control becomes part of the solution you will be able to automatically control link creation, until then it is a manual process.