Melhoria Contínua de Estimativa de Esforço para o Desenvolvimento de Software
Resumo
Buscar a melhoria contínua da precisão das estimativas de esforço pode direcionar a organização a melhorar a sua capacidade de cumprir com os seus compromissos, entregando seus produtos de software dentro dos prazos previstos e, portanto, obter vantagens competitivas. Acreditamos que definir adequadamente as características que causam impactos nas produtividades de projetos de software pode melhorar comparações entre projetos realizados e novos projetos a terem seus esforços estimados. Este artigo apresenta uma abordagem de melhoria para as estimativas de esforço, e sua aplicação numa organização.
Referências
AGARWAL, Manish, Kumar; YOGESH, S. Mallick; BRARADWAJ, R. M., et all, Estimating Software projects, ACM SIGSOFT, p.60, 2001.
BASILI,V.;CALDIERA,Gianluigi;ROMBACH,H.Dieter “The Experience Factory”, Encyclopedia of Software Engineering, John Wiley & Sons, 1994, V.1 pp. 476-496.
BOEHM, Barry et al,Software Cost Estimation With COCOMO II, Prentice Hall PTR, 2000.
COSMIC, Measurement Manual, The COSMIC Implementation Guide for ISO/IEC 19761:2003, Version 2.2, 2003.
DCG, David Consulting Group, retrieved from Internet by the link http://www.davidconsultinggroup.com/ indata.htm in Fev/2005.
DEKKERS, Carol; AGUIAR, Mauricio; Using Function Points Analysis (FPA) do Check the Completeness (Fullness) of Functional User Requirements, Quality Plus, 2000.
FARLEY,Dick. Making Accurate Estimates, IEEE, 2002.
FENTON, N., PFLEEGER, S. Software Metrics A Rigorous & Practical Approach, 2nd. Ed., PWS Publishing Company, 1997.
GARMUS,HERRON, David; HERRON, David. Function Point Analysis – Measurement Practices for Sucessful Software Projects, Addison-Wesley Information Technology Series, 2000.
HAMID,Tarek K. Abdel,The Slippery Path to Productivity Improvement,IEEE Software, 1996.
IFPUG, CPM – Counting Practices Manual, release 4.1.1; IFPUG – International Function Point Users Group; 2000.
ISBSG. International Software Benchmarking Standards Group. The Benchmarking, Release 8, ISBSG,; 2004.
Ishikawa, Kaoru, Guide to Quality Control, Asian Productivity Organization, Tokyo, 1982 JOHNSON, Donna I.; BRODMAN, Judith G.; “Realities and Rewards of Software Process Improvement”, IEEE 1996.
JONES, C. Software Challenges: Function point: a new way of looking at tools, Computer, August, 1994. p. 66 – 67.
JORGENSEN, Magne, OSTVOLD, Kjetil Molokken, Rehaznos for software Effort Estimation Error: Impact of Respondent Role, Information Collection Approach, and Data Análisis Method, IEEE, 2004.
KIRSTEN, Ribu; Estimation Object-Oriented Software Projects with Use Cases, University of Oslo, Department of Informatics, 2001.
LIM, Wayne C., Effects of Resue on quality, Productivity, and Economics, IEEE, 1994.
MAXWELL, Katrina D.; “Colleting Data for Comparability: Benchjmarking Software Development Productivity”, IEEE Software, Setembro/Outubro 2001.
MORASCA,GIULIANO, ,Sandro, GIULIANO, Russo. An Empirical Study of Software Productivity, IEEE, 2002.
NESMA, Estimate Counting, Netherlands Software Metrics Users Association, 2003.
POTOK,VOUK, Tom; VOUK, Mladen. Development productivity for comercial SW Using OO Methods; ACM, 1995.
Methods; ACM, 1995 PUTNAM, Lawrence H., MAYERS, Ware, Five Core Metrics – The Intelligence Behind Sucessful Software Management, Dorset House Publishing, 2003.
RUBIN, Howard A ., Software Process Maturity: Measuring its Impact on Productivity and Quality, IEEE, 1993.
SIMÕES, C. Sistemática de Métricas, Qualidade e Produtividade, Developers’ Magazine, Brasil, 1999.
SPR, “The Programming Language Table”, Software Productivity Research, 2001. The PMBOK Guide – 2000 edition, PMI - Project Management Institute, 2000; PSM, Pratical Software Measurement, Adison Wesley, 2002.
RUS, Ioana, LINDVALL, Mikael, SEAMAN, Carolyn, BASILI, Victor, Packaging and Disseminating Lessons Learned from COTS-Based Software Development, IEEE, 2003.