Enterprise Requirements Management Knowledge Towards Digital Transformation

Conference paper
First Online:
Part of the Lecture Notes in Electrical Engineering book series (LNEE, volume 449)

Abstract

As the enterprise services are rapidly digitized by digital transformation, the need to integrated knowledge management of IT requirements and business requirements is increased.

In this paper, the cause of problems on requirements definition is explained to the lack of requirements management knowledge. The types of requirements management knowledge are defined as discovery, recovery, and transformation types from the points of business, application, and technology. A reference model is proposed to integrate different types of requirements management knowledge. A case study on the integration of different requirements guidelines is described to show the effectiveness of the proposed approach.

Keywords

Enterprise requirements management Digital transformation Requirements knowledge management Case study 
This is a preview of subscription content, log in to check access.

References

  1. 1.
    Sommerville, I., Sawyer, P.: Requirements Engineering—A Good Practice Guide. Wiley, Chichester (1997)MATHGoogle Scholar
  2. 2.
    Leffingwel, D., Widrig, D.: Managing Software Requirements a Unified Approach. Addison-Wesley Professional, Boston (2000)Google Scholar
  3. 3.
    Kotonya, G., Sonnmerville, I.: Requirements Engineering. Wiley, Chichester (2002)Google Scholar
  4. 4.
    Hull, E., Jackson, K., Dick, J.: Requirements Engineering. Springer, Heidelberg (2002)CrossRefMATHGoogle Scholar
  5. 5.
    Wiegers, K.: Software Requirements—Practical Techniques for Gathering and Managing Requirements Through the Product Development Cycle. Microsoft Corporation (2003)Google Scholar
  6. 6.
    Aurum, A., Wohlin, C.: Engineering and Managing Software Requirements. Springer, Heidelberg (2005)CrossRefMATHGoogle Scholar
  7. 7.
    Davis, A.M.: Software Requirements: Objects, Functions and States. Prentice-Hall, Upper Saddle River (1993)MATHGoogle Scholar
  8. 8.
    Davis, A.M.: Just Enough Requirements Management—Where Software Development Meets Marketing. Dorset House Publishing, New York (2005)Google Scholar
  9. 9.
    Berenbach, B., Paulish, D., Kazmeier, J., Dudorfeer, A.: Software and Systems Requirements Engineering in Practice. McGraw Hill, New York (2009)Google Scholar
  10. 10.
    Alford, M.: A requirements engineering methodology for real-time processing requirements. IEEE Trans. SE, SE-3(1), 66–69 (1977)Google Scholar
  11. 11.
    Dorfman, M., Flynn, R.: ARTS—an automated requirements traceability system. J. Syst. Softw. 4, 63–74 (1984)CrossRefGoogle Scholar
  12. 12.
    IEEE Std. 830-1998: Recommended Practice for Software Requirements Specification. IEEE (1998)Google Scholar
  13. 13.
    Ramesh, B., Jarke, M.: Toward reference models for requirements traceability. IEEE Trans. Softw. Eng. 27(1), 58–93 (2001)CrossRefGoogle Scholar
  14. 14.
    Palmer, J.: Traceability. In: Dorfman M., Thayer, R. (eds.) Software Engineering, pp. 266–276. IEEE (1996)Google Scholar
  15. 15.
    IIBA: A Guide to the Business Analysis Body of Knowledge. Lightning Source Inc. (2013)Google Scholar
  16. 16.
    JISA: Requirements Engineering Body of Knowledge (REBOK), Ver. 1.0, Kindaikagakusha (2011) (In Japanese)Google Scholar
  17. 17.
    Pohl, K., Rupp, C.: Requirements Engineering Fundamentals, A Study Guide for the Certified Professional for Requirements Engineering Exam Fundamental level/IREB compliant. Rockynook (2011)Google Scholar
  18. 18.
    The home of Requirements Engineering. http://www.ireb.org/. Accessed 11 May 2017
  19. 19.
    Jacobson, I., Pan Wei N., McMahon, P., Spence, I., Lidman, S.: The Essence of Software Engineering—Applying the SEMAT Kernel. Addison-Wesley Pearson Education (2013)Google Scholar
  20. 20.
    Josely, A.: TOGAF V.9 A Pocket Guide. The Open Group. Van Haren Publishing (2008)Google Scholar
  21. 21.
    Josely, A.: ArchiMate®2.0, A Pocket Guide. The Open Group. Van Haren Publishing (2013)Google Scholar
  22. 22.
    Software reliability Enhancement Center: Requirements Definition Guide for User. Information-Technology Promotion Agency, Japan (2017). (In Japanese)Google Scholar
  23. 23.
    Software reliability Enhancement Center: User Guide for Rebuilding System to the Success. Information-Technology Promotion Agency, Japan (2017). (In Japanese)Google Scholar

Copyright information

© Springer Nature Singapore Pte Ltd. 2018

Authors and Affiliations

  1. 1.Nagoya UniversityNagoyaJapan

Personalised recommendations