The product line and component-based approaches to software engineering both hold the potential to significantly increase the level of reuse in industrial software development and maintenance. They also have complementary strengths, since they address the problem of reuse at opposite ends of the granularity spectrum; product line development essentially supports "reuse in the large" while component based development supports "reuse in the small." This paper describes a method, KobrA, that cleanly integrates the two paradigms into a systematic, unified approach to software development and maintenance. Key synergies resulting from this integration include support for the rapid and flexible instantiation of system variants, and the provision of methodological support for componentbased framework development.

No abstract

International audienceIn this chapter we present an improved and simplified metamodel for product line variability. This model has been consolidated from diverse approaches in the earlier research projects ESAPS, CAF and other existing work, supplied with recent research in FAMILIES. The consolidated metamodel aims to be the starting point for standardization. A standard will lay the grounds for commercial and open-source tool support. We present here a prototype tool based on the metamodel. To put the work in context, we present three different approaches for capturing variability: using standard languages (exemplified by UML 2.0), using annotations to standard languages, and using domain-specific languages. We use the same Watch example to present how variability is handled in all three approaches

This is the unspecified version of the paper.This version of the publication may differ from the final published version.Permanent repository link: http://openaccess.city.ac.uk/281/ Link to published version: http://dx. AbstractReusing assets during application engineering promises to improve the efficiency of systems development. However, in order to benefit from reusable assets, application engineering processes must incorporate when and how to use the reusable assets during single system development. However, when and how to use a reusable asset depends on what types of reusable assets have been created.Product line engineering approaches produce a reusable infrastructure for a set of products. In this paper, we present the application engineering process associated with the PuLSE product line software engineering method -PuLSE-I. PuLSE-I details how single systems can be built efficiently from the reusable product line infrastructure built during the other PuLSE activities.

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 (&oduct 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) Corn 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.