Empirical Studies on Requirement Management Measures
Abstract
The goal of this research is to demonstrate that a subsetof a set of 38 requirements management measures are goodpredictors of stability and volatility of requirements andchange requests. At the time of writing we have theoreticallyvalidated ten of these 38 measures. We are currentlyplanning and performing an industrial case study where wewant to reach the goal described above.
References
[1]
{1} Anderson S., and Felici M., "Requirements Changes Risk/ Cost Analyses: an Avionic Case Study", in Foresight and Precaution, Proceedings of ESREL 2000, SARS and SRA-Europe Annual Conference, 2, Edinburgh, Scotland, UK, 15-17 May 2000, pp. 921-925.
[2]
{2} Basili V.R., and Rombach H.D., "The TAME Project: Towards Improvement-Oriented Software Environments", in IEEE Transactions on Software Engineering, 14(6), 1988, pp. 758-773.
[3]
{3} Basili V.R., and Weiss A., "Methodology for Collecting Valid Software Engineering Data", in IEEE Transactions on Software Engineering, 10(6), November 1984.
[4]
{4} Baumert J.H. and McWhinney M.S., Software Measures and the Capability Maturity Model, Software Engineering Institute Technical Report, CMU/SEI-92-TR-25, ESC-TR-92-0, 1992.
[5]
{5} Briand L.C., El Eman K., and Morasca S. "On the Application of Measurement Theory in Software Engineering", in Journal of Empirical Software Engineering, 1(1), 1996.
[6]
{6} Briand L.C., Morasca S., and Basili V.R., "An Operational Process for Goal Driven Definition of Measures", in IEEE Transactions on Software Engineering, 28(12), December 2002.
[7]
{7} Bush D., & Finkelstein A., "Environmental Scenarios and Requirements Stability", in Proceedings of the 5th International Workshop on Principles of Software Evolution (IWPSE 2002), ACM Press, Orlando, FL, May 2002.
[8]
{8} Costello R. J., and Liu D., "Metrics for Requirements Engineering," in Journal of Systems and Software, 29(1), April 1995, pp. 39-63.
[9]
{9} Fenton, N.E., and Pfleeger, S.L., Software Metrics - A Rigorous & Practical Approach, 2nd Edition, International Thomson Publishing, Boston, MA, 1996.
[10]
{10} Hammer T.F., Huffman L.L., and Rosenberg L.H, "Doing requirements right the first time", in CROSSTALK The Journal of Defence Software Engineering, December 1998, pp. 20-25.
[11]
{11} Kitchenham B., Pfleeger S.L., and Fenton N., "Towards a Framework for Software Measurement Validation," in IEEE Transactions on Software Engineering, 21(12), December 1995.
[12]
{12} Lavazza L., and Valletto G., "Enhancing Requirements and Change Management through Process Modelling and Measurement", in Proceeding of ICRE 2000 - Fourth International Conference on Requirements Engineering, Schaumburg, Illinois, 19-23 June 2000.
[13]
{13} Lavazza L., and Valletto G., "Requirements-Based Estimations of Change Costs", in Empirical Software Engineering - An International Journal, Kluwer, 5(3), November 2000.
[14]
{14} Loconsole A., "Measuring the Requirements Management Key Process Area", Proceedings of ESCOM - European Software Control and Metrics Conference, London, UK, April 2001.
[15]
{15} Loconsole A., "Non Empirical Validation of Requirements Management Measures", in Proceeding of WoSQ - Workshop on Software Quality at ICSE02, Orlando, Fl, May 2002.
[16]
{16} Loconsole A., and Börstler J., Theoretical Validation and Case Study of Requirements Management Measures, Umeå University Internal Report, Uminf 03.02, July 2003.
[17]
{17} Loconsole A. and Börstler J., "A Comparison of two Academic Case Studies on Cost Estimation of Changes to Requirements - Preliminary Results", in Proceeding of SMEF - Software Measurement European Forum, Rome, Italy, 28-30 January 2004.
[18]
{18} Paulk M.C., Weber C.V., Garcia S., Chrissis M.B., and Bush M., Key Practices of the Capability Maturity Model Version 1.1, Software Engineering Institute Technical Report, CMU/SEI-93- TR-25 ESC-TR-93-178, Pittsburgh, PA, USA, February 1993.
[19]
{19} Pflegeer S.L., Software Engineering Theory and Practice, Prentice Hall, Upper Saddle River, New Jersey, 1998.
[20]
{20} Pfleeger S.L., Jeffery R., Curtis B., and Kitchenham B., "Status Report on Software Measurement", IEEE Software, 14(2), 1997.
[21]
{21} Raynus J., Software Process Improvement with CMM, Artech House Publishers, Boston, 1999.
[22]
{22} Reifer D.J., "Requirements Management: The search for Nirvana", in IEEE Software, May/June 2000, pp. 45-47.
[23]
{23} Shneidewind N.F., "Methodology for Validating Software Metrics", in IEEE Transactions on Software Engineering, 18(5), May 1992.
[24]
{24} Sommerville I., and Sawyer P., Requirements Engineering a Good Practice Guide, Wiley, June 2000.
[25]
{25} The Standish Group. The CHAOS Report. Dennis, MA: The Standish Group, 1994.
[26]
{26} Weyuker E., "Evaluating Software Complexity Measures", in IEEE Transactions on Software Engineering, 14(9), 1988, pp. 1357-1365.
[27]
{27} Wiegers K. E., Impact Analysis Checklist for Requirements Changes, http://www.processimpact.com/goodies.shtml, September 2003, Last access: March 2004.
Index Terms
- Empirical Studies on Requirement Management Measures
Recommendations
Requirement Management And Axiomatic Design
There are three main objectives of requirements management; one is to capture the requirements right, the second one is to manage changing requirements, and the third one is to align the system development lifecycle activities with the requirements to ...
Goal Oriented Requirement Engineering: A Critical Study of Techniques
APSEC '06: Proceedings of the XIII Asia Pacific Software Engineering ConferenceThe term "Goal" is increasingly being used in Requirement Engineering. Goal-Oriented requirement engineering (GORE) provides an incremental approach for elicitation, analysis, elaboration & refinement, specification and modeling of requirements. Various ...
Capturing behavior coordination in goal-oriented requirement engineering
SEA '07: Proceedings of the 11th IASTED International Conference on Software Engineering and ApplicationsGoal-Oriented Requirement Engineering (GORE) methodologies use goals to facilitate elicitation, elaboration, analysis, and specification of the required behaviors for software. Traditional GORE approaches focus on the goal refinement and requirement ...
Comments
Please enable JavaScript to view thecomments powered by Disqus.Information & Contributors
Information
Published In
May 2004
761 pages
ISBN:0769521630
Sponsors
Publisher
IEEE Computer Society
United States
Publication History
Published: 23 May 2004
Check for updates
Qualifiers
- Article
Conference
ICSE04
Sponsor:
Acceptance Rates
ICSE '04 Paper Acceptance Rate 58 of 436 submissions, 13%;
Overall Acceptance Rate 276 of 1,856 submissions, 15%
Upcoming Conference
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- View Citations1Total Citations
- 1,236Total Downloads
- Downloads (Last 12 months)1
- Downloads (Last 6 weeks)0
Reflects downloads up to 01 Nov 2024
Other Metrics
Citations
View Options
Get Access
Login options
Check if you have access through your login credentials or your institution to get full access on this article.
Sign in