Example for submitting a reference to a paper in a conference proceedings

 
 


Your e-mail address:  


Mandatory fields

Please use "and" as an author separator as in: E. Chikofksy and
James Cross.

Authors:              

Title:                

Booktitle:            

Publisher:            

Year:                 




Optional fields

Editors:              

Pages:                

Address:              

Month:                


If the contents of your reference is available via the web, please add
the link information here:

URL:                  




Abstract:  
 The field of software reengineering is growing rapidly in response to
the critical need that exists in the software industry for technology
to support legacy system maintenance and evolutionary development of
new systems.  As the field matures, it is essential to achieve
coherence across the many research efforts that are underway to
develop technology to support reengineering. In particular, for
reengineering research to have an impact on actual reengineering
practice, we need to achieve a consensus on the fundamental goals and
products of reengineering research and how they relate to
practitioners' needs, how to assess value and evaluate progress in the
field, and how to facilitate communication among researchers and, more
importantly, between researchers and practitioners. This paper
proposes an infrastructure for drawing together work in the field, to
coordinate and leverage our efforts and to encourage measurable
progress.   


Keywords:                


Your personal note to this reference: 

This paper initiates a common effort in the reverse engineering
community to setup a research infrastructure. The TCSE reverse
engineering bibliography is one project within this infrastructure
project. One should really read this paper. 




Classification:

The classification list box below contains a hierarchy of reengineering-related terms. The indentation (stressed by dots) indicates the subclass relation. Choose any item you find appropriate by clicking on it. Clicking twice on the same item unselects it. Note that a parent class is automatically selected if you select one of its subclasses. Furthermore, you can select different classes for the same reference by multiple choices. Please be as specific as possible.

We tried to select terms that are as self-explanatory as possible. If something is not clear just see the general description of the taxonomy.

Reengineering_in_General

· Reengineering_Collections

· Introductions_to_Reengineering

· Fundamentals

· The_Pros_and_Cons_and_Risks_of_Reengineering

· Experiences

· Process_Models

· Management

· Legality

Reverse_Engineering

· General_Information_on_Reverse_Engineering

· Reverse_Engineering_Collections

· Cognitive_Processes_in_Human_Program_Understanding

· Software_Evolution

· Extracting_Business_Rules

· Intermediate_Representations_of_Source_Code

· · Use_of_data_bases

· · Using_graphs

· Preventive_Measures

· Formal_Methods

· Reverse_Specification

· · Domain_Analysis

· · Model_Generating

· · Software_Animation

· · · Visualization_of_Parallel_and_Distributed_Programs

· · · Visualization_for_Program_Understanding_and_Debugging

· · · Visualizing_Object-Oriented_Programs

· · · Algorithm_Animation

· · · Information_Visualization_and_Visualization_of_Large_Systems

· · · 3D_Computation_Visualization

· · · Empirical_Studies_of_Software_Visualization

· · · Animation_in_User_Interfaces

· · Natural_Language_Processing_in_Reverse_Specification

· · Requirement_Tracability

· Reverse_Design

· · General_Information_about_Reverse_Design

· · Process_Models_for_Reverse_Design

· · Fundamental_Methods_in_Reverse_Design

· · · Code_Views

· · · Reformatting_and_Markup_Languages

· · · Hypertext

· · · Static_Analysis

· · · · Static_Control_Flow_Analysis

· · · · Static_Data_Flow_Analysis

· · · Dynamic_Analysis

· · · · Dynamic_Control_Flow_Analysis

· · · · Dynamic_Data_Flow_Analysis

· · · Source_Code_Queries

· · · Data-Centered_Program_Understanding

· · · Program_Slicing

· · · Others

· · Metric-Based_Methods_in_Reverse_Design

· · · Metrics

· · · · Maintenance_Metrics

· · · · Module_Cohesion

· · · Automated_Reverse_Design

· · Functional_Abstraction

· · Configuration_Structures

· · Knowledge-Based_Concept_Assignment

· · · Program_Plan_Assignment_by_Parsing

· · · · Recognizer

· · · · UNPROG

· · · Human_Oriented_Concept_Assignment_by_Informal_Reasoning

· · Encapsulation_and_Finding_Objects_in_Legacy_Code

· · System_Modularization

· · Recovery_of_Software_Architecture

· Reverse_Engineering_Tools

· · VIFOR

· · LOGISCOPE

· · SEELA

· · Rigi

· Re-Use

Alteration

· Re-Code

· · Control_Flow_Normalization

· · Program_Transformations

· · · Source-to-Source-Translation

· Re-Design

· · Introduction_of_Abstract_Data_Types

· · From_Procedural_to_Object-Oriented

· · Inter-module_Reorganization

· · Inhertiance_Hierarchies_Restructuring

· · From_Sequential_to_Concurrent_Execution

· · From_Mainframe_to_Client-Server_Architecture

· · User_Interface_Migration

· · Database_Migration

· Re-Specify

· Change_Impact

· Change_Test

· Differences_between_Source_Code_Versions

Reengineering_Tools

· User_Interfaces_for_Reengineering_Tools

· Surgeon_s_Assistant

· Maintainer_s_Assistant

Year_2000_Problem

Unresolved_References