Book a Demo

Author Topic: Transitivity of 'Realization' (relation)  (Read 3488 times)

t_s

  • EA Novice
  • *
  • Posts: 11
  • Karma: +0/-0
    • View Profile
Transitivity of 'Realization' (relation)
« on: July 29, 2015, 10:13:56 am »
Consider the following scenario. There are several requirements (e.g., hundreds) and have several layers of parent-child relations represented, say using the the aggregation to whole relation. Further suppose that there is a component or use case that realizes a parent requirement (and parent has several layers of child requirements).

Does EA have any capability to (essentially) make the 'realization' relation/connector transitive over the child requirements: If the parent is realized in some entity, then all of it children must also be realized in the [same] entity?

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Transitivity of 'Realization' (relation)
« Reply #1 on: July 29, 2015, 12:28:49 pm »
No. You have to write your own script/code to materialize the (derived) transitive relationships (since you can't render them on a diagram otherwise).  You will also need to be able to mark and render the derivation correctly.

EA supports the IsDerived property ONLY for Associations.  We have implemented a more generalised IsDerived property for ALL relationship types and use a common rendering to indicate that.

Determining which is the canonical and which the derived relationship can, at times, be problematic.

HTH,
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!