Tolerance Design¶
Creveling, C. M. (1997). Tolerance Design: A Handbook for Developing Optimal Specifications. Addison-Wesley.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Gold Plating
- Software delivery — an engineer adds a feature beyond the sprint scope and QA, ops, documentation, and support silently inherit it. Construction — a contractor over-specifies materials or workmanship beyond contract, then blames the client on change orders for "not appreciating" the upgrade. Public-policy implementation — an agency adds eligibility checks not in the legislation, which harden into unbudgeted operational debt. Research-program execution — a PI adds a side experiment beyond the grant scope, consuming budget the funded aims needed. Manufacturing and engineering specs — a part held to a tolerance tighter than its function requires, raising rework rate with no fit-for-purpose gain
This sourceEstablishes the economics of tolerance specification: tightening a tolerance beyond what the function requires raises scrap and rework cost without improving fitness for purpose.
- Software delivery — an engineer adds a feature beyond the sprint scope and QA, ops, documentation, and support silently inherit it. Construction — a contractor over-specifies materials or workmanship beyond contract, then blames the client on change orders for "not appreciating" the upgrade. Public-policy implementation — an agency adds eligibility checks not in the legislation, which harden into unbudgeted operational debt. Research-program execution — a PI adds a side experiment beyond the grant scope, consuming budget the funded aims needed. Manufacturing and engineering specs — a part held to a tolerance tighter than its function requires, raising rework rate with no fit-for-purpose gain
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:2dafda771de5 · see in the full table