A survey into the rigor of UML use and its perceived impact on quality and productivity

The UML (Unified Modeling Language) has become the de facto standard for software modeling in the software industry. Despite its wide acceptance, little is known about how UML is used in practice, let alone the challenges and difficulties faced by engineers who work with this modeling notation. In this paper, we provide empirical findings from a survey on the use of UML amongst 80 professional software engineers. We explore software engineers' opinions on common styles of using UML and how they perceive the impact of using UML on productivity and quality in software development. One of the results reveals that the impact of using the UML on productivity is perceived mostly in the design, analysis, and implementation phases.

[1]  Michel R. V. Chaudron,et al.  A Survey of the Practice of Design -- Code Correspondence amongst Professional Software Engineers , 2007, First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007).

[2]  Michel R. V. Chaudron,et al.  In practice: UML software architecture and design description , 2006, IEEE Software.

[3]  John Lane,et al.  IEEE Standard Computer Dictionary: Compilation of IEEE Standard Computer Glossaries , 1991 .

[4]  Falk Fraikin,et al.  SeDiTeC-testing based on sequence diagrams , 2002, Proceedings 17th IEEE International Conference on Automated Software Engineering,.

[5]  Jeffrey Parsons,et al.  How UML is used , 2006, CACM.

[6]  Lionel C. Briand,et al.  A UML-Based Approach to System Testing , 2001, UML.

[7]  Mrv Michel Chaudron,et al.  Quantitative techniques for the assessment of correspondence between UML designs and implementations , 2005 .

[8]  A. Jefferson Offutt,et al.  Generating Tests from UML Specifications , 1999, UML.

[9]  Eda Marchetti,et al.  The Cow_Suite Approach to Planning and Deriving Test Suites in UML Projects , 2002, UML.

[10]  P. Killworth,et al.  The Problem of Informant Accuracy: The Validity of Retrospective Data , 1984 .

[11]  David Notkin,et al.  Software Reflexion Models: Bridging the Gap between Design and Implementation , 2001, IEEE Trans. Software Eng..

[12]  Shari Lawrence Pfleeger,et al.  Principles of survey research part 2: designing a survey , 2002, SOEN.

[13]  Robert DeLine,et al.  Let's go to the whiteboard: how and why software developers use drawings , 2007, CHI.

[14]  Barry W. Boehm,et al.  Quantitative evaluation of software quality , 1976, ICSE '76.

[15]  A. Jefferson Offutt,et al.  Using UML Collaboration Diagrams for Static Checking and Test Generation , 2000, UML.

[16]  Siw Elisabeth Hove,et al.  The impact of UML documentation on software maintenance: an experimental evaluation , 2006, IEEE Transactions on Software Engineering.

[17]  Ariadi Nugroho,et al.  Managing the Quality of UML Models in Practice , 2009 .