Quality Assurance in Model-Based Software Development: Challenges and Opportunities

  • Michel R. V. Chaudron
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 94)


Modeling is a common practice in modern day software engineering. Since the mid 1990’s the Unified Modeling Language (UML) has become the de facto standard for modeling software systems. The UML is used in all phases of software development – ranging from the requirements phase to the maintenance phase. However, the manner in which the UML is used differs widely from project to project and from developer to developer. This illustrates an apparent lack of quality awareness in the use of UML. In this paper I will discuss the challenges and opportunities there are for using quality assurance for software modeling for improving the quality and productivity of software development.


Quality Assurance Software Development Unify Modeling Language Sequence Diagram Software Metrics 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Lange, C.F.J., Chaudron, M.R.V., Muskens, J.: In Practice: UML Software Architecture and Design Descriptions. IEEE Software 23(2), 40–46 (2006)CrossRefGoogle Scholar
  2. 2.
    Lange, C.F.J., Chaudron, M.R.V.: Effects of defects in UML models: an experimental investigation. In: Proc. of the 28th Int. Conference on Software Engineering (ICSE 2006), Shanghai, pp. 401–411. ACM (2006)Google Scholar
  3. 3.
    Nugroho, A., Flaton, B., Chaudron, M.R.V.: Empirical Analysis of the Relation between Level of Detail in UML Models and Defect Density. In: Busch, C., Ober, I., Bruel, J.-M., Uhl, A., Völter, M. (eds.) MODELS 2008. LNCS, vol. 5301, pp. 600–614. Springer, Heidelberg (2008)CrossRefGoogle Scholar
  4. 4.
    Nugroho, A., Chaudron, M.R.V.: A survey into the rigour of UML use and its perceived impact on quality and productivity. In: Empirical Software Engineering and Measurement (ESEM 2008), pp. 90–99. ACM (2008)Google Scholar
  5. 5.
    Stettina, C.J., Heijstek, W.: Necessary and Neglected? An Empirical Study of Internal Documentation in Agile Software Development Team. In: 29th ACM International Conference on Design of Communication. ACM (2011)Google Scholar
  6. 6.
    Lange, C.F.J., Chaudron, M.R.V.: Managing Model Quality in UML-based Software Development. In: Workshop on Softwre Technology and Engineering Practice, pp. 7–16. IEEE Computer Society, Washington (2005)Google Scholar
  7. 7.
    Nugroho, A., Chaudron, M.R.V.: A survey of the practice of design-code correspondence amongst professional software engineers. In: Empirical Software Engineering & Measurement, pp. 467–469. IEEE (2007)Google Scholar
  8. 8.
    van Opzeeland, D.J.A., Lange, C.F.J., Chaudron, M.R.V.: Quantitative Techniques for the Assessment of Correspondence between UML Designs and Implementations. In: Proc. 9th QAOOSE Workshop, ECOOP 2005 (2005)Google Scholar
  9. 9.
    Ambler, S.W.: The Elements of UML2.0 Style. Cambridge University Press (2005)Google Scholar
  10. 10.
    Lange, C.F.J., Chaudron, M.R.V., Wijns, M.A.J.: Supporting Task-Oriented Modeling using Interactive UML Views. Journal of Visual Languages and Computing 4, 399–419 (2007)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Michel R. V. Chaudron
    • 1
  1. 1.Leiden Institute of Advanced Computer ScienceLeiden UniversityThe Netherlands

Personalised recommendations