Model-driven impact analysis of software product lines

9Citations
Citations of this article
11Readers
Mendeley users who have this article in their library.
Get full text

Abstract

Software assets, which are developed and maintained at various stages, have different abstraction levels. The structural mismatch of the abstraction levels makes it difficult for developers to understand the consequences of changes. Furthermore, assessing change impact is even more challenging in software product lines because core assets are interrelated to support domain and application engineering. Modeldriven engineering helps software engineers in many ways by lifting the abstraction level of software development. The higher level of abstraction provided by models can serve as a backbone to analyze and design core assets and architectures for software product lines. This chapter introduces modeldriven impact analysis that is based on the synergy of three separate techniques: (1) domain-specific modeling, (2) constraint-based analysis, and (3) software testing. The techniques are used to establish traceability relations between software artifacts, assess the tradeoff of design alternatives quantitatively, and conduct change impact analysis. © 2011, IGI Global.

Cite

CITATION STYLE

APA

Cho, H., Gray, J., Cai, Y., Wong, S., & Xie, T. (2010). Model-driven impact analysis of software product lines. In Model-Driven Domain Analysis and Software Development: Architectures and Functions (pp. 275–303). IGI Global. https://doi.org/10.4018/978-1-61692-874-2.ch013

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free