Quantifying requirements volatility effects

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

A.J. Albrecht, Measuring application development productivity, in: Proceedings of the Joint SHARE/GUIDE/IBM Application Development Symposium, 1979, pp. 83—92

Albrecht, 1983, Software function, source lines of code, and development effort prediction: A software science validation, IEEE Transactions on Software Engineering, 9, 639, 10.1109/TSE.1983.235271

Anthes, 1994, No more creeps! are you a victim of creeping user requirements?, Computerworld, 28, 107

Arranga, 2000, In cobol’s defense, IEEE Software, 17

Barry, 2003, A comparison of traditional and multimedia information systems development practices, Information and Software Technology, 45, 217, 10.1016/S0950-5849(02)00207-0

Boehm, 1981

Brooks, 1995

Charette, 1996, Large-scale project management is risk management, IEEE Software, 13, 110, 10.1109/52.526838

Corless, 1996, On the lambert W function, Advances in Computational Mathematics, 5, 329, 10.1007/BF02124750

Costello, 1995, Metrics for requirements engineering, Journal of Systems Software, 29, 39, 10.1016/0164-1212(94)00127-9

Davis, 1993

Dreger, 1989

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

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

Euler, 1783, De serie Lambertina plurimisque eius insignibus proprietatibus, Acta AcademiæScientarum Imperialis Petropolitinæ, 29

FAA. Blueprint for NAS modernization 2002 update. Available via: www.faa.gov/nasarchitecture/Blueprint2002.htm.

Faust, 2003, Software product line migration and deployment, Software–Practice and Experience, 33, 933, 10.1002/spe.530

Frasera, 2005, The reengineering of a software system for glaucoma analysis, Computer Methods and Programs in Biomedicine, 79, 97, 10.1016/j.cmpb.2005.01.002

Garmus, 2001

Gause, 1989

Glass, 1981, Persistent software errors, IEEE Transactions on Software Engineering, 7, 162, 10.1109/TSE.1981.230831

Glass, 1998

Hammer, 1998, Doing requirements right the first time, CROSSTALK The Journal of Defense Software Engineering, 20

Harker, 1993, The change and evolution of requirements as a challenge to the practice of software engineering, 266

Henry, 1993, Quantitative assessment of the software maintenance process and requirements volatility, 346

Houston, 2001, Stochastic simulation of risk factor potential effects for software development risk management, Journal of Systems and Software, 59, 247, 10.1016/S0164-1212(01)00066-8

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

Jackson, 1995

Jalote, 2004, Timeboxing: A process model for iterative software development, Journal of Systems and Software, 70, 117, 10.1016/S0164-1212(03)00010-4

Javed, 2004, A study to investigate the impact of requirements instability on software defects, ACM Software Engineering Notes, 29, 1, 10.1145/986710.986727

Jeffery, 1993, A comparison of function point counting techniques, IEEE Transactions on Software Engineering, 19, 529, 10.1109/32.232016

Jones, 1996

Jones, 1996

Jones, 1996, Strategies for managing requirements creep, IEEE Computer, 29, 92, 10.1109/2.507640

Jones, 1998

Jones, 2000

C. Jones, Conflict and litigation between software clients and developers, 2001. Version 10–April 13. Technical Note

Jones, 2007

Kemerer, 1993, Reliability of function points measurement — a field experiment, Communications of the ACM, 36, 85, 10.1145/151220.151230

Kemerer, 1992, Improving the reliability of function point measurement: An empirical study, IEEE Transactions on Software Engineering, SE-18, 1011, 10.1109/32.177370

Kerr, 2006, 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, 61, 10.1016/j.compag.2005.09.001

Kettunen, 2005, How to steer an embedded software project: Tactics for selecting the software process model, Information and Software Technology, 47, 587, 10.1016/j.infsof.2004.11.001

Kotonya, 1998

Lambert, 1758, Observationes variae in mathesin puram, Acta Helvetica Physico-Mathematico-Anatomico-Botanico-Medica, III, 128

Laymana, 2006, Essential communication practices for Extreme Programming in a global software development team, Information and Software Technology, 48, 781, 10.1016/j.infsof.2006.01.004

Leffingwell, 1997, Calculating the return on investment from more effective requirements management, American Programmer, 10, 13

Annabella Loconsole, Definition and validation of requirements management measures. Ph.D. Thesis, Umeå University, 2007

Loconsole, 2005, An industrial case study on requirements volatility measures, 249

Lorenzi, 2003, Organizational ISSUES=change, International Journal of Medical Informatics, 69, 197, 10.1016/S1386-5056(02)00105-3

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

Mendes, 2002, Comparison of Web size measures for predicting Web design and authoring effort, IEE Proceedings Software, 149, 86, 10.1049/ip-sen:20020337

Nurmuliani, 2004, Analysis of requirements volatility during software development life cycle, 28

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

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

Putnam, 1992

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

Ramosa, 2005, Requirements engineering for organizational transformation, Information and Software Technology, 47, 479, 10.1016/j.infsof.2004.09.014

Robertson, 2004

Robertson, 2006

L. Rosenberg, L. Hyatt, Developing an effective metrics program, in: Proceedings of the European Space Agency Software Assurance Symposium, The Netherlands, 1996

Ross, 2000

Sheldon, 1992, Reliability measurement: From theory to practice, IEEE Software, 9, 13, 10.1109/52.143095

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

Sommerville, 1997

Stapleton, 2003

Stapleton, 1997

Stark, 1999, An examination of the effects of requirements changes on software maintenance releases, Journal of Systems Software Maintenance: Research and Practice, 11, 293, 10.1002/(SICI)1096-908X(199909/10)11:5<293::AID-SMR198>3.0.CO;2-R

Stark, 1998, An examination of the effects of requirements changes on software releases, CROSSTALK The Journal of Defense Software Engineering, 11

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

Takahashi, 1989, An empirical study of a model for program error prediction, IEEE Transactions on Software Engineering, 15, 82, 10.1109/32.21729

Tavolato, 1984, A prototyping methodology and its tool

Tukey, 1977

Verhoef, 2002, Quantitative IT portfolio management, Science of Computer Programming, 45, 1, 10.1016/S0167-6423(02)00106-5

C. Verhoef, Quantifying software process improvement, 2004. Available via: www.cs.vu.nl/~x/spi/spi.pdf

Verhoef, 2005, Quantifying the Value of IT-investments, Science of Computer Programming, 56, 315, 10.1016/j.scico.2004.08.004

Verhoef, 2007, Quantifying the effects of IT-governance rules, Science of Computer Programming, 67, 247, 10.1016/j.scico.2007.01.010

Watson, 2004, Data warehouse governance: Best practices at Blue Cross and Blue Shield of North Carolina, Decision Support Systems, 38, 435, 10.1016/j.dss.2003.06.001

Weigel, 2003, Interaction of policy choices and technical requirements for a space transportation infrastructure, Acta Astronautica, 52, 551, 10.1016/S0094-5765(02)00122-4

Weinberg, 1995, Just say no! improving the requirements process, American Programmer, 8, 19

G.M. Weinberg, Quality Software Management: Volume 2 First-Order Measurement, Dorset House, 1993

White, 2006, External disturbance control for software project management, International Journal of Project Management, 24, 127, 10.1016/j.ijproman.2005.07.002

Wiegers, 2003

Wikipedia. Bancassurance, Wikipedia http://en.wikipedia.org/wiki/Bancassurance, 2008 (accessed 01. 02. 2008)

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