BACM11 — Clarify the semantics of Roles WRT Capability, Process and CapabilityImplementation

CapabilityImplementation is intended to represent a configuration of Roles, AbstractBusinessObjects and Performers in an actual or planned implementation of the Capability. There may be many CapabilityImplementations of a Capability, each with different Role assignments. This cannot be the case if the Role linked to a Capability is also used by every implementation of that Capability.

Additionally, CapabilityImplementation should be capable of implementing AbstractProcesses.

Add implements_6 to Roles, update documentation, add staffs shortcut

Add implements_6 between CapabilityImplementation and AbstractProcess with the meaning that a CapabilityImplementation represents an implementation configuration of the AbstractProcess.

Change documentation of implements_7, PerformerRole and ResourceRole to clairfy that Roles are not shared - they belong to the CapabilityImplementation, AbstractCapability or AbstractProcess. When implements_5 or implements_6 exists, the Roles of the AbstractCapability or AbstractProcess should be "cloned" and specialize the Role each is cloned from and these clones are owned (implements_7) by the CapabilityImplementation.

Add "staffs" shortcut between OrgUnit and CapabilityImplementation with the meaning that the OrgUnit(s) will supply Performers and AbstractBusinessObjects to be assigned to Roles of the CapabilityImplementation.