PuLSE: a methodology to develop software product lines
SSR '99 Proceedings of the 1999 symposium on Software reusability
Software product lines: practices and patterns
Software product lines: practices and patterns
Component-based product line engineering with UML
Component-based product line engineering with UML
FORM: A feature-oriented reuse method with domain-specific reference architectures
Annals of Software Engineering
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
On the Influence of Variabilities on the Application-Engineering Process of a Product Family
SPLC 2 Proceedings of the Second International Conference on Software Product Lines
Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures
Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures
Product derivation in software product families: a case study
Journal of Systems and Software - Special issue: The new context for software engineering education and training
Software Product Line Engineering: Foundations, Principles and Techniques
Software Product Line Engineering: Foundations, Principles and Techniques
Software Engineering: A Practitioner's Approach
Software Engineering: A Practitioner's Approach
A theoretical foundation of variability in component-based development
Information and Software Technology
Evolution support mechanisms for software product line process
Journal of Systems and Software
Hi-index | 0.00 |
As a key activity in product line engineering (PLE), instantiation is a task to generate target applications by resolving variability embedded in core assets. However, instantiation is often conducted in manual and ad-hoc fashion, largely replying on domain knowledge and experience. Hence, it can easily lead to technical problems in precisely specifying decision model consisting of product-specific variation points and variants, and in handling inter-variant conflicts/dependency. To overcome this difficulty, it is desirable to develop a systematic process which includes a set of systematic activities, detailed instructions, and concrete specification of artifacts. In this paper, we first propose a meta-model of a core asset to specify its key elements. Then, we represent a comprehensive process that defines key instantiation activities, representations of artifacts, and work instructions. With the proposed process, one can instantiate core assets more effectively and systematically.