AN OBJECT-ORIENTED PATTERN LANGUAGE FOR ENGINEERING DESIGN
Bibliographic record
Abstract
Psychological inertia, biases and incomplete knowledge can lead engineering designers to choose a sub-optima design. The use of design patterns can help engineering designers find better solutions. Design patterns are recurring/reusable design solutions that are known to work in a particular design situation or a context. Patterns represent both recurring problems and recurring solutions together with their relationships. A design pattern language is a collection of related design patterns covering a particular design domain. This paper describes an object-oriented framework and methodology for the construction and use of pattern languages for the design of technical systems. Key words: Engineering design patterns; Engineering design pattern language; Engineering design; object-orientation.
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.008 | 0.013 |
| Meta-epidemiology (narrow) | 0.003 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.003 | 0.006 |
| Science and technology studies | 0.002 | 0.003 |
| Scholarly communication | 0.006 | 0.009 |
| Open science | 0.004 | 0.003 |
| Research integrity | 0.003 | 0.007 |
| Insufficient payload (model declined to judge) | 0.018 | 0.012 |
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".