MétaCan
Menu
Back to cohort
Record W1972462572 · doi:10.1504/ijqet.2009.031130

Kano-based Six Sigma utilising quality function deployment

2009· article· en· W1972462572 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueInternational Journal of Quality Engineering and Technology · 2009
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicQuality Function Deployment in Product Design
Canadian institutionsUniversity of New Brunswick
Fundersnot available
KeywordsSix SigmaQuality function deploymentSoftware deploymentQuality (philosophy)Function (biology)SigmaEngineeringReliability engineeringComputer scienceOperations managementPhysicsSoftware engineering

Abstract

fetched live from OpenAlex

For any company, the continuous and timely development of new products, which include creative features expected to satisfy customers, is essential to stay competitive. Currently, companies are not only aiming at satisfying customers, but also at delighting them. In fact, some companies aim at customers' loyalty, such that they only buy and recommend their products. Thus, it is important to attain a comprehensive understanding of the dynamic requirements of customers. One of the key models used to achieve that is Kano model. It strengthens Six Sigma and enhances customer satisfaction. Six Sigma is used to reduce variability. This leads to an almost defect-free level which is the focus of the design for Six Sigma (DFSS) approach in building quality upstream. This level can be essential to customers but may not always be economic. Therefore, it is important to understand customer needs and the company's own capabilities. In this paper, an integrated approach to product development is proposed using a Kano-based Six Sigma, which utilises Six Sigma structure and quality function deployment (QFD). This approach will contribute to the innovation of new and existing products or services.

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 imitation

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

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.505
Threshold uncertainty score0.750

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.029
GPT teacher head0.281
Teacher spread0.252 · 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