COTS‐based software product line development
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
Purpose The purpose of this paper is to provide an overview of a pragmatic approach to components off‐the‐shelf (COTS)‐based development. Software product line (SPL) is at the forefront among the techniques for reducing costs, decreasing schedule time, and ensuring commonality of features across a family of products – as COTS are reused in multiple products. Design/methodology/approach A disciplined process for SPL development is still needed. This paper proposes the Y‐model for COTS‐based SPL development. The model put forward identifies and elaborates the essential phases and activities of SPL development from COTS‐based repository. Findings The Y‐model provides an efficient way of integrating the approaches of SPL and COTS‐based development as a cohesive software development model. Practical implications The model has the potential to tremendously increase software engineers' productivity. Thus, software architects, domain engineers and component designers should become aware of how to use these ideas to structure their models and designs. Originality/value This paper describes a systematic approach for COTS‐based development that takes into account the cataloguing and retrieval of software assets permeating a process that encompasses all stages of software development, from system product requirements engineering to system deployment.
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.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.003 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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 it