Abstract

The research in this paper adds to the discussion linked to the challenge of capturing and modeling tacit knowledge throughout software development projects. The issue emerged when modeling functional requirements during a project for a client. However, using the design science research methodology at a particular point in the project helped to create an artifact, a functional requirements modeling technique, that resolved the issue with tacit knowledge. Accordingly, this paper includes research based upon the stages of the design science research methodology to design and test the artifact in an observable situation, empirically grounding the research undertaken. An integral component of the design science research methodology, the knowledge base, assimilated structuration and semiotic theories so that other researchers can test the validity of the artifact created. First, structuration theory helped to identify how tacit knowledge is communicated and can be understood when modeling functional requirements for new software. Second, structuration theory prescribed the application of semiotics which facilitated the development of the artifact. Additionally, following the stages of the design science research methodology and associated tasks allows the research to be reproduced in other software development contexts. As a positive outcome, using the functional requirements modeling technique created, specifically for obtaining tacit knowledge on the software development project, indicates that using such knowledge increases the likelihood of deploying software successfully.

Highlights

  • To improve software development, the research in this paper details how to utilize tacit knowledge during functional requirements modeling

  • The research aligns to the recognized challenge associated with tacit knowledge when developing software [5, 21, 45, 50] and asks the following Research Question (RQ): how can tacit knowledge be obtained and managed in order to contribute to functional requirements modeling? To answer the RQ, the Design Science Research Methodology (DSRM) [6, 7, 24, 28, 39] empirically grounds the research undertaken [18, 27]

  • The Unified Modeling Language (UML) Computer-Aided Software Engineering (CASE) Tool managed the document for each Normative statement, it linked each document to corresponding dialog reference points in the UML Use case model

Read more

Summary

Introduction

The research in this paper details how to utilize tacit knowledge during functional requirements modeling. The DSRM incorporated input from end-users, a requirements engineer ( the researcher), and the Unified Modeling Language (UML) to change unwanted circumstances into better ones during a software development project for a client. DSRM affords a process that guides researchers to initiate, develop and measure the impact of an artifact in a problem situation. The framework first helped to analyze how end-users conveyed tacit knowledge, and second, assisted when making changes to functional requirements modeling to aid its capture and management. Structuration theory guided the use of semiotic concepts which formalized a functional requirements modeling technique specific to handling tacit knowledge during a repeat of the requirements analysis phase of the software development project

Methods
Results
Conclusion
Full Text
Published version (Free)

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