What Makes a Good Data Model? Evaluating the Quality of Entity Relationship Models

This paper develops a framework for evaluating the quality of data models and choosing between alternative representations of requirements. For any particular set of user requirements there are many possible models, each of which has drastically different implications for database and systems design. In the absence of formally defined and agreed criteria, the choice of an appropriate representation is usually made in an ad hoc way, based on personal opinion. The evaluation framework proposed consists of four major constructs: qualities (desirable properties of a data model), metrics (ways of measuring each quality), weightings (relative importance of each quality) and strategies (ways of improving data models). Using this framework, any two data models may be compared in an objective and comprehensive manner. The evaluation framework also builds commitment to the model by involving all stakeholders in the process: end users, management, the data administrator and application developers.

[1]  G. A. Miller.  THE PSYCHOLOGICAL REVIEW THE MAGICAL NUMBER SEVEN, PLUS OR MINUS TWO: SOME LIMITS ON OUR CAPACITY FOR PROCESSING INFORMATION 1 , 1956 .

[2]  G. A. Miller.  THE PSYCHOLOGICAL REVIEW THE MAGICAL NUMBER SEVEN, PLUS OR MINUS TWO: SOME LIMITS ON OUR CAPACITY FOR PROCESSING INFORMATION 1 , 1956 .

[3]  Bush Jones,et al.  Architecture of systems problem solving , 1986, Journal of the American Society for Information Science.

[4]  D. A Jardine,et al.  Concepts and terminology for the conceptual schema and the information base , 1984 .

[5]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[6]  Ewart R. Carson,et al.  Dealing with complexity: an introduction to the theory & applications of systemsscience , 1988 .

[7]  Michiel van Genuchten,et al.  Empirical study of software maintenance , 1992, Inf. Softw. Technol..

[8]  F. P. Brooks,et al.  The mythical man-month" essays on software engineering, addison-wesley , 1974 .

[9]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[10]  Dinesh Batra,et al.  Conceptual Data Modelling in Database Design: Similarities and Differences between Expert and Novice Designers , 1992, Int. J. Man Mach. Stud..

[11]  Graeme Simsion.  Implementation of Very Generalised Data Structures , 1994, Australasian Database Conference.

[12]  Richard A. Freund,et al.  Definitions and Basic Quality Concepts , 1985 .

[13]  簡聰富,et al.  物件導向軟體之架構(Object-Oriented Software Construction)探討 , 1989 .

[14]  Lowell Jay Arthur,et al.  Measuring Programmer Productivity and Software Quality , 1985 .

[15]  John A. Zachman,et al.  A Framework for Information Systems Architecture , 1987, IBM Syst. J..

[16]  Hans van Vliet,et al.  Software engineering - principles and practice , 1993 .

[17]  Carol Stoak Saunders,et al.  Measuring Performance of the Information Systems Function , 1992, J. Manag. Inf. Syst..

[18]  Barbara A. Kitchenham,et al.  The architecture of system quality , 1987, Softw. Eng. J..

[19]  W. Edwards Deming,et al.  Out of the Crisis , 1982 .

[20]  Juhani Iivari,et al.  Dimensions of information systems design: A framework for a long-range research program , 1986, Inf. Syst..

[21]  Frank F. Land,et al.  Adapting to changing user requirements , 1982, Inf. Manag..

[22]  Ewart R. Carson,et al.  Dealing with Complexity , 1988, Springer US.

[23]  William Kent,et al.  Data and Reality , 1978 .

[24]  Laurie J. Kirsch,et al.  The Impact of Data Integration on the Costs and Benefits of Information Systems , 1992, MIS Q..

[25]  Gordon B. Davis,et al.  Strategies for Information Requirements Determination , 1982, IBM Syst. J..

[26]  Sasa M. Dekleva,et al.  The Influence of the Information Systems Development Approach on Maintenance , 1992, MIS Q..

[27]  Fred Niederman,et al.  Information Systems Management Issues for the 1990s , 1991, MIS Q..

[28]  Robert J. Kauffman,et al.  Reuse and Productivity in Integrated Computer-Aided Software Engineering: An Empirical Study , 1991, MIS Q..

[29]  Dick Bowman,et al.  Principles of software engineering management , 1989, APLQ.

[30]  M. T. Sager.  Data Centred Enterprise Modelling Methodologies - A Study of Practice and Potential , 1988, Aust. Comput. J..

[31]  Gordon B. Davis,et al.  Management information systems : conceptual foundations, structure, and development , 1985 .

[32]  Christopher Alexander.  Notes on the Synthesis of Form , 1964 .

[33]  D. Miller,et al.  Entity Model Clustering: Structuring A Data Model By Abstraction , 1986, Comput. J..

[34]  Herbert A. Simon,et al.  The Sciences of the Artificial , 1970 .

[35]  D. O. Hebb,et al.  The role of experience , 1961 .

[36]  Tarek K. Abdel-Hamid,et al.  The Economics of Software Quality Assurance: A Simulation-Based Case Study , 1988, MIS Q..

[37]  Frederick P. Brooks,et al.  The Mythical Man-Month: Essays on Softw , 1978 .

[38]  Graeme Simsion,et al.  Justifying Investment in Information Resource Management , 1995, Australas. J. Inf. Syst..

[39]  Ron Weber,et al.  A model of systems decomposition , 1989, ICIS '89.

[40]  James Martin,et al.  Strategic data-planning methodologies , 1982 .

[41]  Janis A. Bubenko,et al.  Information System Methodologies - A Research View , 1986, Information Systems Design Methodologies: Improving the Practice.