Usando GQM para Gerenciar Riscos em Projetos de Software
Resumo
Muitos projetos de desenvolvimento falham em entregar o software dentro do cronograma, orçamento e níveis de qualidade, por causa da avaliação inadequada dos fatores de risco. Este trabalho propõe uma abordagem sistemática para prevenir e monitorar riscos, baseado em adaptação do processo de desenvolvimento. Para prevenção de risco é sugerido um procedimento para listar, analisar e priorizar os riscos, visando selecionar ações preventivas para incluir no processo de desenvolvimento, minimizando a exposição ao risco. Utilizando o paradigma Goal/Question/Metric são definidas métricas do processo de software para serem usadas para acompanhar o progresso dos fatores de risco, possibilitando ao gerente de projeto tomar ações corretivas, quando necessário e no momento adequado.Referências
Addison, T., Vallabh, S. Controlling Software Project Risks - An Empirical Study of Methods used by Experienced Project Managers. Proceedings of South African Institute of Computer Scientists & Information Technologists, Port Elizabeth, South Africa, September 2002, p.128-140.
Basili, V. R, Rombach, D. The TAME Project: Towards Improvement-Oriented Software Environments. IEEE Transactions on Software Engineering, v.14, n.6, p. 758-773, June 1988.
Boehm, B. Software Risk Management: Principles and Practices. IEEE Software, v.8, n.1, p. 32-41, January 1991.
Boehm, B. Get Ready for Agile Methods, with care. IEEE Computer, v.35, n.1, p. 64-69, January 2002.
Fenton, N., Neil, M. Software Metrics: A Roadmap. Proceedings of 22th Conference on The Future of Software Engineering, Limerick, Ireland, 2000, p. 357-370.
Manzoni, L. V., Price, R. T. Identifying Extensions Required by RUP (Rational Unified Process) to Comply with CMM (Capability Maturity Model) Levels 2 and 3. IEEE Transaction on Software Engineering, v. 29, n. 2, p. 181-192, February 2003.
Coppendale, J. Managing Risk in Product and Process Development and Avoid Unpleasant Surprises. Engineering Management Journal, v.5, n.1, p. 35-38, February, 1995.
Schmidt, R. C. Managing Delphi Surveys using Nonparametric Statistical Techniques. Decision Sciences Journal, v. 28, n.3, p. 763-774, 1997.
Hall, E. Managing Risk: Methods for Software Systems Development. New York: Addison-Wesley, 1998.
Hightower, R. Lesiecki, N. Java Tools for Extreme Programming. New York: John Wiley & Sons, 2002.
Hirsch, M. Making RUP Agile. Proceedings of Conference on Object Oriented Programming Systems Languages and Applications, Seattle, Washington, 2002, p.1-ff.
Keil, M. et al. A Framework for Identifying Software Project Risks. Communication of the ACM, v. 41, n.11, p. 76-83, November 1998.
Paulk, M. C. et. al. Key Practices of the Capability Maturity Model, Version 1.1. Technical Report CMU/SEI-93-TR-025, 1993.
Project Management Institute. A Guide to the Project Management Body of Knowledge. Pennsylvania, 2000.
Pressman, R. Engenharia de Software, 5 ed. Makron Books, 2002.
Rational Software Corporation. Rational Unified Process, v. 2001. Cupertino, 2001.
Schwaber, K., Beedle, M. Agile Software Development with Scrum. Upper Saddle River: Prentice Hall, 2001.
Software Engineering Institute. Capability Maturity Model Integration (CMMI), Version 1.1. Pittsburgh: Software Engineering Institute, Carnegie Mellon University, 2002. (CMU/SEI-2002-TR-012).
Melo, W. L. Polymorphism Measures for Early Risk Prediction. Proceedings of the 21th International Conference on Software Engineering, Los Angeles, CA, 1999, p.334-344.
Hartmann J., Price, R. T. Pattern-based Methodology Tailoring. Proposta de Dissertação de Mestrado, UFRGS, Porto Alegre, 2004.
Gresse, C. B., Hoisl, J. W. A Process Model for GQM-Based Measurement. Technical Report STTI-95-04-E, Software Technology Transfer Initiative, University of Kaiserslautern, Department of Computer Science, Kaiserslautern, Germany, 1995.
Basili, V. R, Rombach, D. The TAME Project: Towards Improvement-Oriented Software Environments. IEEE Transactions on Software Engineering, v.14, n.6, p. 758-773, June 1988.
Boehm, B. Software Risk Management: Principles and Practices. IEEE Software, v.8, n.1, p. 32-41, January 1991.
Boehm, B. Get Ready for Agile Methods, with care. IEEE Computer, v.35, n.1, p. 64-69, January 2002.
Fenton, N., Neil, M. Software Metrics: A Roadmap. Proceedings of 22th Conference on The Future of Software Engineering, Limerick, Ireland, 2000, p. 357-370.
Manzoni, L. V., Price, R. T. Identifying Extensions Required by RUP (Rational Unified Process) to Comply with CMM (Capability Maturity Model) Levels 2 and 3. IEEE Transaction on Software Engineering, v. 29, n. 2, p. 181-192, February 2003.
Coppendale, J. Managing Risk in Product and Process Development and Avoid Unpleasant Surprises. Engineering Management Journal, v.5, n.1, p. 35-38, February, 1995.
Schmidt, R. C. Managing Delphi Surveys using Nonparametric Statistical Techniques. Decision Sciences Journal, v. 28, n.3, p. 763-774, 1997.
Hall, E. Managing Risk: Methods for Software Systems Development. New York: Addison-Wesley, 1998.
Hightower, R. Lesiecki, N. Java Tools for Extreme Programming. New York: John Wiley & Sons, 2002.
Hirsch, M. Making RUP Agile. Proceedings of Conference on Object Oriented Programming Systems Languages and Applications, Seattle, Washington, 2002, p.1-ff.
Keil, M. et al. A Framework for Identifying Software Project Risks. Communication of the ACM, v. 41, n.11, p. 76-83, November 1998.
Paulk, M. C. et. al. Key Practices of the Capability Maturity Model, Version 1.1. Technical Report CMU/SEI-93-TR-025, 1993.
Project Management Institute. A Guide to the Project Management Body of Knowledge. Pennsylvania, 2000.
Pressman, R. Engenharia de Software, 5 ed. Makron Books, 2002.
Rational Software Corporation. Rational Unified Process, v. 2001. Cupertino, 2001.
Schwaber, K., Beedle, M. Agile Software Development with Scrum. Upper Saddle River: Prentice Hall, 2001.
Software Engineering Institute. Capability Maturity Model Integration (CMMI), Version 1.1. Pittsburgh: Software Engineering Institute, Carnegie Mellon University, 2002. (CMU/SEI-2002-TR-012).
Melo, W. L. Polymorphism Measures for Early Risk Prediction. Proceedings of the 21th International Conference on Software Engineering, Los Angeles, CA, 1999, p.334-344.
Hartmann J., Price, R. T. Pattern-based Methodology Tailoring. Proposta de Dissertação de Mestrado, UFRGS, Porto Alegre, 2004.
Gresse, C. B., Hoisl, J. W. A Process Model for GQM-Based Measurement. Technical Report STTI-95-04-E, Software Technology Transfer Initiative, University of Kaiserslautern, Department of Computer Science, Kaiserslautern, Germany, 1995.
Publicado
18/10/2004
Como Citar
FONTOURA, Lisandra M.; PRICE, Roberto T..
Usando GQM para Gerenciar Riscos em Projetos de Software. In: SIMPÓSIO BRASILEIRO DE ENGENHARIA DE SOFTWARE (SBES), 18. , 2004, Brasília/DF.
Anais [...].
Porto Alegre: Sociedade Brasileira de Computação,
2004
.
p. 39-54.
DOI: https://doi.org/10.5753/sbes.2004.23832.
