Comparing data modeling formalisms
Communications of the ACM
Formal deadlock elimination in an object oriented conceptual schema
Data & Knowledge Engineering
Conceptual schema and relational database design (2nd ed.)
Conceptual schema and relational database design (2nd ed.)
IEEE Transactions on Software Engineering
An ontological analysis of the relationship construct in conceptual modeling
ACM Transactions on Database Systems (TODS)
Understanding relationships with attributes in entity-relationship diagrams
ICIS '99 Proceedings of the 20th international conference on Information Systems
Database Systems: A Practical Approach to Design, Implementation, and Management
Database Systems: A Practical Approach to Design, Implementation, and Management
Introduction to Database Systems
Introduction to Database Systems
The Guidelines of Modeling - An Approach to Enhance the Quality in Information Models
ER '98 Proceedings of the 17th International Conference on Conceptual Modeling
Research Commentary: Information Systems and Conceptual Modeling--A Research Agenda
Information Systems Research
Evaluating modeling techniques based on models of learning
Communications of the ACM - Service-oriented computing
Using ontology to validate conceptual models
Communications of the ACM - Service-oriented computing
An experimental examination of property precedence in conceptual modelling
APCCM '04 Proceedings of the first Asian-Pacific conference on Conceptual modelling - Volume 31
International Journal of Human-Computer Studies
Data & Knowledge Engineering - Special issue: Quality in conceptual modeling
Journal of Management Information Systems
Defining and validating metrics for assessing the understandability of entity-relationship diagrams
Data & Knowledge Engineering
Understanding understandability of conceptual models --- what are we actually talking about?
ER'12 Proceedings of the 31st international conference on Conceptual Modeling
Journal of Database Management
Hi-index | 0.00 |
In UML class diagrams, a many-to-many relationship with attributes can be represented by an association class or by a connecting object class. It is unclear which modeling construct is preferred in particular modeling scenarios. Because of lack of theory, this paper investigates the issue empirically. An experiment was conducted that tested the effect of representational form chosen on the performance of model users at cardinality interpretation tasks. It was shown that, controlling for cardinality knowledge, business users can better interpret the information that a UML class diagram conveys about a many-to-many relationship with attributes if this relationship is represented as an association class. The implication for ‘best practices' in UML modeling is that modelers should refrain from objectifying such relationships if the goal is an effective communication of domain semantics to users that are not modeling experts.