2023Unpublished venueRequires access

Natural Language Processing (NLP) based Extraction of Tacit Knowledge from Written Communication during Software Development

Maham Noor, Zeeshan Ali Rana

Open publisher page 2 citations

Abstract

Software engineering, in general, and Global Software Engineering (GSE), in particular, face challenges such as handling communication and collaboration issues and inappropriate knowledge management. It is difficult to ensure availability of right knowledge at the right time to the right person during software engineering activity. The knowledge needs to be shared across the organization but limitations of knowledge sharing tools or dispersed knowledge sharing media and improper handling of tacit knowledge makes it more challenging to share knowledge. Significant amount of communication during software engineering process takes place via emails and discussion forums. Decisions taken during planning activities are also communicated through emails. These emails and the discussions do not necessarily cover the rationale behind a decision or approach adopted. This leaves a substantial portion of shared knowledge as tacit. Mostly, due to undefined tacit knowledge handling procedures, organizations suffer with the loss of critical knowledge and information. One way to handle this loss of knowledge is to store every information in knowledge repository but this can increase the size of the knowledge repository. This paper presents a three step approach to identify tacit knowledge in the written communication such that the organizations can save the tacit knowledge for future use. The presented approach does not only extract up to 57% of tacit knowledge but also indicates that only 20% of the whole communication need to be externalized hence saving 80% capacity of the knowledge repository, if every communication was to be preserved as potential tacit knowledge.

About this research paper

What this paper is about

Software engineering, in general, and Global Software Engineering (GSE), in particular, face challenges such as handling communication and collaboration issues and inappropriate knowledge management. It is difficult to ensure availability of right knowledge at the right time to the right person during software engineering activity. The knowledge needs to be shared across the organization but limitations of knowledge sharing tools or dispersed knowledge sharing media and improper handling of tacit knowledge makes it more challenging to share knowledge. Significant amount of communication during software engineering process takes place via emails and discussion forums. Decisions taken during planning activities are also communicated through emails. These emails and the discussions do not necessarily cover the rationale behind a decision or approach adopted. This leaves a substantial portion of shared knowledge as tacit. Mostly, due to undefined tacit knowledge handling procedures, organizations suffer with the loss of critical knowledge and information. One way to handle this loss of knowledge is to store every information in knowledge repository but this can increase the size of the knowledge repository. This paper presents a three step approach to identify tacit knowledge in the written communication such that the organizations can save the tacit knowledge for future use. The presented approach does not only extract up to 57% of tacit knowledge but also indicates that only 20% of the whole communication need to be externalized hence saving 80% capacity of the knowledge repository, if every communication was to be preserved as potential tacit knowledge.

Why it matters

OpenAlex reports 2 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Software engineering, in general, and Global Software Engineering (GSE), in particular, face challenges such as handling communication and collaboration issues and inappropriate knowledge management. It is difficult to ensure availability of right knowledge at the right time to the right person during software engineering activity. The knowledge needs to be shared across the organization but limitations of knowledge sharing tools or dispersed knowledge sharing media and improper handling of tacit knowledge makes it more challenging to share knowledge. Significant amount of communication during software engineering process takes place via emails and discussion forums. Decisions taken during planning activities are also communicated through emails. These emails and the discussions do not necessarily cover the rationale behind a decision or approach adopted. This leaves a substantial portion of shared knowledge as tacit. Mostly, due to undefined tacit knowledge handling procedures, organizations suffer with the loss of critical knowledge and information. One way to handle this loss of knowledge is to store every information in knowledge repository but this can increase the size of the knowledge repository. This paper presents a three step approach to identify tacit knowledge in the written communication such that the organizations can save the tacit knowledge for future use. The presented approach does not only extract up to 57% of tacit knowledge but also indicates that only 20% of the whole communication need to be externalized hence saving 80% capacity of the knowledge repository, if every communication was to be preserved as potential tacit knowledge.

Key concepts: Tacit knowledge, Computer science, Knowledge management, Knowledge engineering, Knowledge sharing, Personal knowledge management, Knowledge value chain, Explicit knowledge

Related papers

Back to paper searchBrowse research topicsOriginal source
Natural Language Processing (NLP) based Extraction of Tacit Knowledge from Written Communication during Software Development — Research Paper | ScholarLens