Forward Engineering
Forward Engineering
• Reference : https://canvas.instructure.com/courses/838884/pages/unit-3-lesson-6-reverse-engineering
Reverse Engineering Process
• a. Prediction
• What is the purpose of this product?
• How does it work?
• What market was it designed to appeal to?
• List some of the design objectives for the product.
• List some of the constraints that may have influenced the design.
Reverse Engineering Process
• b. Observation
• How do you think it works?
• How does it meet design objectives (overall)?
• Why is it designed the way it is?
• c. Disassemble
• How does it work?
• How is it made?
• How many parts?
• How many moving parts?
• Any surprises?
Reverse Engineering Process
• d. Analyze
• Carefully examine and analyze subsystems (i.e. structural,
mechanical, and electrical) and develop annotated sketches that
include measurements and notes on components, system design,
safety, and controls.
• e. Test
• Carefully reassemble the product.
• Operate the device and record observations about its
performance in terms of functionality (operational and
ergonomic) and projected durability.
Reverse Engineering Process
• f. Documentation
• Inferred design goals
• Inferred constraints
• Design (functionality, form (geometry), and materials)
• Schematic diagrams
• Lists (materials, components, critical components, flaws, successes,
etc.)
• Identify any refinements that might enhance the product’s usefulness.
• Upgrades and changes
A famous example of reverse-engineering involves San
Jose-based Phoenix Technologies Ltd., which in the
mid-1980s wanted to produce a BIOS for PCs that would
be compatible with the IBM PC's proprietary BIOS. (A
BIOS is a program stored in firmware that's run when a
PC starts up;
To protect against charges of having simply (and illegally)
copied IBM's BIOS, Phoenix reverse-engineered it using
what's called a "clean room," or "Chinese wall," approach.
First, a team of engineers studied the IBM BIOS—about
8KB of code—and described everything it did as
completely as possible without using or referencing any
actual code. Then Phoenix brought in a second team of
programmers who had no prior knowledge of the IBM
BIOS and had never seen its code. Working only from the
first team's functional specifications, the second team
wrote a new BIOS that operated as specified.
The resulting Phoenix BIOS was different from the IBM
code, but for all intents and purposes, it operated
identically. Using the clean-room approach, even if some
sections of code did happen to be identical, there was no
copyright infringement. Phoenix began selling its BIOS to
companies that then used it to create the first
IBM-compatible PCs.