Systems Analysis and Design (SIG SAND)
Loading...
Paper Type
Complete
Paper Number
1333
Description
In conceptual modeling, secondary notation refers to additional graphical details on top of the default syntax to emphasize particular meaning. Applying it in a nonsystematic way or without full knowledge of its impact on the model’s presentation can have a negative influence on the model’s understandability. This paper advocates the idea that secondary notation should be induced by the modeling environment based on each model element's semantics and context. For this, we consider that secondary notation should be treated as an artifact in its own right to be realized by modeling method engineers and not just an afterthought or a usability feature added by tool developers. We propose a set of techniques that can be embedded in a modeling environment to denote rules for notation variability according to various drivers and criteria. This becomes a rule-based cross-cutting aspect of a modeling method, overtaking the traditional approach where the modeling canvas is a drawing surface for prescribed static shapes.
Recommended Citation
Ghiran, Ana-Maria and Buchmann, Robert, "Engineering Semantics-driven Secondary Notation for Domain-specific Conceptual Modeling" (2021). AMCIS 2021 Proceedings. 3.
https://aisel.aisnet.org/amcis2021/sig_sand/sig_sand/3
Engineering Semantics-driven Secondary Notation for Domain-specific Conceptual Modeling
In conceptual modeling, secondary notation refers to additional graphical details on top of the default syntax to emphasize particular meaning. Applying it in a nonsystematic way or without full knowledge of its impact on the model’s presentation can have a negative influence on the model’s understandability. This paper advocates the idea that secondary notation should be induced by the modeling environment based on each model element's semantics and context. For this, we consider that secondary notation should be treated as an artifact in its own right to be realized by modeling method engineers and not just an afterthought or a usability feature added by tool developers. We propose a set of techniques that can be embedded in a modeling environment to denote rules for notation variability according to various drivers and criteria. This becomes a rule-based cross-cutting aspect of a modeling method, overtaking the traditional approach where the modeling canvas is a drawing surface for prescribed static shapes.
When commenting on articles, please be friendly, welcoming, respectful and abide by the AIS eLibrary Discussion Thread Code of Conduct posted here.