2004
DOI: 10.1007/s00766-003-0168-y
|View full text |Cite
|
Sign up to set email alerts
|

Eliciting gaps in requirements change

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
35
0
2

Year Published

2004
2004
2019
2019

Publication Types

Select...
5
3
1

Relationship

2
7

Authors

Journals

citations
Cited by 59 publications
(37 citation statements)
references
References 22 publications
0
35
0
2
Order By: Relevance
“…Requirements change has long been of concern in information systems requirements engineering (RE) research (e.g., [7] [8]). Software evolution has also been a major preoccupation in software engineering (e.g., [9]).…”
Section: Related Workmentioning
confidence: 99%
“…Requirements change has long been of concern in information systems requirements engineering (RE) research (e.g., [7] [8]). Software evolution has also been a major preoccupation in software engineering (e.g., [9]).…”
Section: Related Workmentioning
confidence: 99%
“…It means that there are semantic relationship between both of them such as dependency, association, and generalization. Elements, which are not connected, are referred to as NoRelationship [5]. …”
Section: A Meta-model Of Requirement Elementsmentioning
confidence: 99%
“…MAP has not been considered by Kavakli in the GORE framework, but it is possible to deduce that it is a goal model used in the requirements elicitation stage because it can represent the requirements according to changes in the environment (Babar, et al, 2008;Rolland, et al, 2004).…”
Section: Goal Models and Re Stagesmentioning
confidence: 99%