Skip to main content

Managing Requirements Knowledge: Conclusion and Outlook

  • Chapter
  • First Online:

Abstract

This chapter summarises the Managing Requirements Knowledge book and concludes with the future work. For this purpose, we performed a case-by-case review of the book chapters as well as other relevant publications and extracted the research issues, main contributions, benefits or lessons learned, and future research directions.

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

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   84.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   109.00
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD   109.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

References

  1. Lutz R, Lavin M, Lux J, Peters K, Rouquette NF (2013) Mining requirements from operational experience. In: Managing requirements knowledge (Chapter 3 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  2. Carrillo de Gea JM, Nicolás J, Alemán JLF, Toval A, Vizcaíno A, Ebert C (2013) Reusing requirements in global software engineering. In: Managing requirements knowledge (Chapter 8 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  3. Classen A, Heymans P, Schobbens P (2008) What’s in a feature: a requirements engineering perspective. FASE’08, Lecturer notes in computer science, vol 4961. Budapest, pp 16–30

    Google Scholar 

  4. Ghaisas S, Ajmeri N (2013) Knowledge-assisted ontology-based requirements evolution. In: Managing requirements knowledge (Chapter 7 in this volume). Springer, Heidelberg

    Google Scholar 

  5. Dutoit A, Paech B (2003) Eliciting and maintaining knowledge for requirements evolution. In: Aurum A, Jeffery R, Wohlin C, Handzic M (eds) Managing software engineering knowledge. Springer, New York

    Google Scholar 

  6. Thurimella AK, Bruegge B (2012) Issue-based variability management. Inform Softw Technol 54(9):933–950

    Article  Google Scholar 

  7. Daramola O, Stålhane T, Omoronyia I, Sindre G (2013) Using ontologies and machine learning for hazard identification and analysis. In: Managing requirements knowledge (Chapter 6 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  8. Soffer A, Dori D (2013) Model-based requirements engineering framework for systems lifecycle support. In: Managing requirements knowledge (Chapter 13 in this volume). Springer, Heidelberg

    Google Scholar 

  9. Narayan N, Delater A, Paech B, Bruegge B (2011) Enhanced traceability in model-based CASE tools using ontologies and information retrieval. In: Proceedings of the 4th international workshop on managing requirements knowledge (MaRK’11), Trento, 30 Aug 2011

    Google Scholar 

  10. Hull E, Jackson K, Dick J (2004) Requirements engineering. Springer, London

    Google Scholar 

  11. Gervasi V, Gacitua R, Rouncefield M, Sawyer P, Kof L, Ma L, Piwek P, de Roeck A, Willis A, Yang H, Nuseibeh B (2013) Unpacking tacit knowledge for requirements engineering. In: Managing requirements knowledge (Chapter 2 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  12. Maalej W, Thurimella A (2008–2010) Managing requirements knowledge, international workshop on, 2008–2010, IEEE, Barcelona/Atlanta/Sydney/Trento

    Google Scholar 

  13. Stoiber R, Glinz M (2009) Modelling and managing tacit product line requirements knowledge. In: Proceedings of the 2009 second international workshop on managing requirements knowledge (MARK ’09). IEEE Computer Society, Washington, DC, pp 60–64

    Google Scholar 

  14. Liang P, Avgeriou P, He K (2010) Rationale management challenges in requirements engineering. In: Proceedings of the third international workshop on managing requirements knowledge (MARK), Sydney, Australia, pp 16–21

    Google Scholar 

  15. Maalej W, Thurimella A (2013) DUFICE: practical guidelines for managing requirements knowledge. In: Managing requirements knowledge (Chapter 4 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  16. Smith S, Harrison M (2005) Measuring reuse in hazard analysis. Reliab Eng Syst Safe 89(1): 93–104

    Article  Google Scholar 

  17. Franch X, Quer C, Renault S, Guerlain C, Palomares C (2013) Constructing and using software requirements patterns. In: Managing requirements knowledge (Chapter 5 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  18. Supakkul S, Hill T, Oladimeji EA, Chung L (2009) Capturing, organizing, and reusing knowledge of NFRs: an NFR pattern approach, managing requirements knowledge, Atlanta, USA, pp 75–84

    Google Scholar 

  19. Sim SE, Gallardo-Valencia GE (2013) Performative and lexical knowledge sharing in agile requirements. In: Managing requirements knowledge (Chapter 9 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  20. Lim SL, Damian D, Ishikawa F, Finkelstein A (2013) Using Web 2.0 for stakeholder analysis: StakeSource and its application in ten industrial projects. In: Managing requirements knowledge (Chapter 10 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  21. Castro-Herrera C, Cleland-Huang J (2009) A machine learning approach for identifying expert stakeholders, managing requirements knowledge, international workshop on, second international workshop on managing requirements knowledge, Atlanta, USA, pp 45–49

    Google Scholar 

  22. Ruhe G, Saliu M (2005) The art and science of software release planning. IEEE Computer Society, IEEE Softw 22(6): 47–53

    Article  Google Scholar 

  23. Dardenne A, van Lamsweerde A, Fickas S (1993) Goal-directed requirements acquisition. Sci Comput Prog 20:3–50

    Article  MATH  Google Scholar 

  24. Sharma R, Biswas KK (2013) Resolving inconsistency and incompleteness issues in software requirements. In Managing requirements knowledge (Chapter 11 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  25. Elfaki A (2013) Automated verification of variability models using first order logic. In: Managing requirements knowledge (Chapter 12 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  26. Lohmann S, Heim P, Auer S, Dietzold S, Riechert R (2008) Semantifying requirements engineering – the softWiki approach, I-SEMANTICS, Graz, pp 182–185

    Google Scholar 

  27. Lohmann S, Riechert T, Auer S (2008) Collaborative development of knowledge bases in distributed requirements elicitation. Software engineering (Workshops): agile knowledge sharing for distributed software teams, Munich, Germany pp 22–28

    Google Scholar 

  28. Felfernig A, Friedrich G, Jannach D, Stumptner M, Zanker M (2003) Configuration knowledge representations for semantic web applications. AIEDAM 17(2):31–50

    Google Scholar 

  29. Haarslev V, Möller R (2001) RACER system description. In: IJCAR 2001, LNAI, vol 2083. Siena, pp 701–705

    Google Scholar 

  30. Ruhe G, Eberlein A, Pfahl D (2003) Trade-off analysis for requirements selection. Int J Softw Eng Knowl Eng (IJSEKE) 13(4):354–366

    Google Scholar 

  31. Schrijver A (1998) Theory of linear and integer programming. Wiley, New York

    MATH  Google Scholar 

  32. Felfernig A, Ninaus G, Grabner H, Reinfrank F, Weninger L, Pagano D, Maalej W (2013) An overview of recommender systems in requirements engineering. In: Managing requirements knowledge (Chapter 14 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  33. Burke R (2000) Knowledge-based recommender systems. Encyclop Libr Inform Syst 69(32): 180–200

    Google Scholar 

  34. Knauss E, Meyer S (2013) Experience-based requirements engineering tools. In: managing requirements knowledge (Chapter 15 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  35. Jastram M (2013) The eclipse requirements modelling framework. In: Managing requirements knowledge (Chapter 16 in this volume). Springer, Heidelberg, Germany

    Google Scholar 

  36. Uenalan O, Riegel N, Weber S, Doerr J (2008) Using enhanced wiki-based solutions for managing requirements, first international workshop on managing requirements knowledge (MARK), Barcelona, Spain, pp 63–67

    Google Scholar 

  37. Polanyi M (1966) The tacit dimension. The University of Chicago Press, Garden City

    Google Scholar 

  38. Glinz M (2007) On non-functional requirements. In: IEEE RE2007, New Delhi, India, pp 21–26

    Google Scholar 

  39. Ali R, Solis C, Omoronyia I, Salehie M, Nuseibeh B (2012) Social adaptation: when software gives users a voice. In: Proceedings of the 7th international conference on evaluation of novel approaches to software engineering (ENASE 2012), Wroclaw, 29–30 June 2012

    Google Scholar 

  40. Dutoit A, McCall R, Mistrik I, Paech B (2006) Rationale management in software engineering. Springer, Berlin

    Book  Google Scholar 

  41. Maalej W, Happel H, Rashid A (2009) When users become collaborators: towards continuous and context-aware user input. In: Proceedings of OOPSLA 2009 (Onward!), ACM, Orlando, USA

    Google Scholar 

  42. Maalej W Pagano D (2011) On the socialness of software. In: Proceedings of the international conference on social computing and its applications, IEEE, Sydney, Australia

    Google Scholar 

  43. Ko AJ, DeLine R, Venolia G (2007) Information needs in collocated software development teams. In: Proceedings of the 29th internatinal conference on software engineering, Minneapolis, USA, pp 344–353

    Google Scholar 

  44. Sillito J, Murphy GC, De Volder K (2008) Asking and answering questions during a programming change task. Trans Softw Eng 34:434–451

    Article  Google Scholar 

  45. Robillard MP (2009) What makes APIs hard to learn? Answers from developers. IEEE Softw 26:27–34

    Article  Google Scholar 

  46. Iyer J, Richards D (2004) Evaluation framework for tools that manage requirements inconsistency. In: 9th Australian workshop on requirements engineering (AWRE’04), Adelaide, Australia

    Google Scholar 

  47. Felfernig A, Friedrich G, Jannach D, Stumptner M (2004) Consistency-based diagnosis of configuration knowledge bases. Artif Intell 152(2):213–234

    Article  MathSciNet  MATH  Google Scholar 

  48. Grether D, Plott C (1979) Economic theory of choice and the preference reversal phenomenon. Am Econ Rev 69(4):623–638

    Google Scholar 

  49. Bettman J, Luce M, Payne J (1998) Constructive consumer choice. J Cons Res 25(3):187–217

    Article  Google Scholar 

  50. Felfernig A, Friedrich G, Isak K, Shchekotykhin K, Jannach D, Teppan E (2009) Automated debugging of recommender user interface descriptions. J Appl Intell 31(1):1–14, Springer

    Article  Google Scholar 

  51. Hu M, Liu B (2004) Mining and summarizing customer reviews. In: Proceedings of the 10th ACM SIGKDD international conference on knowledge discovery and data mining, Seattle, USA, pp 168–177

    Google Scholar 

  52. Zimmermann O, Koehler J, Leymann F, Polley R, Schuster N (2009) Managing architectural decision models with dependency relations, integrity constraints, and production rules. J Syst Softw 82(8):1249–1267

    Article  Google Scholar 

  53. Leite JA (2002) Evolving knowledge bases, frontiers in artificial intelligence and applications, IOS Press, Amsterdam, Netherlands

    Google Scholar 

  54. Avgeriou P, Grundy J, Hall JG, Lago P, Mistrík I (2011) Relating software requirements and architectures. Springer, New York

    Book  Google Scholar 

  55. MaRK Community www1.cs.tum.edu/mark/community

  56. Jones P (2011) Can requirements tool vendors tell us about user needs? Fourth international workshop on managing requirements knowledge (MARK), Trento, Italy, pp76–81

    Google Scholar 

  57. Meyer B (1997) Object-oriented software construction, 2nd edn. Prentice-Hall Inc, Upper Saddle River

    MATH  Google Scholar 

  58. Hoenderboom B, Liang P (2009) A survey of semantic wikis for requirements engineering, technical report RUG-SEARCH-09-L03, University of Groningen

    Google Scholar 

  59. Maalej W, Thurimella A (2009) Towards a research agenda for recommendation systems in requirements engineering. In: Proceedings of the 2nd international workshop on managing requirements knowledge, Atlanta

    Google Scholar 

  60. Mairiza D, Zowghi D (2010) An ontological framework to manage the relative conflicts between security and usability requirements. In: Proceedings of the third international workshop on managing requirements knowledge (MARK), Sydney, Australia, pp 1–6

    Google Scholar 

  61. Schubanz M, Pleuss A, Botterweck G, Lewerentz C (2012) Modeling rationale over time to support product line evolution planning. In: VaMoS 2012, Leipzig, Germany, pp 193–199

    Google Scholar 

Download references

Acknowledgements

We thank Rick Rabiser and Yang Li for providing a valuable feedback on this chapter.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to A. K. Thurimella .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2013 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Thurimella, A.K., Maalej, W. (2013). Managing Requirements Knowledge: Conclusion and Outlook. In: Maalej, W., Thurimella, A. (eds) Managing Requirements Knowledge. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-34419-0_17

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-34419-0_17

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-34418-3

  • Online ISBN: 978-3-642-34419-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics