Managing Implicit Requirements Using Semantic Case-Based Reasoning Research Preview

  • Olawande Daramola
  • Thomas Moser
  • Guttorm Sindre
  • Stefan Biffl
Part of the Lecture Notes in Computer Science book series (LNCS, volume 7195)


[Context and motivation] Implicit requirements (ImRs) are defined as requirements of a system which are not explicitly expressed during requirements elicitation, often because they are considered so basic that developers should already know them. Many products have been rejected or users made unhappy because implicit requirements were not sufficiently addressed. [Question/Problem] Requirement management tools have not addressed the issue of managing ImRs, also despite the challenges of managing ImRs that exist in practice the issue has not received sufficient attention in the literature. [Principal Idea/results] This planned research will investigate how automated support can be provided for managing ImRs within an organizational context, which is currently lacking in practice. This work proposed an approach that is based on semantic case-based reasoning for managing ImRs. [Contribution] We present the concept of a tool which enables managing of ImRs through the analogy-based requirements reuse of previously known ImRs. This ensures the discovery, structured documentation, proper prioritization, and evolution of ImRs, which improves the overall success of software development processes.


implicit requirements requirement reuse case-based reasoning analogy-based reuse semantic analysis 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    ISO/IEC 9126: Software Engineering – Product Quality- Part 1: Quality Model. Int’l Organization for Standard (2001)Google Scholar
  2. 2.
    Ahamed, R.: An Integrated and Comprehensive Approach to Software Quality. International Journal of Engineering Science and Technology 2(2), 59–66 (2010)MathSciNetGoogle Scholar
  3. 3.
    Leffingwell, D., Widrig, D.: Managing Software Requirements: A Unified Ap-proach. Addison-Wesley Longman Publishing Co., Boston (2000) ISBN: 0-201-61593-2Google Scholar
  4. 4.
    Drysdale, D.: High-Quality Software Engineering: Lessons from Six-Nines World. David Drysdale (2007)Google Scholar
  5. 5.
    Grehag, Å.: Requirements Management in a Life-Cycle Perspective - A Position Paper. In: Proceedings of the 7th International Workshop on REFSQ 2001, Interlaken, Switzerland, pp. 183–188 (2001)Google Scholar
  6. 6.
    Singer, L., Brill, O., Meyer, S., Schneider, K.: Utilizing Rule Deviations in IT Ecosystems for Implicit Requirements Elicitation. In: Proceedings of the Second International Workshop on Managing Requirements Knowledge (MaRK), pp. 22–26 (2009)Google Scholar
  7. 7.
    Jha, R.: Gathering Implicit Requirements (10-06-2009),
  8. 8.
    Parameswaran, A.: Capturing Implicit Requirements (02-08-2011),
  9. 9.
    Douglass, D.: Understanding Implicit Requirements of Software Architecture (06-08-2009),
  10. 10.
    Glinz, M.: A Risk-based Value-oriented Approach to Quality Requirements. IEEE Software, 34–41 (2008)Google Scholar
  11. 11.
    Deshpande, S., Richardson, I.: Management at the Outsourcing Destination - Global Software Development in India. In: Int’l Conf. on Global Software Engineering, pp. 217–225. IEEE Press (2009)Google Scholar
  12. 12.
    Larsson, A., Steen, O.: Tool Support for Requirements Management Quality from a User Perspective. In: Proceedings of IRIS29, Helsingör, Denmark (2008)Google Scholar
  13. 13.
    Kano, N., Nobuhiku, S., Fumio, T., Shinichi, T.: Attractive Quality and Must-be Quality. Journal of the Japanese Society for Quality Control 14(2), 39–48 (1984)Google Scholar
  14. 14.
    Xu, Q.L., Jiao, R.J., Yang, X., Helander, M.G., Khalid, H.M., Anders, O.: Customer Requirement Analysis Based on an Analytical Kano Model. In: Industrial Engineering and Engineering Management, pp. 1287–1291. IEEE Press (2007)Google Scholar
  15. 15.
    Monzon, A.: A Practical Approach to Requirements Reuse in Product Families of On-Board Systems. In: International Requirements Engineering, pp. 223–228. IEEE Press (2008)Google Scholar
  16. 16.
    Perednikas, E.: Requirements Reuse Based on Forecast of User Needs. In: Proceedings of the 20th EURO Mini Conference on Continuous Optimization and Knowledge-Based Technologies, Neringa, Lithuania, pp. 450–455 (2008)Google Scholar
  17. 17.
    Maiden, N.: Analogy as a Paradigm for Specification Reuse. Software Engineering Journal 6, 3–15 (1991)CrossRefGoogle Scholar
  18. 18.
    Hull, E., Jackson, K., Dick, J.: Requirements Engineering. Springer, Heidelberg (2004)Google Scholar
  19. 19.
    Giunchiglia, F., Shvaiko, P.: Semantic Matching. The Knowledge Engineering Review 18, 265–280 (2003)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Olawande Daramola
    • 1
  • Thomas Moser
    • 2
  • Guttorm Sindre
    • 1
  • Stefan Biffl
    • 2
  1. 1.Department of Computer and Information ScienceNorwegian University of Science and TechnologyTrondheimNorway
  2. 2.Christian Doppler Laboratory for Software Engineering, Integration for Flexible Automation SystemsVienna University of TechnologyAustria

Personalised recommendations