1999
DOI: 10.1016/s0164-1212(99)00062-x
|View full text |Cite
|
Sign up to set email alerts
|

A conceptual basis for feature engineering

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
95
0
3

Year Published

2001
2001
2023
2023

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 201 publications
(98 citation statements)
references
References 18 publications
0
95
0
3
Order By: Relevance
“…Turner et al [38] suggest a conceptual basis for feature engineering of software systems, and argue that by organizing requirements and life-cycle artifacts along their proposed notion of features, the gap between the problem space and solution space can be bridged. Although we have similar motivation, we believe that a more formal framework to reason about traceability between these artifacts helps improve software quality [19].…”
Section: Related Workmentioning
confidence: 99%
“…Turner et al [38] suggest a conceptual basis for feature engineering of software systems, and argue that by organizing requirements and life-cycle artifacts along their proposed notion of features, the gap between the problem space and solution space can be bridged. Although we have similar motivation, we believe that a more formal framework to reason about traceability between these artifacts helps improve software quality [19].…”
Section: Related Workmentioning
confidence: 99%
“…So, from the automated test case generation perspective, it can be viewed as a case of feature oriented automated test case generation method. Therefore, it can be viewed as a case on applying feature oriented Software Engineering [18] in automated test case generation.…”
Section: Related Workmentioning
confidence: 99%
“…A more global view of how features can bridge the gap between the problem and solution domain is presented in [9]. In their view features are composed out of requirements fragments and realised in one or more design fragments, which make up the complete design.…”
Section: Featuresmentioning
confidence: 99%
“…In ideal cases, a particular feature implementation is localised to a single module; but in many cases features will cut across multiple components [8]. Consequently, features are an important early aspect to consider, as they try to bridge the gap between the problem domain and solution domain [9].…”
Section: Introductionmentioning
confidence: 99%