FORM: A feature-oriented reuse method with domain-specific reference architectures
Annals of Software Engineering
Integrating Feature Modeling with the RSEB
ICSR '98 Proceedings of the 5th International Conference on Software Reuse
Feature Diagrams: A Survey and a Formal Semantics
RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
A UML 2 Profile for Variability Models and their Dependency to Business Processes
DEXA '07 Proceedings of the 18th International Conference on Database and Expert Systems Applications
Automating Mappings between Use Case Diagrams and Feature Models for Software Product Lines
SPLC '07 Proceedings of the 11th International Software Product Line Conference
Modeling Variability in Business Process Models Using UML
ITNG '08 Proceedings of the Fifth International Conference on Information Technology: New Generations
A Use Case Based Approach to Feature Models' Construction
RE '09 Proceedings of the 2009 17th IEEE International Requirements Engineering Conference, RE
Automated Feature Model-Based Generation of Refinement Transformations
SEAA '09 Proceedings of the 2009 35th Euromicro Conference on Software Engineering and Advanced Applications
Integration testing in software product line engineering: a model-based technique
FASE'07 Proceedings of the 10th international conference on Fundamental approaches to software engineering
Formal definition of syntax and semantics for documenting variability in activity diagrams
SPLC'10 Proceedings of the 14th international conference on Software product lines: going beyond
| Hi-index | 0.00 |
It is well known that during the domain requirement engineering phase with UML, both feature models and UML notations (e.g. UML use case diagrams and activity diagrams for describing use cases) are necessary. The development in parallel of UML models and a feature model could introduce inconsistencies between such models that should be removed. The construction of UML models for requirements from a feature model is usually a complex task, the generation of UML models from a feature model cannot be automated, and it cannot be expected that UML specialists will construct feature models of high quality; for these reasons we propose in this paper to first develop UML models for requirements and from them to automatically generate a feature model. We have found only a few papers proposing methods for the construction of feature model from UML models for requirements, but these methods do not consider the mapping of use case descriptions, expressed using a UML notation, onto a feature model. In this paper we extend our previous work in requirements engineering of product lines with new kinds of variabilities for use case diagrams, and new stereotypes for classifying activity diagram actions. Additionally, we defined a transformation from these use case diagram and activity diagram notations onto feature model.