% % This file was created by the Typo3 extension % sevenpack version 0.7.16 % % --- Timezone: CEST % Creation date: 2013-06-20 % Creation time: 11-58-48 % --- Number of references % 152 % @Article { SchmidEichelbergerKroeher12, title = {{Domain-Oriented Customization of Service Platforms: Combining Product Line Engineering and Service-Oriented Computing}}, journal = {{Journal of Universal Computer Science (JUCS)}}, year = {2013}, abstract = {Service-Oriented Computing (SoC) has been established as an important paradigm over the last decade. A particularly important part in a service-oriented solution is the service-oriented platform. This provides an environment and infrastructure for a number of service-oriented applications. An important challenge in complex application areas is the need to customize these platforms to the demands of a specific context. Product line technologies can support this by providing the concept of variability management to SoC. In this paper, we will provide a reference model for (domain-specific) service platforms and describe different approaches that provide customization possibilities in a service platform context. The complexity of handling the customization of large-scale service platforms in an integrated manner will be addressed by introducing the concept of production strategies for variability implementation techniques.}, tags = {SSE_SCHMID SSE_EICHELBERGER SSE_KROEHER SSE_INDENICA}, state = {accepted}, author = {Schmid, Klaus and Eichelberger, Holger and Kr{\"o}her, Christian} } @Inproceedings { SchmidKoschkeKroeher+13, title = {Towards identifying evolution smells in Software Product Lines}, year = {2013}, abstract = {As more and more companies shift to a product line approach, supporting the evolution of software product lines becomes increasingly important. While today already significant work exists along the lines of quality analysis for software product lines, there is much less work that addresses the evolution scenario. In this paper, we briefly describe different categories of approaches for identifying problems in product lines. Based on this we describe a new research direction for identifying problems in product line evolution scenarios.}, tags = {SSE_SCHMID SSE_KROEHER SSE_EVOLINE}, editor = {Stefan Sauer and Benjamin Klatt and Thomas Ruhroth}, publisher = {Gesellschaft f{\"u}r Informatik e.V. (GI)}, booktitle = {Proceedings of the 5th Workshop ''Design For Future - Langlebige Softwaresysteme'' (DFF)}, author = {Schmid, Klaus and Koschke, Rainer and Kr{\"o}her, Christian and L{\"u}demann, Dierk} } @Inproceedings { EichelbergerSchmid13, title = {{A Systematic Analysis of Textual Variability Modeling Languages}}, year = {2013}, tags = {SSE_EICHELBERGER SSE_SCHMID SSE_INDENICA}, booktitle = {{17th International Software Product Line Conference (SPLC '13)}}, state = {accepted}, author = {Eichelberger, Holger and Schmid, Klaus} } @Inproceedings { EichelbergerKroeherSchmid13, title = {{An Analysis of Variability Modeling Concepts: Expressiveness vs. Analyzability}}, year = {2013}, abstract = {Variability modeling is a core activity of software product line engi-neering. Over the years, many different approaches to variability modeling have been proposed. Typically, the individual approaches have been designed with-out a detailed justification on why certain modeling concepts should be used. This yields a rather unfunded selection of modeling approaches in practice, e.g., selecting approaches that provide higher modeling concepts than actually need-ed, but less analyses capabilities than required. Thus, we propose that the focus of an analysis should not be to determine the best modeling language, but rather to provide a characterization on when to use what kind of approach. In particu-lar, the selection of one approach for a specific situation should be driven from the required modeling concepts (expressiveness) and the required analyzability. In this paper, we propose a classification of core concepts of variability model-ing based on expressiveness and analyzability. We discuss the methodology for and the classification of variability modeling concepts illustrated by a running example. The contribution of this paper is a modeling approach-independent classification of variability modeling concepts and their dependencies to pro-vide a systematic and rationale basis to anyone designing, standardizing, im-plementing or selecting a specific variability modeling approach.}, tags = {SSE_EICHELBERGER SSE_KROEHER SSE_SCHMID SSE_INDENICA}, booktitle = {{Proceeding of the 13th International Conference on Software Reuse (ICSR '13)}}, state = {accepted}, author = {Eichelberger, Holger and Kr{\"o}her, Christian and Schmid, Klaus} } @Inproceedings { BrummermannKeuneckeSchmid13, title = {Managing the Evolution and Customization of Database Schemas in Information System Ecosystems}, year = {2013}, abstract = {We present an approach that supports the customization and evolution of a database schema in a software ecosystem context. The approach allows for the creation of customized database schemas according to selected, supported feature packs and can be used in an ecosystem context, where third-party providers and customers augment the system with their own capabilities. The creation of the final database schema is automatic and also the relevant updates of individual feature packs can be automatically handled by the system.}, tags = {SSE_BRUMMERMANN SSE_KEUNECKE SSE_SCHMID}, booktitle = {Proceedings of the 25th International Conference on Advanced Information Systems Engineering (CAISE '13)}, state = {accepted}, author = {Brummermann, Hendrik and Keunecke, Markus and Schmid, Klaus} } @Techreport { Schmid13a, title = {Technical Debt - From Metaphor to Engineering Guidance: A Novel Approach based on Cost Estimation}, year = {2013}, pages = {31}, abstract = {In this report, we discuss the notion of Technical Debt and formalize the concept as a basis of disciplined study. This formalization allows us to characterize and measure Technical Debt independent of its source. We will then introduce approximations to measuring Technical Debt that can be more easily applied in practice. As a result we arrive at a method for deciding on tackling Technical Debt, which relies on a formal approach, with clearly identified approximations. We will also illustrate our approach with an example.}, keywords = {Technical Debt, Formal Model, Cost Model, Optimization Approach Iterative Development, Evolution, Software Architecture}, tags = {SSE_SCHMID}, url = {media/fb4/informatik/AG_SSE/PDFs/publications/Schmid13a.pdf}, institute = {Institute of Computer Science}, organization = {University of Hildesheim}, institution = {Institut f{\"u}r Informatik, Universit{\"a}t Hildesheim, Germany}, author = {Schmid, Klaus} } @Inproceedings { SchmidRummler12, title = {Cloud-based Software Product Lines}, year = {2012}, volume = {2}, abstract = {The traditional focus of Product Line Engineering (PLE) is on the customization of whole software solutions. So far, the combination of cloud computing with PLE techniques has hardly been discussed. In this paper, we discuss different approaches to cloud computing and their relation to product line technologies. We also describe both, specific opportunities and drawbacks, of these approaches. We also provide a discussion of different combinations of these approaches as a way to combine their strengths.}, tags = {SSE_SCHMID SSE_INDENICA}, editor = {Eduardo Santana de Almeida and Christa Schwanninger and David Benavides}, publisher = {ACM}, booktitle = {Proceedings of the 2nd International Workshop on Services, Clouds, and Alternative Design Strategies for Variant-Rich Software Systems (SCArVeS 2012) at the 16th International Software Product Line Conference (SPLC '12)}, DOI = {10.1145/2364412.2364440}, author = {Schmid, Klaus and Rummler, Andreas} } @Inproceedings { TischerBossMueller+12, title = {Developing Long-Term Stable Product Line Architectures}, year = {2012}, volume = {1}, pages = {86-95}, abstract = {Product lines are usually built for the long term in order to repay the initial investment. While long-term stable software systems are already hard, if they are developed individually, it is even harder for complete product lines. At the time a new product line is created, the details of future product line characteristics are typically not known, no matter how well and detailed scoping and planning is done. Thus, any product line needs to evolve and adapt over time to incorporate new customer requirements as well as new technology constraints. Stability of the product line architecture is very important to the successful long-term evolution of a product line. In this paper, we discuss how a form of domain decomposition, which we call conceptual architecture, can be used to guide product line engineering towards long-term viability. We will illustrate this approach in the context of a large-scale product line development and analyze the evolution properties of the product line. Transferability of the approach is suggested to other embedded software systems that drive mature, well-understood physical control system.}, tags = {SSE_SCHMID}, editor = {Eduardo Santana de Almeida and Christa Schwanninger and David Benavides}, publisher = {ACM}, booktitle = {Proceedings of the 16th International Software Product Line Conference (SPLC '12)}, DOI = {10.1145/2362536.2362551}, author = {Tischer, Christian and Boss, Birgit and M{\"u}ller, Andreas and Thums, Andreas and Acharya, Rajneesh and Schmid, Klaus} } @Inproceedings { BrummermannKeuneckeSchmid12, title = {Formalizing Distributed Evolution of Variability in Information System Ecosystems}, year = {2012}, pages = {11-19}, abstract = {The open variability of software product line ecosystems allows customers and third party organizations to create extensions to a system which may refine the variability model. In this paper we will describe an approach to evolution support, which was developed in the context of one specific company, HIS GmbH. However, the approach is much more generic than this. In particular, it is based on the formalization of modifications to configuration values and constraints on both the model and the data in the context of the evolution of multi-level configurations. Our approach supports the identification of inconsistencies in evolution.}, tags = {SSE_BRUMMERMANN SSE_KEUNECKE SSE_SCHMID}, editor = {Ulrich W. Eisenecker and Sven Apel and Stefania Gnesi}, publisher = {ACM}, booktitle = {Proceedings of the 6th Workshop on Variability Modeling of Software-Intensive Systems (VaMoS '12)}, DOI = {10.1145/2110147.2110149}, author = {Brummermann, Hendrik and Keunecke, Markus and Schmid, Klaus} } @Inproceedings { CzarneckiGruenbacherRabiser+12, title = {Cool Features and Tough Decisions: A Comparison of Variability Modeling Approaches}, year = {2012}, pages = {173-182}, abstract = {Variability modeling is essential for defining and managing the commonalities and variabilities in software product lines. Numerous variability modeling approaches exist today to support domain and application engineering activities. Most are based on feature modeling (FM) or decision modeling (DM) but so far no systematic comparison exists between these two major classes of approaches. Over the last two decades many new features have been added to both FM and DM and it is a tough decision which approach to use for what purpose. This paper clarifies the relation between FM and DM. We aim to systematize the research field of variability modeling and to explore potential synergies. We compare multiple aspects of FM and DM ranging from historical origins and rationale, through syntactic and semantic richness, to tool support, identifying commonalities and differences. We hope that this effort will improve the understanding of the range of approaches to variability modeling by discussing the possible variations. This will provide insights to users considering adopting variability modeling in practice and to designers of new languages, such as the new OMG Common Variability Language.}, tags = {SSE_SCHMID SSE_INDENICA}, editor = {Ulrich W. Eisenecker and Sven Apel and Stefania Gnesi}, publisher = {ACM}, booktitle = {Proceedings of the 6th International Workshop on Variability Modelling of Software-Intensive Systems (VaMoS '12)}, ISBN = {978-1-4503-1058-1}, DOI = {10.1145/2110147.2110167}, author = {Czarnecki, Krzysztof and Gr{\"u}nbacher, Paul and Rabiser, Rick and Schmid, Klaus and Wasowski, Andrzej} } @Inproceedings { EichelbergerSchmid12, title = {Erhebung von Produkt-Laufzeit-Metriken: Ein Vergleich mit dem SPASS-Meter-Werkzeug}, year = {2012}, pages = {171-180}, abstract = {Die Erfassung von Produktmetriken zur Laufzeit ist ein wesentlicher Baustein einer Qualit{\"a}tsstrategie in der Produktentwicklung. Die Erfassung von Produktmetriken in der Entwicklung ist jedoch oft mit signifikantem Aufwand verbunden, da viele Werkzeuge nur bestimmte Eigenschaften erfassen k{\"o}nnen und ihre Verwendung oft sehr komplex ist. Dar{\"u}ber hinaus entsteht durch die Durchf{\"u}hrung der Messung meist ein signifikanter Laufzeit-Overhead. Das Ziel des SPASS-meter-Werkzeugs ist die integrierte Erfassung einer Vielzahl von Metriken bei einfacher Konfiguration und geringem Laufzeit-Overhead. In diesem Beitrag stellen wir SPASS-meter vor und vergleichen es mit bekannten {\"a}hnlichen Werkzeugen wie Kieker, OpenCore, Xprof und HPROF. Eine {\"U}bersicht der St{\"a}rken und Schw{\"a}chen schlie{\ss}t den Vergleich ab.}, tags = {SSE_EICHELBERGER SSE_SCHMID SSE_SPASSMETER}, editor = {G. B{\"u}ren and R. R. Dumke and C. Ebert and H. M{\"u}nch}, publisher = {Shaker Verlag}, booktitle = {Proceedings of the DASMA Metrik Kongress (MetriKon '12)}, author = {Eichelberger, Holger and Schmid, Klaus} } @Inproceedings { EichelbergerKroeherSchmid12, title = {Variability in Service-Oriented Systems: An Analysis of Existing Approaches}, year = {2012}, pages = {516-524}, abstract = {In service-oriented systems services can be easily reused and shared without modification. However, there are business situations where a variation of services is needed to meet the requirements of a specific customer or context. Variation of software systems has been well researched in product line engineering in terms of Variability Implementation Techniques (VITs). While most VITs focus on the customization of traditional software systems, several VITs have been developed for service-oriented systems. In this paper, we discuss the problem of service customization and provide an overview of different VITs for service variability. For this purpose, we will define four dimensions to describe, characterize and analyze existing VITs: the technical core idea, the object of variation, the forms of variation, and the binding time.}, tags = {SSE_SCHMID SSE_EICHELBERGER SSE_KROEHER SSE_INDENICA}, editor = {Chengfei Liu and Heiko Ludwig and Farouk Toumani and Qi Yu}, publisher = {Springer}, booktitle = {Proceedings of the 10th International Conference on Service Oriented Computing (ICSOC '12)}, author = {Eichelberger, Holger and Kr{\"o}her, Christian and Schmid, Klaus} } @Inproceedings { El-SharkawyDederichsSchmid12, title = {From Feature Models to Decision Models and Back Again: An Analysis Based on Formal Transformations}, year = {2012}, volume = {1}, pages = {126-135}, abstract = {In Software Product Line Engineering, variability modeling plays a crucial rule. Over the years, a couple of different modeling paradigms with a plethora of different approaches have been proposed. However, only little attention was spend to compare these concepts. In this paper, we compare the capabilities and expressiveness of basic feature modeling with basic decision modeling. In this paper, we also present a formalization of basic decision modeling and show that in combination with a powerful constraint language both approaches are equivalent, while in their very basic forms they are not equivalent. These results can be used to transfer existing research results between the two paradigms.}, tags = {SSE_ELSHARKAWY SSE_SCHMID SSE_INDENICA}, editor = {Eduardo Santana de Almeida and Christa Schwanninger and David Benavides}, publisher = {ACM}, booktitle = {Proceedings of the 16th International Software Product Line Conference (SPLC '12)}, DOI = {10.1145/2362536.2362555}, author = {El-Sharkawy, Sascha and Dederichs, Stephan and Schmid, Klaus} } @Inproceedings { El-SharkawySchmid12, title = {Supporting the Effective Configuration of Software Product Lines}, year = {2012}, volume = {2}, pages = {119-126}, abstract = {Most research in product line engineering focuses on the domain engineering phase. However, the ultimate reason of any Software Product Line Engineering (SPLE) activity is the derivation of products and thus application engineering. In this research we focus on how the configuration activity within application engineering can be supported to achieve sufficient efficiency. We aim to provide a broad overview of the potential research landscape where we also discuss the actual coverage of the field by research work. As a result, we do not only provide an overview of the field, but do also describe several potential research approaches that have so far received very little attention.}, tags = {SSE_ELSHARKAWY SSE_SCHMID SSE_INDENICA}, editor = {Eduardo Santana de Almeida and Christa Schwanninger and David Benavides}, publisher = {ACM}, booktitle = {Proceedings of the 4th International Workshop on Model-driven Approaches in Software Product Line Engineering (MAPLE '12) at the 16th International Software Product Line Conference (SPLC '12)}, DOI = {10.1145/2364412.2364432}, author = {El-Sharkawy, Sascha and Schmid, Klaus} } @Article { SchmidEl-Sharkawy11, title = {Kreativit{\"a}t in der Anforderungsgewinnung: ein Experiment}, journal = {Softwaretechnik-Trends}, year = {2011}, volume = {31}, number = {1}, abstract = {Im modernen Requirements Engineering werden Anforderungen nicht nur erfasst, sondern gestaltet. Entsprechend ist Innovation in der Anforderungsgewinnung eine wichtige Aufgabe, die entscheidenden Einfluss auf den Produkterfolg hat. Doch k{\"o}nnen innovative Ideen systematisch entwickelt werden? Fr{\"u}here Fallstudien zeigten bereits, dass dies m{\"o}glich ist. In diesem Beitrag zeigen wir, dass der kreative Nutzen einzelner Techniken mit empirischen Methoden systematisch analysiert und belegt werden kann.}, tags = {SSE_SCHMID SSE_ELSHARKAWY}, author = {Schmid, Klaus and El-Sharkawy, Sascha} } @Inproceedings { SchmidRabiserGruenbacher11, title = {A Comparison of Decision Modeling Approaches in Product Lines}, year = {2011}, pages = {119-126}, abstract = {It has been shown that product line engineering can significantly improve the productivity, quality and time-to-market of software development by leveraging extensive reuse. Variability models are currently the most advanced approach to define, document and manage the commonalities and variabilities of reusable artifacts such as software components, requirements, test cases, etc. These models provide the basis for automating the derivation of new products and are thus the key artifact to leverage the flexibility and adaptability of systems in a product line. Among the existing approaches to variability modeling feature modeling and decision modeling have gained most importance. A significant amount of research exists on comparing and analyzing different feature modeling approaches. However, despite their significant role in product line research and practical applications, only little effort has been devoted to compare and analyze decision modeling approaches. In order to address this shortcoming and to provide a basis for more structured research on decision modeling in the future, we present a comparative analysis of representative approaches. We identify their major modeling concepts and present an analysis of their commonalities and variabilities.}, tags = {SSE_SCHMID}, editor = {Patrick Heymans and Krzysztof Czarnecki and Ulrich W. Eisenecker}, publisher = {ACM}, booktitle = {Proceedings of the 5th International Workshop on Variability Modeling of Software-intensive Systems (VaMoS '11)}, DOI = {10.1145/1944892.1944907}, author = {Schmid, Klaus and Rabiser, Rick and Paul Gr{\"u}nbacher, Paul} } @Inproceedings { BrummermannKeuneckeSchmid11, title = {Variability Issues in the Evolution of Information System Ecosystems}, year = {2011}, pages = {159-164}, abstract = {In a software ecosystem with open variability customers create their own products based on a reuse infrastructure provided by a development company. While an open approach has many benefits, it brings along a number of specific issues, especially related to evolution. In this problem statement we discuss some of the issues that arise in merging local variabilities with evolved versions of the reuse infrastructure of the development organization. In our discussion we focus on information systems, inspired by the situation of a specific company.}, tags = {SSE_BRUMMERMANN SSE_KEUNECKE SSE_SCHMID}, editor = {Patrick Heymans and Krzysztof Czarnecki and Ulrich W. Eisenecker}, publisher = {ACM}, booktitle = {Proceedings of the 5th Workshop on Variability Modeling of Software-Intensive Systems (VaMoS '11)}, DOI = {10.1145/1944892.1944912}, author = {Brummermann, Hendrik and Keunecke, Markus and Schmid, Klaus} } @Inproceedings { El-SharkawyKroeherSchmid11a, title = {Supporting Heterogeneous Compositional Multi Software Product Lines}, year = {2011}, volume = {2}, abstract = {Software Product Line Engineering is inherently complex. This complexity increases further if multiple product line infrastructures are composed to yield the final products, an approach sometimes referred to as Multi Software Product Lines (MSPL). In this paper, we present an approach that targets this development scenario. The approach we present here aims at a lightweight, scalable, and practical approach to variability management for multi software product lines. Our approach explicitly supports heterogeneous product lines, i.e. situations where the various product lines use different generation approaches. The approach has been implemented in the EASy-Producer tool set and applied on some case studies.}, tags = {SSE_ELSHARKAWY SSE_KROEHER SSE_SCHMID SSE_INDENICA}, editor = {Ina Schaefer and Isabel John and Klaus Schmid}, publisher = {ACM}, booktitle = {Proceedings of the Joint Workshop of the 3rd International Workshop on Model-driven Approaches in Software Product Line Engineering and the 3rd Workshop on Scalable Modeling Techniques for Software Product Lines (MAPLE/SCALE 2011) at the 15th International Software Product Line Conference (SPLC '11)}, ISBN = {978-1-4503-0789-5}, DOI = {10.1145/2019136.2019164}, author = {El-Sharkawy, Sascha and Kr{\"o}her, Christian and Schmid, Klaus} } @Inproceedings { El-SharkawySchmid11, title = {A Heuristic Approach for Supporting Product Innovation in Requirements Engineering: A Controlled Experiment}, year = {2011}, pages = {78-93}, abstract = {[Context and motivation] While requirements engineering earlier focused on gathering requirements, it has been recognized today that creativity and innovation are required as a basis for novel products. [Question/problem] We described earlier an approach to support creativity in requirements engineering. Here, we focus on a thorough validation of the approach. [Principal ideas/results] Our approach uses semantic-based technologies to derive new idea triggers. Here, we show an evaluation of this approach. We find that the approach provides better results than other existing creativity techniques like random triggers. [Contribution] The paper provides evidence for creativity enhancement using our approach. It also shows how a controlled experiment to analyze creativity in requirements engineering can be performed.}, tags = {SSE_ELSHARKAWY SSE_SCHMID}, editor = {Daniel Berry and Xavier Franch}, publisher = {Springer}, booktitle = {Proceedings of the 17th International Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ '11)}, DOI = {10.1007/978-3-642-19858-8_10}, author = {El-Sharkawy, Sascha and Schmid, Klaus} } @Inproceedings { El-SharkawyKroeherSchmid11b, title = {Support for Complex Product Line Populations}, year = {2011}, volume = {2}, abstract = {In this paper, we describe EASy-Producer, a prototypical tool for complex and large-scale Software Product Line (SPL) development. The tool enables SPL engineers to reduce complexity by combining derivation and composition techniques to manage one large SPL as a combination of individual, but interrelated SPLs.}, tags = {SSE_ELSHARKAWY SSE_KROEHER SSE_SCHMID SSE_INDENICA}, editor = {Ina Schaefer and Isabel John and Klaus Schmid}, publisher = {ACM}, booktitle = {Demonstration and Tools at the 15th International Software Product Line Conference (SPLC '11)}, ISBN = {978-1-4503-0789-5}, DOI = {10.1145/2019136.2019191}, author = {El-Sharkawy, Sascha and Kr{\"o}her, Christian and Schmid, Klaus} } @Techreport { IndenicaD221, title = {Variability Implementation Techniques for Platforms and Services (Interim)}, year = {2011}, abstract = {Creating domain-specific service platforms requires the capability of (automatically) customizing and configuring service platforms according to the specific needs of a domain. In this deliverable we address this demand. We focus on how to create customized service platforms using variability implementation techniques. The focus is on understanding variability implementation in the context of a service platform specific situation and with respect to the specific demands of the INDENICA project. Towards this end, we provide an analysis of this situation, structure and analyze a large body of relevant approaches for customizing service technologies and finally describe the core concepts that provide the basis of the INDENICA approach to implement the customization of service platforms.}, note = {Public Deliverable D2.2.1, EU-Project INDENICA}, tags = {SSE_SCHMID SSE_INDENICA}, institution = {Institut f{\"u}r Informatik, Universit{\"a}t Hildesheim, Germany}, author = {of Hildesheim, University and of Vienna, University and di Milano, Politecnico and SAP and Siemens and Telcordia} } @Article { Schmid10a, title = {Produktlinienentwicklung}, journal = {Informatik-Spektrum}, year = {2010}, volume = {33}, number = {6}, pages = {621-625}, abstract = {Softwareentwickelnde Unternehmen sind heute meist auf Produkte fokussiert, die sie immer wieder in {\"a}hnlicher Weise realisieren (Finanzinformationssysteme, Motorensteuerungen etc.). Entsprechend k{\"o}nnen diese Unternehmen signifikante Vorteile erzielen, falls es ihnen gelingt, {\"a}hnliche Funktionalit{\"a}t jeweils nur einmal zu entwickeln und in mehreren Produkten wiederzuverwenden. Produktlinienentwicklungsans{\"a}tze unterst{\"u}tzen genau dies und f{\"u}hren so zu deutlichen Vorteilen in Bezug auf Kosten, Qualit{\"a}t und Entwicklungszeit, wie Industrieerfahrungen zeigen [3, 7]. Produktlinienans{\"a}tze unterscheiden sich von anderen Softwareentwicklungsans{\"a}tzen vor allem darin, dass sie auf die integrierte Entwicklung einer Menge von Systemen (Produkten) abzielen,w{\"a}hrend klassische Ans{\"a}tze den Fokus auf Einzelsysteme legen.}, tags = {SSE_SCHMID}, author = {Schmid, Klaus} } @Article { SchmidEichelbergerGoltz+10a, title = {Evolving Adaptable Systems: Potential and Challenges}, journal = {Softwaretechnik-Trends}, year = {2010}, volume = {30}, number = {2}, pages = {48-49}, tags = {SSE_SCHMID SSE_EICHELBERGER SSE_EVOLINE}, author = {Schmid, Klaus and Eichelberger, Holger and Goltz, Ursula and Lochau, Malte} } @Article { EichelbergerSchmid10, title = {Anpassbare {RE}-Werkzeuge - Eine Fallstudie}, journal = {Softwaretechnik-Trends}, year = {2010}, volume = {30}, number = {1}, pages = {16-17}, abstract = {Die Anpassung von Anforderungswerkzeugen an den Projektkontext ist im Regelfall durch die Anpassungsf{\"a}higkeiten des jeweiligen Werkzeuges stark eingeschr{\"a}nkt. In diesem Beitrag stellen wir einen generativen Ansatz zur Anpassung von Anforderungswerkzeugen vor und demonstrieren den Ansatz im Rahmen einer Fallstudie. Unser Ansatz erm{\"o}glicht die einfache, zielgerichtete und weitreichende Anpassung an die Anwendungssituation.}, tags = {SSE_EICHELBERGER SSE_SCHMID}, author = {Eichelberger, Holger and Schmid, Klaus} } @Article { GrubeEl-SharkawySchmid10, title = {Automatisierte Kreativit{\"a}tsunterst{\"u}tzung in der Anforderungserhebung}, journal = {Softwaretechnik-Trends}, year = {2010}, volume = {30}, number = {1}, abstract = {Traditionell wird die Anforderungserhebung vor allem als eine reine Erfassung existierender W{\"u}nsche gesehen. In letzter Zeit setzt sich jedoch die Ansicht durch, dass Anforderungen f{\"u}r neue Produkte meist erst entwickelt werden m{\"u}ssen; Anforderungserhebung also mit Innovation verbunden ist. Damit ist auch das Interesse an der Unterst{\"u}tzung von Kreativit{\"a}t in der Anforderungserhebung stark gewachsen. Kreativit{\"a}tsunterst{\"u}tzung wird meist im Zusammenhang mit moderierten Workshops gesehen. Hier stellen wir jedoch einen Ansatz dar, bei dem ein Assistenzsystem basierend auf modelliertem Wissen versucht zus{\"a}tzliche Anhaltspunkte f{\"u}r die kreative Entwicklung von Anforderungen zu geben.}, tags = {SSE_ELSHARKAWY SSE_SCHMID}, author = {Grube, Pascal and El-Sharkawy, Sascha and Schmid, Klaus} } @Inproceedings { Schmid10b, title = {Variability Modeling for Distributed Development - A Comparison with Established Practice}, year = {2010}, pages = {155-165}, abstract = {The variability model is a central artifact in product line engineering. Existing approaches typically treat this as a single centralized artifact which describes the configuration of other artifacts. This approach is very problematic in distributed development as a monolithic variability model requires significant coordination among the involved development teams. This holds in particular if multiple independent organizations are involved. At this point very little work exists that explicitly supports variability modeling in a distributed setting. In this paper we address the question how existing, real-world, large-scale projects deal with this problem as a source of inspiration on how to deal with this in variability management.}, tags = {SSE_SCHMID}, editor = {Jan Bosch and Jaejoon Lee}, publisher = {Springer}, booktitle = {Proceedings of the 14th International Software Product Line Conference (SPLC '10)}, DOI = {10.1007/978-3-642-15579-6_11}, author = {Schmid, Klaus} } @Inproceedings { SchmidEichelbergerGoltz+10b, title = {Evolving Adaptable Systems: Potential and Challenges}, year = {2010}, tags = {SSE_SCHMID SSE_EICHELBERGER SSE_EVOLINE}, booktitle = {Proceedings of the 2nd Workshop ''Design for Future}, author = {Schmid, Klaus and Eichelberger, Holger and Goltz, Ursula and Lochau, Malte} } @Article { BirkHellerJanzen+09, title = {Orientierung in der Landschaft des Requirements-Engineering: Ein {\"U}berblick {\"u}ber {RE}-Frameworks und ihre Anwendungsgebiete}, journal = {Softwaretechnik-Trends}, year = {2009}, volume = {29}, number = {1}, pages = {2-3}, abstract = {Das Requirements-Engineering (RE) hat in den vergangenen Jahren viele RE-Frameworks hervor gebracht, die zentrale Konzepte des RE detailliert und umfassend beschreiben sowie Anleitungen f{\"u}r die RE-Praxis bieten wollen. Zugleich sind mit der Ausweitung der Software-Produktlinien(SPL)-Entwicklung in der Industrie neue Herausforderungen an das RE entstanden, f{\"u}r die RE-Frameworks L{\"o}sungen bieten sollten. Der Arbeitskreis ''Requirements-Engineering-Frameworks und Produktlinien'' der GI-Fachgruppe „Require-ments-Engineering“ hat das Ziel, einen {\"U}berblick {\"u}ber die wichtigsten RE-Frameworks zu erstellen, die Relevanz aus Sicht der Industrie zu bewerten und ihre Anwendbarkeit in der Produktlinien-Entwicklung zu untersuchen [4][1]. Dies soll Software-Projekte, die Anleitung f{\"u}r Ihr RE suchen, unterst{\"u}tzen, das f{\"u}r sie passende Framework auszuw{\"a}hlen. Dieser Artikel stellt erste Ergebnisse dieser Arbeit vor.}, tags = {SSE_SCHMID}, author = {Birk, Andreas and Heller, Gerald and Janzen, Dirk and Schmid, Klaus} } @Article { AdamEhresmannKrause+09, title = {Zwischenbericht des Arbeitskreises Requirements Engineering f{\"u}r Adaptive Systeme}, journal = {Softwaretechnik-Trends}, year = {2009}, volume = {29}, number = {1}, pages = {8}, abstract = {Die wirtschaftliche Bedeutung von Flexibilit{\"a}t und Adaptivit{\"a}t w{\"a}chst. Viele Techniken wie Produktlinienentwicklung oder Service-orientierte Architekturen wurden entwickelt, um mit dieser Herausforderung umzugehen. Aber auch Fragestellungen der Softwareevolution sind von Bedeutung. Die genannten Techniken und Entwicklungsans{\"a}tze haben auch Auswirkungen auf das Requirements Engineering. Diese Herausforderungen stehen im Mittelpunkt des Arbeitskreises Requirements Engineering f{\"u}r Adaptive Systeme.}, tags = {SSE_SCHMID}, author = {Adam, Sebastian and Ehresmann, Michael and Krause, Stefan and Schmid, Klaus and Sitou, Wassilou} } @Article { EichelbergerSchmid09a, title = {Guidelines on the Aesthetic Quality of {UML} Class Diagrams}, journal = {Information and Software Technology}, year = {2009}, volume = {51}, number = {12}, pages = {1686-1698}, abstract = {In the past, formatting guidelines have proved to be a successful method to improve the readability of source code. With the increasing success of visual specification languages such as UML for model-driven software engineering visual guidelines are needed to standardize the presentation and the exchange of modeling diagrams with respect to human communication, understandability and readability. In this article, we introduce a new and encompassing taxonomy of visual guidelines capturing the aestheticquality of UMLclassdiagrams. We propose these guidelines as a framework to improve the aestheticquality and thus the understandability of UMLclassdiagrams. To validate this claim, we describe in detail a controlled experiment carried out as a pilot study to gather preliminary insights on the effects of some of the guideline rules on the understandability of UMLclassdiagrams.}, tags = {SSE_EICHELBERGER SSE_SCHMID}, DOI = {10.1016/j.infsof.2009.04.008}, author = {Eichelberger, Holger and Schmid, Klaus} } @Article { GrubeSchmid09, title = {Systematische Auswahl von Kreativit{\"a}tstechniken f{\"u}r die Anforderungserhebung}, journal = {Softwaretechnik-Trends}, year = {2009}, volume = {29}, number = {1}, pages = {9-10}, abstract = {Ziel der Anforderungserhebung ist es Anforderungen des Kunden korrekt und vollst{\"a}ndig zu erfassen. Doch oft ist auch dem Kunden nicht bewusst, wie eine L{\"o}sung aussehen kann. Hier haben sich Kreativit{\"a}tstechniken als guter Ansatz gezeigt, um die Entwicklung einer Systemvision zu unterst{\"u}tzen. Hier stellen wir einen Ansatz vor, um aus der gro{\ss}en Zahl verf{\"u}gbarer Techniken systematisch die f{\"u}r eine konkrete Situation passende Technik auszuw{\"a}hlen.}, tags = {SSE_SCHMID}, author = {Grube, Pascal and Schmid, Klaus} } @Incollection { HelferichSchmidHerzwurm09, title = {Product Management for Software Product Lines}, year = {2009}, pages = {79-100}, tags = {SSE_SCHMID}, editor = {Kyo Chul Kang and Vijayan Sugumaran and Sooyong Park}, publisher = {Auerbach Publications}, booktitle = {Applied Software Product-Line Engineering}, author = {Helferich, Andreas and Schmid, Klaus and Herzwurm, Georg} } @Inproceedings { SarmadBarbarSchmid09, title = {A Comparative Survey of Economic Models for Software Product Lines}, year = {2009}, pages = {275-278}, abstract = {Software product line engineering aims at achieving systematic reuse by exploiting commonalities among related products in order to reduce cost and time-to market. Before adopting this approach, organizations are likely to estimate the benefits they can expect to achieve and the level of investment required to transition to product line engineering. Several economic models and analysis approaches have been developed in order to help make a sound business case. There is a need to review the existing approaches in order to better understand the overall landscape of economic models. To this objective, this paper provides an overview of some existing economic models and discusses important issues and directions in product line economic modeling.}, tags = {SSE_SCHMID}, publisher = {IEEE Computer Society}, booktitle = {Proceedings of the 35th Euromicro Conference on Software Engineering and Advanced Applications (SEAA '09)}, DOI = {10.1109/SEAA.2009.89}, author = {Muhammad Sarmad, Ali and Barbar, Ali and Schmid, Klaus} } @Inproceedings { Schmid09b, title = {Reasoning on Requirements Knowledge to Support Creativity}, year = {2009}, pages = {7-11}, abstract = {Developing innovative products is an important challenge for companies these days. Meanwhile it is in requirements engineering widely recognized that requirements elicitation has to go beyond mere recording of knowledge, rather is has to be an active process where new ideas are created. Thus, creativity is an important issue in requirements engineering. While so far tool support for creativity focused mainly on recording the creative outcome or providing relevant knowledge, we will describe an approach where tool support is used to actively support people in the creation of ideas.}, tags = {SSE_SCHMID}, publisher = {IEEE Computer Society}, booktitle = {Proceedings of the 2nd International Workshop on Managing Requirements Knowledge (MaRK '09) at the 17th IEEE International Requirements Engineering Conference (RE '09)}, DOI = {10.1109/MARK.2009.10}, author = {Schmid, Klaus} } @Inproceedings { Schmid09a, title = {Verteilte Evolution von Softwareproduktlinien: Herausforderungen und ein L{\"o}sungsansatz}, year = {2009}, pages = {99-110}, abstract = {Die Evolution einzelner Systeme ist bereits relativ komplex, doch alle diese Probleme findet man potenziert in einer Produktlinienentwicklung. Zus{\"a}tzlich zu den Einzelsystemproblemen treten weitere Schwierigkeiten hinzu. In diesem Beitrag gehen wir auf die Herausforderungen der Produktliniensituation ein und legen unser Augenmerk vor allem auf die Situation verteilter Evolution. Wir stellen einen m{\"o}glichen Ansatz zur L{\"o}sung vor.}, tags = {SSE_SCHMID}, publisher = {Gesellschaft f{\"u}r Informatik (GI)}, booktitle = {Proceedings of the 1st Workshop of the GI-Arbeitskreis Langlebige Softwaresysteme (L2S2): ''Design for Future - Langlebige Softwaresysteme''}, author = {Schmid, Klaus} } @Inproceedings { SchmidKroeher09, title = {An Analysis of Existing Software Configuration Systems}, year = {2009}, abstract = {Dynamic Software Product Lines (DSPL) focuses on product lines where the resolution of variants happens at a later point in time, ideally at runtime. While runtime reconfiguration is still rather innovative, preconfiguration of software systems is well established and to some degree even standardized. Thus, we study such preconfiguration approaches to better understand how their capabilities relate to classical product line engineering on one hand and to dynamic software product lines on the other.}, tags = {SSE_SCHMID SSE_KROEHER}, editor = {Dirk Muthig and John D. McGregor}, publisher = {ACM}, booktitle = {Proceedings of the 3rd International Workshop on Dynamic Software Product Lines (DSPL '09) at the 13th International Software Product Line Conference (SPLC '09)}, author = {Schmid, Klaus and Kr{\"o}her, Christian} } @Inproceedings { EichelbergerEldoganSchmid09b, title = {A Comprehensive Survey of UML Compliance in Current Modelling Tools}, year = {2009}, pages = {39-50}, abstract = {The Unified Modeling Language (UML) specification is widely adopted in software engineering. When tools do not fully implement the UML specification, the user might be locked-in to a modeling tool, e.g. when exported models are not compatible among tools or tools implement different subsets of the UML. These compatibility problems also have significant impact on the effectiveness of model-driven development approaches. Compliance, as defined by the UML standard, is intended to characterize tools and to highlight such problems. In this paper we describe an approach to asses the UML compliance levels of modeling tools. Using UML definition of compliance, we could only identify 4 out of 68 tools as being acceptable.}, tags = {SSE_EICHELBERGER SSE_SCHMID}, editor = {P. Liggesmeyer and G. Engels and J. M}, publisher = {K{\"o}llen Verlag}, booktitle = {Proceedings of the Software Engineering 2009 Fachtagung des GI-Fachbereich Softwaretechnik}, author = {Eichelberger, Holger and Eldogan, Yilmaz and Schmid, Klaus} } @Inproceedings { EichelbergerEldoganSchmid09c, title = {How much UML is in my UML Tool? An Overview}, year = {2009}, abstract = {The Unified Modeling Language (UML) has been widely adopted in industrial software engineering as the reference standard for software and systems modeling. A wide range of different tools have been developed both by industrial vendors as well as by the open source community. However, due to the complexity of the UML specification it is very difficult for a single tool to support the full range of UML standards faithfully. In practice tools differ significantly in terms of the parts of the UML specification they support}, tags = {SSE_EICHELBERGER SSE_SCHMID}, booktitle = {Proceedings of the 2nd Systems Engineering Infrastructure Conference (SEISCONF '09)}, author = {Eichelberger, Holger and Eldogan, Yilmaz and Schmid, Klaus} } @Inproceedings { DologLinGrube+09, title = {Creativity Support at the Workplace}, year = {2009}, abstract = {In this paper, we discuss creativity as a form of learning from the perspective of idea generation in the creative process. We analyze forms of creativity and present the statement-based creativity techniques. Based on these concepts a tool prototype IdeaTrigger is presented and verified. It shows the advantages for innovative activity, especially in collaborative environment.}, tags = {SSE_SCHMID}, publisher = {Fraunhofer Verlag}, booktitle = {Proceedings of the 2nd International ELBa Science Conference (ELBa '09)}, author = {Dolog, Peter and Lin, Yujian and Grube, Pascal and Schmid, Klaus} } @Inproceedings { HellebooghWeynsSchmid+09, title = {Adding Variants on-the-fly: Modeling Meta-Variability in Dynamic Software Product Lines}, year = {2009}, pages = {18-27}, abstract = {Dynamic software product lines (DSPL) are software product lines (SPL) that support runtime variability. Runtime variability is typically interpreted as binding variation points at runtime. We emphasize meta-variability as an important dimension of runtime variability in DSPL. Whereas dynamic binding considers the runtime (de)activation of variants within the scope of a given variability model, meta-variability considers runtime changes to the variability model itself. Meta-variability is essential to support longlived software products that are subject to evolution. In this paper, we consider meta-variability in an industrial DSPL that is developed in a joint project with Egemin N.V., a leading company that provides full life cycle support for automated transportation systems (ATS). The contribution of this paper is threefold. First, we introduce a way to model meta-variability in DSPL in an explicit manner. Second, we put forward a meta-variability meta model that extends the variability meta model with concepts that explicitly support meta-variability. Third, we capture and apply metavariability in an industrial DSPL for automated transportation systems.}, tags = {SSE_SCHMID}, editor = {Dirk Muthig and John D. McGregor}, publisher = {ACM}, booktitle = {Proceedings of the 3rd International Workshop on Dynamic Software Product Lines (DSPL '09) at the 13th International Software Product Line Conference (SPLC '09)}, author = {Helleboogh, Alexander and Weyns, Daniel and Schmid, Klaus and Holvoet, Tom and Schelfthout, Kurt and Van Betsbrugge, Wim} } @Inproceedings { EichelbergerSchmid09b, title = {Anpassbare RE-Werkzeuge - Eine Fallstudie}, year = {2009}, abstract = {Die Anpassung von Anforderungswerkzeugen an den Projektkontext ist im Regelfall durch die Anpassungsf{\"a}higkeiten des jeweiligen Werkzeuges stark eingeschr{\"a}nkt. In diesem Beitrag stellen wir einen generativen Ansatz zur Anpassung von Anforderungswerkzeugen vor und demonstrieren den Ansatz im Rahmen einer Fallstudie. Unser Ansatz erm{\"o}glicht die einfache, zielgerichtete und weitreichende Anpassung an die Anwendungssituation.}, tags = {SSE_EICHELBERGER SSE_SCHMID}, booktitle = {GI-Fachgruppentreffen Requirements Engineering}, author = {Eichelberger, Holger and Schmid, Klaus} } @Inproceedings { El-SharkawyGrubeSchmid09, title = {Using Semantically Linked Content to Support Creativity in Product Innovation}, year = {2009}, pages = {638-642}, abstract = {In competitive markets product innovation becomes a major issue for companies. Many creativity techniques have been proposed over time to improve creativity.In this paper, we discuss a platform and a specific reasoning approach to support product innovation. This reasoning approach is based on a specific form of heuristic (or almost correct) reasoning, most instances rely on analogies.}, tags = {SSE_ELSHARKAWY SSE_SCHMID}, publisher = {IEEE Computer Society}, booktitle = {Proceedings of Future Computing, Service Computation, Cognitive, Adaptive, Content, Patterns (COMPUTATIONWORLD '09)}, DOI = {10.1109/ComputationWorld.2009.29}, author = {El-Sharkawy, Sascha and Grube, Pascal and Schmid, Klaus} } @Techreport { EichelbergerEldoganSchmid09a, title = {A Comprehensive Analysis of UML Tools, their Capabilities and their Compliance}, year = {2009}, number = {1/2012}, abstract = {Im letzten Jahrzehnt hat sich die Unified Modeling Language (UML) als Modellierungssprache f{\"u}r den praktischen Einsatz im Software Engineering weitgehend durchgesetzt. Aufgrund der Komplexit{\"a}t der UML Spezifikation ist es allerdings f{\"u}r ein einzelnes Werkzeug sehr schwierig, die gesamte Bandbreite der UML Modellierungselemente getreu der UML Spezifikationen umzusetzen. Werkzeugrealisierungen unterscheiden sich daher ma{\ss}geblich anhand der von ihnen unterst{\"u}tzten Teile der UML Spezifikation. Die Entscheidung einer Entwicklungsorganisation f{\"u}r ein konkretes Modellierungswerkzeug ist bedeutsam f{\"u}r das ganze Unternehmen. Im Regelfall zieht eine derartige Entscheidung empfindliche Kosten nach sich, z.B. f{\"u}r das Training der Mitarbeiter. Lizenzkosten stellen dabei oft nur einen geringen Anteil der tats{\"a}chlichen Kosten f{\"u}r ein Werkzeug dar. Folglich sollte eine Werkzeugauswahl mit gro{\ss}er Sorgfalt durchgef{\"u}hrt werden. Die vorliegende Studie ist zurzeit der wohl umfassendste Vergleich von UML Werkzeugen und stellt damit ein geeignetes Hilfsmittel dar, um zu einer rationalen Entscheidung {\"u}ber einzusetzende Werkzeuge zu gelangen. Der Schwerpunkt dieser Studie liegt auf der Umsetzung von Modellierungf{\"a}higkeiten durch die Werkzeuge, d.h. ob und wie Modellierungselementen und –eigenschaften der UML umgesetzt wurden. Um die UML Modellierungsf{\"a}higkeiten detailliert pr{\"u}fen zu k{\"o}nnen, wurde die UML Spezifikation in 476 Merkmale aufgegliedert, die individuell f{\"u}r jedes betrachtete Werkzeug gepr{\"u}ft wurden. Eine detaillierte Aufschl{\"u}sselung verkn{\"u}pft die f{\"u}r jedes Werkzeug identifizierten F{\"a}higkeiten mit den Anforderungen, die von der UML f{\"u}r einzelne Diagrammtypen gemacht werden. Auf diese Weise kann die Anwendbarkeit eines konkreten Werkzeuges f{\"u}r einen gegebenen Anwendungskontext schnell {\"u}berpr{\"u}ft werden. Als Bestandteil unserer Analyse charakterisieren wir jedes Werkzeug durch Angabe der individuellen UML compliance, einem Kategorisierungsschema der OMG.}, tags = {SSE_EICHELBERGER SSE_SCHMID}, institution = {Institut f{\"u}r Informatik, Universit{\"a}t Hildesheim, Germany}, author = {Eichelberger, Holger and Eldogan, Yilmaz and Schmid, Klaus} } @Article { Schmid08b, title = {Zwischenbericht des Arbeitskreises Requirements Engineering f{\"u}r Adaptive Entwicklung und Systeme}, journal = {Softwaretechnik-Trends}, year = {2008}, volume = {28}, number = {1}, pages = {27}, abstract = {Die wirtschaftliche Bedeutung von Flexibilit{\"a}t und Adaptivit{\"a}t w{\"a}chst. Viele Techniken wie Produktlinienentwicklung oder Service-orientierte Systeme wurden entwickelt, um mit dieser Herausforderung umzugehen. Aber auch Fragestellungen der Softwareevolution sind von Bedeutung. Diese Techniken und Entwicklungsans{\"a}tze haben auch Auswirkungen auf das Requirements Engineering. Diese Herausforderungen stehen im Mittelpunkt des Arbeitskreises Adaptive Entwicklung und Systeme.}, tags = {SSE_SCHMID}, author = {Schmid, Klaus} } @Article { Schmid08a, title = {Produktlinien in der industriellen Softwareentwicklung}, journal = {iX-Magazin f}, year = {2008}, volume = {5}, pages = {110-114}, abstract = {Software ist ein entscheidender Wertsch{\"o}pfungs- und Kostenfaktor in industriellen Produkten. Dies gilt sowohl f{\"u}r Informationssysteme als auch f{\"u}r eingebettete Systeme wie Anlagensteuerungen oder Automobilkomponenten. Systematische Produktlinienentwicklung hat sich als probates Mittel erwiesen, gleichzeitig Kosten und Fehlerzahl zu senken.}, note = {Online available at: http://www.heise.de/developer/artikel/Produktlinien-in-der-industriellen-Softwareentwicklung-227160.html}, tags = {SSE_SCHMID}, author = {Schmid, Klaus} } @Article { SchmidEichelberger08a, title = {A Requirements-Based Taxonomy of Software Product Line Evolution}, journal = {Electronic Communications of the EASST}, year = {2008}, volume = {8}, abstract = {Software product lines are, by their very nature, complex software systems. Due to the interconnectedness of the various products in the product line any form of evolution becomes significantly more complex than in a single system situation. So far most work on product line evolution has focused on specific approaches to supporting special cases of the evolution problem. In this paper, we take a different approach and provide a broad taxonomy of requirements-driven evolution in software product lines. This serves as a basis for the identification of requirements on evolution support.}, tags = {SSE_SCHMID SSE_EICHELBERGER}, author = {Schmid, Klaus and Eichelberger, Holger} } @Article { HallsteinsenHinchey+08, title = {Dynamic Software Product Lines}, journal = {IEEE Computer}, year = {2008}, volume = {41}, number = {4}, pages = {93-95}, abstract = {The Software Engineering Institute (SEI) defines an SPL as a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission. A fundamental principle of SPLs is variability management, which involves separating the product line into three parts - common components, parts common to some but not all products, and individual products with their own specific requirements - and managing these throughout development. Using SPLs seeks to maximize reusable variation and eliminate wasteful generic development of components used only once. Although traditional SPL engineering recognizes that variation points are bound at different stages of development, and possibly also at runtime, it typically binds variation points before delivery of the software. In contrast, DSPL engineers typically aren't concerned with pre-runtime variation points. However, they recognize that in practice mixed approaches might be viable, where some variation points related to the environment's static properties are bound before runtime and others related to the dynamic properties are bound at runtime.}, tags = {SSE_SCHMID}, DOI = {10.1109/MC.2008.123}, author = {Hallsteinsen, Svein and Hinchey, Mike and Park, Soyong and Schmid, Klaus} } @Article { LorenzBodeSchmid08, title = {Requirements Engineering im Customer Relationship Management: Erfahrungen in der Werkzeugauswahl}, journal = {Softwaretechnik-Trends}, year = {2008}, volume = {28}, number = {1}, pages = {15-16}, abstract = {Customer Relationship Management (CRM) ist eine komplexe Dom{\"a}ne und erfordert entsprechende ITUnterst{\"u}tzung. Die arvato direct services GmbH ist europaweit einer der gr{\"o}{\ss}ten Dienstleister in diesem Bereich. Die ad{\"a}quate IT-Unterst{\"u}tzung wird in der Regel individuell entwickelt, daher ist das Requirements Engineering (RE) entscheidend f{\"u}r den Erfolg in diesen Projekten. Um das RE bei arvato direct services zu st{\"a}rken, wurde eine systematische Auswahl eines RE-Werkzeugs durchgef{\"u}hrt. Ausgehend von den Herausforderungen eines ITDienstleisters im CRM, wird auf die erhobenen Anforderungen an das gesuchte RE-Werkzeug und die Vorgehensweise bei der Auswahl eingegangen. Anschlie{\ss}end werden sowohl die Erfahrungen bei der Werkzeugauswahl als auch bei der Einf{\"u}hrung des Werkzeugs dargestellt. Diese sind zum Teil auch {\"u}ber den Bereich des CRM hinaus {\"u}bertragbar.}, tags = {SSE_SCHMID}, author = {Lorenz, Michael and Bode, Markus and Schmid, Klaus} } @Inproceedings { SchmidEichelberger08b, title = {From Static to Dynamic Software Product Lines}, year = {2008}, volume = {2}, pages = {33-38}, tags = {SSE_SCHMID SSE_EICHELBERGER}, editor = {Steffen Thiel and Klaus Pohl}, publisher = {Lero Int. Science Centre, University of Limerick, Ireland}, booktitle = {Proceedings of the 2nd International Workshop on Dynamic Software Product Lines (DSPL '08) at the 12th International Software Product Line Conference (SPLC '08)}, author = {Schmid, Klaus and Eichelberger, Holger} } @Inproceedings { SchmidEichelberger08c, title = {Model-Based Implementation of Meta-Variability Constructs: A Case Study using Aspects}, year = {2008}, pages = {63-71}, abstract = {In this paper, we introduce the concept of metavariability, i.e., variability with respect to basic variability attributes like binding time or constraints. While the main focus of this paper is on the introduction of the concept, we will also illustrate the concept by providing a case study. The case study will feature a simple implementation environment based on aspect-oriented programming and will include an example that will exhibit some key characteristics of the envisioned production process.}, tags = {SSE_SCHMID SSE_EICHELBERGER}, editor = {Patrick Heymans and Kyo Chul Kang and Andreas Metzger and Klaus Pohl}, publisher = {Institut f{\"u}r Informatik und Wirtschaftsinformatik, Universit{\"a}t Duisburg}, booktitle = {Proceedings of the 2nd International Workshop on Variability Modelling of Software-intensive Systems (VaMos'08)}, author = {Schmid, Klaus and Eichelberger, Holger} } @Inproceedings { BirkFiegeSchmid08, title = {Produktlinien im Kontext: Technologie, Prozesse, Business und Organisation. PIK2008 Workshop-Einleitung und {\"U}berblick}, year = {2008}, pages = {235-239}, abstract = {Produktlinien sind heute in vielen Bereichen der Software-Industrie vertreten. Dennoch bergen sie f{\"u}r viele Unternehmen noch bedeutende Herausforderungen und Risiken. Der Workshop beleuchtet aktuelle Erfahrungen mit Produktlinien und bietet ein Forum f{\"u}r den Dialog zwischen Praxis und anwendungsorientierter Forschung. Im Mittelpunkt steht das Wechselspiel zwischen technischen Fragestellungen und den gesch{\"a}ftlichen, organisatorischen und Prozessaspekten.}, tags = {SSE_SCHMID}, editor = {Walid Maalej and Bernd Bruegge}, publisher = {Gesellschaft f{\"u}r Informatik (GI)}, booktitle = {Proceedings of the 2008 Workshop Produktlinien im Kontext (PIK '08) at the Conference on Software Engineering (SE '08)}, author = {Birk, Andreas and Fiege, Ludger and Schmid, Klaus} } @Inproceedings { GrubeSchmid08, title = {Selecting Creativity Techniques for Innovative Requirements Engineering}, year = {2008}, pages = {32-36}, abstract = {While the traditional focus of requirements engineering was mainly on the systematic, reliable and adequate translation of the customers intentions into requirements documentation, it became recently increasingly accepted that requirements engineering, especially for innovative and novel products, is probably more adequately described as a process of joint discovery of requirements that can be supported by creativity techniques. However, so far little work exists on how to systematically select techniques as a basis for requirements engineering. As part of the IdSpace Project, which focuses on collaborative product innovation, we are currently investigating this area. This paper provides a brief overview of our work in this domain.}, tags = {SSE_SCHMID}, publisher = {IEEE Computer Society}, booktitle = {Proceedings of the 3rd International Workshop on Multimedia and Enjoyable Requirements Engineering - Beyond Mere Descriptions and with More Fun and Games (MERE '08)}, ISBN = {978-0-7695-3626-2}, DOI = {10.1109/MERE.2008.6}, author = {Grube, Pascal and Schmid, Klaus} } @Inproceedings { EichelbergerSchmid08b, title = {Concepts for Flexible Component Integration for Product Lines}, year = {2008}, tags = {SSE_EICHELBERGER SSE_SCHMID}, booktitle = {Work in Progress Session at the 38th EUROMICRO Conference on Software Engineering and Advanced Applications 2008 (SEAA '08)}, author = {Eichelberger, Holger and Schmid, Klaus} } @Inproceedings { EichelbergerSchmid08a, title = {EASy-Producer - A Product Line Production Environment}, year = {2008}, pages = {357}, abstract = {In this paper, we describe EASy-producer, a prototypical production environment for software product lines (SPL), in particular for the realization of adaptive systems and dynamic SPL.}, tags = {SSE_EICHELBERGER SSE_SCHMID}, publisher = {IEEE Computer Society}, booktitle = {Proceedings of the 12th International Software Product Line Conference (SPLC '08)}, DOI = {10.1109/SPLC.2008.24}, author = {Eichelberger, Holger and Schmid, Klaus} } @Unpublished { EichelbergerSchmid08c, title = {Experimental Material for the Software Engineering Experiment {SoSe} 2008}, year = {2008}, note = {Online available at: http://www.sse.uni-hildesheim.de/experimentSoSe08.zip}, tags = {SSE_EICHELBERGER SSE_SCHMID}, author = {Eichelberger, Holger and Schmid, Klaus} } @Article { Schmid07, title = {Ambient Intelligence}, journal = {KI}, year = {2007}, volume = {2}, pages = {5-9}, tags = {SSE_SCHMID}, author = {Schmid, Klaus} } @Article { SchmidHerzwurmHelferich07, title = {Software-Produktlinien aus Sicht des Marktes und der Technik}, journal = {WISU}, year = {2007}, volume = {07}, number = {5}, pages = {686-692}, tags = {SSE_SCHMID}, author = {Schmid, Klaus and Herzwurm, Georg and Helferich, Andreas} } @Book { LindenSchmidRommes07, title = {Software Product Lines in Action: The Best Industrial Practice in Product Line Engineering}, year = {2007}, tags = {SSE_SCHMID}, publisher = {Springer}, author = {van der Linden, Frank and Schmid, Klaus and Rommes, Eelco} } @Inproceedings { SchneiderBunseSchmid07, title = {Towards Adaptive Service Engineering}, year = {2007}, pages = {33-38}, abstract = {Technical systems are increasingly becoming an imminent part of human life. A growing trend is that systems are embedded in technical devices and working continuously without human intervention. However, this implies that these systems run for a long time without human control. As the environment changes, the systems need to adapt themselves. One approach to address these challenges is the use of service-oriented development paradigms. This paper highlights the challenges and research issues in the context of engineering adaptable, service-oriented systems. Challenges are identified based on the development plane they might appear in (i.e., service-, application-, and infrastructure engineering). We finish by discussing in detail the expected benefits and open research issues.}, tags = {SSE_SCHMID}, editor = {Grace A. Lewis and Dennis B. Smith}, publisher = {Software Engineering Institute (SEI)}, booktitle = {Proceedings of the International Workshop on the Foundations of Service-Oriented Architecture (FSOA '07) at the 3rd International Conference on Interoperability of Enterprise Software and Applications (I-ESA '07)}, author = {Schneider, Daniel and Bunse, Christian and Schmid, Klaus} } @Article { Schmid06a, title = {A Study on Creativity in Requirements Engineering}, journal = {Softwaretechnik-Trends}, year = {2006}, volume = {26}, number = {1}, pages = {20-21}, abstract = {The first step of requirements engineering is always: deciding what to build. While it may seem trivial, it is sometimes the hardest step in the whole project. In this report, we illustrate some experiences with a miniature creativity session that focused on the what-to-build question. The very limited time frame allowed at the same time very detailed controlling of the overall results. Thus, we can provide here quantitative results on the success of the workshop.}, tags = {SSE_SCHMID}, author = {Schmid, Klaus} } @Article { HelferichSchmidHerzwurm06c, title = {Product Management for Software Product Lines: An Unsolved Problem?}, journal = {Communications of the ACM}, year = {2006}, volume = {49}, number = {12}, pages = {66-67}, abstract = {The goal of this article is to call attention to an area that is yet not sufficiently researched: product management for software product lines (SPLs). Many companies developing standardized software products have adopted product management as a function that coordinates research and development, marketing, sales, and software development. Even though this function coordinates all of these areas, it is traditionally mainly a marketing function and often organized as part of the marketing department. This may be sufficient for “normal” software products, but not in a SPL context, as we will discuss here.}, tags = {SSE_SCHMID}, author = {Helferich, Andreas and Schmid, Klaus and Herzwurm, Georg} } @Inproceedings { Schmid06c, title = {The Self-Adaptation Problem in Software Specifications}, year = {2006}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the Workshop on Software Engineering Challenges for Ubiquitous Computing (SEUC '06)}, author = {Schmid, Klaus} } @Inproceedings { Schmid06b, title = {Goal-Based Requirements Modelling as a Basis for Adaptivity to the Service Context}, year = {2006}, pages = {31-42}, tags = {SSE_SCHMID}, editor = {Klaus David and Olaf Dr{\"o}gehorn and Sandra Haseloff}, publisher = {Kassel University Press}, booktitle = {Proceedings of the 2nd Workshop on Context Awareness for Proactive Systems (CAPS '06)}, author = {Schmid, Klaus} } @Inproceedings { SchmidKrennrichEisenbarth06, title = {Requirements Management for Product Lines: Extending Professional Tools}, year = {2006}, pages = {113-122}, abstract = {The key idea of software product lines is the integrated development of a set of products, exploiting commonalities and variabilities among the products to achieve high levels of reuse. The commercial potential of this approach has already been demonstrated in numerous case studies. However, while requirements management tools are already widespread, the range of professional tool support for product line development is still very poor. In this paper we analyze the question whether and how existing requirement management tools can be seamlessly extended to product line development. We present a general approach, which has been prototyped based on the DOORS requirements management tool and leads to the REMAP-tool extension.}, tags = {SSE_SCHMID}, publisher = {IEEE Computer Society}, booktitle = {Proceedings of the 10th International Software Product Line Conference (SPLC '06)}, DOI = {10.1109/SPLINE.2006.1691583}, author = {Schmid, Klaus and Krennrich, Karsten and Eisenbarth, Michael} } @Inproceedings { HelferichSchmidHerzwurm06b, title = {Softwareproduktlinien f{\"u}r Anwendungssysteme: eine Analyse aus Techniksicht und Marktsicht}, year = {2006}, volume = {2}, pages = {237-248}, tags = {SSE_SCHMID}, booktitle = {Multikonferenz Wirtschaftsinformatik (MKWI '06) - Software-Produktmanagement}, author = {Helferich, Andreas and Schmid, Klaus and Herzwurm, Georg} } @Inproceedings { HelferichSchmidHerzwurm06a, title = {Reconciling Marketed and Engineered Software Product Lines}, year = {2006}, pages = {23-27}, abstract = {Basically all companies today go beyond the development of single products and offer set(s) of similar and related products. In marketing, one such set is often called a product line. Nevertheless, still today most products are not yet engineered as product lines, i.e., they are not yet derived from a single platform. In this paper, we will explore the relation of these two forms of product lines. It is shown that under certain circumstances Engineered and Marketed Software Product Line subsume different products. This paper shows how these two perspectives differ and why a difference in products between these perspectives may be appropriate from a company perspective. Finally, it is argued that activities currently subsumed under Product Management and Scoping should be closely coordinated, allowing companies to optimize their product portfolios since decision-making is facilitated.}, tags = {SSE_SCHMID}, publisher = {IEEE Computer Society}, booktitle = {Proceedings of the 10th International on Software Product Line Conference (SPLC '06)}, ISBN = {0-7695-2599-7}, DOI = {http://doi.acm.org/10.1145/1753235.1753276}, author = {Helferich, Andreas and Schmid, Klaus and Herzwurm, Georg} } @Article { SchmidBiffl05, title = {Systematic Management of Software Product Lines}, journal = {Software Process: Improvement and Practice}, year = {2005}, volume = {10}, number = {1}, pages = {61-76}, abstract = {Software product lines can effectively facilitate large-scale reuse and can thus bring about order of magnitude improvements in terms of time to market (TTM), costs, and quality. This comes at the price of a more complex development environment in which many interdependencies are created through shared generic assets. Owing to this complexity, the specific strategy chosen for product line development can be expected to have a strong impact on the benefits that can be gained from product line development. This is systematically studied in this work, as we vary different strategies and apply them to various forms of products lines. On the basis of the analysis of the performed simulations, we were able to determine optimal, heuristic strategies to the integrated management of the product line. As a result of the analysis, we identify strategies and guidelines that can be employed by practitioners in order to improve the success of their management of a software product line.}, tags = {SSE_SCHMID}, DOI = {http://dx.doi.org/10.1002/spip.215}, author = {Schmid, Klaus and Biffl, Stefan} } @Inproceedings { SchmidKoenig05, title = {Adapting Business Processes to Varying Business Needs: Some Case Studies}, year = {2005}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the 1st International Workshop on Requirements Engineering for Business Needs and IT Alignment (REBNITA '05) at the 13th IEEE International Conference on Requirements Engineering (RE '05)}, author = {Schmid, Klaus and Koenig, Thomas} } @Inproceedings { SchmidEisenbarthGrund05, title = {From Requirements Engineering to Knowledge Engineering: Challenges in Adaptive Systems}, year = {2005}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the 1st International Workshop on Service-Oriented Computing: Consequences for Engineering Requirements (SOCCER '05) at the 13th IEEE International Requirements Engineering Conference (RE '05)}, author = {Schmid, Klaus and Eisenbarth, Michael and Grund, Mathias} } @Inproceedings { SchmidJohnKolb+05, title = {Introducing the PuLSE Approach to an Embedded System Population at Testo AG}, year = {2005}, pages = {544-552}, abstract = {Over the last few years, product line engineering has become a major theme in software engineering research, and is increasingly becoming a central topic of software engineering practice in the embedded domain. Migrating towards a product line approach is not an easy feat. It is even less so, if it is done under tight technology constraints in an embedded environment. It becomes even more difficult if the transition directly aims at integrating two product families into a single product population. In this paper, we discuss our experiences with a project where we successfully dealt with these difficulties and achieved a successful product line transition. In our paper, we strongly emphasize the role of technology transfer, as many facets of product line know-how had to be transferred to guarantee a complete transition to product line engineering. From the experiences of this project many lessons learned can be deduced, which can be transferred to different environments.}, tags = {SSE_SCHMID}, editor = {Gruia-Catalin Roman and William G. Griswold and Bashar Nuseibeh}, publisher = {ACM}, booktitle = {Proceedings of the 27th International Conference on Software Engineering (ICSE '05)}, author = {Schmid, Klaus and John, Isabel and Kolb, Ronny and Meier, Gerald} } @Techreport { OlssonDengerKoenig+05b, title = {Applying the IESE Requirements Reference Model}, year = {2005}, number = {045.05/E}, abstract = {This report describes mapping of several requirements engineering models to the ForPICS reference model.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Olsson, Thomas and Denger, Christian and Koenig, Tom and Eisenbarth, Michael and Schmid, Klaus} } @Techreport { OlssonDengerKoenig+05a, title = {A Reference Model for Requirements}, year = {2005}, number = {043.05/E}, abstract = {This report describes the reference model underlying the transformation between different models and the traceability between the same.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Olsson, Thomas and Denger, Christian and Koenig, Tom and Eisenbarth, Michael and Schmid, Klaus} } @Techreport { SchmidKrennrichEisenbarth05, title = {Requirements Management for Product Lines: A Prototype}, year = {2005}, number = {061.05/E}, abstract = {The key idea of software product lines is the integrated development of a set of products, exploiting commonalities and variabilities among the products to achieve high levels of reuse. The commercial potential of this approach has already been demonstrated in numerous case studies. However, while requirements management tools are already widespread, the range of professional tool support for product line development is still very poor. In this paper we analyze the question whether and how existing requirement management tools can be seamlessly extended to product line development. We present a general approach, which has been prototyped based on the DOORS requirements management tool and lead to the REMAP tool.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Schmid, Klaus and Krennrich, Karsten and Eisenbarth, Michael} } @Article { Schmid04a, title = {Systematische Wiederverwendung im Produktlinienumfeld}, journal = {KI}, year = {2004}, volume = {18}, pages = {33-35}, abstract = {BMW ist bekannt f{\"u}r seine Autos, Bosch f{\"u}r seine Motorensteuerungen und Microsoft f{\"u}r seine Betriebssysteme. Nahezu alle Firmen sind auf gewisse Bereiche spezialisiert und stellen nur eine kleine Zahl von Produktgruppen her. Je Produktgruppe kann die Zahl der Varianten jedoch gewaltig sein, so produziert Bosch alleine weit {\"u}ber tausend verschiedene Motorensteuerungen. Trotz dieser Vielzahl von Varianten {\"u}berwiegen die Gemeinsamkeiten, da diese sie gerade zu einer Produktgruppe machen. K{\"o}nnte man diese Gemeinsamkeiten systematisch ausnutzen indem man sie nur einmal entwickelt, so erg{\"a}be sich hier ein enormes Wiederverwendungspotential! Genau das ist das Ziel der Produktlinienans{\"a}tze wie PuLSE. Diese zielen darauf ab die Entwicklung einer Vielzahl von Systemen durch eine gemeinsame Referenzarchitektur zu integrieren. In der Praxis wurden so bereits Wiederverwendungsraten von 75\% und mehr erreicht!}, tags = {SSE_SCHMID}, author = {Schmid, Klaus} } @Article { OlssonDengerKoenig+04, title = {Ein Referenzmodell f{\"u}r Anforderungsspezifikationen}, journal = {Softwaretechnik-Trends}, year = {2004}, volume = {24}, number = {4}, pages = {15-16}, abstract = {Viele verschiedene Ans{\"a}tze zur Modellierung von Anforderungen wurden im Verlauf der Zeit entwickelt. Doch der prinzipielle Zusammenhang zwischen diesen Notationen ist weitestgehend unklar. Im Rahmen der beschriebenen Arbeit wurde ein Referenzmodell abgeleitet, dass mehrere sehr verschiedene Notationen integriert. Das mittelfristige Ziel der beschriebenen Arbeiten ist eine Basis f{\"u}r die semi-automatische Transformation von Anforderungsmodellen zu bieten.}, tags = {SSE_SCHMID}, author = {Olsson, Thomas and Denger, Christian and Koenig, Tom and Eisenbarth, Michael and Schmid, Klaus} } @Article { SchmidJohn04, title = {A Customizable Approach to Full Lifecycle Variability Management}, journal = {Science of Computer Programming}, year = {2004}, volume = {53}, number = {3}, pages = {259-284}, abstract = {In order to enable a smooth transition to product line development for an organization that so far only performed single system development, it is necessary to keep as many of the existing notations and approaches in place as possible.This requires adaptability of the basic variability management approach to the specific situation at hand. In this paper we describe an approach that enables homogenous variability management across the different lifecycle stages, independent of the specific notation. The approach is accompanied by a meta-model and a process for introducing the variability management approach by developing a notation-independent representation. This approach has so far been applied in several cases where our Product Line engineering method PuLSETM has been introduced into a software development organization.}, tags = {SSE_SCHMID}, author = {Schmid, Klaus and John, Isabel} } @Article { BunseKalmarSchmid04, title = {Objektorientierte Konzepte f{\"u}r die SW-Entwicklung - Teile und Herrsche!}, journal = {Automotive Electronics \& Systems}, year = {2004}, volume = {9-10}, pages = {48-50}, tags = {SSE_SCHMID}, author = {Bunse, Christian and Kalmar, Ralf and Schmid, Klaus} } @Article { BoeckleClementsMcGregor+04, title = {Calculating the ROI for Software Product Lines}, journal = {IEEE Software}, year = {2004}, volume = {21}, number = {3}, pages = {23-31}, abstract = {Product line engineering has become an important and widely used approach for efficiently developing portfolios of software products. The idea is to develop a set of products as a single, coherent development task from a core asset base (sometimes called a platform), a collection of artifacts specifically designed for use across a portfolio. This approach produces order-of-magnitude economic improvements compared to one-at-a-time software system development. Because the product line approach isn't limited to specific technical properties of the planned software but rather focuses on economic characteristics, high return on investment has become the anthem of the approach's protagonists. Our software product line cost model can calculate the costs and benefits (and hence the ROI) that we can expect to accrue from various product line development situations. It's also straightforward and intuitive.}, tags = {SSE_SCHMID}, author = {B{\"o}ckle, G{\"u}nther and Clements, Paul and McGregor, John and Muthig, Dirk and Schmid, Klaus} } @Article { MassenBirkHeller+04b, title = {Herausforderungen bei industriellen Produktlinien-Entwicklungen}, journal = {OBJEKT-Spektrum}, year = {2004}, volume = {5}, pages = {69-75}, abstract = {Produktlinien-Ans{\"a}tze bergen hohe Potentiale, um den Entwicklungsprozess und die Vermarktung {\"a}hnlicher Produkte zu optimieren. Die Einf{\"u}hrung oder sogar die Umstellung auf eine Produktlinien-Entwicklung stellen jedoch eine gro{\ss}e Herausforderung f{\"u}r jeden Gesch{\"a}ftsbereich einer Organisation dar. Diese wurden in einer Studie des GI-Arbeitskreises „Requirements Engineering f{\"u}r Produktlinien“ untersucht. In diesem Artikel werden die Hauptprobleme analysiert und m{\"o}gliche L{\"o}sungen vorgestellt.}, tags = {SSE_SCHMID}, author = {von der Ma{\ss}en, Thomas and Birk, Andreas and Heller, Gerald and John, Isabel and Schmid, Klaus} } @Article { JohnKohlerSchmid04, title = {Benutzbare Produktlinien: Integration von Usability- und Produktlinienaspekten in der Anforderungsanalyse}, journal = {Softwaretechnik-Trends}, year = {2004}, volume = {24}, number = {1}, pages = {13-14}, abstract = {Softwareproduktlinien unterst{\"u}tzen die Entwicklung mehrerer Produkte in Varianten. Diese Variantenbildung betrifft die Architektur der Software insgesamt, materialisiert sich f{\"u}r den Kunden aber vor allem in der Benutzungsoberfl{\"a}che seiner'' L{\"o}sung, bspw. durch die Unterschiede in der verf{\"u}gbaren Funktionalit{\"a}t. Die Benutzungsfreundlichkeit der Features und Prozesse steht im Mittelpunkt des Usability Engineering, das Methoden zur Spezifikation und Bewertung der Benutzbarkeit von Software zur Verf{\"u}gung stellt. Wir stellen hier ein integriertes Vorgehen zum Usability- und Produktlinienengineering im Rahmen der Anforderungsermittlung, -modellierung und -bewertung vor, das insbesondere f{\"u}r kleine und mittlere Unternehmen geeignet ist, f{\"u}r die eine integrierte Analyse aus Aufwands- und Kostengr{\"u}nden besonders angebracht ist.}, tags = {SSE_SCHMID}, author = {John, Isabel and Kohler, Kirstin and Schmid, Klaus} } @Book { BoeckleKnauberPohl+04, title = {Software-Produktlinien}, year = {2004}, tags = {SSE_SCHMID}, publisher = {Dpunkt-Verlag}, author = {B{\"o}ckle, G{\"u}nther and Knauber, Peter and Pohl, Klaus and Schmid, Klaus} } @Inbook { Schmid04c, title = {Software-Produktlinien}, year = {2004}, pages = {43-54}, tags = {SSE_SCHMID}, editor = {G{\"u}nter B{\"o}ckle and Peter Knauber and Klaus Pohl and Klaus Schmid}, publisher = {Dpunkt-Verlag}, chapter = {Scoping als Basis optimierter Wiederverwendung}, author = {Schmid, Klaus} } @Inbook { Schmid04d, title = {Trendbarometer Technik: Vision{\"a}re Produkte - Neue Werkstoffe - Fabriken der Zukunft}, year = {2004}, pages = {168-169}, tags = {SSE_SCHMID}, editor = {Hans-J{\"o}rg Bullinger}, publisher = {Carl Hanser Verlag}, chapter = {Scoping - Entscheidend f{\"u}r das Design von Softwareproduktlinien}, author = {Schmid, Klaus} } @Inbook { Schmid04b, title = {Perspectives on Software Requirements}, year = {2004}, pages = {223-252}, tags = {SSE_SCHMID}, editor = {Julio Leite and Jorge Doorn}, publisher = {Kluwer Academic Publishers}, chapter = {Strategically Defining and Exploiting Product Portfolios with a Product Line Approach}, author = {Schmid, Klaus} } @Inbook { SchmidKnauber04, title = {Software-Produktlinien}, year = {2004}, pages = {43-54}, tags = {SSE_SCHMID}, editor = {G{\"u}nther B{\"o}ckle and Peter Knauber and Klaus Pohl and Klaus Schmid}, publisher = {Dpunkt-Verlag}, chapter = {Zusammenfassung}, author = {Schmid, Klaus and Knauber, Peter} } @Inbook { SchmidJohnKolb04, title = {Software-Produktlinien}, year = {2004}, pages = {221-232}, tags = {SSE_SCHMID}, editor = {G{\"u}nther B{\"o}ckle and Peter Knauber and Klaus Pohl and Klaus Schmid}, publisher = {Dpunkt-Verlag}, chapter = {Eingebettete Systeme bei der Testo AG}, author = {Schmid, Klaus and John, Isabel and Kolb, Ronny} } @Inproceedings { Schmid03d, title = {Requirements Engineering for Ambient Systems: A Viewpoint}, year = {2004}, tags = {SSE_SCHMID}, publisher = {IEEE Computer Society}, booktitle = {Proceedings of the International Workshop on Service-Oriented Requirements Engineering (SoRE '04) at the 12th IEEE International Conference on Requirements Engineering (RE '04)}, author = {Schmid, Klaus} } @Inproceedings { DoerrOlssonSchmid+04, title = {Qualit{\"a}t im Automobil: Systematische Definition nichtfunktionaler Anforderungen Sicherheit und Zuverl{\"a}ssigkeit f{\"u}r automobile Informationstechnik}, year = {2004}, pages = {65-71}, abstract = {In diesem Artikel haben wir einen Ansatz zur effizienten Identifikation und Dokumentation von nichtfunktionalen Anforderungen vorgestellt, der insbesondere zur Erfassung von Zuverl{\"a}ssigkeits- und Sicherheitsanforderungen eingesetzt wird. Der Ansatz beruht auf erfahrungsoptimierten Qualit{\"a}tsmodellen, Templates und Checklisten, die projekt{\"u}bergreifend eingesetzt werden. Diese werden in einer Tailoringphase an das jeweilige Projekt angepasst. Die Vorteile des Ansatzes gegen{\"u}ber anderen Techniken zur Identifikation nichtfunktionaler Anforderungen sind: - Geringer Aufwand, durch Workshopformat, Fokussierung auf Kernanforderungen und vielf{\"a}ltige, erfahrungsbasierte Vorgaben - Verbesserungsorientierung durch die integrierte Iteration der Ausgangsdokumente - Testbarkeit durch die Fokussierung auf messbare NFRs.}, tags = {SSE_SCHMID}, editor = {E. Pl{\"o}dereder and H. Keller and H. von Sommerfeld and P. Dencker and M. Tonndorf and F. Saglietti}, publisher = {Shaker Verlag}, booktitle = {Proceedings of the Workshop Automotive - Safety \& Security at the Ada Deutschland Tagung 2004}, author = {D{\"o}rr, J{\"o}rg and Olsson, Thomas and Schmid, Klaus} } @Inproceedings { GyimothyLiggesmeyerNiebuhr+04, title = {A Software Engineering Perspective on Ambient Intelligence}, year = {2004}, tags = {SSE_SCHMID}, booktitle = {Positionspapier als Grundlage des Deutsch-Ungarischen Projektworkshops im Rahmen des BelAmI-Projekts}, author = {Gyimothy, Tibor and Liggesmeyer, Peter and Niebuhr, Dirk and Rausch, Andreas and Rombach, Dieter and Schmid, Klaus} } @Inproceedings { JohnKerkowSchmid04, title = {Usable Product Lines: Issues and Requirements}, year = {2004}, pages = {29-35}, abstract = {In this paper we describe synergies and conflicts between the two at first sight incompatible fields Usability engineering and Product Line Engineering. We describe how both fields can benefit from each other and give requirements on an approach that covers both usability and product line aspects.}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the Workshop W1L Bridging the Gaps II: Bridging the Gaps Between Software Engineering and Human-Computer Interaction at the 26th International Conference on Software Engieneering (ICSE '04)}, DOI = {http://dx.doi.org/10.1049/ic:20040183}, author = {John, Isabel and Kerkow, D. and Schmid, Klaus} } @Inproceedings { MassenBirkHeller+04a, title = {Key Challenges in Industrial Product Line Engineering.}, year = {2004}, volume = {1}, pages = {260-272}, abstract = {This paper summarizes the results of the ''Gesellschaft f{\"u}r Informatik'' (GI) working group on ''Requirements Engineering for Software Product Lines'' which is part of the requirements engineering group within in the GI. This work group met regularly to identify the key problems in product line engineering practice with potential (and proven) solutions. While this started originally as an effort focused purely on requirements engineering issues, we soon understood that we had to take a broader perspective due to the tight interconnection of requirements engineering with other issues in a product line context. We will provide a characterization of the different organizations that participated in this effort. This will demonstrate that overall a good coverage of different types of software organizations has been achieved. We will then provide an overview of the main problems in product line development. Based on both our own experience as well as our understanding of the technology,we derived and described potential solutions for the main problems.}, tags = {SSE_SCHMID}, editor = {H. Dieter Rombach and Stefan Eicker and Klaus Pohl and Heimo H. Adelsberger and Volker Wulf and Helmut Krcmar and Jan M. Pawlowski}, publisher = {Akademische Verlagsgesellschaft Aka GmbH}, booktitle = {Multikonferenz Wirtschaftsinformatik (MKWI '04) - E-Learning Modelle, Instrumente und Erfahrungen, Software-Produktlinien, Communities in E-Business}, author = {von der Massen, Thomas and Birk, Andreas and Heller, Gerald and John, Isabel and Schmid, Klaus and Joos, Stefan and M{\"u}ller, Klaus} } @Techreport { SchmidJohnKolb+04, title = {Introducing the PuLSE Approach to an Embedded System Population at Testo AG}, year = {2004}, number = {015.04/E}, abstract = {Over the last few years, product line engineering has become a major theme in software engineering research, and is increasingly becoming a central topic of software engineering practice in the embedded domain.Migrating towards a product line approach is not an easy feat. It is even less so, if it is done under tight technology constraints in an embedded environment. It becomes even more difficult if the transition directly aims at integrating two product families into a single product population. In this paper, we discuss our experiences with a project where we successfully dealt with these difficulties and achieved a successful product line transition. In our paper we strongly emphasize the role of technology transfer, as many facets of product line know-how had to be transferred to guarantee a complete transition to product line engineering. From the experiences of this project many lessons learned can be deduced, which can be transferred to different environments.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Schmid, Klaus and John, Isabel and Kolb, Ronny and Meier, Gerald} } @Techreport { MuthigJohnAnastasopoulos+04, title = {GoPhone - A Software Product Line in the Mobile Phone Domain}, year = {2004}, number = {025.04/E}, abstract = {This report provides insights into component-based product line engineering on the basis of a case study from the mobile phones domain. The reader follows the systematic creation of a hypothetical software product line according to the PuLSE and KobrA methods developed at Fraunhofer IESE. Scoping as well as Application and Framework Engineering are covered. Our goal was to provide as broad an overview as possible. For that reason many details haven been intentionally left out.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Muthig, Dirk and John, Isabel and Anastasopoulos, Michalis and Forster, Thomas and D{\"o}rr, J{\"o}rg and Schmid, Klaus} } @Techreport { JohnDoerrSchmid04, title = {User Documentation Based Product Line Modeling}, year = {2004}, number = {004.04/E}, abstract = {This report describes an approach for extraction of product line requirements based on existing user documentation. The approach we describe in this report supports capturing of the information found in user documentation of legacy systems, e.g., user manuals, and the specification of this information in product line models, using, e.g., Use Cases. The main goal of the approach is expert load reduction; as we found out during our product line technology activities at IESE that the domain experts are a serious bottleneck during the product line scoping and modeling activities. The approach is based on a variability modeling approach that allows integrating arbitrary modeling formalisms to capture the extracted requirements in a product line model. We propose a conceptual model describing the transition from user documentation to product line artifacts describing common and variable elements of a product line model. The approach uses extraction patterns that allow an easyidentification of text elements in user documents. The pattern are then used to create a significant part of the requirements specification and product line model, respectively and we present an extraction process that guides the user in using the pattern. In this report we present the approach itself and show the application of our approach for three case studies, one from the embedded/ mobile phone domain, two from the information system domain. The case studies have shown that the approach is applicable to information systems and embedded systems and that it produces relatively complete and correct results. With one of our case studies that was performed in real industrial settings we could not only show expert load reduction when applying the approach but also an overall time saving when applying the approach for product line scoping. A predecessor of this report with a different focus can be found in [JD03b].}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {John, Isabel and D{\"o}rr, J{\"o}rg and Schmid, Klaus} } @Unpublished { ZuehlkeBernsThiels+04, title = {{White Paper in the Area of MMI for the Research Topic ''Ambient Intelligence'' (AmI)}}, year = {2004}, tags = {SSE_SCHMID}, author = {Z{\"u}hlke, D. and Berns, K. and Thiels, N. and Schmid, Klaus} } @Article { Schmid03b, title = {L{\"o}sungen f{\"u}r Probleme des Requirements Engineering f{\"u}r Produktlinien: Bericht des Arbeitskreises Requirements Engineering f{\"u}r Produktlinien}, journal = {Softwaretechnik-Trends}, year = {2003}, volume = {23}, number = {1}, pages = {20-21}, abstract = {Softwareproduktlinien entstehen wo auch immer Produkte in Varianten entwickelt werden. Dies stellt ein gigantisches Wiederverwendungspotential dar, schafft aber auch Schwierigkeiten, vor allem f{\"u}r den Anforderungsprozess. Daher wurde vor zwei Jahren ein GI-Arbeitskreis zu diesem Thema gegr{\"u}ndet, der sich mit Problemen und L{\"o}sungen des Requirements Engineering f{\"u}r Produktlinien besch{\"a}ftigt.}, tags = {SSE_SCHMID}, author = {Schmid, Klaus} } @Article { BirkHellerJohn+03a, title = {Product Line Engineering: The State of the Practice}, journal = {IEEE Software}, year = {2003}, volume = {20}, number = {6}, pages = {52-60}, abstract = {Software product lines are powerful tools for ensuring quality, economic efficiency, and manageability of families of software systems. SPL is important for many companies in the software business, ranging from small start-ups to large industrial enterprises. However, SPL is also a challenging technology that's not always easy to implement and maintain. Members from five different organizations formed a work group that investigated and compared their SPL practices over a period of two and a half years. The group identified key practice areas including organization and support, balancing platform versus client interests, requirements engineering practices, and architecture. The investigation's results detail the SPL state of the practice.}, tags = {SSE_SCHMID}, author = {Birk, Andreas and Heller, Gerald and John, Isabel and von der Ma{\ss}en, Thomas and M{\"u}ller, Klaus and Schmid, Klaus} } @Proceedings { SchmidGeppert03, title = {Proceedings of the PLEES '03. International Workshop on Product Line Engineering: The Early Steps: Planning, Modeling, and Managing}, year = {2003}, tags = {SSE_SCHMID}, editor = {Klaus Schmid and Birgit Geppert} } @Inproceedings { Schmid03e, title = {People Management in Institutionalizing Product Lines}, year = {2003}, pages = {175-189}, abstract = {Currently, the key approach to large-scale software reuse is product line development, an approach built upon the systematic development of building blocks for reuse. While most work on product lines focusses on technical issues, in the end they are built by by people. Winning them for product line development is a key issue in successfully introducing and institutionalizing product line development in an organization. This makes people issues a key concern in technology transfer. Based on our experience in technical transfer in the product line area we developed some hypotheses on how these people issues can be formed in a way favorable to product line development. In particular, we focus on the relation between the mind set of people, communication patterns, and the organizational structure. We then give concrete rules based on our own industrial experience as well as industry reports that support instutionalizing product line development.}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the Net.ObjectDays Conference (NODe '03)}, author = {Schmid, Klaus} } @Inproceedings { Schmid03c, title = {A Quantitative Model of the Value of Architecture in Product Line Adoption}, year = {2003}, pages = {32-43}, abstract = {Product line adoption is a key issue in product line development, as the right adoption approach is central to the overall success of product line de velopment. Thus, this is a strongly discussed area of product line engineering. While so far, guidelines and experiences on the best approach to product line adoption have been presented, no detailed quantitative model was provided. In this paper we present a quantitative model of the product line adoption problem. From this model we deduce general guidelines for product line adoption, particularly highlighting the role of the architecture in the cost-effective adoption of a product line.}, tags = {SSE_SCHMID}, editor = {Frank van der Linden}, publisher = {Springer}, booktitle = {Proceedings of the 5th International Workshop on Product Family Engineering (PFE}, author = {Schmid, Klaus} } @Inproceedings { ShawButlerErdogmus+03, title = {CourseForges. Open Source Curriculum Design for Value-Based Software Engineering}, year = {2003}, abstract = {As a relatively young discipline within software engineering, value-based software engineering does not yet have an established curriculum. The area draws on models and techniques in so many other disciplines that it is likely to be some time before a single individual is ready to prepare a course or a textbook. Several of the EDSER-4 participants expressed interest and enthusiasm for sharing the effort of developing curriculum and course materials. Inspired by the success of open source software development, especially the distributed collaboration, the free public access to the results, and the lack of administrative overhead; we decided to try to establish a similar community for curriculum development. This report describes progress to date, with emphasis on the community standards for cooperation and sharing.}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the 5th International Workshop on Economics-Driven Software Engineering Research (EDSER-5) at the 25th International Conference on Software Engineering (ICSE '03)}, author = {Shaw, Mary and Butler, Shawn and Erdogmus, Hakan and Schmid, Klaus} } @Inproceedings { SchmidJohn03b, title = {A Practical Approach to Full Lifecycle Variability Management}, year = {2003}, pages = {41-46}, abstract = {In order to enable a smooth transition to product development for an organization that so far did only perform single system development, it is necessary to keep as much of the existing notations and approaches in place as possible. In this position paper we propose a specific approach to the comprehensive management of variability that enables to leave as much of the existing notations and approaches in place as possible. This approach has so far been applied in several cases where PuLSETM has been introduced into a software development organization.}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the Workshop on Software Variability Management at the 25th International Conference on Software Engineering (ICSE '03)}, author = {Schmid, Klaus and John, Isabel} } @Inproceedings { SchmidJohn03a, title = {Generic Variability Management and Its Application to Product Line Modelling}, year = {2003}, pages = {13-18}, abstract = {In order to enable a smooth transition to product development for an organization that so far did only perform single system development, it is necessary to keep as much of the existing notations and approaches in place as possible. In this position paper we propose a specific approach to the handling of variability which can be applied in the context of many different requirements engineering notations. This allows to extend existing requirements engineering notations to domain analysis notations.}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the Workshop on Software Variability Management at the 25th International Conference on Software Engineering (ICSE '03)}, author = {Schmid, Klaus and John, Isabel} } @Inproceedings { BoeckleClementsMcGregor+03, title = {A Cost Model for Software Product Lines}, year = {2003}, pages = {310-316}, abstract = {In this paper we present a first-order cost model that describes the costs associated with developing products in a product line organization. The model addresses a number of issues that we present as a set of scenarios. The goal of this work is to develop models of varying granularity that support a manager’s decision-making needs at a variety of levels. The basis of these models is the relationships among the artifacts of the product line.}, tags = {SSE_SCHMID}, editor = {Frank van der Linden}, publisher = {Springer}, booktitle = {Proceedings of the 5th International Workshop on Product Family Engineering (PFE '03)}, author = {B{\"o}ckle, G{\"u}nther and Clements, Paul and McGregor, John and Muthig, Dirk and Schmid, Klaus} } @Phdthesis { Schmid03a, title = {Planning Software Reuse}, year = {2003}, abstract = {Software organizations increasingly face the challenge to develop a large number of product variants for their customers. While many organizations still focus on a single product at a time, successful software organizations address the whole range of products in an integrated manner. If the existing reuse potential is adequately exploited, enormous cost savings and quality improvements can result. So far, the incremental introduction of a product line approach and the exploitation of the reuse potential mostly depended on the experience of the responsible personnel due to a lack of systematicapproaches. In this Ph.D. thesis we describe a disciplined approach for systematically planning the development of a software product line. This approach supports (1) identifying an incremental transitioning plan to product line development that determines the sequence and the scope of the introduction based on benefit-and-risk tradeoffs, and (2) determining the specific software components that should be developed for reuse, based on the specific development goals of the organization. The explicit link to the company goals guarantees that the resulting product line approach is optimally aligned to the strategy of the company.}, tags = {SSE_SCHMID}, school = {Universit}, author = {Schmid, Klaus} } @Techreport { Schmid03f, title = {Integrated Cost and Investment Models for Product Family Development}, year = {2003}, number = {067.03/E}, abstract = {Product family development focusses on systematically developing reusable assets over time that are used in later projects to achieve benefits in terms of development effort, time-to-market reduction, and quality improvement. Consequently, the costs from the initial development for reuse are more than compensated by the derived benefits. The initial costs of development for reuse thus take the role of an investment in later product line benefits [CN01]. Therefore it is key to successful product family engineering to identify costs and benefits that are associated with product family development. This provides the basis for the subsequent optimization of the investment. In this deliverable we focus on the relationship between costs and benefits and show the implications and constraints on the associated investment decisions. We present a basic economic model, which provides the necessary background for understanding the impact of investments in a product family. This modelenables a systematic analysis of the product family situation and any consequences of product line investments. A key part of any investment decisions is to define the cost implications of these decisions. Unfortunately, there is no fixed model of product family development and consequently also no fixed model of product family development costs. Thus, we provide a reference model for product family costs in this deliverable together with a collection of the most important cost drivers that we could identify through expert interviews. This will support the organizations in systematically deriving product family cost models that are particularly adapted to their situation. In order to consistently and successfully evolve the product family infrastructure a strategy driven from a market point of view is required [KLD02]. This strategy is needed in order to decide on the appropriateness of an investment and to do so consistently over time. Thus product family strategy shouldbe the basis for any product family investment. In this deliverable we show approaches to derive such a product family strategy and combine it with the most advanced techniques for evaluating the potential benefits of the product family even when facing considerable uncertainties. As a result, this deliverable provides a basis for analyzing costs and benefits of product family development and enables to connect these aspects through an appropriate strategy that is optimally aligned with the existing product family and the company objectives.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Schmid, Klaus} } @Techreport { Schmid03g, title = {Planung von Softwarewiederverwendung - Ein systematischer Ansatz zum Scoping von Softwareproduktlinien}, year = {2003}, number = {102.03/D}, abstract = {Moderne Unternehmen bieten typischerweise eine stark diversifizierte Produktpalette an. Diese Notwendigkeit zur Entwicklung {\"a}hnlicher Systeme gilt nat{\"u}rlich auch f{\"u}r die Software. Der PuLSE-Eco1 Ansatz erlaubt es aus dieser {\"A}hnlichkeit der Systeme maximalen wirtschaftlichen Nutzen zu ziehen. In dieser Zusammenfassung werden die Grundlagen des Ansatzes und seine wesentlichen Schritte erl{\"a}utert. Der Ansatz wurde bereits erfolgreich in verschiedenen Unternehmen angewendet.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Schmid, Klaus} } @Techreport { BirkHellerJohn+03b, title = {Product Line Engineering Industrial Nuts and Bolts}, year = {2003}, number = {113.03/E}, abstract = {Software product lines (SPL) are a powerful concept for ensuring quality, economic efficiency, and manageability of families of software systems. SPL are relevant to large industrial enterprises that want to manage the development of their software-intensive systems well. It can also provide small start-ups with unique and striking business models. SPL is important for many companies in the software business. However, it is also a challenging technology, which is not always easy to implement and maintain. This article sheds light on SPL practices in today's software industry. Members from five different organizations have formed a workgroup that over a period of two years and a half have investigated and compared their SPL practices. The companies are as different as a global IT vendor (Hewlett-Packard), a leading supplier of automotive electronics (Robert Bosch GmbH), a large supplier of industrial energy solutions (represented by RWTH), a small company that develops softwarefor the on-line management of stock market information (Market Maker Software AG, this knowledge was provided by Fraunhofer IESE, a longstanding cooperation partner of the company) and a renowned software house (sd\&m AG). Moreover, most workgroup members have contributed experience from more than one product family or business department allowing a rather broad overview of the state of software product line development in industrial practice. In the remainder of the article, company references are omitted to preserve anonymity of sensitive information. Clements and Northrop [4] define a software product line (SPL) as a set of software-intensive systems sharing a common, managed set of features that satisfy the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way. The workgroup, which met under the umbrella of the German Computer Society (GI, a sister organization of IEEE), set out to understand better howsoftware organizations can successfully set up and manage SPL. Key practice areas identified were: Organization and Support Practices, Practices of Balancing Platform versus Client Interests, Requirements Engineering Practices, Architectural Practices. For each area, the workgroup identified and compared the various practices found in their organizations. They also contrasted them with published reports of SPL practices. The result, which is reported in this article, provides a detailed look on the SPL state of practice.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Birk, Andreas and Heller, Gerald and John, Isabel and von der Ma{\ss}en, Thomas and M{\"u}ller, Klaus and Schmid, Klaus} } @Techreport { BirkHellerJohn+03c, title = {Report of the GI Work Group ''Requirements Engineering for Product Lines''}, year = {2003}, number = {121.03/E}, abstract = {This report summarizes the results of the GI working on ''Requirements Engineering for Software Product Lines'', a working of the GI 2.1.6. This work group met regularly to identify the key problems in product line engineering practice with potential (and proven) solutions. While this started originally as an effort focused purely on requirements engineering issues, we soon understood that we had to take a broader perspective due to the tight interconnection of requirements engineering with other issues in a product line context. We will provide a characterization of the different organizations that participated in this effort. This will demonstrate that overall a good coverage of organizational types has been achieved. In Section 3, we will then provide an overview of the main problems in product line development. These could be clustered in the following main problem categories: - Organization and Management - Requirements Engineering - Product-specific vs.Platform-specific Interests - Architecture These categories resulted from a systematic gathering of known problems along with a clustering. Based on both our own experience as well as our understanding of the technology we derived and described potential solutions for the main problems (cf. Section 5). As far as possible, we described necessary preconditions for the implementation of the solution approaches.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Birk, Andreas and Heller, Gerald and John, Isabel and Joos, Stefan and M{\"u}ller, Klaus and Schmid, Klaus and von der Ma{\ss}en, Thomas} } @Techreport { BayerGanesanGirard+03, title = {Definition of Reference Architectures based on Existing Systems}, year = {2003}, number = {085.03/E}, abstract = {The success of a product family depends greatly on the quality of its reference architecture. To achieve high-quality reference architectures, it is important to leverage the experience embodied in successful system from the same set of domains. However, the literature provides limited guidance on how to mine prior related systems for this specific purpose. This report addresses this issue by introducing an approach, which defines the views needed to express the architectures of a specific product family, recovers and analyzes these views, and provides a systematic process to define the reference architecture integrating the experience of past systems. This first version of this document focuses on architectural views: how they can be recovered, and how architectures can be analyzed and compared among themselves. The second version will emphasize the selection of reuse candidates and the development of the reference architecture for the product family.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Bayer, Joachim and Ganesan, Dharmalingam and Girard, Jean-Francois and Knodel, Jens and Kolb, Ronny and Schmid, Klaus} } @Article { SchmidVerlage02, title = {The Economic Impact of Product Line Adoption and Evolution}, journal = {IEEE Software}, year = {2002}, volume = {19}, number = {6}, pages = {50-57}, abstract = {An organization faces many challenging decisions when transitioning to product line development: What is the best way to adopt a product line approach? How can we avoid disrupting regular product development? Once adopted, how should we evolve the product line? The article discusses how to optimize a product line's economic benefits by considering the adoption context and using product line scoping techniques.}, tags = {SSE_SCHMID}, author = {Schmid, Klaus and Verlage, Martin} } @Proceedings { SchmidGeppert02, title = {Proceedings of the PLEES '02. International Workshop on Product Line Engineering: The Early Steps: Planning, Modeling, and Managing}, year = {2002}, tags = {SSE_SCHMID}, editor = {Klaus Schmid and Birgit Geppert} } @Proceedings { GeppertSchmid02a, title = {Proceedings of the International Workshop on Requirements Engineering for Product Lines (REPL '02)}, year = {2002}, tags = {SSE_SCHMID}, editor = {Birgit Geppert and Klaus Schmid} } @Inproceedings { Schmid02b, title = {The Product Line Mapping Approach to Defining and Structuring Product Portfolios}, year = {2002}, pages = {219-226}, abstract = {A key activity in product line development is to define and structure the product portfolio which shall be the basis for product line development. We present an approach that aims at supporting this activity. This approach also provides a conceptual structuring of the product line in terms of the features and technical domains that are relevant to it. This structure then provides a basis for the planning of the actual product line development and for architecture definition. We also discuss the validation of our approach in the context of some case studies.}, tags = {SSE_SCHMID}, publisher = {IEEE Computer Society}, booktitle = {Proceedings of the 10th Anniversary IEEE Joint International Requirements Engineering Conference (RE '02)}, DOI = {10.1109/ICRE.2002.1048532}, author = {Schmid, Klaus} } @Inproceedings { Schmid02c, title = {Integrating Reference Architecture Definition and Reuse Investment Planning}, year = {2002}, pages = {137-152}, abstract = {When developing a product line, the definition of an appropriate reference architecture that supports the required variabilities is of crucial importance to the success of the product line. In this paper we present an approach to the identification of the key variabilities and to determining the economic benefit of packaging these variabilities in terms of reusable components. This approach provides reusability requirements that can then be taken as an input to product line development. The analysis is based on the economics of the product line. Thus, the approach ensures the optimization of the economic benefit of a product line that is based on a reference architecture that takes these reusability requirements into account. In this paper, we will describe our approach for deriving the reusability requirements, discuss its relationship to different possible investment scenarios, and study the results of the application of our approach in some case studies.}, tags = {SSE_SCHMID}, editor = {Cristina Gacek}, publisher = {Springer}, booktitle = {Proceedings of the 7th International Conference on Software Reuse (ICSR '02)}, DOI = {10.1007/3-540-46020-9_10}, author = {Schmid, Klaus} } @Inproceedings { Schmid02a, title = {A Comprehensive Product Line Scoping Approach and its Validation}, year = {2002}, pages = {593-603}, abstract = {Product Line Engineering is a recent approach to software development that specifically aims at exploiting commonalities and systematic variabilities among functionally overlapping systems in terms of large scale reuse. Taking full advantage of this potential requires adequate planning and management of the reuse approach as otherwise huge economic benefits will be missed due to an inappropriate alignment of the reuse infrastructure.Key in product line planning is the scoping activity, which aims at focussing the reuse investment where it pays. Scoping actually happens on several levels in the process: during the domain analysis step (analysis of product line requirements) a focusing needs to happen just like during the decision of what to implement for reuse. The latter decision has also important ramifications for the development of an appropriate reference architecture as it provides the reusability requirements for this step.In this paper, we describe an integrated approach that has been developed, improved, and validated over the last few years. The approach fully covers the scoping activities of domain scoping and reuse infrastructure scoping and was validated in several industrial case studies.}, tags = {SSE_SCHMID}, editor = {Will Tracz and Michal Young and Jeff Magee}, publisher = {ACM}, booktitle = {Proceedings of the 24th International Conference on Software Engineering (ICSE '02)}, author = {Schmid, Klaus} } @Inproceedings { Schmid02d, title = {Reuse Economics from a Product Line Point of View}, year = {2002}, pages = {4-7}, abstract = {Due to the specific approach to reuse in product line engineering, this approach brings a specific point of view to reuse economics. As a consequence some established assumptions and abstractions of reuse economics that are valid in most opportunistic approaches to reuse must be revisited. The list of issues ranges from the basic estimation models used as input to reuse economics models to real options used for valuing uncertainty and flexibility in reuse. Some of the issues we uncover are also relevant for reuse economics in general.}, tags = {SSE_SCHMID}, editor = {Christina Gacek}, publisher = {Springer}, booktitle = {Proceedings of the International Workshop on Reuse Economics (IWRE '02) at the 7th International Conference on Software Reuse (ICSR '02)}, author = {Schmid, Klaus} } @Inproceedings { SchmidWieczorek02, title = {Practical Problems of Cost Estimation in the Product Line Context}, year = {2002}, abstract = {Existing software cost estimation methods are far from being suitable for the reuse of software in the context of product line development. This paper points out the product line specific aspects of reuse compared to opportunistic reuse in single product development. Implications for existing estimation approaches are drawn and important topics of work are identified.}, tags = {SSE_SCHMID}, booktitle = {Proceedings of th 4th International Workshop on Economics-Driven Software Engineering Research (EDSER-4) at the 24th International Conference on Software Engineering (ICSE '02)}, author = {Schmid, Klaus and Wieczorek, I.} } @Inproceedings { SchmidJohn02, title = {Developing, Validating, and Evolving an Approach to Product Line Benefit and Risk Assessment}, year = {2002}, pages = {272-283}, abstract = {Product line engineering is usually a very beneficial, but sometimes also a very risky endeavor, as there is no guarantee for economic success. In this paper, we describe an assessment approach that is designed to address the problem of quantifying reuse risks by providing an efficient means for determining the benefits and risks associated with a specific product line development. In particular, the approach supports decomposition and individual assessment of the technical domains of the product line, thus also furthering the incremental introduction of product lines. At the core of this paper is the development of the underlying assessment technology and how this approach was evolved over time based on multiple case studies. This evolution approach is rather general. Thus, we see the potential of applying these techniques also for evolving other assessment approaches.}, tags = {SSE_SCHMID}, publisher = {IEEE Computer Society}, booktitle = {Proceedings of the 28th EUROMICRO Conference (EUROMICRO '02)}, DOI = {http://doi.ieeecomputersociety.org/10.1109/EURMIC.2002.1046172}, author = {Schmid, Klaus and John, Isabel} } @Inproceedings { MuthigSchmid02, title = {Balancing Evolution with Revolution to Optimize Product Line Development}, year = {2002}, tags = {SSE_SCHMID}, booktitle = {Technology for Evolutionary Software Development, a Symposium organised by NATO's Research \& Technology Organization (RTO)}, author = {Muthig, Dirk and Schmid, Klaus} } @Inproceedings { GeppertSchmid02b, title = {Requirements Engineering for Product Lines: An Overview}, year = {2002}, pages = {1-4}, abstract = {Often requirements engineering for product lines is treated as just a kind of requirements engineering. However, the specific situation of a product family poses specific demands on the underlying requirements engineering approaches. Foremost among them is of course the need to capture the envisioned degree of variability in the product line. As a result of this other aspects change as well, like requirements traceability, requirements negotiation, requirements management, and of course tool support. In this introduction we provide an overview of these views and describe in more detail the impact of product lines on requirements engineering.}, tags = {SSE_SCHMID}, editor = {Birgit Geppert and Klaus Schmid}, publisher = {IEEE Computer Society}, booktitle = {Proceedings of the International Workshop on Requirements Engineering for Product Lines (REPL '02) at the 10th Anniversary IEEE Joint International Conference on Requirements Engineering (RE '02)}, author = {Geppert, Birgit and Schmid, Klaus} } @Incollection { GacekKnauberSchmid+01a, title = {Successful Software Product Line Development in a Small Organization}, year = {2001}, pages = {485-512}, tags = {SSE_SCHMID}, publisher = {Addison Wesley Longman}, booktitle = {Software Product Lines: Practices and Patterns}, author = {Gacek, Cristina and Knauber, Peter and Schmid, Klaus and Clements, Paul} } @Inproceedings { Schmid01b, title = {An Assessment Approach To Analyzing Benefits and Risks of Product Lines}, year = {2001}, pages = {525-530}, abstract = {Software Product Lines is still a new field within software reuse that aims at large-scale, systematic reuse. Hugh benefits regarding the reduction of time-to-markets, reduction of effort, and quality improvement have been reported as a result of adopting a product line approach. Since a product line program involves major investments, considerable risks are associated with it. Thus, it is important to evaluate at the start of a product line project, i.e., before the major investments are performed, its potential benefits and risks.In this paper we describe an approach that allows to identify the benefits and risks in a systematic manner, thus enabling the early development of risk-avoiding measures. As opposed to other techniques our approach supports the identification of subdomains that are particular appropriate for systematic reuse and by means of the detailed evaluation enables trade-off decisions on where to invest for reuse.}, tags = {SSE_SCHMID}, publisher = {IEEE Computer Society}, booktitle = {Proceedings of the 25th Annual International Computer Software and Applications Conference (COMPSAC '01)}, DOI = {10.1109/CMPSAC.2001.960663}, author = {Schmid, Klaus} } @Inproceedings { Schmid01a, title = {An Initial Model of Product Line Economics}, year = {2001}, pages = {38-50}, abstract = {In this paper we describe an initial model of product line economics, which aims at filling exactly this gap. The model integrates characteristics of the software process with aspects of the market, where the later are used for valuation. We present the model in three layers, each adding a layer of issues that are taken into account to the previous one. This layering mirrors the levels of complexity in existing models of reuse economics}, tags = {SSE_SCHMID}, editor = {Frank van der Linden}, publisher = {Springer}, booktitle = {Proceedings of the 4th International Workshop on Product Family Engineering (PFE}, author = {Schmid, Klaus} } @Inproceedings { SchmidJohn01, title = {Product Line Development as a Rational, Strategic Decision}, year = {2001}, pages = {4-7}, abstract = {Product line development requires a certain amount of up front investment in order to make assets reusable. This investment often keeps organizations from planning and realizing their products in a product line. But there are also major advantages of doing product line development which are often not taken into account when deciding for or against product lines. In this paper we present problems that need to be addressed in the strategic planning of transition towards product lines. These aspects include the involvement of uncertainty, the interdependence of technical solution and decision making, and the interdependence among the decision making and the market aspects. An approach which covers these aspects will determine an objective valuation of a product line.}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the International Workshop on Product Line Engineering The Early Steps: Planning, Modeling, and Managing (PLEES '01)}, type = {IESE-Report}, author = {Schmid, Klaus and John, Isabel} } @Techreport { SchmidGeppert01, title = {International Workshop on Product Line Engineering. The Early Steps: Planning, Modeling, and Managing. Proceedings of the PLEES'01}, year = {2001}, number = {050.01/E}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Schmid, Klaus and Geppert, Birgit} } @Techreport { JohnKnauberMuthig+01, title = {Qualifikationen von kleinen und mittleren Unternehmen (KMU) im Bereich Software Variantenbildung: Abschlu{\ss}bericht zum Projekt}, year = {2001}, number = {026.01/D}, abstract = {Die mittelst{\"a}ndische Wirtschaft kann mittel- und langfristig nicht mit den gro{\ss}en internationalen Firmen im Bereich der Massenfertigung oder durch das Angebot von Standardprodukten konkurrieren. Ihre St{\"a}rken liegen vielmehr im Angebot kundenspezifischer Speziall{\"o}sungen in Einzel- bzw. Kleinserien. Im Rahmen dieses Forschungsvorhabens wurden existierende Forschungsl{\"o}sungen f{\"u}r die Anwendung ingenieurm{\"a}{\ss}iger Grunds{\"a}tze auf die Entwicklung von Software {\"u}bertragen. Besonderes Augenmerk lag dabei auf der {\"o}konomischen Entwicklung kundenspezifischer Varianten.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {John, Isabel and Knauber, Peter and Muthig, Dirk and Schmid, Klaus and Widen, Tanya} } @Techreport { MaldonadoSchmid01, title = {A Case Study of the Structural Properties of Product Line Mapping Approach Based on the Blaupunkt Car Audio Simulation Line of Products}, year = {2001}, number = {093.01/E}, abstract = {Product Line Mapping is an approach for rapidly capturing and describing a line of products. However, the approach goes beyond the realms of traditional requirements.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Maldonado, Raul and Schmid, Klaus} } @Techreport { GacekKnauberSchmid+01b, title = {Successful Software Product Line Development in a Small Organization. A Case Study}, year = {2001}, number = {013.01/E}, abstract = {This report details the experience of a small company, Market Maker Software AG of Kaiserslautern, Germany, as they adopted and used the paradigm of software product lines to help their business grow successfully into a new market area. While software product lines are often associated with large, traditional software organizations, the experience of Market Maker and other small companies like it shows that software product lines represent an ideal development concept for companies of all sizes. This case study reports on the history of the company, how it came to adopt product lines as its prominent development strategy, the role of the key individuals involved, and how they met and overcame various technical challenges. The report concludes with a section analyzing the Market Maker approach.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Gacek, Cristina and Knauber, Peter and Schmid, Klaus and Clements, Paul} } @Article { KnauberMuthigSchmid+00, title = {Applying Product Line Concepts in Small- and Medium-Sized Companies}, journal = {IEEE Software}, year = {2000}, volume = {17}, number = {5}, pages = {88-95}, abstract = {Small and medium-sized enterprises work under heavy constraints: They need to be very flexible and fast in their reaction to customer requests, thus limiting their possibility for long-term planning. In a partially publicly funded project, the authors have started to apply their Product Line Software Engineering method developed at Fraunhofer IESE, in six small and medium-sized companies addressing six different domains. The article presents first experience and lessons learned from 24 months of project work; including first results within the companies.}, tags = {SSE_SCHMID}, author = {Knauber, Peter and Muthig, Dirk and Schmid, Klaus and Widen, Tanya} } @Inproceedings { SchmidBeckerKornstaedtKnauber+00, title = {Introducing a Software Modeling Concept in a Medium-Sized Company}, year = {2000}, pages = {558-567}, abstract = {In this paper, we describe, using the Quality Improvement Paradigm (QIP), how an improvement project aimed at improving the modeling and documentation approach of a medium-sized company (MSuD) was conducted. We discuss the new modeling approach which may serve for other companies as a template for deriving their own adapted approach. Further, we illustrate our insights from this project that can help in future technology transfer projects. A major characteristic of this project was that it was embedded in a long-term consulting relationship.}, tags = {SSE_SCHMID}, editor = {Carlo Ghezzi and Mehdi Jazayeri and Alexander L. Wolf}, publisher = {ACM}, booktitle = {Proceedings of the 22nd International Conference on Software Engineering (ICSE 2000)}, author = {Schmid, Klaus and Becker-Kornstaedt, Ulrike and Knauber, Peter and Bernauer, Florian} } @Inproceedings { Schmid00b, title = {Multi-Staged Scoping for Software Product Lines}, year = {2000}, pages = {8-11}, abstract = {Scoping is a core planning activity in product line development. It is central to determining and optimizing the economical benefits of product line development. In this position paper we discuss the requirements on a sound and practically useful product line development approach and will propose a specific approach which fulfills these requirements.}, note = {Fraunhofer IESE 070.00/E}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the International Workshop on Software Product Lines - Economics, Architectures, and Implications at the 22nd International Conference on Software Engineering (ICSE 2000)}, author = {Schmid, Klaus} } @Inproceedings { Schmid00a, title = {Scoping Software Product Lines - An Analysis of an Emerging Technology}, year = {2000}, pages = {513-532}, abstract = {Software Product Line development is a rather new topic area within domain-specific software engineering that builds on previous work in domain engineering. A crucial step in developing a product line is the scoping step, which aims at determining the boundaries for the product line. This is one of the core planning activities which may determine success or failure of the whole product line effort. In this paper, we aim at analyzing the existing body of knowledge on product line scoping. As the relation to domain engineering is very tight we will also include domain scoping approaches in our analysis. Further, we will look at product line scoping related activities in other fields of study besides software engineering. As a result of this survey we provide a taxonomy of existing approaches both on a problem level, as well as on a solution level, discuss the relative advantages of the various approaches, and show some ways on using the results of this paper for enhancing existing scoping approaches and developing new approaches.}, keywords = {PLE, Scoping}, tags = {SSE_SCHMID}, editor = {Patrick Donohoe}, publisher = {Kluwer}, booktitle = {Proceedings of the 1st Software Product Line Conference (SPLC 1) - Software Product Lines: Experience and Research Directions}, author = {Schmid, Klaus} } @Inproceedings { SchmidSchank00, title = {PuLSE-BEAT: A Decision Support Tool for Scoping Product Lines}, year = {2000}, pages = {64-74}, abstract = {Determining the scope of a product line is a core activity in product line development, as it has a major impact on the economic results of the project. Only recently an approach was proposed that allows to base this decision explicitly on a detailed analysis of the relevant business goals [2]. As the approach requires gathering and evaluating a lot of data, tool support becomes mandatory. In this paper, we describe the tool PuLSE-BEAT, which was specifically developed to address this need.}, tags = {SSE_SCHMID}, editor = {Frank van der Linden}, publisher = {Springer}, booktitle = {Proceedings of the International Workshop on Software Architectures for Product Families (IW-SAPF 2000)}, author = {Schmid, Klaus and Schank, Michael} } @Inproceedings { SchmidWiden00, title = {Customizing the PuLSE Product Line Approach to the Demands of an Organization}, year = {2000}, pages = {221-238}, abstract = {It is well-known that software processes need to be adapted to the specifics of the organization, the application domain, and the development techniques of the environments in which they are used. This is particularly important for reuse processes as they impact the whole software life-cycle and the reuse of artifacts creates additional relationships among multiple process instances (projects). Nevertheless the support for tailoring existing reuse approaches is at best weak. As a consequence of this realization we made customization support for the method a first rate objective while developing the Product Line Software Engineering method (PuLSE). The technology used for customization is called PulSE Baselining and Customization (PuLSE-BC). This approach relies on an explicit characterization of the environment and the explicit connection of these characteristics to customizable properties of a process. In this paper, we describe the technical foundations of this approach and illustrate them with an example.}, tags = {SSE_SCHMID}, editor = {Reidar Conradi}, publisher = {Springer}, booktitle = {Proceedings of the 7th European Workshop on Software Process Technology (EWSPT 2000)}, DOI = {10.1007/BFb0095031}, author = {Schmid, Klaus and Widen, Tanya} } @Inproceedings { SchmidGacek00, title = {Implementation Issues in Product Line Scoping}, year = {2000}, pages = {170-189}, abstract = {Often product line engineering is treated similar to the waterfall model in traditional software engineering, i.e., the different phases (scoping, analysis, architecting, implementation) are treated as if they could be clearly separated and would follow each other in an ordered fashion. However, in practice strong interactions between the individual phases become apparent. In particular, how implementation is done has a strong impact on economic aspects of the project and thus how to adequately plan it. Hence, assessing these relationships adequately in the beginning has a strong impact on performing a product line project right. In this paper we present a framework that helps in exactly this task. It captures on an abstract level the relationships between scoping information and implementation aspects and thus allows to quickly analyze implementation aspects of the project. We will also discuss the application of our framework to a specific industrial project.}, tags = {SSE_SCHMID}, editor = {William B. Frakes}, publisher = {Springer}, booktitle = {Proceedings of the 6th International Conference on Software Reuse: Advances in Software Reusability (ICSR 2000)}, author = {Schmid, Klaus and Gacek, Cristina} } @Inproceedings { SchmidJohn00, title = {Case Study of a Product Line Benefit and Risk Analysis}, year = {2000}, pages = {15-22}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the 1. Deutscher Software-Produktlinien Workshop (DSPL-1)}, author = {Schmid, Klaus and John, Isabel} } @Inproceedings { KnauberSchmid00, title = {Using a Quantitative Approach for Defining Generic Components: A Case Study}, year = {2000}, pages = {131-135}, abstract = {In this paper we give a sketch of a new quantitative approach which can be used to identify and cluster system functionality that should be developed in a reusable fashion, for example, when starting product line development. We demonstrate the applicability of the approach and its validity in a case study.}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the 4th International Software Architecture Workshop (ISAW-4) at the 22nd International Conference on Software Engineering (ICSE 2000)}, author = {Knauber, Peter and Schmid, Klaus} } @Techreport { Schmid00d, title = {Product Line Mapping Report}, year = {2000}, number = {028.00/E}, abstract = {As opposed to traditional domain analysis approaches [Ara89, KCH+90,PD87], the product line mapping approach starts by thoroughly analyzing the product development plans. Thus it is akin to industrial strength domain analysis approaches like ODM [ODM96] or Synthesis [RSP93], but actually goes further in its product orientation. However, the approach given here is explicitly not meant as a full-fledged domain analysis approach, but aims at identifying solely the information necessary as a prerequisite to scoping. Thus, the aimed-at endresult is solely to identify the major products and how they differ in terms of features they support. For identifying the products, the relevant subdomains and their interrelationships the following approach is used: 1 Identify the existing and future systems that may be relevant to the product line. 2 Develop an overview plan of these products. 3 Identify the major functions/features that are relevant to the functionality of these systems. (Thisencompasses end-user features as well as internal functions.) 4 Group these functions into major functional areas (initial domains). 5 Develop an overview of the domains that shows the interrelations among them. 6 Analyze the information for the presence of additional internal domains. 7 Ensure consistency with existing systems. 8 Develop initial product/function matrix In the following sections we describe in more detail how to perform each of these steps.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Schmid, Klaus} } @Techreport { Schmid00c, title = {A Framework for Product Line Quality Model Development: The PuLSE-Eco Meta Quality Model}, year = {2000}, number = {047.00/E}, abstract = {In this report, we described the basis for developing quality models that can be used by the PuLSE-Eco scoping approach to provide a quantitative basis for the scoping of the asset base. We described the general structure of these models as well as the necessary notation and terminology to discuss the specific models and perhaps needed deviations from the standard model. In particular, we discussed the process aspects of product line development, we discussed the general structure of product line quality models, and discussed how specific quality models can be developed. Further, we discussed in detail the relationship between the meta-quality model and the specific quality model guides and how these can be instantiated for the specific projects.}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {IESE-Report}, author = {Schmid, Klaus} } @Inproceedings { Schmid99, title = {An Economic Perspective on Product Line Software Development}, year = {1999}, abstract = {In this paper, we discuss the view that planning software development — and particularly software reuse — should be based not on standardized criteria, but on those criteria that are particularly relevant to the environment for which the planning is done. We also describe how this tailoring of the decision-making process is performed in PuLSE-Eco, an approach for scoping software product lines developed at the Fraunhofer IESE.}, tags = {SSE_SCHMID}, publisher = {ACM}, booktitle = {Proceedings of the 1st Workshop on Economics-Driven Software Engineering (EDSER-1) at the 21st International Conference on Software Engineering (ICSE '99)}, author = {Schmid, Klaus} } @Inproceedings { BayerFlegeKnauber+99, title = {PuLSE: A Methodology to Develop Software Product Lines}, year = {1999}, pages = {122-131}, abstract = {Software product lines have recently been introduced as one of the most promising advances for efficient software development. Yet upon close examination, there are few guidelines or methodologies available to develop and deploy product lines beyond existing domain engineering approaches. The latter have had mixed success within commercial enterprises because of their deployment complexity, lack of customizability, and especially their misplaced focus, that is on domains as opposed to products. To tackle these problems we developed the PuLSETM (Product Line Software Engineering) methodology for the purpose of enabling the conception and deployment of software product lines within a large variety of enterprise contexts. This is achieved via product-centric focus throughout the phases of PuLSETM, customizability of its components, incremental introduction capability, maturity scale for structured evolution, and adaptations to a few main product development situations. PuLSETM is the result of a bottom-up effort: the methodology captures and leverages the results (the lessons learned) from our technology transfer activities with our industrial customers. We present in this paper the main ideas behind PuLSETM and illustrate the methodology with a running example taken from our transfer experience.}, tags = {SSE_SCHMID}, publisher = {ACM}, booktitle = {Proceedings of the 5th Symposium on Software Reusability (SSR '99)}, ISBN = {ISBN:1-58113-101-1}, DOI = {10.1145/303008.303063}, author = {Bayer, Joachim and Flege, Oliver and Knauber, Peter and Laqua, Roland and Muthig, Dirk and Schmid, Klaus and Widen, Tanya and DeBaud, Jean-Marc} } @Inproceedings { DeBaudSchmid99, title = {A Systematic Approach to Derive the Scope of Software Product Lines}, year = {1999}, pages = {34-43}, abstract = {Product line scoping is a critical activity because it elicits the common realms upon which the different products of a product line can be optimally engineered with respect to economies of scope. This, in turn, upper bounds the overall economic benefits that can be accrued from product line based development. Inherently, product line scoping is difficult because of the complexity of the factors that must be taken into account. Many are not known a priori. Traditional scoping approaches (from domain engineering) have focused on the notion of application domains. However, domains proved difficult to optimally scope and engineer from an enterprise standpoint because a domain captures extraneous elements that are of no interest to an enterprise which must focus on particular products, whether existing, under development, or anticipated. Hence, the domain view provides a flawed economic basis for making a scoping decision. We introduce in this paper PULSE-Eco, a technique especially developed to address the aforementioned issues. Its main characteristics are: a complete product-centric orientation done via product maps, the separation of concerns achieved through the definition and operationalization of strategical business objectives, and last, diverse types of analyses performed upon product maps allowing scoping decisions based on these objectives. We illustrate the technique with a running example.}, tags = {SSE_SCHMID}, editor = {Barry W. Boehm and David Garlan and Jeff Kramer}, publisher = {ACM}, booktitle = {Proceedings of the 21st International Conference on Software Engineering (ICSE '99)}, author = {DeBaud, Jean-Marc and Schmid, Klaus} } @Inproceedings { DeBaudSchmid98c, title = {PuLSE-Eco, a Context-based Approach to Scope a Software Product Line}, year = {1998}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the 2nd Annual Software Architectures in Product Line Acquisitions Workshop}, author = {DeBaud, Jean-Marc and Schmid, Klaus} } @Inproceedings { DeBaudSchmid98b, title = {Identifying and Evolving the Scope of Software Product Lines}, year = {1998}, pages = {69-72}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the ESI European Reuse Workshop (ERW '98)}, author = {DeBaud, Jean-Marc and Schmid, Klaus} } @Inproceedings { DeBaudSchmid98a, title = {A Practical Comparison of Major Domain Analysis Approaches: Towards a Customizable Domain Analysis Framework}, year = {1998}, pages = {128-131}, abstract = {When attempting to perform a domain analysis, practi tioners face a difficult choice. Which of the existing methods should be chosen and will it work in their particular envi ronment? A number of domain analysis approaches have been proposed in the literature. Most argue that they are appli cable to any domain and situation. Yet, we found that this was not always the case as illustrated by the practical situ ations our technology transfer group faced. We observed that depending on the context, each method possesses strengths and weaknesses. The optimal solution should then be to combine parts of these methods in a way specifically adapted to the project situation encountered. Using a case study where we applied three major ap proaches to a particular domain, we argue for a customiz able domain analysis approach that would be instantiated depending both on the nature of the domain(s) and on the project characteristics in which it would be applied.}, tags = {SSE_SCHMID}, booktitle = {Proceedings of the 10th International Conference on Software Engineering and Knowledge Engineering (SEKE '98)}, author = {DeBaud, Jean-Marc and Schmid, Klaus} } @Article { Schmid96a, title = {Making AI Systems more Creative: The IPC-Model}, journal = {Knowledge-Based Systems}, year = {1996}, volume = {9}, number = {6}, pages = {385-397}, abstract = {In this article, a model of information processing in human creativity, called the { IPC-model}, is presented. This model has been developed based on a review of psychological studies and models. Using this model as a baseline deficiencies of current AI systems are identified and several approaches for providing them with a higher level of creativity are proposed. A discussion of the range of applicability of these approaches and their implications for the overall system behaviour is provided.}, tags = {SSE_SCHMID}, DOI = {http://dx.doi.org/10.1016/S0950-7051(96)01049-0}, author = {Schmid, Klaus} } @Inproceedings { Schmid96b, title = {Towards Creative AI Systems: A Psychology-Based Approach}, year = {1996}, pages = {123-134}, tags = {SSE_SCHMID}, editor = {Linda Candy and Ernest A. Edmonds}, publisher = {LUTCHI Research Centre}, booktitle = {Proceedings of the 2nd International Symposium: Creativity and Cognition}, author = {Schmid, Klaus} } @Inproceedings { AbeckerSchmid96, title = {From Theory Refinement to Knowledge Base Maintenance: A Position Statement}, year = {1996}, abstract = {Since we consider theory refinement (TR) as a possible key concept for a methodologically clear view of knowledge-base maintenance, we try to give a structured overview about the actual state-of-the-art in TR. This overview is arranged along the description of TR as a search problem. We explain the basic approach, show the variety of existing systems and try to give some hints about the direction future research should go.}, tags = {SSE_SCHMID}, booktitle = {Workshop on Validation, Verification and Refinement of KBS at the European Conference on Artifical Intelligence (ECAI '96)}, author = {Abecker, Andreas and Schmid, Klaus} } @Inproceedings { SchmidFettig95, title = {Towards an Efficient Construction of Test Sets for Deciding Ground Reducibility}, year = {1995}, pages = {86-100}, abstract = {We propose a method for constructing test sets for deciding whether a term is ground reducible w.r.t. an arbitrary, many-sorted, unconditional term rewriting system. Our approach is based on a suitable characterization of such test sets using a certain notion of transnormality. It generates very small test sets and shows some promise to be an important step towards a practicable implementation.}, tags = {SSE_SCHMID}, editor = {Jieh Hsiang}, publisher = {Springer}, booktitle = {Proceedings of the 6th International Conference on Rewriting Techniques and Applications (RTA '95)}, author = {Schmid, Klaus and Fettig, Roland} } @Techreport { Schmid95, title = {Creative Problem Solving and Automated Discovery - An Analysis of Psychological and AI Research}, year = {1995}, number = {TM-95-04}, abstract = {Since creativity is the ability to produce something novel and unexpected, it has always fascinated people. Consequently, efforts have been made in AI to invent creative computer programs. At the same time much effort was spent in psychology to analyze the foundations of human creative behaviour. However, until now efforts in AI to produce creative programs have been largely independent from psychological research. In this study, we try to combine both fields of research. First, we give a short summary of the main results of psychological research on creativity. Based on these results we propose a model of creative process that emphasizes its information processing aspects. Then we describe AI approaches to the implementation of the various components of this model and contrast them with the results of psychological research. As a result we will not only reveal weakness of current AI systems hindering them in achieving creativity, but we will also make plausible suggestions - based on psychological research - for overcoming these weaknesses.}, tags = {SSE_SCHMID}, institution = {German Research Center for Artificial Intelligence (DFKI), Germany}, type = {Technical Memo}, author = {Schmid, Klaus} } @Techreport { Schmid93, title = {Ground Reducibility Tests - Even for Nonlinear Term Rewriting Systems}, year = {1993}, number = {SR-93-11 (SFB)}, tags = {SSE_SCHMID}, institution = {Fraunhofer IESE, Germany}, type = {SEKI Report}, author = {Schmid, Klaus} }