| Key | Issue | Reported | Fixed | Disposition | Status | |
|---|---|---|---|---|---|---|
| ALMAS14-20 | PSM sections duplicate code | SCE 1.0b2 | open | |||
| SCE11-8 | SCE Model XMI File is not an instance of SCE but UML | SCE 1.0b2 | open | |||
| SCE11-7 | Add Mapping of SCE Term functions to MVF in Spec | SCE 1.0b1 | open | |||
| SCE11-6 | SCE Relationship Kinds Should Cover All BPM+ Relationships | SCE 1.0b1 | open | |||
| SCE11-1 | Add Notations for Relationship Kinds in SCE | SCE 1.0b1 | open |
The PSM sections of the specification include the code from the PSM machine readable files. This is duplication and a potential source of error, whilst not especially helpful to be provided outside of an IDE editor.
The Kinds should be instances of Kind from SCE not instances of UML InstanceSpecification. It needs to be converted from UML to use the SCE metamodel itself. See SCE model files for an example. Pete Rivett has XSLT to automate this.
The changes to the current SCEVocabulary models should be mapped to MVF.
Basically all lines between model elements in all the BPM+ models (BPMN, CMMN, DMN, SDMN, BKPMN, Parties, and PPMN) should be (theoretically maybe) derived from one of the SCE Relationship Kinds.
And if we define the basic notation for each of these relationships, then all subsequent models will provide consistent relationship notations.
This will ensure that all downstream languages will use the same notation if they have connectors based on the RelationshipKinds.