2000
DOI: 10.1007/978-3-540-44995-9_12
|View full text |Cite
|
Sign up to set email alerts
|

Requirements Classification and Reuse: Crossing Domain Boundaries

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
18
0
1

Year Published

2002
2002
2017
2017

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 38 publications
(19 citation statements)
references
References 30 publications
0
18
0
1
Order By: Relevance
“…As part of this reuse need, Requirements Reuse has been subject of research [17] [18]. This trend is oriented to use knowledge of prior experiences in requirements elicitation, and this drives to knowledge reuse.…”
Section: B Requirements Elicitation and Requirements Reusementioning
confidence: 99%
“…As part of this reuse need, Requirements Reuse has been subject of research [17] [18]. This trend is oriented to use knowledge of prior experiences in requirements elicitation, and this drives to knowledge reuse.…”
Section: B Requirements Elicitation and Requirements Reusementioning
confidence: 99%
“…The main problem with this ad hoc approach, however, is that a good specification is completely dependent on the one engineer being the very expert in the given domain for years. It can be very useful to regard systematic recycling of existing specifications as an explicit step of the specification process [8], [9], [10]. From a requirements engineering process point of view we will come back to this point in discussing the next statement below.…”
Section: General Issuesmentioning
confidence: 99%
“…Related to semi-structured document processing, we found the following contributions: the RARE project [3] is focused on parsing texts based on a semantic network assisted by a thesaurus. Concerning requirement texts, Cleland-Huang et al [4] work on detection of viewpoints.…”
Section: Related Workmentioning
confidence: 99%