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 - 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 -