Reverse-Engineering Task

A Reverse-Engineering Task is an engineering task that requires the translation of a designed system into a system specification.

• Context:
  • Task Input: Designed System, System Artifact
    • Optional Input: Domain Knowledge, Analysis Tool, Reference Documentation
  • Task Output: System Specification, Design Documentation, Reverse-Engineered System
  • Task Performance Measure: Reverse-Engineering Accuracies such as reverse-engineering completeness, reverse-engineering fidelity, and reverse-engineering analysis time
  • ...
  • It can typically analyze Unknown System through reverse-engineering techniques.
  • It can typically extract Design Pattern from reverse-engineering targets.
  • It can typically reconstruct System Architecture through reverse-engineering investigations.
  • It can typically identify Component Relationship through reverse-engineering analysiss.
  • It can typically recover Implementation Logic through reverse-engineering examinations.
  • It can typically parse System Structure through reverse-engineering parsing methods.
  • ...
  • It can often generate Functional Model from reverse-engineering findings.
  • It can often create Technical Documentation from reverse-engineering results.
  • It can often develop Compatibility Specification through reverse-engineering insights.
  • It can often produce Security Assessment via reverse-engineering evaluations.
  • It can often support Model-Driven Development through reverse-engineering specifications.
  • It can often enable Free Software Development through reverse-engineering compatibility analysiss.
  • ...
  • It can range from being a Simple Reverse-Engineering Task to being a Complex Reverse-Engineering Task, depending on its reverse-engineering target complexity.
  • It can range from being a Static Reverse-Engineering Task to being a Dynamic Reverse-Engineering Task, depending on its reverse-engineering analysis approach.
  • It can range from being a Manual Reverse-Engineering Task to being an Automated Reverse-Engineering Task, depending on its reverse-engineering automation level.
  • ...
  • It can integrate with Analysis Framework for reverse-engineering workflow automation.
  • It can connect to Documentation System for reverse-engineering knowledge management.
  • It can support Development Environment for reverse-engineering result integration.
  • It can utilize Reverse-Engineering Algorithms for reverse-engineering process automation.
  • ...
• Examples:
  • Software Reverse-Engineering Tasks, such as:
    • Program Structure Reverse-Engineering Tasks, such as:
      • Software Program Structure analysis for reverse-engineering code architectures.
      • Parsing Tasks for reverse-engineering syntax structures.
    • Legacy System Reverse-Engineering Tasks, such as:
      • CASE Tool Reverse-Engineering Tasks for reverse-engineering software models.
      • Free Software Reverse-Engineering Tasks for reverse-engineering compatibility interfaces.
  • Biological Reverse-Engineering Tasks, such as:
    • Neural System Reverse-Engineering Tasks, such as:
      • Brain Reverse-Engineering Tasks for reverse-engineering neural networks.
      • Blue Brain Project tasks for reverse-engineering cortical columns.
    • Cognitive Reverse-Engineering Tasks, such as:
      • Psychological Nativism analysis for reverse-engineering innate structures.
      • Decision-Making Utility Function analysis for reverse-engineering preference structures.
  • Hardware Reverse-Engineering Tasks, such as:
    • Circuit Analysis Reverse-Engineering Tasks, such as:
      • PCB Layout Reverse-Engineering Task for reverse-engineering electronic circuit designs.
      • IC Function Reverse-Engineering Task for reverse-engineering chip functionalitys.
    • Physical System Reverse-Engineering Tasks, such as:
      • Mechanical Component Reverse-Engineering Task for reverse-engineering physical parts.
      • Manufacturing Process Reverse-Engineering Task for reverse-engineering production methods.
  • Protocol Reverse-Engineering Tasks, such as:
    • Network Protocol Reverse-Engineering Tasks, such as:
      • Communication Protocol Reverse-Engineering Task for reverse-engineering message formats.
      • Encryption Algorithm Reverse-Engineering Task for reverse-engineering security mechanisms.
    • File Format Reverse-Engineering Tasks, such as:
      • Proprietary Format Reverse-Engineering Task for reverse-engineering data structures.
      • Legacy Format Reverse-Engineering Task for reverse-engineering historical file types.
  • ...
• Counter-Examples:
  • Forward Engineering Tasks, which create new systems from requirements rather than analyzing existing systems.
  • Black Box Testing Tasks, which test functionality without examining internal structure or implementation.
  • System Documentation Tasks, which record known design information rather than discovering unknown design.
  • Code Review Tasks, which examine source code for quality assurance rather than understanding unknown implementation.
• See: Engineering Task, Analysis Task, System Analysis, Design Recovery, Reverse Engineering, Computer-Aided Software Engineering Task.

---

---

References

2013

• http://en.wikipedia.org/wiki/Reverse_engineering
  • Reverse engineering is the process of discovering the technological principles of a device, object, or system through analysis of its structure, function, and operation. It often involves taking something (a mechanical device, electronic component, computer program, or biological, chemical, or organic matter) apart and analyzing its workings in detail to be used in maintenance, or to try to make a new device or program that does the same thing without using or simply duplicating (without understanding) the original.

    Reverse engineering has its origins in the analysis of hardware for commercial or military advantage. The purpose is to deduce design decisions from end products with little or no additional knowledge about the procedures involved in the original production. The same techniques are subsequently being researched for application to legacy software systems, not for industrial or defence ends, but rather to replace incorrect, incomplete, or otherwise unavailable documentation.

1990

• (Chikofsky & Cross II, 1990) ⇒ Elliot J. Chikofsky, and James H. Cross II. (1990). “Reverse Engineering and Design Recovery: A Taxonomy.” In: IEEE Software Journal, 7(1). doi:10.1109/52.43044

---