A large subset of requirements for complex systems, services and product lines is traditionally specified by hierarchical structures of features. Features are usually gathered and represented in the form of a feature tree. The feature tree is a structural model. It represents mainly composition and specialization relations between features and does not provide the possibility to specify requirements in the form of ordering relations defined on functional features. Use case scenarios are usually employed for specification of the ordering relations. However, use case scenarios comprise isolated sequences of features, and therefore they may be inconsistent and even may contradict each other and the feature tree. Moreover, some use case scenari...
One basic construct in feature models (FMs) is the constraints between features, which play the role...
This paper states that many of the problems which arise when features combine (i.e. feature interact...
[Context and motivation] Requirements catalogues for software release planning are often not complet...
A large subset of requirements for complex systems, services and product lines is traditionally spec...
The proper elicitation and specification of functional and non-functional requirements of an informa...
A feature model captures various possible configurations of products within a product family. When c...
This tutorial compares two requirements-led approaches to strengthen product line engineering and ca...
Requirements engineering is often, especially in the context of major open source software projects,...
A successful information systems development (ISD) depends on a complete, correct, and consistent se...
The specification of requirements is a key activity for achieving the goals of any software project ...
The specification of requirements is a key activity for achieving the goals of any software project ...
Abstract. We present a method to systematically detect feature interactions in requirements, which a...
Abstract. Goal-oriented requirements engineering (GORE) approaches offer a natural way to capture si...
In software development, requirements define the expected behaviour of a system. Requirements can ha...
Reuse is a fundamental activity in software development lifecycle, which can be employed at any stag...
One basic construct in feature models (FMs) is the constraints between features, which play the role...
This paper states that many of the problems which arise when features combine (i.e. feature interact...
[Context and motivation] Requirements catalogues for software release planning are often not complet...
A large subset of requirements for complex systems, services and product lines is traditionally spec...
The proper elicitation and specification of functional and non-functional requirements of an informa...
A feature model captures various possible configurations of products within a product family. When c...
This tutorial compares two requirements-led approaches to strengthen product line engineering and ca...
Requirements engineering is often, especially in the context of major open source software projects,...
A successful information systems development (ISD) depends on a complete, correct, and consistent se...
The specification of requirements is a key activity for achieving the goals of any software project ...
The specification of requirements is a key activity for achieving the goals of any software project ...
Abstract. We present a method to systematically detect feature interactions in requirements, which a...
Abstract. Goal-oriented requirements engineering (GORE) approaches offer a natural way to capture si...
In software development, requirements define the expected behaviour of a system. Requirements can ha...
Reuse is a fundamental activity in software development lifecycle, which can be employed at any stag...
One basic construct in feature models (FMs) is the constraints between features, which play the role...
This paper states that many of the problems which arise when features combine (i.e. feature interact...
[Context and motivation] Requirements catalogues for software release planning are often not complet...