Assessing quality in software development: An agile methodology approach


  • V. Rodríguez-Hernández
  • M.C. Espino-Gudiño
  • J.L. González-Pérez
  • J. Gudiño-Bazaldúa
  • Victor Castano Universidad Nacional Autonoma de Mexico





Software Develoment, Quality Assesment, Agile Technology, Education, Software Training.


A novel methodology, result of 10 years of in-field testing, which makes possible the convergence of different types of models and quality standards for Engineering and Computer Science Faculties, is presented. Since most software-developing companies are small and medium sized, the projects developed must focuson SCRUM and Extreme Programming (XP), opposed to a RUP, which is quite heavy, as well as on Personal Software Process (PSP) and Team Software Process (TSP), which provide students with competences and a structured framework. ISO 90003:2004 norm is employed to define the processes by means of a quality system without new requirements or changing the existing ones. Also, the model is based on ISO/IEC 25000 (ISO (IEC 9126 – ISO/IEC 14598)) to allow comparing software built by different metrics.


[1] B. Kent (n.d.). Manifesto for Agile Software Development: Retrieved 11/15, 2009.

[2] F. Scalone. Estudio comparativo de los modelos y estándares de calidad del software. Buenos Aires, Argentina, 2006.

[3] ISO/IEC 25000:2005 “Software Engineering – Software product Quality Requirements and Evaluation (SQuaRE) – Guide to SQuaREâ€.

[4] ISO/IEC 90003:2004 “Sofware engineering – Guidelines for the application of ISO/IEC 9001:2000 to computer softwareâ€.

[5] ISO/IEC 25001:2005 “Software Engineering –Software product Quality Requirements and Evaluation (SQuaRE) – Planning and managementâ€.

[6] ISO/IEC 9126-1:2001 “Sofware engineering – Product quality – Part I: Quality modelâ€.

[7] ISO/IEC 9126-2:2003 “Sofware engineering – Product quality – Part 2: External metricsâ€.

[8] ISO/IEC 9126-3:2003 “Sofware engineering – Product quality – Part 3: Internal metricsâ€.

[9] ISO/IEC 9126-4:2004 “Sofware engineering – Product quality – Part 4: Quality in use metricsâ€.

[10] ISO/IEC 14598-1:1999 “Information technology –Software product evaluation. Part 1: General overviewâ€.

[11] ISO/IEC 14598-2:2000 “Information technology – Software product evaluation. Part 2: Planning and managementâ€.

[12] ISO/IEC 14598-3:2000 “Information technology –Software product evaluation. Part 3: Process for developersâ€.

[13] ISO/IEC 14598-4:1999 “Information technology –Software product evaluation. Part 4: Process for acquirersâ€.

[14] ISO/IEC 14598-5:1998 “Information technology –Software product evaluation. Part 5: Process for evaluatorsâ€.

[15] ISO/IEC 14598-6:2001 “Information technology –Software product evaluation. Part 6: Documentation of evaluation modulesâ€.

[16] M. A. Babar. Architecture-Centric Methods and Agile Approaches. Limerick, Limerick, Ireland, 2008.

[17] Mountain Goat Software. (1998-2009). Recovered on 15 November 2009.

[18] N. Tomayko. Software Architecture-Centric Methods and Agile Development. In I. Software, IEEE Software. 2006, pp. 47.

[19] S. Fraser. How Do Agile/XP Development Methods. San Diego, San Diego, Estados Unidos de Norte America, 2007.

[20] S. M. Priolo. Métodologías Ãgiles. En S. M. Priolo, Métodos Ãgiles. pp. 84.Buenos Aires, Argentina: Gradi S.A. 2009.

[21] W. Humprey. PSP: A Self-Improvement Process for Software Engineers. Addison Wesley. 2006.

[22] X. Shu. A Case Study of the Implementation of Agile Methods in a Bioinformatics Project. Calgary, Calgary, Canadá. 2006.

View Full Article: