@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{Schubanz, author = {Schubanz, Mathias}, title = {Design Rationale Capture in Software Architecture: What has to be captured?}, series = {WCOP '14 Proceedings of the 19th international doctoral symposium on Components and architecture}, booktitle = {WCOP '14 Proceedings of the 19th international doctoral symposium on Components and architecture}, publisher = {ACM}, address = {New York, USA}, isbn = {978-1-4503-2593-6}, doi = {10.1145/2601328.2601329}, pages = {31 -- 36}, abstract = {More than thirty years of research on the topic of design rationale (DR) have passed. However, as of today there are just some exceptional cases where DR are applied in industrial practise. Researchers analysed them for its nature, its structure, its quality, and for analyses to be performed on them. The results showed that DR have the potential to sustainably contribute to the product life cycle in terms of product design, product re-design, product testing, maintenance, and product quality. Hence, this paper presents a proposal to tackle the lack DR usage in documenting software architectures. We strive to promote the use of DR for designing software architectures. Therefore, as a complement to the numerous approaches to formalise the representation of DR, this paper is proposing to pay more attention on research how to capture rationale. In short, within this paper we introduce the topic of DR, related research and elaborate on the intended research on the topic of DR capture.}, language = {en} } @inproceedings{Schubanz, author = {Schubanz, Mathias}, title = {Towards Enabling Design Rationale Capture by Asking the Right Questions}, series = {Informatik 2014, 44. Jahrestagung der Gesellschaft f{\"u}r Informatik, Big Data - Komplexit{\"a}t meistern, 22. - 26. September 2014 in Stuttgart, Deutschland, Doktorandenprogramm}, booktitle = {Informatik 2014, 44. Jahrestagung der Gesellschaft f{\"u}r Informatik, Big Data - Komplexit{\"a}t meistern, 22. - 26. September 2014 in Stuttgart, Deutschland, Doktorandenprogramm}, editor = {Pl{\"o}dereder, Erhard and Grunske, Lars and Schneider, Eric and Ull, Dominik}, publisher = {Gesellschaft f{\"u}r Informatik}, address = {Bonn}, isbn = {978-3-88579-626-8}, pages = {2257 -- 2268}, abstract = {Over the last thirty years many research has been conducted to capture the "how" and "why" behind design decisions. This information is known as design rationales (DR). Approaches to capture, store, preserve, and use DR have emerged from research activities. However, as of today they only found exceptional application within industrial practice. Rationales have been analysed in respect to its nature, its structure, and its quality. Additionally, some researchers performed analyses on them. They found out that DR have the potential to sustainably contribute to design, re-design, testing, maintenance, and improving product quality over the whole product-life cycle. Within this paper a research proposal is presented striving to tackle the exceptional use of DR in software documentation. We want to promote the capture of DR by paying more attention on the questions "What information has to be captured by rationales?", "How detailed should the captured information be?", and "How should rationale capture be integrated into the development process?". It is the goal to promote the use of DR within the whole software development process. In short, within this paper we introduce the topic of DR, related research and elaborate on the intended research on the topic of DR capture.}, 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{SchubanzLewerentz, author = {Schubanz, Mathias and Lewerentz, Claus}, title = {What Matters to Students - A Rationale Management Case Study in Agile Software Development}, series = {SEUH 2020: Software Engineering im Unterricht der Hochschulen : Tagungsband des 17. Workshops "Software Engineering im Unterricht der Hochschulen" 2020\$dInnsbruck, {\"O}sterreich, 26.-27.02.2020}, journal = {SEUH 2020: Software Engineering im Unterricht der Hochschulen : Tagungsband des 17. Workshops "Software Engineering im Unterricht der Hochschulen" 2020\$dInnsbruck, {\"O}sterreich, 26.-27.02.2020}, editor = {Krusche, Stephan and Wagner, Stefan}, publisher = {RWTH}, address = {Aachen}, pages = {17 -- 26}, abstract = {Documenting design decisions and their rationale (Design Rationale, DR) in software development projects is vital for supporting the comprehension of the product, product quality, and future maintenance. Although an increasing number of research publications address this topic, systematic approaches and supporting DR tools are found very rarely in practice. In software engineering education, DR is usually not well covered in teaching. The lack of suitable decision documentation is mainly an issue in agile software development. In agile approaches, documentation is regarded as less important than working products. To explore possibilities for integrating decision documentation into Scrum processes for educational software development projects, we conducted a series of eight case studies. These were part of software lab courses in three universities, i.e., BTU Cottbus, PUT Poznan, University of Stuttgart, with about 400 participants in 82 project teams. We introduced additional process elements in Scrum and developed a lightweight capture technique to support the decision capture. This paper describes the case study setup and corresponding implementation and, thus, an example approach of managing rationale in Scrum. Additionally, it presents a data analysis of the students' most relevant decisions documented throughout the case studies. We conclude the paper with a discussion on the observations we made during the case study executions and the applicability of the approach in educational software projects.}, language = {en} } @misc{Schubanz, author = {Schubanz, Mathias}, title = {Custom-MADE - Leveraging Agile Rationale Management by Employing Domain-Specific Languages}, series = {13th ZEUS Workshop, ZEUS 2021, Bamberg - European Workshop on Services and their Composition, 25-26 February 2021, online}, volume = {2021}, journal = {13th ZEUS Workshop, ZEUS 2021, Bamberg - European Workshop on Services and their Composition, 25-26 February 2021, online}, editor = {Manner, Johannes and Haarmann, Stephan and Kolb, Stefan and Herzberg, Nico and Kopp, Oliver}, issn = {1613-0073}, url = {http://nbn-resolving.de/nbn:de:0074-2839-5}, pages = {34 -- 41}, abstract = {Managing rationale in software development projects can be a cumbersome task with a potentially low return on investment. Especially in the agile context, documentation is therefore very unpopular. Research has not yet properly addressed an agile documentation workflow. In this paper, the author presents an integrated approach to agile rationale management based on a highly-flexible modelling approach using domainspecific languages. It facilitates the complete documentation workflow from capture to reuse, partially automates it and offers various customisation opportunities, making it applicable to agile methods.}, 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} }