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