You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MangoObject.associatedMangoObjects
Figure 2 has this as a Reference to AssociatedMangoObject, and it is described as such, but I think the MangoObject should own (Composition) these containers which create the link between the MangoObject and another MangoObject.
AssociatedMangoObject.mangoObject
Figure 2 has this as a Composition relation, while the description says “Reference to the associated MangoObject”
A MangoObject should own the ‘AssociatedMangoObject’ instances, each of which references the MangoObject being associated.
AssociatedMangoObject
could this include one or more examples, perhaps extracted from the use cases, for when you would want to use this? eg: to associate a Source record to individual Detections
If the example above is correct, the AssociatedMangoObject is tagged with it’s role relative to the parent MangoObject (ie: “Detection”)
how is the MangoObject identified as the “Source”?
I don't see these in the implementation files to help out on how these fit together in practice.
The text was updated successfully, but these errors were encountered:
MangoObject.associatedMangoObjects
Figure 2 has this as a Reference to AssociatedMangoObject, and it is described as such, but I think the MangoObject should own (Composition) these containers which create the link between the MangoObject and another MangoObject.
AssociatedMangoObject.mangoObject
Figure 2 has this as a Composition relation, while the description says “Reference to the associated MangoObject”
A MangoObject should own the ‘AssociatedMangoObject’ instances, each of which references the MangoObject being associated.
AssociatedMangoObject
I don't see these in the implementation files to help out on how these fit together in practice.
The text was updated successfully, but these errors were encountered: