Implementation & Migration Layer – relationship anomaly
I can’t think of an explanation as to why a Work Package is allowed to realise a Deliverable, when in all other Layers only the access relationship is permitted between Behaviours and Passive Structures.
This anomaly stands out in Example 35. The WPs access Deliverables on their input side and realise Deliverables on their output side. Compare this for example with Equipment accessing Material.
I propose this anomaly be eliminated – realisation isn’t need anyway since a Deliverable can realise a Plateau.