UML 2 upgrade | DATEX II

Issue ID

Component

Methodology

Category

Feature request

Priority

Normal

Assigned

Josef Kaltwasser

Status

Fixed

Source

Website

Description

The methodology should be based un UML 2.x instead of the outdated UML 1.4. This would also imply that all tagged values are expressed as belonging to stereotypes. Hence, the "unstereotyped UML classes" (i.e. the components in DATEX II terminology) shoudl also have a stereotype (e.g. <<component>>). In this process, the UML profile provided with the Enterprise Architect model should also be revised and improved.

{"changeLogs":[{"date":1528114035381,"statusOLD":"- None -","status":"Fixed","assignedOLD":"","assigned":"Josef Kaltwasser (18)","priorityOLD":"- None -","priority":"Normal","categoryOLD":"- Select a value -","category":"Feature request","componentOLD":"- Select a value -","component":"Methodology"},{"date":1537270892274}]}

#1

Posted by Josef Kaltwasser on May 18, 2039 Permalink

#2

Posted by Josef Kaltwasser on February 18, 2039 Permalink

Proposal to base future releases of DATEX II on UML 2.x will be proposed to steering level.

DATEX II v2.0 will remain to be based on UML 1.4 to keep alignment with CEN standardisation.

The UML profile will be improved.

#3

Posted by Josef Kaltwasser on July 18, 2033 Permalink

DATEX II v3.0 will have a fully UML2 compliant UML profile.