Construction of a Systemic Quality Model for Evaluating a Software Product

Quality is currently considered one of the main assets with which a firm can enhance its competitive global position. This is one reason why quality has become essential for ensuring that a company's products and processes meet customers' needs. A recent innovation in the systems area is the development of a set of mechanisms and models for evaluating quality. This article describes the design of a Quality Model with a systemic approach to software products that assesses a product's efficiency and effectiveness. Different quality models were studied: McCall, Boehm, FURPS, ISO 9126, Dromey, ISO 15504 in an attempt to identify the aspects present in these models that are deemed important in a Systemic Quality model. We designed a model prototype that reflects the essential attributes of quality. This model was evaluated using a method so it can be validated and also enhanced. The evaluation method consisted of: designing a survey, formulating, validating and applying the measurement instruments; defining an algorithm to obtain the quality estimate and analyzing the results. The model prototype enabled the strengths and weaknesses of the software products studied to be identified. When evaluating a software product using the model prototype, it was possible to ascertain its compliance with the standards and use the results to improve it. Since the evaluation was systemic, processes that affect certain characteristics of the product could be identified. Companies can benefit from the model proposed because it serves as a benchmark that allows their products to evolve and be competitive.

[1]  Edward G. Carmines,et al.  Reliability and Validity Assessment , 1979 .

[2]  Shari Lawrence Pfleeger,et al.  Software metrics (2nd ed.): a rigorous and practical approach , 1997 .

[3]  Ian Sommerville,et al.  Ingeniería de software , 1988 .

[4]  Will Venters,et al.  Software engineering: theory and practice , 2006 .

[5]  OrtegaMaryoly,et al.  Construction of a Systemic Quality Model for Evaluating a Software Product , 2003 .

[6]  John E. Gaffney,et al.  Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation , 1983, IEEE Transactions on Software Engineering.

[7]  Roger S. Pressman,et al.  Ingeniería del software: un enfoque práctico , 1998 .

[8]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.

[9]  T Rojas,et al.  A COMPARISON OF THREE INFOMATION SYSTEMS DEVELOPMENT METHODOLOGIES RELATED TO EFFECTIVENESS / EFFICIENCY CRITERIA , 2001 .

[10]  Alan C. Gillies,et al.  Software Quality: Theory and Management , 1992 .

[11]  Alain Wegmann,et al.  A Systems Perspective on the Quality Description of Software Components , 2002 .

[12]  Anna Grimán,et al.  Systemic Quality Model for System Development Process: Case Study , 2001 .

[13]  E. GaffneyJ.,et al.  Software Function, Source Lines of Code, and Development Effort Prediction , 1983 .

[14]  R. G. Dromey,et al.  Cornering the Chimera , 1996, IEEE Softw..

[15]  TR,et al.  Information technology — Software process assessment — Part 2 : A reference model for processes and process capability , 1998 .

[16]  Jeffrey M. Voas Certification: reducing the hidden costs of poor quality , 1999, IEEE Software.

[17]  Shari Lawrence Pfleeger,et al.  Software Metrics : A Rigorous and Practical Approach , 1998 .

[18]  Barry Boehm,et al.  Characteristics of software quality , 1978 .

[19]  Nagib Callaos,et al.  Designing with Systemic Total Quality , 1994 .

[20]  Robert B. Grady,et al.  Software Metrics: Establishing a Company-Wide Program , 1987 .