TY - CHAP A1 - Schubanz, Mathias A1 - Pleuss, Andreas A1 - Pradhan, Ligaj A1 - Botterweck, Goetz A1 - Thurimella, Anil Kumar ED - Gnesi, Stefania ED - Collet, Philippe ED - Schmid, Klaus T1 - Model-driven Planning and Monitoring of Long-term Software Product Line Evolution T2 - Proceedings of the Seventh International Workshop on Variability Modelling of Software-intensive Systemsm, Conference VaMoS 2013, Pisa , Italy — January 23 - 25, 2013 N2 - 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. KW - software product lines KW - software evolution KW - software maintenance KW - software release planning Y1 - 2013 SN - 978-1-4503-1541-8 U6 - https://doi.org/10.1145/2430502.2430527 PB - ACM CY - New York, NY ER - TY - CHAP A1 - Schubanz, Mathias A1 - Pleuss, Andreas A1 - Botterweck, Goetz A1 - Lewerentz, Claus ED - Eisenecker, Ulrich W. ED - Apel, Sven ED - Gnesi, Stefania T1 - Modeling Rationale over Time to support Product Line Evolution Planning T2 - Proceedings of the Sixth International Workshop on Variability Modeling of Software-Intensive Systems, Conference VaMoS 2012, Leipzig, Germany — January 25 - 27, 2012 N2 - 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. KW - software product lines KW - software evolution KW - software maintenance KW - rationale Y1 - 2012 SN - 978-1-4503-1058-1 U6 - https://doi.org/10.1145/2110147.2110169 SP - 193 EP - 199 PB - ACM CY - New York, NY ER - TY - CHAP A1 - Schubanz, Mathias A1 - Pleuss, Andreas A1 - Jordan, Howell A1 - Botterweck, Goetz T1 - Guidance for Design Rationale Capture to Support Software Evolution T2 - 6. Workshop "Design for Future'', 28. - 30. April 2014 in Bad Honnef N2 - 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. KW - design rationale KW - software erosion KW - decision making KW - question catalogue KW - literature review Y1 - 2014 UR - http://fg-sre.gi.de/fileadmin/gliederungen/fg-sre/wsre2014/wsre_dff_2014_proceedings.pdf UR - http://pi.informatik.uni-siegen.de/stt/34_2/index.html N1 - ISSN 0720-8928 SP - 60 EP - 61 PB - Gesellschaft für Informatik CY - Bonn ER - TY - GEN A1 - Thurimella, Anil Kumar A1 - Schubanz, Mathias A1 - Pleuss, Andreas A1 - Botterweck, Goetz T1 - Guidelines for Managing Requirements Rationales T2 - IEEE Software N2 - 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. KW - Stakeholders KW - Requirements engineering KW - Organizations KW - Software engineering KW - Systematics Y1 - 2017 UR - https://www.computer.org/csdl/mags/so/2017/01/mso2017010082-abs.html U6 - https://doi.org/10.1109/MS.2015.157 SN - 0740-7459 SN - 1937-4194 VL - 34 IS - 1 SP - 82 EP - 90 ER -