design recovery

design recovery

(process)
A subtask of reverse engineering in which domain knowledge, external information, and deduction of fuzzy reasoning are added to the observations of the subject system to identify meaningful higher level abstractions beyond those obtained directly by examining the system itself.

In other words, design recovery aims to work out what a system or component was designed to do rather than just examining its subcomponents and their interrelationships.
This article is provided by FOLDOC - Free Online Dictionary of Computing (foldoc.org)
References in periodicals archive ?
Simulations based on the testwork results support an overall plant design recovery of 85% when targeting a 6.0% Li2O spodumene concentrate product.
"Design recovery by automated search for structural design patterns in object- oriented software." In Reverse Engineering, 1996, Proceedings of the Third Working Conference on, pp.
P., Wendehals, L., and Welsh, J."Towards pattern-based design recovery." In Proceedings of the 24th international conference on Software engineering, pp.
However, due to unexpectedly high chlorine concentrations in the processing water and equipment failures, the plant was shut down in late December and is currently operating at 60% of design throughput and up to 14 ppts below design recovery (80-85%).
While we are extremely pleased with these operating results, particularly as they relate to our ability to contain costs and operate the upgraded concentrator at design recovery rates for copper, mine management recognises that further upside exists with improved recovery rates from our molybdenum circuit and increased reliability and throughput of the SAG mill.
From the 22nd IEEE International Conference on Software Maintenance held in Philadelphia in September 2006, this volume compiles the proceedings, consisting of biographies of the three keynote speakers, 45 papers, panels, dissertation forums, and working sessions on source-code analysis, testing, software evolution and integration, software migration, metrics, and architectural design recovery. Other sessions cover interfaces, change impact analysis, runtime integration, open source, cross-cutting, UML models, tool demos, program comprehension, concept location, safety security faults, reengineering, and design quality.
Nowadays reengineering is divided into several areas: systems reengineering (for hardware and software), software reengineering (including reverse engineering and design recovery technology), business process reengineering, and infrastructure reengineering.
The full papers explore new approaches to migrating systems to service-oriented architecture, system analysis and testing, dynamic analysis, system refactoring, design recovery, and system assessment.
This volume consists of 55 full papers and 25 short papers presented at the September 2005 conference on source code analysis, testing, software evolution and integration, software migration, metrics, and architectural design recovery. The researchers propose annotated inclusion constraints for precise flow analysis, an automated technique for feature location, an Eclipse plug-in debugging tool for Java programs, a support tool for modeling reconfigurations to complex systems.

Full browser ?