TY - CHAP A1 - John, Isabel A1 - Villela, Karina ED - Bosch, Jan ED - Lee, Jaejoon T1 - Evolutionary Product Line Scoping T2 - Software Product Lines: Going Beyond (SPLC 2010) N2 - 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. Y1 - 2010 SN - 978-3-642-15578-9 SN - 978-3-642-15579-6 U6 - https://doi.org/10.1007/978-3-642-15579-6_57 SP - 515 EP - 516 PB - Springer CY - Berlin, Heidelberg ER - TY - CHAP A1 - John, Isabel A1 - Schwanninger, Christa A1 - Almeida, Eduardo ED - Bosch, Jan ED - Lee, Jaejoon T1 - The rise and fall of product line architectures T2 - Software Product Lines: Going Beyond (SPLC 2010) N2 - 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. Y1 - 2010 SN - 978-3-642-15578-9 SN - 978-3-642-15579-6 U6 - https://doi.org/10.1007/978-3-642-15579-6_49 SP - 500 EP - 501 PB - Springer CY - Berlin, Heidelberg ER - TY - CHAP A1 - Bläsius, Karl-Hans A1 - Grawemeyer, Beate A1 - John, Isabel A1 - Kuhn, Norbert T1 - Knowledge-based document analysis T2 - Proceedings of the Fourth International Conference on Document Analysis and Recognition Y1 - 1997 VL - 2 SP - 728 EP - 731 PB - IEEE ER - TY - CHAP A1 - Villela, Karina A1 - Dörr, Jörg A1 - John, Isabel T1 - Evaluation of a Method for Proactively Managing the Evolving Scope of a Software Product Line T2 - Requirements Engineering: Foundation for Software Quality (REFSQ 2010) N2 - [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. T3 - Lecture Notes in Computer Science - 6182 Y1 - 2010 SN - 978-3-642-14191-1 SN - 978-3-642-14192-8 U6 - https://doi.org/10.1007/978-3-642-14192-8_13 PB - Springer CY - Berlin, Heidelberg ER - TY - CHAP A1 - Beuche, Danilo A1 - John, Isabel T1 - Managing requirements in product lines T2 - International Conference on Software Product Lines (SPLC 2010) N2 - 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. Y1 - 2010 SN - 978-3-642-15578-9 SN - 978-3-642-15579-6 U6 - https://doi.org/10.1007/978-3-642-15579-6_56 SP - 513 EP - 514 PB - Springer CY - Berlin, Heidelberg ER - TY - CHAP A1 - Tschaitschian, B. A1 - Wenzel, C. A1 - John, Isabel T1 - Tuning the quality of informal software requirements with KARAT T2 - Proceedings of the Third International Workshop on Requirements Engineering: Foundations of Software Quality (REFSQ’97) Y1 - 1997 SP - 81 EP - 92 ER - TY - CHAP A1 - John, Isabel A1 - Bass, L. A1 - Lami, G. T1 - Software product lines doctoral symposium T2 - 10th International Software Product Line Conference (SPLC'06) N2 - 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. Y1 - 2006 U6 - https://doi.org/10.1109/SPLINE.2006.1691613 PB - IEEE ER - TY - CHAP A1 - Kolb, Ronny A1 - John, Isabel A1 - Knodel, Jens A1 - Muthig, Dirk A1 - Haury, Uwe A1 - Meier, Gerald T1 - Experiences with product line development of embedded systems at testo AG T2 - 10th International Software Product Line Conference (SPLC'06) N2 - 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 KW - Embedded system KW - System testing KW - Software testing KW - Costs KW - Investments KW - Business KW - Temperature measurement KW - Software engineering KW - Embedded software KW - Flue gases KW - Production Line KW - Testo AG KW - Product Line Development KW - Components Of Quality KW - Quality Assurance KW - Product Development KW - Source Code KW - Model Architecture KW - Development Efforts KW - Layering KW - Component Of Development KW - Reverse Engineering KW - Unified Modeling Language KW - Phases Of Life Cycle KW - Software Product KW - Development Of Architecture KW - Quality Of Implementation KW - Components Of The Framework KW - Production Team KW - Exclamation Mark KW - Reference Architecture KW - Quality Assurance Activities KW - Clone Detection KW - View Of Architecture KW - Partial Products KW - Software Architecture Y1 - 2006 U6 - https://doi.org/10.1109/SPLINE.2006.1691589 SP - 172 EP - 181 PB - IEEE ER - TY - CHAP A1 - Ganesan, D. A1 - John, Isabel A1 - Knodel, Jens T1 - Combining reverse engineering techniques for product lines T2 - 2nd International Workshop on Program Comprehension through Dynamic Analysis, PCODA 2006 N2 - 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. Y1 - 2006 ER - TY - CHAP A1 - John, Isabel A1 - Knodel, Jens A1 - Lehner, Theresa A1 - Muthig, Dirk T1 - A practical guide to product line scoping T2 - 10th International Software Product Line Conference (SPLC'06) N2 - 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. KW - Software engineering KW - Engineering management KW - Knowledge engineering KW - Trademarks KW - Application software KW - Product development KW - Packaging KW - Computer industry KW - Industrial relations KW - Productivity KW - Scoping KW - Production Line KW - Organizational Constraints KW - Measurement Data KW - Model Quality KW - Product Characteristics KW - Economic Model KW - User Manual KW - High-level Features KW - Domain Features KW - Domain Experts KW - Software Engineering KW - Activity Goals KW - Technical Staff KW - Software Product KW - Product Description KW - Output Of Step KW - Market Knowledge KW - Technical Components KW - Goal Of Phase KW - Potential Reuse Y1 - 2006 U6 - https://doi.org/10.1109/SPLINE.2006.1691572 SP - 3 EP - 12 PB - IEEE ER -