Document No. 3 — Reverse Engineering and Reconstruction of Design Logic
Principles of This Document
Principle 1 — Reverse Engineering Goes Beyond Measurement
The objective is to reconstruct the engineering decisions that led to the component’s existing shape and performance.
Principle 2 — Understanding the Component Before Measurement
The component’s function, place of use, history, condition, repairs, and available documentation must be understood before carrying out precise measurements.
Principle 3 — Distinguishing Reconstruction from Redesign
When design information is unavailable, the boundary between reconstructing the existing design and redesigning the component must be clearly defined.
Principle 4 — Reconstructing the Design Philosophy
It must be determined whether the component was designed to prevent failure, allow controlled failure, provide warning before failure, or achieve a specified service life.
Principle 5 — Material Characteristics Are Determined by Multiple Factors
Chemical composition alone does not determine material behavior. The process, heat treatment, coating, and service conditions also have an influence.
Principle 6 — Reconstruction Before Improvement
The existing logic must first be reconstructed. Only then, if sufficient grounds exist, should an improved solution be designed.
Principle 7 — Validating the Prototype Under Actual Conditions
The prototype must be tested under actual operating conditions, and the test results must be used in developing the next prototype.
Principle 8 — Project Evidence Takes Precedence Over External Clues
Reference samples, manufacturers, and external sources should be treated as leads, and their claims must be validated against project evidence.
Principle 9 — Every Test Must Address an Engineering Question
The selection of tools and tests must be purposeful and appropriate to the engineering question being addressed.
Principle 10 — Documentation Is Essential to Converting Experience into Organizational Knowledge
Experience must be recorded in the engineer’s logbook, project file, and a retrievable archive.