Entity-relationship modeling

Abstract

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.