0% found this document useful (0 votes)
188 views8 pages

Forward Engineering

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
188 views8 pages

Forward Engineering

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Forward Engineering

Forward Engineering is the standard way of developing software by


understanding the requirements, specifications and developing the
software or system by following an SDLC.
SDLC will consist of all the phases of software development ie
1. Requirements
2. Analysis and Design
3. Implementation and Testing
4. Maintenance
Reverse Engineering
• Reverse Engineering is also known as backward engineering. The
information regarding the software, application is collected. Then the
application is disintegrated, and knowledge about the application is
obtained.
• Steps for reverse engineering
• 1. Existing software
• 2. Understanding the software
• 3. Re-engineering the software/system
• Question : Difference between Forward and Reverse Engineering
Reasons for reverse engineering
1. The original manufacturer of a product no longer produces a product
2. There is inadequate documentation of the original design
3. The original manufacturer no longer exists, but a customer needs the product
4. The original design documentation has been lost or never existed
5. Some bad features of a product need to be designed out. For example, excessive wear might indicate where a product should be improved
6. To strengthen the good features of a product based on long-term usage of the product
7. To analyze the good and bad features of competitors' product
8. To explore new avenues to improve product performance and features
9. To gain competitive benchmarking methods to understand competitor's products and develop better products
10. The original CAD model is not sufficient to support modifications or current manufacturing methods
11. The original supplier is unable or unwilling to provide additional parts
12. The original equipment manufacturers are either unwilling or unable to supply replacement parts, or demand inflated costs for sole-source
parts
13. To update obsolete materials or antiquated manufacturing processes with more current, less-expensive technologies

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

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy