Quantifying requirements volatility effects

Science of Computer Programming

Volumn 72, Issue 3, 2008, Pages 136-175

  Kulk, G P ^a   Verhoef, C ^a  

^a VU UNIVERSITY AMSTERDAM   (Netherlands)

Author keywords

ratio; ratio; Compound monthly growth rate; IT dashboard; IT portfolio management; Quantitative IT portfolio management; Requirements churn; Requirements creep; Requirements metric; Requirements scrap; Requirements volatility; Requirements volatility dashboard; Scope creep; Volatility benchmark; Volatility tolerance factor

Indexed keywords

FUNCTION EVALUATION; MATHEMATICAL MODELS; REQUIREMENTS ENGINEERING; RISK ASSESSMENT; SOCIETIES AND INSTITUTIONS;

DECISION MAKER (DM); EARLY WARNING SYSTEM (EWS); ELSEVIER (CO); FAILURE RATES; FUNCTION POINTS; IN LINE; IT GOVERNANCE (ITG); IT PROJECTS; METRICS (CO); REAL WORLD; REQUIREMENTS VOLATILITY; SOFTWARE PRODUCT LINE (SPL); SOURCE CODING; TOLERANCE FACTORS;

RISKS;

EID: 48149086400     PISSN: 01676423     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.scico.2008.04.003     Document Type: Article

References (85)

1. D.A. Adamo, S. Fabrizi, M.G. Vergati, A light functional dimension estimation model for software maintenance, in: E. Chikofsky, R. Kazman, C. Verhoef, (Eds.) Proceedings of the first IEEE International Conference on Exploring Quantifiable Information Technology Yields, EQUITY 2007, 2007
2. A.J. Albrecht, Measuring application development productivity, in: Proceedings of the Joint SHARE/GUIDE/IBM Application Development Symposium, 1979, pp. 83-92
3. Albrecht A.J., and Gaffney J.E. Software function, source lines of code, and development effort prediction: A software science validation. IEEE Transactions on Software Engineering 9 9 (1983) 639-648
4. Anthes G. No more creeps! are you a victim of creeping user requirements?. Computerworld 28 18 (1994) 107-110
5. Arranga E., Archbell I., Bradley J., Coker P., Langer R., Townsend C., and Weathley M. In cobol's defense. IEEE Software 17 (2000) 70-72,75
6. Barry C., and Lang M. A comparison of traditional and multimedia information systems development practices. Information and Software Technology 45 (2003) 217-227
7. Boehm B. Software Engineering Economics (1981), Prentice Hall
8. Brooks Jr. F.P. The Mythical Man-Month-Essays on Software Engineering. anniversary edition (1995), Addison-Wesley
9. Charette R.N. Large-scale project management is risk management. IEEE Software 13 4 (1996) 110-117
10. Corless R.M., Gonnet G.H., Hare D.E.G., Jeffrey D.J., and Knuth D.E. On the lambert W function. Advances in Computational Mathematics 5 (1996) 329-359
11. Costello R.J., and Liu D.-B. Metrics for requirements engineering. Journal of Systems Software 29 1 (1995) 39-63
12. Davis A.M. Software Requirements: Objects Functions, and States (1993), Prentice Hall
13. Dreger J.B. Function Point Analysis (1989), Prentice Hall
14. Gerald L. Dillingham, et al. Report to congressional requesters: NATIONAL AIRSPACE SYSTEM - FAA has made progress but continues to face challenges in acquiring major air traffic control systems, Technical Report, United States Government Accountability Office, US GAO, GAO-05-331, 2005
15. Mark O. Hatfield, et al. AIR TRAFFIC CONTROL - status of FAA's modernization program, Technical Report, United States General Accounting Office, US GAO, GAO/RCED-95-175FS, 1995
16. Euler L. De serie Lambertina plurimisque eius insignibus proprietatibus. Acta AcademiæScientarum Imperialis Petropolitinæ (1783) 29-51
17. FAA. Blueprint for NAS modernization 2002 update. Available via: www.faa.gov/nasarchitecture/Blueprint2002.htm.
18. Faust D., and Verhoef C. Software product line migration and deployment. Software-Practice and Experience 33 (2003) 933-955
19. Frasera R.G., Armarego J., and Yogesan K. The reengineering of a software system for glaucoma analysis. Computer Methods and Programs in Biomedicine 79 (2005) 97-109
20. Garmus D., and Herron D. Function Point Analysis - Measurement Practices for Successful Software Projects (2001), Addison-Wesley
21. Gause D.C., and Weinberg G.M. Exploring Requirements: Quality Before Design (1989), Dorset House Publishing
22. Glass R.L. Persistent software errors. IEEE Transactions on Software Engineering 7 2 (1981) 162-168
23. Glass R.L. Software Runaways (1998), Prentice Hall
24. Hammer T.F., Huffman L.L., and Rosenberg L.H. Doing requirements right the first time. CROSSTALK The Journal of Defense Software Engineering (1998) 20-25
25. Harker S.D.P., Eason K.D., and Dobson J.E. The change and evolution of requirements as a challenge to the practice of software engineering. Proceedings of the IEEE International Symposium on Requirements Engineering (1993), IEEE Computer Society 266-272
26. Henry J., and Henry S. Quantitative assessment of the software maintenance process and requirements volatility. Proceedings of the 1993 ACM conference on Computer science (1993), ACM Press 346-351
27. Houston D.X., Mackulak G.T., and Collofello J.S. Stochastic simulation of risk factor potential effects for software development risk management. Journal of Systems and Software 59 (2001) 247-257
28. International function point users group, Software engineering ifpug 4.1 unadjusted functional size measurement method counting practices manual, Technical Report ISO/IEC 20926:2003, International Standardization Organization. www.iso.org, November 2003
29. Jackson M. Software Requirements And Specifications (1995), Addison-Wesley
30. Jalote P., Palit A., Kurien P., and Peethamber V.T. Timeboxing: A process model for iterative software development. Journal of Systems and Software 70 (2004) 117-127
31. Javed T., e Maqsoo M., and Durrani Q.S. A study to investigate the impact of requirements instability on software defects. ACM Software Engineering Notes 29 4 (2004) 1-7
32. Jeffery D.R., Low G.C., and Barnes M. A comparison of function point counting techniques. IEEE Transactions on Software Engineering 19 5 (1993) 529-532
33. Jones C. Applied Software Measurement: Assuring Productivity and Quality. second edition (1996), McGraw-Hill
34. Jones C. Patterns of Software Systems Failure and Success (1996), International Thomsom Computer Press
35. Jones C. Strategies for managing requirements creep. IEEE Computer 29 (1996) 92-94
36. Jones C. The Year 2000 Software Problem - Quantifying the Costs and Assessing the Consequences (1998), Addison-Wesley
37. Jones C. Software Assessments, Benchmarks, and Best Practices. Information Technology Series (2000), Addison-Wesley
38. C. Jones, Conflict and litigation between software clients and developers, 2001. Version 10-April 13. Technical Note
39. Jones C. Estimating Software Costs. second edition (2007), McGraw-Hill
40. Kemerer C.F. Reliability of function points measurement - a field experiment. Communications of the ACM 36 2 (1993) 85-97
41. Kemerer C.F., and Porter B.S. Improving the reliability of function point measurement: An empirical study. IEEE Transactions on Software Engineering SE-18 11 (1992) 1011-1024
42. Kerr D., and Winklhofer H. The effect of rapid rural industry changes on the development of a decision support system for dairy farmers in Australia. Computers and Electronics in Agriculture 50 (2006) 61-69
43. Kettunen P., and Laanti M. How to steer an embedded software project: Tactics for selecting the software process model. Information and Software Technology 47 (2005) 587-608
44. Kotonya G., and Sommerville I. Requirements Engineering: Processes and Techniques (1998), Wiley
45. Lambert J.H. Observationes variae in mathesin puram. Acta Helvetica Physico-Mathematico-Anatomico-Botanico-Medica III (1758) 128-168. Available via: www.few.vu.nl/~erald/lambert.pdf
46. Laymana L., Williamsa L., Damianb D., and Buresc H. Essential communication practices for Extreme Programming in a global software development team. Information and Software Technology 48 (2006) 781-794 Special Issue Section: Distributed Software Development
47. Leffingwell D. Calculating the return on investment from more effective requirements management. American Programmer 10 4 (1997) 13-16
48. Annabella Loconsole, Definition and validation of requirements management measures. Ph.D. Thesis, Umeå University, 2007
49. Loconsole A., and Börstler J. An industrial case study on requirements volatility measures. 12th Asia-Pacific Software Engineering Conference, APSEC'05 (2005), IEEE CS Press 249-256
50. Lorenzi N.M., and Riley R.T. Organizational ISSUES=change. International Journal of Medical Informatics 69 (2003) 197-203
51. Yashwant K. Malaiya, Jason Denton, Requirements volatility and defect density, in: Proceedings of the 10th International Symposium on Software Reliability Engineering, 1998, pp. 285-294
52. Mendes E., Mosley N., and Counsell S. Comparison of Web size measures for predicting Web design and authoring effort. IEE Proceedings Software 149 3 (2002) 86-92
53. Nurmuliani N., Zowghi D., and Fowell S. Analysis of requirements volatility during software development life cycle. Proceedings of the 2004 Australian Software Engineering Conference. ASWEC04 (2004), IEEE 28
54. Fra Luca Bartolomeo de Pacioli, Summa de arithmetica, geometrica, proportioni et proportionalita. Venice, 1494. Available via: http://www.cs.vu.nl/~x/yield/yield.pdf
55. R.J. Peters, C. Verhoef, Quantifying the yield of risk-bearing IT-portfolios, 2007. Available via: http://www.cs.vu.nl/x/yield/yield.pdf
56. Putnam L.H., and Myers W. Measures for Excellence-Reliable Software on Time, Within Budget. Yourdon Press Computing Series (1992)
57. L.H. Putnam, D.T. Putnam, A Data verification of the Software Fourth Power Trade-Off Law, in: Proceedings of the International Society of Parametric Analysts-Sixth Annual Conference, volume III(I), 1984, pp. 443-471
58. Ramosa I., Berry D.M., and Carvalho J.Á. Requirements engineering for organizational transformation. Information and Software Technology 47 (2005) 479-495
59. Robertson S., and Robertson J. Requirements-Led Project Management: Discovering David's Slingshot (2004), Addison-Wesley
60. Robertson S., and Robertson J. Mastering the Requirements Process. second edition (2006), Addison-Wesley
61. L. Rosenberg, L. Hyatt, Developing an effective metrics program, in: Proceedings of the European Space Agency Software Assurance Symposium, The Netherlands, 1996
62. Ross S.A., Westerfield R.W., and Jordan B.D. Fundamentals of Corporate Finance. fifth edition (2000), Irwin McGraw-Hill
63. Sheldon F.T., Kavi K.M., Tausworth R.C., Yu J.T., Brettschneider R., and Everett W.W. Reliability measurement: From theory to practice. IEEE Software 9 (1992) 13-20
64. Harry M. Sneed, Peter Brössler, Critical success factors in software maintenance: A case study, in: Proceedings of the International Conference on Software Maintenance, ICSM '03, 2003, pp. 190-198
65. Sommerville I., and Sawyer P. Requirements Engineering: A Good Practice Guide (1997), Wiley
66. Stapleton J. DSDM - Business Focused Development. 2nd edition (2003), Addison-Wesley
67. Stapleton J., and Constable P. DSDM - Dynamic System Development Method (1997), Addison-Wesley
68. Stark G.E., Oman P., Skillicorn A., and Ameele A. An examination of the effects of requirements changes on software maintenance releases. Journal of Systems Software Maintenance: Research and Practice 11 (1999) 293-309
69. Stark G.E., Skillicorn A., and Ameele R. An examination of the effects of requirements changes on software releases. CROSSTALK The Journal of Defense Software Engineering (1998) 11-16
70. Martin J. Steele, Mansooreh Mollaghasemi Ghaith Rabadi, Grant Cates, Generic simulation models of reusable launch vehicles, in: Proceedings of the 34th Conference on Winter Simulation: Exploring New Frontiers, Winter Simulation Conference, 2002, pp. 747-753
71. Takahashi M., and Kamayachi Y. An empirical study of a model for program error prediction. IEEE Transactions on Software Engineering 15 1 (1989) 82-86
72. Tavolato P., and Vincena K. A prototyping methodology and its tool. In: Budde R., et al. (Ed). Approaches to Prototyping (1984), Springer-Verlag
73. Tukey J.W. Exploratory Data Analysis (1977), Addison-Wesley
74. Verhoef C. Quantitative IT portfolio management. Science of Computer Programming 45 1 (2002) 1-96. Available via: www.cs.vu.nl/~x/ipm/ipm.pdf
75. C. Verhoef, Quantifying software process improvement, 2004. Available via: www.cs.vu.nl/~x/spi/spi.pdf
76. Verhoef C. Quantifying the Value of IT-investments. Science of Computer Programming 56 (2005) 315-342. Available via: www.cs.vu.nl/~x/val/val.pdf
77. Verhoef C. Quantifying the effects of IT-governance rules. Science of Computer Programming 67 2-3 (2007) 247-277. Available via www.cs.vu.nl/~x/gov/gov.pdf
78. Watson H.J., Fullerb C., and Ariyachandraa T. Data warehouse governance: Best practices at Blue Cross and Blue Shield of North Carolina. Decision Support Systems 38 (2004) 435-450
79. Weigel A.L., and Hastings D.E. Interaction of policy choices and technical requirements for a space transportation infrastructure. Acta Astronautica 52 (2003) 551-562
80. Weinberg G.M. Just say no! improving the requirements process. American Programmer 8 10 (1995) 19-23
81. G.M. Weinberg, Quality Software Management: Volume 2 First-Order Measurement, Dorset House, 1993
82. White A.S. External disturbance control for software project management. International Journal of Project Management 24 (2006) 127-135
83. Wiegers K.E. Software Requirements. second edition (2003), Microsoft Press
84. Wikipedia. Bancassurance, Wikipedia http://en.wikipedia.org/wiki/Bancassurance, 2008 (accessed 01. 02. 2008)
85. Didar Zowghi, N. Nurmuliani, A study of the impact of requirements volatility on software project performance, in: Proceedings of the Ninth Asia-Pacific Software Engineering Conference, APSEC'02, 2002, p. 3