Specification Common Elements (SCE) 1.0 FTF — Open Issues - OMG Issue Tracker

Key: SCE-53

Status: closed

Source: BPM Advantage Consulting ( Dr. Stephen White)

Summary:

Theoretically, SCEDI should be able to be re-used by other BPM+ languages (e.g., SDMN) without the other language creating simple marker classes that do not extend the SCE classes. However, SCEDI was developed with abstract classes. If these classes were changed to concrete, the other languages can remove their unnecessary classes from their languages.

Reported: SDMN 1.0b1 — Wed, 8 Nov 2023 17:34 GMT

Disposition: Resolved — SCE 1.0b2

Disposition Summary:

Update SCEDI classes to allow direct re-use by other languages

Theoretically, SCEDI should be able to be re-used by other BPM+ languages (e.g., SDMN) without the other language creating simple marker classes that do not extend the SCE classes. However, SCEDI was developed with abstract classes. If these classes were changed to concrete, the other languages can remove their unnecessary classes from their languages.

Updated: Mon, 16 Sep 2024 14:12 GMT

Attachments:

Figure 2 - SCE High-Level Elements v7.svg 573 kB (image/svg+xml)
Figure 25 - SCEDI MM.svg 38 kB (image/svg+xml)
Figure 26 - SCEDI Diagrams.svg 240 kB (image/svg+xml)
Figure 27 - SCEDI Diagram Element.svg 183 kB (image/svg+xml)
Figure 4 - The SCE Packaging Elements Metamodel V2.svg 185 kB (image/svg+xml)
Figure 5 - SCE Packaging Elements Metamodel V5.svg 424 kB (image/svg+xml)
Figure 7 - SCEModel MM V5.svg 534 kB (image/svg+xml)