2014 IEEE International Conference on Industrial Engineering and Engineering Management 2014
DOI: 10.1109/ieem.2014.7058645
|View full text |Cite
|
Sign up to set email alerts
|

Identifying knowledge components in software requirement elicitation

Abstract: This paper considers the importance of knowledge in software development organizations which are highly knowledge-intensive and focuses on knowledge audit in their requirement elicitation process. Requirement elicitation process involves a great deal of knowledge and there are several problems regarding eliciting and using the knowledge in this process. Misunderstanding, undefined scope, conflicting information and constant changes of requirements are some of the problems of requirement elicitation. A knowledg… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2015
2015
2024
2024

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(3 citation statements)
references
References 22 publications
0
3
0
Order By: Relevance
“…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 (). The model was refined in accordance to the results of the survey to illustrate it in a more understandable way.…”
Section: Knowledge Audit Model For Requirements Elicitation Processmentioning
confidence: 99%
See 1 more Smart Citation
“…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 (). The model was refined in accordance to the results of the survey to illustrate it in a more understandable way.…”
Section: Knowledge Audit Model For Requirements Elicitation Processmentioning
confidence: 99%
“…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 (2014). The model was refined in accordance to the results of the survey to illustrate it in a more understandable way.…”
Section: Knowledge Audit Model For Requirements Elicitation Processmentioning
confidence: 99%
“…Basically, these processes are bound to vary at different levels depending on the kind of people that will be involved, organisational requirements and the application domain that is being employed. RE-E is a process that is used to determine and discover the needs of the clients or customers to find application domain [4], RA declares exactly what the software project is aimed to achieve [5], RS is used to document and presents a blueprint to the stakeholders for the process of software development [6], RVV acts as a proof that the software product may meet the needs of the stakeholders or customers [2] and finally RM is responsible for ensuring the existing requirements' modification are done in a controlled manner [7]. Figure 1 shows the activities involved in RE.…”
Section: Requirement Engineeringmentioning
confidence: 99%