Are size measures better than expert judgment? An industrial case study on requirements volatility

Proceedings - Asia-Pacific Software Engineering Conference, APSEC

Volumn , Issue , 2007, Pages 238-245

  Loconsole, Annabella ^a   Börstler, Jürgen ^a  

^a UMEÅ UNIVERSITY   (Sweden)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER SOFTWARE; DATA REDUCTION; DECISION MAKING; MANAGERS; OBJECT ORIENTED PROGRAMMING; PROBLEM SOLVING; PROJECT MANAGEMENT; REQUIREMENTS ENGINEERING; SOFTWARE ENGINEERING; STATISTICAL METHODS; STRUCTURAL ANALYSIS; TECHNOLOGY;

ASIA PACIFIC; CASE STUDIES; DATA ANALYSIS; EFFORT ESTIMATION; EXPERT JUDGMENT; INDUSTRIAL CASE STUDIES; LITTLE RESEARCH; OBJECTIVE MEASURES; PROJECT MANAGER (PM); REQUIREMENTS VOLATILITY; SIZE MEASURING; SOFTWARE PROJECTS; STRUCTURAL MEASURES; USE CASES;

ESTIMATION;

EID: 44949187433     PISSN: 15301362     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/APSEC.2007.28     Document Type: Conference Paper

References (30)

1. V. Ambriola and V. Gervasi. Process metrics for requirements analysis. In Proc. of the 7th European Workshop on Software Process Technology, pages 90-95, Feb. 2000.
2. V. R. Basili, F. Shull, and F. Lanubile. Building knowledge through families of experiments. IEEE Transactions on Software Engineering, 25(4):456-473, 1999.
3. J. Baumert and M. McWhinney. Software Measures and the Capability Maturity Model. Technical Report CMU/SEI-92-TR-025, Pittsburgh, July 1992.
4. L. Briand and J. Wüst. Advances in computers, chapter: Empirical studies of quality models in object-oriented systems. Academic Press, INC, USA, 2002.
5. L. Briand, J. Wüst, J. Daly, and D. Porter. Exploring the relationships between design measures and software quality in object-oriented systems. Journal of Systems and Software, 51(3):245-273, 2000.
6. M. Chrissis, M. Konrad, and S. Shrum. CMMI: Guidelines for Process Integration and Product Improvement. AddisonWesley, Boston, MA, USA, 2003.
7. N. Fenton and S. Pfleeger. Software Metrics: A rigorous and practical approach. International Thomson Computer Press, London, UK, second edition, 1996.
8. G. Ham. Four roads to use case discovery-there is a use (and a case) for each one. CrossTalk-The Journal of Defense Software Engineering, Dec. 1998.
9. R. Hughes. Expert judgement as an estimating method. Information and Software Technology, 38(2):67-75, 1996.
10. L. Hyatt and L. Rosenberg. A software quality model and metrics for identifying project risks and assessing software quality. In ESA 1996 Product Assurance Symposium and Software Product Assurance Workshop, pages 209-212, ESTEC, Noordwijk, The Netherlands, 1996. European Space Agency.
11. I. Jacobson. Use cases - yesterday, today, and tomorrow. Software and Systems Modeling, 3(3):210-220, Aug. 2004.
12. M. Jørgensen. Top-down and bottom-up expert estimation of software development effort. Information and Software Technology, 46(1):3-16, 2004.
13. B. A. Kitchenham and L. M. Pickard. Evaluating software eng. methods and tools part 9: quantitative case study methodology. SIGSOFT Softw. Eng. Notes, 23(1):24-26, 1998.
14. Y. Lau. Service-oriented architecture and the C4ISR framework. CrossTalk-The Journal of Defense Software Engineering, Sept. 2004.
15. S. Lilly. Use case pitfalls: top 10 problems from real projects using use cases. In Proceedings TOOLS30, pages 174-183, 1999.
16. A. Loconsole. Definition and Validation of Requirements Management Measures. PhD Thesis, UMINF 07.22, November 2007.
17. A. Loconsole and J. Börstler. An industrial case study on requirements volatility measures. Appendices: http://www.cs.umu.se/research/ software/apsec05/. In 12th IEEE Asia Pacific Conference on Software Engineering, pages 249-256, Taipei, Taiwan, Dec. 2005. IEEE Computer Press.
18. A. Loconsole and J. Börstler. Appendices to Are size measures better than expert judgement? An industrial case study on requirements volatility. http://www.cs.umu.se/research/software/apsec07, June 2007.
19. A. Loconsole and J. Börstler. Construction and Validation of Prediction Models for Number of Changes to Requirements. Technical Report, UMINF 07.03, Feb. 2007.
20. J. C. Nunnally. Psychometric Theory. New York: McGrawHill Book Company, 1967.
21. N. Nurmuliani, D. Zowghi, and S. Fowell. Analysis of requirements volatility during software development life cycle. In ASWEC '04: Proceedings of the 2004 Australian Software Engineering Conference (ASWEC04), page 28, Washington, DC, USA, 2004. IEEE Computer Society.
22. J. Raynus. Software process improvement with CMM. Artech House, Inc., Norwood, MA, USA, 1999.
23. G. Schneider and J. Winters. Applying use cases: a practical guide. Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA, 1998.
24. G. Stark, P. Oman, A. Skillicorn, and A. Ameele. An examination of the effects of requirements changes on software maintenance releases. Journal of Software Maintenance, 11(5):293-309, 1999.
25. P. Tomaszewski, J. Hakansson, L. Lundberg, and H. Grahn. The accuracy of fault prediction in modified code-statistical model vs. expert estimation. In Proceedings of the 13th Annual IEEE International Symposium and Workshop on Engineering of Computer Based Systems (ECBS'06), pages 334343, 2006.
26. C. Wohlin and A. A. Andrews. Assessing project success using subjective evaluation factors. Software Quality Control, 9(l):43-70, 2001.
27. C. Wohlin, P. Runeson, M. Höst, M. Ohlsson, B. Regnell, and A. Wesslén. Experimentation in software engineering: an introduction. Kluwer Academic Publishers, Norwell, MA, USA, 2000.
28. R. Young. The Requirements Engineering Handbook. Artech House, 2004.
29. J. Zar. Bio statistical Analysis. Prentice-Hall, New Jersey, 1999.
30. D. Zowghi and N. Nurmuliani. A study of the impact of requirements volatility on software project performance. In APSEC '02: Proceedings of the Ninth Asia-Pacific Software Engineering Conference, page 3, Washington, DC, USA, 2002. IEEE Computer Society.