Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Modelling of set membership: the notion and the issues
Data & Knowledge Engineering
The data model resource book: a library of logical data models and data warehouse designs
The data model resource book: a library of logical data models and data warehouse designs
Analysis patterns: reusable objects models
Analysis patterns: reusable objects models
Object models (2nd ed.): strategies, patterns, and applications
Object models (2nd ed.): strategies, patterns, and applications
Advanced object-oriented analysis and design using UML
Advanced object-oriented analysis and design using UML
Data Model Patterns: Conventions of Thought
Data Model Patterns: Conventions of Thought
Business Process Engineering
Accounting,Information Technology,and Business Solutions
Accounting,Information Technology,and Business Solutions
International Journal of Human-Computer Studies
Model-Driven Design Using Business Patterns
Model-Driven Design Using Business Patterns
Utilizing domain models for application design and validation
Information and Software Technology
The use of a knowledge-based system in conceptual data modeling
Decision Support Systems
Design science in information systems research
MIS Quarterly
AOIS'04 Proceedings of the 6th international conference on Agent-Oriented Information Systems II
Journal of Database Management
An ontological analysis of the notion of community in the RM-ODP enterprise language
Computer Standards & Interfaces
| Hi-index | 0.00 |
This research note shows that the scope of conceptual data modeling patterns can be identified, clarified, and explicitly represented by positioning them into an ontology-based framework. A clear and explicit definition of scope could help deciding which patterns match which parts of the domain to be represented. The authors demonstrate their argument by positioning existing conceptual data modeling patterns into a two-dimensional structuring framework that is constructed using two ontology-derived 'benchmark' patterns: an enterprise pattern for representing transactions derived from the REA domain ontology and an abstraction pattern for representing reality at different levels of abstraction derived from the UFO foundational ontology. By means of an application scenario dealing with the conceptual design of a transactional enterprise database, the authors illustrate how the framework can be used to evaluate the relevancy and completeness of candidate patterns with respect to the problem at hand.