Miguel Goulão

Feature Models are commonly used to specify commonalities and variabilities in Software Product Lines (SPL). Our goal is to enhance feature modeling with traceability and improved support for crosscutting concerns. While traceability will show the features’ requirement-origins, providing means to reason about
their existence, crosscutting concerns will be handled through advanced modularity mechanisms (e.g. aspects), making the impact of changes to SPL models less difficult to understand and analyze. The result is Theme/SPL, a novel SPL requirements technique based on a concern-driven approach (Theme/Doc). Theme/SPL includes the proposal of a domain-specific language for specifying Theme/Doc models and uses model-driven development to generate automatically feature models from them. We show the applicability of the technique through a case study using a within-group design to evaluate the final results and tools developed.

There are several tools currently available in the i * community. These tools have different features and purposes. Choosing the most adequate tool for a specific modelling situation can be a challenge. To overcome this diffculty, we present a systematic comparison of the i * tools listed in the i * wiki page, according to their features, syntax coverage and semantic analysis support. Our comparison highlights the
different strengths of those tools, to help identifying situations for which each tool might be particularly useful. We contribute with an aggregated vision of current i * tool support to the body of knowledge of the i * community. In addition, this comparison also helps identifying opportunities for further evolution of the surveyed tools.