A Software Testing Strategy Based on a Software Product Quality Model
Abstract
Getting software testing to meet the needs of the organization is not an easy task, it goes beyond identifying problems. It also implies achieving a common understanding of the domain on the part of those involved in the project, and being able to face the current technological changes as part of the context. To this end, a strategy was defined for the evaluation of a software product based on the ISO 25000 quality standard and program tests directed by use cases. For this work, surveys were carried out with experts in the domain. The quality model proposed by the ISO 25010 standard was extended in accordance with current technological requirements, such as the cloud computing paradigm. In addition, metrics and indicators were defined in order to carry out a study, analysis and evaluation of the problem being studied: migration to the cloud of the business processes of a company in the environment, case study for the practical validation of the proposed strategy.
Keywords
Testing directed by use cases Quality Model Strategy Metrics and IndicatorsReferences
- 1.Pressman, R.: Isn’t web engineering all about and technology. In: Web Engineering: A Practitioner’s Approach, 1st edn., pp. 19–20 (1991)Google Scholar
- 2.Bermeo Conto, J., Sánchez, M., Maldonado, J.J., Carvallo, J.P.: Modelos de calidad de software en la práctica: Mejorando su construcción con el soporte de modelos conceptuales. CEDIA (2016)Google Scholar
- 3.Carvallo, J.P., Franch, X., Quer, C.: Calidad de componentes software. In: Calero, C., Moraga, Mª.A., Piattini Velthuis, M.G. Calidad del producto y proceso software - capítulo 10, pp. 287–316. R.-M. Editorial (2010)Google Scholar
- 4.McCall, J.A., Richards, P.K., Walters, G.F.: Factors in software quality. RADC TR-77-369, vols. I, II, III, US Rome Air Development Center Reports NTIS AD/A-049 (1977)Google Scholar
- 5.Boehm, B.W., Brown, J.R., Kaspar, H., Lipow, M., Macleod, G.J., Merrit, M.J.: Characteristics of Software Quality. North Holland Publishing Company, Amsterdam (1978)zbMATHGoogle Scholar
- 6.IEEE, “IEEE std 1061-1998”: Institute of Electrical Electronic Engineering (1998)Google Scholar
- 7.Horgan, G., Khaddaj, S., Forte, P.: An essential views model for software quality assurance. In: Project Control for Software Quality. Shaker Publishing (1999)Google Scholar
- 8.Gilb, T.: Principles of Software Engineering Management. Addison Wesley, Boston (1988)zbMATHGoogle Scholar
- 9.ISO, “ISO/IEC 9126-1:2001”: Software engineering - software product quality -part 1: Quality model, int’l org. For standardization, Geneva (2001)Google Scholar
- 10.ISO “ISO/IEC 25010:2011”: Systems and software engineering – Systems and software Quality Requirements and Evaluation - System and software quality models (2011)Google Scholar
- 11.Granda, M.F.: An experiment design for validating a test case generation strategy from requirements models. In: EmpiRE 2014, Karlskrona, Sweden (2014)Google Scholar
- 12.Bystrický, M., Vranić, V.: Use case driven modularization as a basis for test driven modularization. In: Federated Conference on Computer Science and Information Systems (2017)Google Scholar
- 13.Wang, C., Pastore, F., Briand, L.: System testing of timing requirements based on use cases and timed automata. In: 10th IEEE International Conference on Software Testing, Verification and Validation (2017)Google Scholar
- 14.Kapor, M.: A software design manifesto. Dr. Dobbs’ J. 172, 62–68 (1991)Google Scholar
- 15.Pressman, R.: What are the elements of a design model? In: Web Engineering: A Practitioner’s Approach, 1st edn., p. 37 (1991)Google Scholar