David Vincent
ABSTRACT
This position paper proposes the use of “Entity Diagrams” as a pivotal mechanism for abstracting the use of data by an organization and then selectively implementing data base systems developed using the abstraction as a normative force. The entity diagram is not dependent on either a particular DBMS or on organization subunits, thus making it particularly useful for raising the level of computer system design in a changing environment.
- 1.Bachman, C.W., "Data Structure Diagrams," DataBase, 1,2 (Summer 1969), 4-10. Google Scholar
Digital Library
- 2.Brooks, F.P., The Mythical Man-Month: Essays On Software Engineering, Addison-Wesley, Reading, Mass., 1975. Google ScholarDigital Library
- 3.Dyba, J.E., Data Element Identification, Auerbach, Pennsauken, NJ., 1976.Google Scholar
- 4.Everest, G.C., Database Management: Objectives, System Function and Administration, McGraw-Hill, (draft) 1977. Google ScholarDigital Library
- 5.Fry, J.P., notes from course "Data Base Design Methodology," Engineering Summer Conferences, University of Michigan College of Engineering, July 25-29, 1977.Google Scholar
- 6.Kahn, B.K., "A Method for Describing Information Required by the Database Design Process," Proceedings of the ACM SIGMOD International Conference on Management of Data, J. Rothie, editor, Washington, D.C., 1976, 53-64. Google Scholar
- 7.Novak, D.O. and Kahn, B.K., "A Framework for Logical Database Design," Working Paper DE3.1, Data Translation Project, Graduate School of Business Administration, The University of Michigan, Ann Arbor, Michigan, 1976.Google Scholar
- 8.ANSI/X3/SPARC Study Group on Data Base Management Systems, Interim Report, American Standards Committee Project 226, Document No. 7514TS01, CBSMA, Washington, D.C., 1975.Google Scholar
Index Terms
- The use of Entity Diagrams in data base systems implementation
Recommendations
Handling data quality in entity resolution
IQIS '05: Proceedings of the 2nd international workshop on Information quality in information systemsEntity resolution (ER) is a problem that arises in many information integration scenarios: We have two or more sources containing records on the same set of real-world entities (e.g., customers).However, there are no unique identifiers that tell us what ...
Collective entity resolution in relational data
Many databases contain uncertain and imprecise references to real-world entities. The absence of identifiers for the underlying entities often results in a database which contains multiple references to the same entity. This can lead not only to data ...
Comments