MEASURING REQUIREMENT EVOLUTION - A Case Study in the E-commerce Domain

Päivi Ovaska

2004

Abstract

Although requirement evolution is a widely recognized phenomenon, there are only a few approaches for measuring it. These existing approaches are based on the assumption that all the requirements exist and can be seen in the requirement elicitation and analysis phases. They do not include provisions for the emergence during systems development of new requirements, which cannot be anticipated in the requirement elicitation and analysis phase. This paper shows how the concept of requirements creep is adopted for the measurement of emergent requirement evolution. We use a case study in the E-commerce domain to illustrate the use of this measure in the prediction of systems development. The findings of this study suggest that requirement evolution can be measured in a practical software project, and the findings demonstrate the strong influence of requirements creep on the systems development effort. The findings of our study encourage us to undertake further studies involving other organizations and projects.

References

  1. Andersson, S., M. Felici, 2001. Requirements Evolution: From Process to Product Oriented Management. In 3rd International Conference on Product Focused Software Profess Improvement, Springer-Verlag.
  2. Andersson, S. M. Felici, 2002. Quantitative Aspects of Requirement Evolution. In 26th Annual International Conference on Computer Software and Applications Conference, Oxford, England, IEEE Computer Society.
  3. Booch, G., 1993. Object-Oriented Analysis and Design with Applications, Addison Wesley Pub Co, 2 nd editions.
  4. Briand, L.,C., J. W. Daly, J. K. Wüst, 1999. A Unified Framework for Coupling Measurement in ObjectOriented Systems. In IEEE Transactions on Software Engineering, 25(1).
  5. Chen, P., P., 1976. The entity-relationship model: toward a unified view of data. In ACM Transactions on Database Systems.
  6. Chidamber, S.,R. and Chris F. Kemerer, 1994. A Metric Suite for Object Oriented Design. In IEEE Transactions on Software Engineering, Vol. 20, No. 6.
  7. Cockburn, A., 2001. Agile Software Development. Addison-Wesley.
  8. Curtis, B., H. Krasner, and N. Iscoe, 1988. A Field Study of the Software Design Process for Large Systems. In Communications of the ACM 31.
  9. Davidson, E.J., 2002. Technology Frames and Framing: A Socio-Cognitive Investigation of Requirement Determination. In MIS Quarterly, Vol. 26, Issue 4.
  10. Harker, S., K.Eason, and J. Dobson, 1993. The change and evolution of requirements as a challenge to the practice of software engineering. In IEEE International Symposium on Requirements Engineering, pages 266- 272, IEEE Computer Society Press.
  11. Henderson-Sellers, B.,1996. Object-Oriented Metrics: Measures of complexity, Prentice Hall, New Jersey.
  12. IEEE Std 982.1, 1988. IEEE Standard Dictionary of Measures to Produce Reliable Software.
  13. IEEE Std 982.2 , 1988. IEEE Guide for the Use of IEEE Standard Dictionary of Measures to Produce Reliable Software.
  14. Jacobson, I., 1992. Object-Oriented Software Engineering. Addison Wesley Pub Co, 1 st edition.
  15. Jarke, C. Rolland, A. Sutcliffe, R. Dömges, 1999. The nature of Requirements Engineering. Aachen: Shaker Verlag GmbH.
  16. Kotonya, G., I.Sommerville, 1998. Requirement Engineering, John Wiley & Sons, NY.
  17. Lawson, C.L., R. J. Hanson, 1995. Solving Least Squares Problems. Society for Industrial & Applied Mathematics.
  18. Lehman, M.,1998. Software's future: Managing evolution, In IEEE Software, Jan-Feb, pages 40-44.
  19. Lehman, M., D. Perry, and J. Ramil, 1998. On evidence supporting the feast hypothesis and the laws of software evolution. In Metrics 7898, Bethesda, Maryland.
  20. MATLAB® the Language of Technical Computing, 2003. The MathWorks, Inc., [URL: http://www.mathworks.com/, Referred 20 Sep 2003].
  21. Ovaska, P., 2003. On the Organizational Factors in Understanding of Information System Requirements. In Scandinavian Conference on Information Systems (IRIS26), Finland August 9-12.
  22. Pedrycz, W., J.F. Peters, S. Ramanna, 1999. A Fuzzy Set Approach to Cost Estimation of Software Project. (Editor: Meng, M.), In IEEE Canadian Conference on Electrical and Computer Engineering.
  23. Rumbaugh, J., 1990. Object-Oriented Modeling and Design. Prentice Hall.
  24. Ryan A. R. Carter, I. Annie, I. Antón, A. Dagnino, L. Williams, 2001. Evolving Beyond Requirement Creep: A Risk-Based Evolutionary Prototyping.In IEEE 5th International Symposium on Requirements Engineering.
  25. Tomayko, J.E, 2002.Engineering an unstable requirements using agile methods. In International Workshop on Time Constraint Requirement Engineering.
  26. van Lamsweerde, A., 2000. Requirements engineering in the year 00: A research perspective. In International Conference on Software Engineering (ICSE'2000), pages 5-19, Limerick, Ireland.
  27. Venkatachalam, A., R., 1993. Software Cost Estimation Using Artificial Neural Networks. In International Joint Conference on Neural Networks, October 25-29, Volume 1, Pages: 987 - 990.
  28. Wiegers, K.E., 1999. Software Requirements, Microsoft Press.
  29. Xia, F.,1996. Module Coupling: A Design Metric.In AsiaPacific Conference on Software Engineering. Seoul, South Korea, 4-7 Dec. Pages: 44 - 54.
Download


Paper Citation


in Harvard Style

Ovaska P. (2004). MEASURING REQUIREMENT EVOLUTION - A Case Study in the E-commerce Domain . In Proceedings of the Sixth International Conference on Enterprise Information Systems - Volume 3: ICEIS, ISBN 972-8865-00-7, pages 669-673. DOI: 10.5220/0002628806690673


in Bibtex Style

@conference{iceis04,
author={Päivi Ovaska},
title={MEASURING REQUIREMENT EVOLUTION - A Case Study in the E-commerce Domain},
booktitle={Proceedings of the Sixth International Conference on Enterprise Information Systems - Volume 3: ICEIS,},
year={2004},
pages={669-673},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0002628806690673},
isbn={972-8865-00-7},
}


in EndNote Style

TY - CONF
JO - Proceedings of the Sixth International Conference on Enterprise Information Systems - Volume 3: ICEIS,
TI - MEASURING REQUIREMENT EVOLUTION - A Case Study in the E-commerce Domain
SN - 972-8865-00-7
AU - Ovaska P.
PY - 2004
SP - 669
EP - 673
DO - 10.5220/0002628806690673