Linking Feature Models to Code Artifacts Using Executable Acceptance Tests

Ghanam, Yaser; Maurer, Frank

doi:10.1007/978-3-642-15579-6_15

Cited by 12 publications

(23 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Secondly, quality attributes may be transformed directly to functional features, e.g., security transformed to access control features [9]. Transformation from quality requirements to functionality is one architectural strategy [4].…”

Section: Discussion On the Resultsmentioning

confidence: 99%

“…As an example of this category, optional feature "Usability" has alternative child features "Usability for handicapped", "Usability for APT resident", and "Usability for VIPs" [27]. Quality attribute features are used in [27,7,10,12,11,9,20]. Not all studies call quality attribute features as "features", but the topology and relations resemble features very much.…”

Section: Capturing Quality Attribute Variabilitymentioning

confidence: 99%

“…An example is [9], where security variability is achieved by varying functionality, like different access control methods. Another example is privacy variability in personalized web systems [38,15], where personalization is characterized by privacy-violating functionality (e.g.…”

Section: Specific Quality Attributes That Varymentioning

confidence: 99%

See 2 more Smart Citations

A systematically conducted literature review

Myllärniemi

Raatikainen

Männistö

2012

Proceedings of the 16th International Software Product Line Conference - Volume 1

View full text Add to dashboard Cite

Typically, products in a software product line differ by their functionality, and quality attributes are not intentionally varied. Why, how, and which quality attributes to vary has remained an open issue. A systematically conducted literature review on quality attribute variability is presented, where primary studies are selected by reading all content of full studies in Software Product Line Conference. The results indicate that the success of feature modeling influences the proposed approaches, different approaches suit specific quality attributes differently, and empirical evidence on industrial quality variability is lacking.

show abstract

Section: Discussion On the Resultsmentioning

confidence: 99%

Section: Capturing Quality Attribute Variabilitymentioning

confidence: 99%

See 1 more Smart Citation

A systematically conducted literature review

Myllärniemi

Raatikainen

Männistö

2012

Proceedings of the 16th International Software Product Line Conference - Volume 1

View full text Add to dashboard Cite

show abstract

“…Some work [5,9] has used dynamic methods to support SPL extraction. For example, Eisenbarth and others [5] mapped features to source code when a visual behavior activated by a user was detected.…”

Section: Introductionmentioning

confidence: 99%

“…For example, Eisenbarth and others [5] mapped features to source code when a visual behavior activated by a user was detected. Ghanam and Maurer [9] also mapped executable acceptance test to feature models. Following this pathway, this paper accomplishes an exploratory study on dynamic SPL extraction based on test coverage and existing artifacts of an already developed system.…”

Section: Introductionmentioning

confidence: 99%

Test-based SPL extraction

Santos

Gaia

Figueiredo

et al. 2013

Proceedings of the 28th Annual ACM Symposium on Applied Computing

View full text Add to dashboard Cite

Many software systems have been developed as single products before Software Product Lines (SPLs) have emerged. Although some promising approaches have been proposed, extracting an SPL from existing software products is still expensive and time consuming. This paper presents an exploratory study that relies on a test-based SPL extraction from systems already developed. We aim to evaluate testing as the main mean to locate feature code and different sorts of existing artifacts to support the test-based location. We conduct two case studies starting from the derivation of the SPL feature model to the feature code location. Our preliminary results indicate (i) good rates of precision for feature seed location, where seed means a small portion of the feature code that allows the identification of the remaining portion, and (ii) good rates of recall for locating the whole feature code.

show abstract

Agile software product lines: a systematic mapping study

Silva¹,

Neto²,

O’Leary³

et al. 2011

Softw Pract Exp

View full text Add to dashboard Cite

Background: Software product lines and Agile methods have been an effective solution for dealing with the growing complexity of software and handling competitive needs of software organizations. They also share common goals, such as improving productivity, reducing time‐to‐market, decreasing development costs and increasing customer satisfaction. There has been growing interest in whether the integration of Agile and SPL could provide further benefits and solve many of the outstanding issues surrounding software development. Objective: This study investigates the state‐of‐the‐art in Agile SPL approaches, while identifying gaps in current research and synthesizing available evidence. It also provides a basis for a deeper understanding of the issues involved in the integration of Agile and SPL. Method: A mapping study was undertaken to analyze the relation between Agile and SPL methods. A set of four research questions were defined in which the 32 primary studies were evaluated. Results: This study provides insights into the integration of Agile and SPL approaches, it identifies the current gaps in the research, synthesize the available evidence and propose specific Agile methods and practices for integration in SPL. Conclusions: In general, few studies describe the underlying Agile principles being adopted by proposed Agile SPL solutions. The most common Agile practices proposed by the studies came from the XP and Scrum methods, particularly in the pro‐active SPL strategy. We identify certain Agile methods that are being overlooked by the Agile SPL community, and propose specific SPL practices areas suitable for adoption of Agile practices. Copyright © 2011 John Wiley & Sons, Ltd.

show abstract

Linking Feature Models to Code Artifacts Using Executable Acceptance Tests

Cited by 12 publications

References 12 publications

A systematically conducted literature review

A systematically conducted literature review

Test-based SPL extraction

Agile software product lines: a systematic mapping study

Contact Info

Product

Resources

About