DAGAR: a process for domain architecture definition and asset implementation
Proceedings of the conference on TRI-Ada '96: disciplined software development with Ada
Software reuse: architecture, process and organization for business success
Software reuse: architecture, process and organization for business success
Featured-based approach to object-oriented engineering of applications for reuse
Software—Practice & Experience
Product line software engineering of embedded systems
SSR '01 Proceedings of the 2001 symposium on Software reusability: putting software reuse in context
FORM: A feature-oriented reuse method with domain-specific reference architectures
Annals of Software Engineering
Automatic Generation of Use Cases from Workflows: A Petri Net Based Approach
FASE '02 Proceedings of the 5th International Conference on Fundamental Approaches to Software Engineering
Requirements variability models: meta-model based transformations
MIS '05 Proceedings of the 2005 symposia on Metainformatics
| Hi-index | 0.00 |
A product line definition must cover several systems, for this reason additional requirements are included as product line assets during domain engineering. Generic assets are presented to cover all components the product line instances are built from, and their corresponding composition rules. These generic assets embrace common and variable product aspects supporting the variability in product line definition and instantiation.This paper is devoted to present the problem of handling product line variability in every life-cycle stage by the integration of the ideas of the domain engineering method FORM (Feature-Oriented Reuse Method) and the Mecano Model, which defines a coarse-grained reusable element structure.