One of the most important issues in the development of software product lines is the elicitation, management, and representation of the variability. In this context, one of the most used instruments is the feature model. But a feature model (due to the open definition of feature) usually contains an amalgamation of various different variability aspects as structural, behavioral, non-functional, or platform variability. We propose to separate these variability aspects of the product line, using other models as goals or UML diagrams but keeping features as the core model. The second part of the article explores the possibilities of identifying mappings between the feature models and the correspondent architectural counterparts. With these mappings, the automated creation of traceability links between the product line models is possible and hence the productivity in the development process of the product line will be enhanced. This approach also simplifies the separation in several development stages, using the appropriate paradigms as goals, features, package models, platforms
@inproceedings{wer200806,
author = {Laguna, M. A. and González-Baixauli, B.},
title = {Product Line Requirements: Multi-Paradigm Variability Models},
booktitle = {Proceedings of the WER2008-11th Workshop on Requirements Engineering, Barcelona, Catalonia - Spain},
year = {2008},
issn = {2675-0066},
isbn = {978-84-7653-144-0},
doi = {}
}