@inproceedings{SchubanzPleussPradhanetal., author = {Schubanz, Mathias and Pleuss, Andreas and Pradhan, Ligaj and Botterweck, Goetz and Thurimella, Anil Kumar}, title = {Model-driven Planning and Monitoring of Long-term Software Product Line Evolution}, series = {Proceedings of the Seventh International Workshop on Variability Modelling of Software-intensive Systemsm, Conference VaMoS 2013, Pisa , Italy — January 23 - 25, 2013}, booktitle = {Proceedings of the Seventh International Workshop on Variability Modelling of Software-intensive Systemsm, Conference VaMoS 2013, Pisa , Italy — January 23 - 25, 2013}, editor = {Gnesi, Stefania and Collet, Philippe and Schmid, Klaus}, publisher = {ACM}, address = {New York, NY}, isbn = {978-1-4503-1541-8}, doi = {10.1145/2430502.2430527}, abstract = {In order to increase the level of efficiency and automation, we propose a conceptual model and corresponding tool support to plan and manage the systematic evolution of softwareintensive systems, in particular software product lines (SPL). We support planning on a high abstraction level using decision-making concepts like goals, options, criteria, and rationale. We extend earlier work by broadening the scope in two dimensions: 1) in time, supporting continuous planning over long periods of time and many releases, and 2) in space, supporting traces from high-level decisions down to the implementation. We present a metamodel which allows to represent these concepts, corresponding prototypical tool support, and a first example case using data extracted from an open-source project, Eclipse SWT.}, language = {en} } @inproceedings{SchubanzPleussBotterwecketal., author = {Schubanz, Mathias and Pleuss, Andreas and Botterweck, Goetz and Lewerentz, Claus}, title = {Modeling Rationale over Time to support Product Line Evolution Planning}, series = {Proceedings of the Sixth International Workshop on Variability Modeling of Software-Intensive Systems, Conference VaMoS 2012, Leipzig, Germany — January 25 - 27, 2012}, booktitle = {Proceedings of the Sixth International Workshop on Variability Modeling of Software-Intensive Systems, Conference VaMoS 2012, Leipzig, Germany — January 25 - 27, 2012}, editor = {Eisenecker, Ulrich W. and Apel, Sven and Gnesi, Stefania}, publisher = {ACM}, address = {New York, NY}, isbn = {978-1-4503-1058-1}, doi = {10.1145/2110147.2110169}, pages = {193 -- 199}, abstract = {Software Product Lines are a strategic long-term investment and must evolve to meet new requirements over many years. In previous work, we have shown a model-driven approach (called EvoPL [21]) for planning and managing long-term evolution of product lines. It allows specifying historic and planned future evolution in terms of changes on feature model level. It provides benefits like abstraction, efficiency through automation, and the capability to perform analysis based on models. In this paper, we argue that specifying changes alone is beneficial but not sufficient. This is because for strategic evolution planning "decision drivers" like goals, requirements, and rationale are essential information as well. Hence, we propose a modeling approach that represents such decision drivers and their interrelationships. The approach is based on concepts from literature (e.g., QOC and goal-oriented requirements engineering) and combines and extends them to address the specific needs of model-driven long-term evolution management. Beyond the basic usage for documentation, the suggested models can be used for systematic future planning and tool-supported analysis, e.g., to evaluate the consistency of planned evolutionary changes.}, language = {en} } @inproceedings{SchubanzPleussJordanetal., author = {Schubanz, Mathias and Pleuss, Andreas and Jordan, Howell and Botterweck, Goetz}, title = {Guidance for Design Rationale Capture to Support Software Evolution}, series = {6. Workshop "Design for Future'', 28. - 30. April 2014 in Bad Honnef}, booktitle = {6. Workshop "Design for Future'', 28. - 30. April 2014 in Bad Honnef}, publisher = {Gesellschaft f{\"u}r Informatik}, address = {Bonn}, pages = {60 -- 61}, abstract = {Documenting design rationale (DR) helps to preserve knowledge over long time to diminish software erosion and to ease maintenance and refactoring. However, use of DR in practice is still limited. One reason for this is the lack of concrete guidance for capturing DR. This paper provides a first step towards identifying DR questions that can guide DR capturing and discusses required future research.}, language = {en} } @misc{ThurimellaSchubanzPleussetal., author = {Thurimella, Anil Kumar and Schubanz, Mathias and Pleuss, Andreas and Botterweck, Goetz}, title = {Guidelines for Managing Requirements Rationales}, series = {IEEE Software}, volume = {34}, journal = {IEEE Software}, number = {1}, issn = {0740-7459}, doi = {10.1109/MS.2015.157}, pages = {82 -- 90}, abstract = {Requirements are identified and elaborated on the basis of stakeholders' decisions. The reasoning behind those decisions can be expressed as rationales. Systematic rationale management offers both short-term benefits, such as clearer requirements leading to fewer defects, and long-term benefits, such as simplified requirements evolution. However, little guidance exists for managing requirements rationales. This article presents guidelines to pragmatically capture, trace, maintain, and reuse such rationales. A list of questions augments the guidelines, improving their usability.}, language = {en} }