Risk Management in Software Quality Processes: a Comparative Analysis

• Cristine Martins Gomes de Gusmão UFPE
• Hermano Perrelli de Moura UFPE

DOI: https://doi.org/10.5753/sbqs.2004.16181

Abstract

The software development is generally full of uncertainties and problems that cause the delays of schedules, increase the costs or the delivery of products in an unsatisfactory form. Although some problems cannot be totaly solved, some ones can be controlled through preventive actions. Projects Management area that deals with these uncertainties or problems even before they occur, are Risk Management. In Software Quality Processes, Risk Management is a key to assurance the software quality. This article has the purpose to provide an overview of risk management process in quality models, through the comparative analysis of its activities.

Keywords: Software Engineering, Risk Management, Quality Process, Process Models

References

HALL, E. M. 1998. Managing Risk. 2a Ed. USA: Addison Wesley. p 88-103.

BOEHM, B. W. 1991. Software Risk Management: principles and practices, IEEE Software, Volume 8. No1. p 32-40.

CHARETTE, R. 1990. Application strategies for risk analysis. New York: MultiScience Press. p 17-21.

HIGUERAG, P.R. 1994. An Introduction to Team Risk Management, Technical Report. Software Engineering Institute, Carnegie Mellon University. USA.

HUMPHREY, W. 1987. Characterizing the software process: a maturity framework, Technical Report. Software Engineering Institute, Carnegie Mellon University, USA.

FAIRLEY, R., 1994. Risk Management For Software’s Projects. IEEE Software. p 54-66.

CHAPMAN, C. e WARD, S. 1997. Project Risk Management: Processes, Techniques and Insights. John Wiley & Sons. p 30-41.

KRUCHTEN, P. 2003. Introdução ao Rup: Rational Unified Process. 2a Ed. Ciência Moderna. São Paulo. p 25-36.

PMI - PROJECT MANAGEMENT INSTITUTE. 2000. A Guide to the Project Management Body of Knowledge. Disponível na URL: <http://www.pmi.org/pmi/publictn/pmboktoc.htm >. Acesso em: 25.07.2003.

SOFTWARE ENGINEERING INSTITUTE, 2001. CMMI - Capability Maturity Model Integration version 1.1 Pittsburgh, PA. Software Engineering Institute, Carnegie Mellon University. USA.

HUMPHREY, W.S. 1990. Managing the Software Process. Addison – Wesley. p 9-17.

NBR ISO 9001, 2000. ISO 9001 - Sistema de Gestão de Qualidade Requisitos. Associação Brasileira de Normas Técnicas – ABNT. Rio de Janeiro.

NBR ISO 12207. 1998. ISO 12207 – Tecnologia de Informação – Processos de ciclo de vida de software. Associação Brasileira de Normas Técnicas – ABNT. Rio de Janeiro.

ISO/IEC 15504. 1999. ISO 15504 Part 5: An Assessmente Model and Indicator Guidance, ISO/IEC JTC1 SC7. International Standard Organization – ISO/IEC.

ISO/IEC PDAM 12207. 2002. ISO/IEC 12207 Information Tecnology – Ammendment to ISO/IEC 12207, ISO/IEC JTC1 SC7. International Standard Organization – ISO/IEC.

ISO/IEC 15504. 1999. ISO 15504 Software Process, ISO/IEC JTC1 SC7. International Standard Organization – ISO/IEC.

HUMPHREY, W. 1987. A method for assessing the software engineering capability of contractors. Pittsburgh, PA. Software Engineering Institute, Carnegie Mellon University. USA.

PAULK, M. 1993. Capability Maturity Model for Software version 1.1. Pittsburgh, PA. Software Engineering Institute, Carnegie Mellon University. USA.