Using objects for systems analysis
Communications of the ACM
Integrated process modeling: an ontological evaluation
Information Systems - The 11th international conference on advanced information systems engineering (CAiSE*
Understanding relationships with attributes in entity-relationship diagrams
ICIS '99 Proceedings of the 20th international conference on Information Systems
GOL: toward an axiomatized upper-level ontology
Proceedings of the international conference on Formal Ontology in Information Systems - Volume 2001
Towards Ontologically Based Semantics for UML Constructs
ER '01 Proceedings of the 20th International Conference on Conceptual Modeling: Conceptual Modeling
Introduction to the special issue on word sense disambiguation: the state of the art
Computational Linguistics - Special issue on word sense disambiguation
An experimental examination of property precedence in conceptual modelling
APCCM '04 Proceedings of the first Asian-Pacific conference on Conceptual modelling - Volume 31
Unified Modeling Language User Guide, The (2nd Edition) (Addison-Wesley Object Technology Series)
Unified Modeling Language User Guide, The (2nd Edition) (Addison-Wesley Object Technology Series)
Complexity and clarity in conceptual modeling: comparison of mandatory and optional properties
Data & Knowledge Engineering - Special issue: Quality in conceptual modeling
Communications of the ACM - Two decades of the language-action perspective
Information Systems Research
| Hi-index | 0.00 |
UML is used as a language for object-oriented software design, and as a language for conceptual modeling of applications domains. Given the differences between these purposes, UML's origins in software engineering might limit its appropriateness for conceptual modeling. In this context, Evermann and Wand have proposed a set of well-defined ontological rules to constrain the construction of UML diagrams to reflect underlying ontological assumptions about the real world. The authors extend their work using a design research approach that examines these rules by studying the consequences of integrating them into a UML CASE tool. The paper demonstrates how design insights from incorporating theory-based modeling rules in a software artifact can be used to shed light on the rules themselves. In particular, the authors distinguish four categories of rules for implementation purposes, reflecting the relative importance of different rules and the degree of flexibility available in enforcing them. They propose distinct implementation strategies that correspond to these four rule categories and identify some redundant rules as well as some rules that cannot be implemented without changing the UML specification. The rules are implemented in an open-source UML CASE tool.