Andere Kunden interessierten sich auch für
![Metaheuristics to solve some variants of vehicle routing problems]( "Metaheuristics to solve some variants of vehicle routing problems")
Metaheuristics to solve some variants of vehicle routing problems38,99 €![Software Product Line Testing Process]( "Software Product Line Testing Process")
Software Product Line Testing Process44,99 €![CAD Tools and Algorithms for Product Design]( "CAD Tools and Algorithms for Product Design")
CAD Tools and Algorithms for Product Design74,99 €![Application of the warehouse management system software in the management of finished product inventories in the company]( "Application of the warehouse management system software in the management of finished product inventories in the company")
Application of the warehouse management system software in the management of finished product inventories in the company26,99 €![Software Reliability using Mathematical Modeling]( "Software Reliability using Mathematical Modeling")
Software Reliability using Mathematical Modeling51,99 €![A software platform for modeling imaging systems]( "A software platform for modeling imaging systems")
A software platform for modeling imaging systems40,99 €![Optimales Anforderungsmanagement im agilen Software Engineering aus Sicht des Product Owner]( "Optimales Anforderungsmanagement im agilen Software Engineering aus Sicht des Product Owner")
Optimales Anforderungsmanagement im agilen Software Engineering aus Sicht des Product Owner47,95 €
The difference between the conventional software engineering and software product line engineering is variant management. The main idea of software product line is to identify the common core functionality that can be implemented once and reused afterwards for all members of the product line. To facilitate this reuse opportunity the domain engineering phase makes the domain model comprising common as well as variant requirements. Common requirements are easy to handle. However, problem arises during handling the variants. Different variants have dependencies on each other. A single variant can affect several variants in the domain model. These problems become complex when the volume of information grows and there are a lot of variants with several interdependencies. A separate model is required to handle the variants. This book discusses an approach to modeling variants in a domain model. Deriving from the common requirements, the default domain models are drawn in UML. By using the variant model the required variants are then added to or deleted from the defaults for the specific system.