MétaCan
Menu
Back to cohort
Record W3040286910 · doi:10.1017/dsj.2020.16

Set-based design: a review and new directions

2020· review· en· W3040286910 on OpenAlexaff
Boris Toche, Robert Pellerin, Clément Fortin

Bibliographic record

VenueDesign Science · 2020
Typereview
Languageen
FieldEngineering
TopicManufacturing Process and Optimization
Canadian institutionsPolytechnique Montréal
Fundersnot available
KeywordsComputer scienceDocumentationNew product developmentEnablingProcess (computing)Set (abstract data type)Process managementManagement scienceSystems engineeringKnowledge managementEngineering

Abstract

fetched live from OpenAlex

Set-based design (SBD), sometimes referred to as set-based concurrent engineering (SBCE), has emerged as an important component of lean product development (LPD) with all researchers describing it as a core enabler of LPD. Research has explored the principles underlying LPD and SBCE, but methodologies for the practical implementation need to be better understood. A review of SBD is performed in this article in order to discover and analyse the key aspects to consider when developing a model and methodology to transition to SBCE. The publications are classified according to a new framework, which allows us to map the topology of the relevant SBD literature from two perspectives: the research paradigms and the coverage of the generic creative design process (Formulation–Synthesis–Analysis–Evaluation–Documentation–Reformulation). It is found that SBD has a relatively low theoretical development, but there is a steady increase in the diversity of contributions. The literature abounds with methods, guidelines and tools to implement SBCE, but they rarely rely on a model that is in the continuum of a design process model, product model or knowledge-based model with the aim of federating the three Ps (People–Product–Process) towards SBCE and LPD in traditional industrial contexts.

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 imitation

Not 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.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.005
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.008
Threshold uncertainty score0.026

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.005
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0020.001
Bibliometrics0.0050.007
Science and technology studies0.0010.001
Scholarly communication0.0030.004
Open science0.0020.001
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0080.002

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.

Opus teacher head0.122
GPT teacher head0.316
Teacher spread0.194 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreReview

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".

Quick stats

Citations38
Published2020
Admission routes1
Has abstractyes

Explore more

Same venueDesign ScienceSame topicManufacturing Process and OptimizationFrench-language works237,207