Add the entity ProjectOrganization to provide an explicit representation of the organizations involved in a project.
ENTITY Project; id : OPTIONAL IdentifierSelect; -- 242 name : OPTIONAL DescriptorSelect; description : OPTIONAL DescriptorSelect; classifiedAs: OPTIONAL SET[1:?] OF ClassificationSelect; sameAs : OPTIONAL SET[1:?] OF ProxySelect; responsibleOrganizations : OPTIONAL SET[1:?] OF ProjectOrganization; actualStartDate : OPTIONAL DateTimeString; actualEndDate : OPTIONAL DateTimeString; plannedStartDate : OPTIONAL DateOrEventSelect; plannedEndDate : OPTIONAL DateOrEventSelect; END_ENTITY; ENTITY ProjectOrganization; description : OPTIONAL SET [1:?] OF DescriptorSelect; classifiedAs : OPTIONAL SET [1:?] OF Classification; contacts : OPTIONAL SET [1:?] OF PersonInOrganization; projectOrganization : Organization; INVERSE organizationFor : Project FOR responsibleOrganizations;
END_ENTITY;
REJECT:
Explicits can make it easier to understand how a particualr need is to be cater for by the model. However there are no end to the list of possible explicits that could be included in th model. Hence the policy is to avoid explicts. The recommende modeling style is to support explicits by means of classifications and reference data. This approach results in a cleaner model and supports full flexiblity for the various business needs.