The Conceptual/Logical/Platform layers, in the default UDDL textual format, make creating Entities bulky. But if we rely on defaults (that every Composition has the same Characteristic attributes as the thing it realizes (which is the most common case), then we can specify that info once and use it at all 3 levels. We then only need to specify the Composition element type at each level.
Several possible solutions:
- a new textual syntax that supports this compressed approach - from which we generate the larger version
- GUI that hides the details even though they all exist at the time of data entry/ viewing (Sirius could be used here to create tabular entry)
- Other?
We could solve this multiple ways and then see which approach users pick. Or we can survey users and find out.
The Conceptual/Logical/Platform layers, in the default UDDL textual format, make creating Entities bulky. But if we rely on defaults (that every Composition has the same Characteristic attributes as the thing it realizes (which is the most common case), then we can specify that info once and use it at all 3 levels. We then only need to specify the Composition element type at each level.
Several possible solutions:
We could solve this multiple ways and then see which approach users pick. Or we can survey users and find out.