Understanding “why” in software process modelling, analysis, and design
ICSE '94 Proceedings of the 16th international conference on Software engineering
Haemo dialysis software architecture design experiences
Proceedings of the 21st international conference on Software engineering
Managing variability in software architectures
SSR '01 Proceedings of the 2001 symposium on Software reusability: putting software reuse in context
Making a World of Difference: It in a Global Context
Making a World of Difference: It in a Global Context
Domain-Specific Runtime Variability in Product Line Architectures
OOIS '02 Proceedings of the 8th International Conference on Object-Oriented. Information Systems
Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Visual Variability Analysis for Goal Models
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
A taxonomy of variability realization techniques: Research Articles
Software—Practice & Experience
On Goal-based Variability Acquisition and Analysis
RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
Supporting multiple perspectives in feature-based configuration
Software and Systems Modeling (SoSyM)
| Hi-index | 0.00 |
Variability in complex software systems arises from the diverse characteristics, views, preferences, and goals of stakeholders. Recent variability research focuses on stakeholders' goals, using models, to analyze the space of alternative solutions for software functionalities. In our study we extend the goals-requirements-features approach by considering variability along multiple product development stages. We depict variability at the early and late requirements definition stage, architecture design, detailed design, and runtime, proposing a role-based framework for variability analysis. Variability design involves the placement of a decision boundary to identify the space of alternative features that can be left 'open' for the next stage of product decisions. We also analyze softgoals variability to allow early identification of variation points in the product architecture.