@inproceedings{JohnVillela, author = {John, Isabel and Villela, Karina}, title = {Evolutionary Product Line Scoping}, series = {Software Product Lines: Going Beyond (SPLC 2010)}, booktitle = {Software Product Lines: Going Beyond (SPLC 2010)}, editor = {Bosch, Jan and Lee, Jaejoon}, publisher = {Springer}, address = {Berlin, Heidelberg}, isbn = {978-3-642-15578-9}, doi = {10.1007/978-3-642-15579-6_57}, pages = {515 -- 516}, abstract = {Product Line Engineering has a widespread use in industry now. Therefore there is a high need for customizable, adaptable, and also for mature methods. Scoping is an integral part of Product Line Engineering. In this phase we determine where to reuse and what to reuse, establishing the basis for all technical, managerial, and investment decisions in the product line to come. In this tutorial we will give an introduction on how to analyze an environment with the purpose of planning a product line and its future evolution.}, language = {en} } @inproceedings{JohnSchwanningerAlmeida, author = {John, Isabel and Schwanninger, Christa and Almeida, Eduardo}, title = {The rise and fall of product line architectures}, series = {Software Product Lines: Going Beyond (SPLC 2010)}, booktitle = {Software Product Lines: Going Beyond (SPLC 2010)}, editor = {Bosch, Jan and Lee, Jaejoon}, publisher = {Springer}, address = {Berlin, Heidelberg}, isbn = {978-3-642-15578-9}, doi = {10.1007/978-3-642-15579-6_49}, pages = {500 -- 501}, abstract = {This panel addresses questions around architecture like: How do you think a good product line architecture should look like? How much up-front design do we need for a product line architecture? What are hot research topics in product line architecture? The panel is organized as a goldfish bowl, where the panelists are in the middle of the audience and panelists change during the panel.}, language = {en} } @inproceedings{BlaesiusGrawemeyerJohnetal., author = {Bl{\"a}sius, Karl-Hans and Grawemeyer, Beate and John, Isabel and Kuhn, Norbert}, title = {Knowledge-based document analysis}, series = {Proceedings of the Fourth International Conference on Document Analysis and Recognition}, volume = {2}, booktitle = {Proceedings of the Fourth International Conference on Document Analysis and Recognition}, publisher = {IEEE}, pages = {728 -- 731}, language = {en} } @inproceedings{VillelaDoerrJohn, author = {Villela, Karina and D{\"o}rr, J{\"o}rg and John, Isabel}, title = {Evaluation of a Method for Proactively Managing the Evolving Scope of a Software Product Line}, series = {Requirements Engineering: Foundation for Software Quality (REFSQ 2010)}, booktitle = {Requirements Engineering: Foundation for Software Quality (REFSQ 2010)}, publisher = {Springer}, address = {Berlin, Heidelberg}, isbn = {978-3-642-14191-1}, doi = {10.1007/978-3-642-14192-8_13}, abstract = {[Context and motivation]PLEvo-Scoping is a method intended to help Product Line (PL) scoping teams anticipate emergent features and distinguish unstable from stable features, with the aim of preparing their PL for likely future adaptation needs. [Question/problem]This paper describes a quasi-experiment performed to characterize PLEvo-Scoping in terms of adequacy and feasibility. [Principal ideas/results] This quasi-experiment was performed by two scoping teams in charge of scoping the same PL, where one scoping team applied first an existing PL scoping approach and then PLEvo-Scoping, while the other scoping team interweaved activities from both. The two approaches achieved similar results: The method could be applied in just one day, and it was considered adequate and feasible. [Contribution] Ideas on how to improve the method and its tool support have been obtained, and similar results are expected from other professionals facing the problem of evolution-centered PL scoping. However, further empirical studies should be performed.}, language = {en} } @inproceedings{BeucheJohn, author = {Beuche, Danilo and John, Isabel}, title = {Managing requirements in product lines}, series = {International Conference on Software Product Lines (SPLC 2010)}, booktitle = {International Conference on Software Product Lines (SPLC 2010)}, publisher = {Springer}, address = {Berlin, Heidelberg}, isbn = {978-3-642-15578-9}, doi = {10.1007/978-3-642-15579-6_56}, pages = {513 -- 514}, abstract = {Any organizations develop software or software -intensive products, which are can be seen as variants or members of a product line. Often the market demands variability and the software organization expects productivity benefits from reuse. In any case, complexity of the software development increases. Requirements management plays a central role in this, when it comes to mastering the complexity. In this tutorial we will give an overview on how to analyze, build and manage common and variable requirements for a product line.}, language = {en} } @inproceedings{TschaitschianWenzelJohn, author = {Tschaitschian, B. and Wenzel, C. and John, Isabel}, title = {Tuning the quality of informal software requirements with KARAT}, series = {Proceedings of the Third International Workshop on Requirements Engineering: Foundations of Software Quality (REFSQ'97)}, booktitle = {Proceedings of the Third International Workshop on Requirements Engineering: Foundations of Software Quality (REFSQ'97)}, pages = {81 -- 92}, language = {en} } @inproceedings{JohnBassLami, author = {John, Isabel and Bass, L. and Lami, G.}, title = {Software product lines doctoral symposium}, series = {10th International Software Product Line Conference (SPLC'06)}, booktitle = {10th International Software Product Line Conference (SPLC'06)}, publisher = {IEEE}, doi = {10.1109/SPLINE.2006.1691613}, abstract = {The SPLC doctoral symposium provides a platform for young researchers to present their work to an international audience and discuss it with each other and with experts in the field. The symposium addresses research activities in the field of Software Product Lines Topics of Interest include all aspects of the development phases, management, evaluation, reuse, and maintenance of software product lines.}, language = {en} } @inproceedings{KolbJohnKnodeletal., author = {Kolb, Ronny and John, Isabel and Knodel, Jens and Muthig, Dirk and Haury, Uwe and Meier, Gerald}, title = {Experiences with product line development of embedded systems at testo AG}, series = {10th International Software Product Line Conference (SPLC'06)}, booktitle = {10th International Software Product Line Conference (SPLC'06)}, publisher = {IEEE}, doi = {10.1109/SPLINE.2006.1691589}, pages = {172 -- 181}, abstract = {Product line practices are increasingly becoming popular in the domain of embedded software systems. This paper presents results of assessing success, consistency, and quality of Testo's product line of climate and flue gas measurement devices after its construction and the delivery of three commercial products. The results of the assessment showed that the incremental introduction of architecture-centric product line development can be considered successful even though there is no quantifiable reduction of time-to-market as well as development and maintenance costs so far. The success is mainly shown by the ability of Testo to develop more complex products and the satisfaction of the involved developers. A major issue encountered is ensuring the quality of reusable components and the conformance of the products to the architecture during development and maintenance}, language = {en} } @inproceedings{GanesanJohnKnodel, author = {Ganesan, D. and John, Isabel and Knodel, Jens}, title = {Combining reverse engineering techniques for product lines}, series = {2nd International Workshop on Program Comprehension through Dynamic Analysis, PCODA 2006}, booktitle = {2nd International Workshop on Program Comprehension through Dynamic Analysis, PCODA 2006}, abstract = {In a product line context, the migration strategy to exploit functionality embodied in existing components having a high reuse potential can be fourfold: reuse as is, reuse and adapt, recover and reconstruct, or (re-)implement. This position paper focuses on the recover and reconstruct strategy and presents an integrated architecture reconstruction approach that aims at migrating core functionality, major variants and key features of existing systems into a product line infrastructure. We combine dynamic and static reverse engineering techniques within a systematic reconstruction approach, whereby one of the main goals is to be compliant to the product line architecture. In this paper, we present the reconstruction approach and illustrate the technique interactions techniques in a case study.}, language = {en} } @inproceedings{JohnKnodelLehneretal., author = {John, Isabel and Knodel, Jens and Lehner, Theresa and Muthig, Dirk}, title = {A practical guide to product line scoping}, series = {10th International Software Product Line Conference (SPLC'06)}, booktitle = {10th International Software Product Line Conference (SPLC'06)}, publisher = {IEEE}, doi = {10.1109/SPLINE.2006.1691572}, pages = {3 -- 12}, abstract = {Over the last years scoping has been established as the initial activity for starting product line engineering. To be successful in defining the right scope for more than 5 years in industrial projects, we always had to customize our generic scoping process to the organizational context, projects constraints, available artifacts, and resources. In this paper, we present an update of the scoping process that explicitly integrates 21 customization factors. In our experience customization of scoping is crucial to the overall product line success, since the scope is the basis for all further product line activities.}, language = {en} }