Software Product Line – Advanced Topic
I have published a chapter with other colleagues about handling variability and traceability over SPL disciplines in the following book. It is free for downloading. Enjoy it! 
Software Product Line – Advanced Topic
The Software Product Line (SPL) is an emerging methodology for developing software products. Currently, there are two hot issues in the SPL: modelling and the analysis of the SPL. Variability modelling techniques have been developed to assist engineers in dealing with the complications of variability management. The principal goal of modelling variability techniques is to configure a successful software product by managing variability in domain-engineering. In other words, a good method for modelling variability is a prerequisite for a successful SPL. On the other hand, analysis of the SPL aids the extraction of useful information from the SPL and provides a control and planning strategy mechanism for engineers or experts. In addition, the analysis of the SPL provides a clear view for users. Moreover, it ensures the accuracy of the SPL. This book presents new techniques for modelling and new methods for SPL analysis.
Software maintenance and evolution are characterised by their huge cost and slow speed of implementation. Yet they are inevitable activities ? almost all software that is useful and successful stimulates user-generated requests for change and improvements. A set of studies has stated along the years that software maintenance and evolution is the most expensive phase of software development, taking up to 90% of the total costs. All those characteristics from software maintenance lead the academia and industry to constantly investigate new solutions to reduce costs in such phase. In this context, Software Configuration Management (SCM) is a set of activities and standards for managing and evolving software. For all these activities it has been proposed different tools, such as version control systems and bug trackers. However, some issues may arise due to these tools usage, such as the dynamic assignment of a developer to a bug report or the bug report duplication problem. In this sense, this work investigates the problem of bug report duplication emerged by the use of bug trackers on software development projects.