Abstract

Software requirements engineering deals with: elicitation, specification, and validation of software requirements. Furthermore there is a need to facilitate collaboration amongst stakeholders and analysts. Fewer efforts were deployed to support them in performing their job on a day to day basis. To solve this problem we use knowledge management for software requirements engineering. This paper proposes a knowledge management framework, based on the SECI model of knowledge creation, aimed at exploiting tacit and explicit knowledge related to software requirements within a given software project. The core part of the proposed framework is a set of four sub systems “Socializer”; “Externalizer”; “Combiner”; and “Internalizer”, attached to a couple of domain ontologies and a set of knowledge assets. Indeed we aim to facilitate a semantic based interpretation of knowledge assets related to software requirements by restricting their interpretation through the application domain and software requirements ontologies. We anticipate that this framework would be very helpful for stakeholders as well as analysts to exchange and manage their knowledge within a given software project. We show in the case study, through a virtual payroll project using the two-step approach: domain level requirements plus design level requirements, how the key elicitation SRE techniques are used during the first phase of domain requirements elicitation through the four subsystems of our framework.

Highlights

  • The communities of software engineering and knowledge engineering share a number of common topics

  • This paper proposes a knowledge management framework, based on the SECI model of knowledge creation, aimed at exploiting tacit and explicit knowledge related to software requirements within a given software project

  • We aim to enable advanced services for all key actors of the software requirements processes

Read more

Summary

Introduction

The communities of software engineering and knowledge engineering share a number of common topics. Activities in the domain of SRE typically involve people from at least two fields: 1) the business field (customers /users and other stakeholders) and 2) the IT field (analysts, requirements engineers and software project managers). This diversity of actors often produces important information flows and knowledge exchange that are difficult to manage. There is a need to help those actors managing collaboratively and exchanging their knowledge building shared practices (best practices) The last section concludes the paper and points out directions for future work

Software Requirements Engineering
Using Ontologies in Software Requirements Engineering
The SECI Model of Knowledge Creation
A Knowledge Management Framework in SRE Based on the SECI Model
Applying Domain Ontologies to SRE
Applying the SECI Model to SRE
Framework’s Architecture
Case Study
Conclusions
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.