Analyzing the Quality of Domain Models Developed by Novice Systems Analysts

Assuring quality in capturing and representing the systems requirements is extremely important. This study is aimed at understanding errors frequently committed by novice systems analysts in developing domain models using the Unified Modeling Language (UML). Understanding of errors that affect the quality of resulting conceptual models and the relationships among those errors would be beneficial to both practice and research. This paper reports the results from analyzing the class diagrams produced by teams of novice systems analysts as part of different e-business systems requirements specification. The results include errors grouped into different quality categories and some interesting observations on relationships among errors from different categories.

[1]  S. Hitchman.  Practitioner perceptions on the use of some semantic concepts in the entity–relationship model , 1995 .

[2]  Daniel L. Moody,et al.  Evaluating the quality of information models: empirical testing of a conceptual model quality framework , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[3]  Mario Piattini,et al.  Quality in Conceptual Modeling - New Research Directions , 2002, ER.

[4]  Paloma Martínez,et al.  An Empirical Perspective of Using Ternary Relationships in Database Conceptual Modelling , 2003, Informatics Educ..

[5]  Michael Fagan.  Design and Code Inspections to Reduce Errors in Program Development , 1976, IBM Syst. J..

[6]  The Challenges of Complex IT Projects , 2004 .

[7]  Bertrand Meyer,et al.  Object-Oriented Software Construction, 2nd Edition , 1997 .

[8]  Antoni Olivé,et al.  Specific Relationship Types in Conceptual Modeling: The Cases of Generic and with Common Participants , 2002, ICEIS.

[9]  Graeme G. Shanks,et al.  Conceptual Data Modelling: an empirical study of expert and novice data modellers , 1997, Australas. J. Inf. Syst..

[10]  Someswar Kesh,et al.  Evaluating the quality of entity relationship models , 1995, Inf. Softw. Technol..

[11]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[12]  Charlene Walrad,et al.  Measurement: The Key to Application Development Quality , 1993, IBM Syst. J..

[13]  Graeme G. Shanks,et al.  What Makes a Good Data Model? Evaluating the Quality of Entity Relationship Models , 1994, ER.

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

[15]  Robert L. Glass,et al.  A Snapshot of Systems Development Practice , 1999 .

[16]  Forrest Shull,et al.  The empirical investigation of Perspective-Based Reading , 1995, Empirical Software Engineering.

[17]  Wei-Tek Tsai,et al.  To Object-oriented Software Development Transition to Object-oriented Software Development , 2022 .

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

[19]  Jeffrey A. Hoffer,et al.  An Examination of Procedural and Object‐oriented Systems Analysis Methods: Does Prior Experience Help or Hinder Performance?* , 1999 .

[20]  Kangde Yao,et al.  A Brief Guide to the Standard Object Modelling Language , 2000 .

[21]  Marco Balduzzi.  On the Influence of Free Software on Code Reuse in Software Development , .

[22]  James Martin,et al.  Information Engineering: Introduction , 1989 .

[23]  Shamkant B. Navathe,et al.  Conceptual Database Design: An Entity-Relationship Approach , 1991 .

[24]  Mario Piattini,et al.  Metrics for databases: a way to assure the quality , 2002, Information and Database Quality.

[25]  S. Lauesen,et al.  Preventing Requirement Defects: An Experiment in Process Improvement , 2001, Requirements Engineering.

[26]  H. James Nelson,et al.  Exploring the Difficulties of Learning Object-Oriented Techniques , 1997, J. Manag. Inf. Syst..

[27]  Kendall Scott,et al.  UML distilled - a brief guide to the Standard Object Modeling Language (2. ed.) , 2000, notThenot Addison-Wesley object technology series.

[28]  John Mylopoulos,et al.  On formal requirements modeling languages: RML revisited , 1994, Proceedings of 16th International Conference on Software Engineering.

[29]  Graeme G. Shanks,et al.  What Makes a Good Data Model? A Framework for Evaluating and Improving the Quality of Entity Relationship Models , 1998, Aust. Comput. J..

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

[31]  Graeme Shanks,et al.  A Semiotic Information Quality Framework , 2004 .

[32]  Alexander Borgida,et al.  Features Of Languages for the Development of Information Systems at the conceptual Level , 1985, IEEE Software.

[33]  Arne Sølvberg,et al.  Understanding quality in conceptual modeling , 1994, IEEE Software.

[34]  Susanne Patig,et al.  Die Evolution von Modellierungssprachen , 2006 .

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

[36]  Adam A. Porter,et al.  Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment , 1995, IEEE Trans. Software Eng..

[37]  Hans van Vliet.  Software Engineering: Principles and Practice, 2nd Edition , 2000 .

[38]  Michael E. Fagan.  Design and Code Inspections to Reduce Errors in Program Development (Reprint) , 2002, Software Pioneers.

[39]  BryantA.,et al.  B. W. Boehm software engineering economics , 1983 .

[40]  M. Lynn.  Hawaii International Conference on System Sciences , 1996 .