2015 9th Malaysian Software Engineering Conference (MySEC) 2015
DOI: 10.1109/mysec.2015.7475204
|View full text |Cite
|
Sign up to set email alerts
|

A knowledge audit model to assess the knowledge in requirement elicitation process

Abstract: There is a great deal of knowledge in requirement elicitation process (REP), because there are different stakeholders with various knowledge backgrounds. Different backgrounds of knowledge lead to different ways of knowledge expression that negatively affect knowledge understandability and cause ambiguity. Knowledge ambiguity results in incorrect interpretation of knowledge and requirements. On the other hand, different stakeholders have different needs and expectations from the software to be developed. This … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2017
2017
2024
2024

Publication Types

Select...
2
1
1

Relationship

1
3

Authors

Journals

citations
Cited by 4 publications
(5 citation statements)
references
References 33 publications
0
5
0
Order By: Relevance
“…The importance of the application domain knowledge in order to improve the requirements elicitation process is widely accepted. However, currently the most of the methods and tools of requirements elicitation are designed for general problem domains, where problem-specific domain knowledge is not completely necessary [25]. The KMoS-RE © strategy emphasizes the importance of the application domain knowledge, either tacit or explicit, besides of proposing techniques and methods to facilitate its discovery, representation, sharing and appropriation among all involved in the project.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…The importance of the application domain knowledge in order to improve the requirements elicitation process is widely accepted. However, currently the most of the methods and tools of requirements elicitation are designed for general problem domains, where problem-specific domain knowledge is not completely necessary [25]. The KMoS-RE © strategy emphasizes the importance of the application domain knowledge, either tacit or explicit, besides of proposing techniques and methods to facilitate its discovery, representation, sharing and appropriation among all involved in the project.…”
Section: Discussionmentioning
confidence: 99%
“…The model allows the incorporation of new proposals from methods and techniques to knowledge management models or perspectives of elicitation of requirements. For example, we are currently analysing the adaptation that is based on goals elicitation approach [26], the knowledge audit model [25] and the social network analysis [27].…”
Section: Discussionmentioning
confidence: 99%
“…The relationship among these components was also identified through reviewing the literature. Based on the theoretical study, an initial model was proposed; this model was described in Taheri, Pa, Abdullah, and Abdullah (). The KA components and their relationships were verified based on the results of a survey that is presented in Taheri, Pa, Abdullah, Abdullah, and Shafazand ().…”
Section: Knowledge Audit Model For Requirements Elicitation Processmentioning
confidence: 99%
“…Furthermore, the main focus of previous studies was on domain knowledge, whereas, as noted above, different categories of knowledge are involved in REP. For this reason, there is a need of KA model with the focus on knowledge assessment. The KA model for REP is developed and presented in a previous paper by the researchers (Taheri et al, ). In this paper, the methods used to develop and validate the KA model are elaborated; the results of validation are discussed as well.…”
Section: Existing Studiesmentioning
confidence: 99%
See 1 more Smart Citation