https://onlinelibrary.wiley.com/doi/pdf/10.1002/stvr.247

Problem frames: analyzing and structuring software development problems. By Michael Jackson. Published by Addison‐Wesley, Boston, Massachusetts, U.S.A., ACM Press Series, 2001. ISBN: 0‐201‐59627‐X, 390 pages. Price: U.K. ?32.95, U.S.A. $49.99, soft cover.

/pdf/software-product-lines-in-action-1cemejsm3o.pdf

Software product lines in action

https://www.cin.ufpe.br/~in1037/AllFinal/SE46%20Khurum%202009.pdf

A systematic review of domain analysis solutions for product lines

Scoping can be defined as the process of deciding in which parts of an organization's products, features and domains systematic reuse is economically useful. It generally is the first phase in product line engineering. For a decade now scoping has been recognized as a discipline of it's own in product line engineering. So it's time to look at what has been done in scoping in the last years and what is still to be done. In this survey, we identify and characterize existing scoping approaches with the main goal to derive open areas and research questions for further research in scoping. We analyze and compare existing approaches and derive open and partially addressed research questions that can be tackled by researchers in product line engineering in the next years.

A decade of scoping: a survey

It is often believed that reusable solutions, being generic, must necessarily compromise performance In this paper, we consider a family of Role-Playing Games (RPGs) We analyzed similarities and differences among four RPGs By applying a reuse technique of XVCL, we built an RPG product line architecture (RPG-PLA) from which we could derive any of the four RPGs We built into the RPG-PLA a number of performance optimization strategies that could benefit any of the four (and possibly other similar) RPGs By comparing the original vs the new RPGs derived from the RPG-PLA, we demonstrated that reuse allowed us to achieve improved performance, both speed and memory utilization, as compared to each game developed individually At the same time, our solution facilitated rapid development of new games, for new mobile devices, as well as ease of evolving with new features the RPG-PLA and custom games already in use

Reuse without compromising performance: industrial experience from RPG software product line for mobile devices

A Product Line Potential Analysis enables us to make a quick decision as to whether the product line approach (PLA) is suitable for a given set of products and target market. The PLA framework offers no support for this as yet.

/pdf/product-line-potential-analysis-45sbjqoftq.pdf

Product Line Potential Analysis

A Product Line Potential Analysis enables us to make a quick decision as to whether the product line approach (PLA) is suitable for a given set of products and target market. The PLA framework offers no support for this as yet. A Product Line Potential Analysis is executed in a half-day workshop. A structured interview based on a questionnaire examines products, software, markets, and customers. The answers are compared to a set of criteria for the applicability of the PLA. The analysis results primarily in one of these decisions: yes (the PLA is suitable for these products and markets), no, or investigation required. Up to now, our team has performed four Product Line Potential Analyses. We present the list of criteria, a part of our questionnaire, and the workshop format. We discuss Product Line Potential Analysis in the light of related work and its limits and lessons learned, and we look at future work.

For more than ten years we have developed and maintained a software product line of legal expert systems. They share certain func- tionality, such as interaction with the user by means of a graphical in- terface, capturing data, storing information in a database, and printing documents. They differ mainly in two points: Domain descriptions and technical infrastructure. When we designed the architecture for this software product line, we focused on two requirements in particular: Domain experts should be involved in development, but should not have to learn a general-purpose programming language. Changes in domain descriptions should leave technical code untouched - and vice versa. Using a meta-level architecture we achieved a sound decoupling: Domain descriptions are kept in the meta level. Appropriate engines included in the base level act according to these descriptions. We present the four meta-level mechanisms which we have developed for the design of this software product line. They separate domain de- scriptions from technical code in the following areas: data reference and access, input and output control, application and domain logic, and user command control.

Four Mechanisms for Adaptable Systems A Meta-Level Approach to Building a Software Product Line

For more than ten years we have developed and maintained a software product line of legal expert system. They share certain functionality, such as interaction with the user by means of a graphical interface, capturing data, storing information in a database, and printing documents. They differ mainly in two points: Domain descriptions and technical infrastructure. When we designed the architecture for this software product line, we focused on two requirements in particular: Domain experts should be involved in development, but should not have to learn a general-purpose programming language. Changes in domain descriptions should leave technical code untouched - and vice versa. Using a meta-level architecture we achieved a sound decoupling: Domain descriptions are kept in the meta level. Appropriate engines included in the base level act according to these descriptions. We present the four meta-level mechanisms which we have developed for the design of this software product line. They separate domain descriptions from technical code in the following areas: data reference and access, input and output control, application and domain logic, and user command control.

Four mechanisms for adaptable systems: A meta-level approach to building a software product line

For more than ten years we have developed and maintained a software product line of legal expert systems. They share certain functionality, such as interaction with the user by means of a graphical interface, capturing data, storing information in a database, and printing documents. They differ mainly in two points: Domain descriptions and technical infrastructure.

Claudia Fritsch

Papers

Product Line Potential Analysis

Product Line Potential Analysis

Four Mechanisms for Adaptable Systems A Meta-Level Approach to Building a Software Product Line

Four mechanisms for adaptable systems: A meta-level approach to building a software product line

Four Mechanisms for Adaptable Systems