What Makes a Good Data Model? A Framework for Evaluating and Improving the Quality of Entity Relationship Models

Australian Computer Journal

Volumn 30, Issue 3, 1998, Pages 97-110

  Moody, D L ^a   Shanks, G G ^b  

^a Simsion Bowles and Associates   (Australia)

^b MONASH UNIVERSITY   (Australia)

Author keywords

Conceptual schema; Corporate data model; Data model; Entity Relationship Model; Information model; Quality assurance; Software quality; Systems development; Total Quality Management

Indexed keywords

COMPUTER SYSTEMS PROGRAMMING; DATA ACQUISITION; DATA REDUCTION; KNOWLEDGE REPRESENTATION; QUALITY ASSURANCE; SOFTWARE ENGINEERING; TOTAL QUALITY MANAGEMENT;

ENTITY RELATIONSHIP MODELS;

DATA STRUCTURES;

EID: 0032139061     PISSN: 00048917     EISSN: None     Source Type: Journal    
DOI: None     Document Type: Article

References (74)

1. ALEXANDER, C. (1964): Notes on the Synthesis of Form, Harvard University Press, Boston.
2. AUSTRALIAN SOFTWARE METRICS ASSOCIATION (ASMA) (1996): ASMA Project Database, Release 7, November, P.O. Box 1287, Box Hill, Victoria, Australia, 3128.
3. AVISON, D.E. and FITZERALD, G. (1995): Information Systems Development: Methodologies, Techniques and Tools, 2nd Edition, Blackwell Scientific, Oxford.
4. BANKER, R.D. and KAUFFMAN, R.J. (1991): Reuse and Productivity in Integrated Computer Aided Software Engineering: An Empirical Study, MIS Quarterly, 15(3), September: 375-401.
5. BATINI, C., CERI, S. and NAVATHE, S.B. (1992): Conceptual Database Design: An Entity Relationship Approach, Benjamin Cummings, Redwood City, California.
6. BATINI, C., LENZERINI, M. and NAVATHE, S. (1986): A Comparative Analysis of Methodologies for Database Schema Integration, ACM Computing Surveys, 18(4), December: 323-364.
7. BOEHM, B.W. (1981): Software Engineering Economics, Prentice-Hall Inc., Englewood Cliffs, New Jersey.
8. BROOKS, F.P. (1975): The Mythical Man-Month: Essays on Software Engineering, Addison-Wesley, New York.
9. BUBENKO, J.A. (1986): Information Systems Methodologies: A Research View, in OLLE, T.W., SOL, H.G., VERRIJN-STUART, A.A. (eds.), Information Systems Design Methodologies: Improving the Practice, North-Holland, Amsterdam: 289-318.
10. BUTLER COX FOUNDATION (1987): Requirements Definition: The Key to Systems Development Productivity, Position Paper No. 4, Butler Cox and Partners Limited, November, London.
11. CHEN, P.P. (1976): The Entity Relationship Model: Towards an Integrated View of Data, ACM Transactions on Database Systems, 1(1), March: 9-36.
12. CODD, E.F. (1970) A Relational Model of Data for Large Shared Data Banks, Communications of the ACM, 13 (6), June: 377-387.
13. DATE, C.J. (1989): Introduction to Database Systems (4th Edition), Addison Wesley.
14. DEMING, W.E. (1986): Out of the Crisis, MIT Center for Advanced Engineering, Cambridge, MA.
15. DUBIN, R. (1978): Theory Building, The Free Press, New York.
16. DUE, R. (1992): Enterprise Modelling: Still in Pursuit, Database Programming and Design, 5(11), November: 24-32.
17. FELDMAN, P. and MILLER, D. (1986): Entity Model Clustering: Structuring a Data Model by Abstraction, The Computer Journal, 29(4): 348-360.
18. FLOOD, R.L. and CARSON, E.R. (1988): Dealing With Complexity: An Introduction to the Theory and Application of Systems Science, Plenum Press, New York.
19. FREUND, R. A. (1985): Definitions and Basic Quality Concepts, in SEPEHRI, M. (ed.), Quest for Quality: Managing the Total System, Industrial Engineering and Management Press, Atlanta, Georgia.
20. GARTNER RESEARCH GROUP (1992): Sometimes You Gotta Break the Rules, Gartner Group Strategic Management Series Key Issues, November 23.
21. GOODHUE, D.L., KIRSCH, L.J. and WYBO, M.D. (1992): The Impact of Data Integration on the Costs and Benefits of Information Systems, MIS Quarterly, 16(3), September: 293-311.
22. HALPIN, T. (1995): Conceptual Schema and Relational Database Design: A Fact Oriented Approach, Prentice Hall, Sydney.
23. HITCHMAN, S. (1995): Practitioner Perceptions On The Use Of Some Semantic Concepts In The Entity Relationship Model, European Journal of Information Systems, 4:31-40.
24. HUFFORD, D. (1993): Data Administration Support for Business Process Improvement, Database Newsletter, September/October: 1-4.
25. HULL, R. and KING, R. (1987): Semantic Data Models, ACM Computing Surveys, 19(3), September: 201-260.
26. INMON, W.H. (1991): Don't Forget to Stretch, Database Programming and Design, 4(3), March: 24-26.
27. INMON, W.H. (1992): EIS and the Data Warehouse, Database Programming and Design. 5(11), November: 36-38.
28. INSTITUTE OF ELECTRONICS AND ELECTRICAL ENGINEERS (IEEE) (1983): IEEE Standard Glossary of Software Engineering Terminology, IEEE Standard 729.
29. INTERNATIONAL STANDARDS ORGANISATION (ISO) (1987): Information Processing Systems - Concepts and Terminology for the Conceptual Schema and the Information Base, ISO Technical Report 9007.
30. IVARI, J. (1986): Dimensions Of Information Systems Design: A Framework For A Long Range Research Program. Information Systems, June: 39-42.
31. JACOBSON, I. (1995): The Object Advantage, Addison-Wesley, New York.
32. KENT, W. (1978): Data and Reality, North-Holland, Amsterdam.
33. KLIR, G.J. (1985): Architecture of Systems Problem Solving, Plenum Press, New York.
34. LAND, F.F. (1982): Adapting to Changing User Requirements, Information and Management, 5(2):59-75.
35. LIENTZ, B.P. and SWANSON, E.B. (1980): Software Maintenance Management: A Study of the Maintenance of Computer Application Software in 487 Data Processing Organisations, Addison-Wesley, Reading.
36. LOFFMAN, R.S. and RUSH, R.M (1991): Improving Data Quality, Database Programming and Design, 4(4), April: 17-19.
37. MARTIN, J. (1989): Strategic Data Planning Methodologies, Prentice Hall, New Jersey.
38. McCALL, J.A., RICHARDS, P.K. and WALTERS, G.F. (1977): Factors in Software Quality, U.S. Department of Commerce.
39. MEYER, B. (1988): Object Oriented Software Construction, Prentice Hall, New York.
40. MILLER, G. (1956): The Magical Number Seven, Plus or Minus Two: Some Limits on our Capacity for Processing Information, The Psychological Review, 63, March: 81-97.
41. MOODY, D.L. (1996a): Graphical Entity Relationship Models: Towards A More User Understandable Representation of Data, in B. THALHEIM (ed.) Proceedings of the Fourteenth International Conference on the Entity Relationship Approach, Cottbus, Germany, October 7-9:227-244.
42. MOODY, D.L. (1996b): The Seven Habits of Highly Effective Data Modellers, Database Programming and Design, October: 21-30.
43. MOODY, D.L. (1997): A Multi-Level Architecture for Representing Enterprise Data Models, Proceedings of the Sixteenth International Conference on the Entity Relationship Approach, Los Angeles, November 1-3.
44. MOODY, D.L. and SHANKS, G.G. (1994): What Makes A Good Data Model? Evaluating the Quality of Entity Relationship Models, in P. LOUCOPOLIS (ed.) Proceedings of the Thirteenth International Conference on the Entity Relationship Approach, Manchester, December 14-17, 94-111.
45. MOODY, D.L. and SIMSION, G.C. (1995): Justifying Investment in Information Resource Management, Australian Journal of Information Systems, 3(1), September: 25-37.
46. MOODY, D.L., SIMSION, G.C., SHANKS, G.G., OLSON, N.G. and VENABLE, J. (1995): Stakeholder Perceptions in Conceptual Modelling, Proceedings of the Sixth Australian Conference on Information Systems, Curtin University, Perth, Australia, September 26-28, 187-206.
47. MORIARTY, T. (1993): Testing from the Top, Database Programming and Design, 6(8), August: 65-67.
48. MUMFORD, E. (1983): Designing Human Systems, Manchester Business School, Manchester, UK.
49. O'BRIEN, C. and O'BRIEN, S. (1994): Mining Your Legacy Systems: A Data-Based Approach, Asia Pacific DB2 User Group Conference, Melbourne, Australia, November 21-23.
50. OLLE, T.W. (1993): Data Modelling and Data modelling: A Comparative Analysis of Functionality and Roles, Australian Journal of Information Systems, 1(1), September: 46-57.
51. PECKHAM, J. and MARYANSKI, F. (1988): Semantic Database Modelling: Survey, Application and Research Issues, ACM Computing Surveys, 20(3), September: 153-189.
52. PIPPENGER, N. (1978): Complexity Theory, Scientific American, 238(6): 1-15.
53. ROSS, R.G. (1996): The Business Rule Book, Database Research Group, Boston, MA, 2nd edition.
54. SHANKS, G. (1996): Building and Using Corporate Data Models, Unpublished PhD Thesis, Department of Information Systems, Monash University, Melbourne, Australia.
55. SHANKS, G. (1997): Conceptual Data Modelling: An Empirical Study of Expert and Novice Data Modellers, Australian Journal of Information Systems, 4(2):63-73.
56. SHANKS, G. and DARKE, P. (1997): Qualily in Conceptual Modelling: Linking Theory and Practice, Proc Pacific Asia Conference on Information Systems, Brisbane, (May), Queensland University of Technology, 805-814.
57. SIMON, H.A. (1982): Sciences of the Artificial, MIT Press, MA.
58. SIMSION, G.C. (1988): Data Planning in a Volatile Business Environment, Australian Computer Society Conference on Strategic Planning for Information Technology, Ballarat, March: 88-92.
59. SIMSION, G.C. (1991): Creative Data Modelling, Proceedings of the Tenth International Entity Relationship Conference, San Francisco, 112-123.
60. SIMSION, G.C. (1993): The Implementation of Very Generalised Data Structures, Proceedings of Australian Database Conference, Brisbane, Australia, December: 18-27.
61. SIMSION, G.C. (1994): Data Modelling Essentials, Van Nostrand Reinhold, New York.
62. SYMONS, C.R. (1988): Function Point Analysis: Difficulties and Improvements, IEEE Transactions on Software Engineering, 14(1), January.
63. SYMONS, C.R. (1991): Software Sizing and Estimating: MkII Function Point Analysis, J. Wiley and Sons.
64. THOMPSON, C. (1993): Living with an Enterprise Model, Database Programming and Design, 6(12), March: 32-38.
65. VAN GENUCHTEN, M., BRETHOUWER, G., VAN DEN BOOMEN, T. and HEEMSTRA, F, (1992): Empirical Study of Software Maintenance, Information and Software Technology, 34(8), August: 22-35.
66. VAN VLIET, J.C. (1993): Software Engineering: Principles and Practice, John Wiley and Sons, Chichester, England.
67. VERYARD, R. (1984): Pragmatic Data Analysis, Blackwell Scientific Publications, Oxford.
68. VON HALLE, B. (1991): Data: Asset or Liability?, Database Programming and Design, 4(7), July: 13-15.
69. VON HALLE, B. and CONKEY, J. (1997): Rewiring the Business, Database Programming and Design, 10(1), January: 11-15
70. WALRAD, C. and MOSS, E. (1993): Measurement: The Key to Application Development Quality, IBM Systems Journal, 32(3):445-460.
71. WAND, Y. and WEBER, R. (1989): A Model for Systems Decomposition, Proceedings of the AAANZ Conference, Canberra, Australia.
72. ZACHMAN, J. A. (1987): A Framework for Information Systems Architecture, IBM Systems Journal, 26(3):276-292.
73. ZULTNER, R.E. (1992a): QFD for Software: Satisfying Customers, American Programmer, February: 1-14.
74. ZULTNER, R.E. (1992b) The Deming Way: Total Quality Management for Software, Proceedings of Total Quality Management for Software Conference, April, Washington, DC, April: 134-145.