ER model clustering as an aid for user communication and documentation in database design
Communications of the ACM
A structured approach to data modelling
Australian Computer Journal
Database management (3rd ed.)
Determining a useful balance between understandability and Rigor in data modelling
New Zealand Journal of Computing
Introduction to systems analysis and design (2nd ed.)
Introduction to systems analysis and design (2nd ed.)
The entity-relationship model—toward a unified view of data
ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
Data Analysis for Data Base Design
Data Analysis for Data Base Design
Software Engineering Economics
Software Engineering Economics
Data Models
A Preliminary Framework for Entity-Relationship Models
ER '81 Proceedings of the Second International Conference on the Entity-Relationship Approach to Information Modeling and Analysis
Data models in database management
Proceedings of the 1980 workshop on Data abstraction, databases and conceptual modeling
Prescription or Description: Some observations on the conceptual modelling process
SEEP '96 Proceedings of the 1996 International Conference on Software Engineering: Education and Practice (SE:EP '96)
| Hi-index | 0.00 |
In the business environment data modeling diagrams are used as a user communication tool during Data Analysis, as a Database Design tool, as part of Systems Documentation and, increasingly, as a base for automatic generation of data definition language statements by CASE software.In this paper it is argued that the first two uses have conflicting requirements and that there is a need for a separate, more appropriate, nomenclature and notation for user communication than that which is currently in use.A modified form of Chen's approach is considered and rejected in favour of a Resource-Activity diagram.The conversion of this to an Entity diagram, and thence to Relational form is briefly discussed.Implications for the design of CASE tools and the adoption of a CASE standard are considered.