Skip to main content

A Controlled Experiment of a Method for Early Requirements Triage Utilizing Product Strategies

  • Conference paper
Requirements Engineering: Foundation for Software Quality (REFSQ 2009)

Part of the book series: Lecture Notes in Computer Science ((LNPSE,volume 5512))

  • 1185 Accesses

Abstract

[Context and motivation] In market-driven product development of software intensive products large numbers of requirements threaten to overload the development organization. It is critical for product management to select the requirements aligned with the overall business goals, product strategies and discard others as early as possible. Thus, there is a need for an effective and efficient method that deals with this challenge and supports product managers in the continuous effort of early requirements triage [1, 2] based on product strategies. This paper evaluates such a method – A Method for Early Requirements Triage Utilizing Product Strategies (MERTS), which is built based on the needs identified in literature and industry. [Question/problem] The research question answered in this paper is “If two groups of subjects have a product strategy, one group in NL format and one in MERTS format, will there be a difference between the two groups with regards to effectiveness and efficiency of requirements triage?” The effectiveness and efficiency of the MERTS were evaluated through controlled experiment in a lab environment with 50 software engineering graduate students as subjects. [Principal ideas/results] It was found through results that MERTS method is highly effective and efficient. [Contribution] The contribution of this paper is validation of effectiveness and efficiency of the product strategies created through MERTS method for requirements triage, prior to industry trials. A major limitation of the results is that the experiment was performed with the graduate students and not the product managers. However, the results showed that MERTS is ready for industry trials.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Similar content being viewed by others

References

  1. Davis, A.M.: The art of requirements triage. IEEE Computer 36, 42–49 (2003)

    Article  Google Scholar 

  2. Simmons, E.: Requirements Triage: What Can We Learn from a “Medical” Approach? IEEE Software 21, 86–88 (2004)

    Article  Google Scholar 

  3. Carmel, E., Becker, S.: A process model for packaged software development. IEEE Transactions on Engineering Management 42, 50–61 (1995)

    Article  Google Scholar 

  4. El Emam, K., Madhavji, N.H.: A field study of requirements engineering practices in information systems development. In: Proceedings of the Second IEEE International Symposium on Requirements Engineering, pp. 68–80. IEEE Computer Society, Los Alamitos (1995)

    Google Scholar 

  5. Karlsson, L., Dahlstedt, Å., Nattoch Dag, J., Regnell, B., Persson, A.: Challenges in Market-Driven Requirements Engineering - an Industrial Interview Study. In: Proceedings of the Eighth International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ 2002), pp. 101–112. Universität Duisburg-Essen, Essen (2003)

    Google Scholar 

  6. Gorschek, T., Wohlin, C.: Requirements Abstraction Model. Requirements Engineering journal 11, 79–101 (2006)

    Article  Google Scholar 

  7. Potts, C.: Invented Requirements and Imagined Customers: Requirements Engineering for Off-the-Shelf Software. In: Proceedings of the Second IEEE International Symposium on Requirements Engineering, pp. 128–130. IEEE, Los Alamitos (1995)

    Google Scholar 

  8. Scott, G.M.: Top priority management concerns about new product development, vol. 13. The Academy of Management Executive (1999)

    Google Scholar 

  9. Krishnan, V., Karl, T.U.: Product Development Decisions: A Review of the Literature. Manage. Sci. 47, 1–21 (2001)

    Article  Google Scholar 

  10. Khurum, M., Aslam, K., Gorschek, T.: MERTS – A method for early requirements triage and selection utilizing product strategies. In: APSEC 2007, Nagoya, Japan (2007)

    Google Scholar 

  11. Gorschek, T., Garre, P., Larsson, S., Wohlin, C.: A Model for Technology Transfer in Practice. IEEE Softw. 23, 88–95 (2006)

    Article  Google Scholar 

  12. Kappel, T.A.: Perspectives on roadmaps: how organizations talk about the future. Journal of Product Innovation Management 18, 39–50 (2001)

    Article  MathSciNet  Google Scholar 

  13. Fenton, N.E., Pfleeger, S.L.: Software Metrics - A Rigorous & Practical Approach. International Thomson Computer Press (1996)

    Google Scholar 

  14. Berander, P.: Evolving Prioritization for Software Product Management. APS, PhD. Blekinge tekniska hogskola (2007)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2009 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Khurum, M., Gorschek, T., Angelis, L., Feldt, R. (2009). A Controlled Experiment of a Method for Early Requirements Triage Utilizing Product Strategies. In: Glinz, M., Heymans, P. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2009. Lecture Notes in Computer Science, vol 5512. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-02050-6_3

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-02050-6_3

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-02049-0

  • Online ISBN: 978-3-642-02050-6

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics