Assessing quality in software development: An agile methodology approach

 
 
 
  • Abstract
  • Keywords
  • References
  • PDF
  • Abstract


    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.


  • Keywords


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

  • References


      [1] B. Kent (n.d.). Manifesto for Agile Software Development: http://www.agilemanifesto.org/ 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. http://dx.doi.org/10.1007/978-3-540-68255-4_39.

      [17] Mountain Goat Software. (1998-2009). http://www.mountaingoatsoftware.com/terms-of-use 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

Download

Article ID: 4173
 
DOI: 10.14419/jacst.v4i2.4173




Copyright © 2012-2015 Science Publishing Corporation Inc. All rights reserved.