Patterns for Success in the Adoption and Execution of Feature‐based Product Line Engineering: A Report from Practitioners
Bibliographic record
Abstract
Abstract Systems and Software Product Line Engineering (PLE) is a general approach to engineer a portfolio of related products in an efficient manner, taking advantage of the products’ similarities while respecting and managing their differences. The approach manages a product portfolio as a single entity, as opposed to a multitude of separate products. Numerous resources describe the organizational benefits associated with incorporating PLE techniques and tools. Feature‐based System and Software Product Line Engineering is a specific form of PLE that is powered by commercial off‐the‐shelf automation, fully defined processes, and a formal language of variation based on features. Many case studies show the efficacy of Feature‐based PLE and the improvements in cost, schedule, and quality that can come with it. In this paper, practitioners from four of world's six largest defense companies highlight their experience with the practices that enable and inhibit success with this powerful engineering discipline.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.023 | 0.120 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.004 | 0.004 |
| Science and technology studies | 0.002 | 0.003 |
| Scholarly communication | 0.005 | 0.004 |
| Open science | 0.001 | 0.005 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".