NClass is missing several major features like undo or round-trip engineering which are frequently requested.

It can reverse engineer diagrams from code, and provide round-trip engineering for various programming languages.

Round-trip engineering is often wrongly defined as simply supporting both forward and reverse engineering.

Metamill is a round-trip engineering tool.

Another characteristic of round-trip engineering is automatic update of the artifacts in response to automatically detected inconsistencies.

Model-driven software development (MDSD) is an alternative to round-trip engineering.

The prototype implementation supports automated round-trip engineering of Eclipse plug-ins that implement workbench parts and part interactions.

Round-trip engineering is the concept of being able to make any kind of change to a model as well as to the code generated from that model.

Perhaps the most common form of round-trip engineering is synchronization between UML (Unified Modeling Language) models and the corresponding source code.

With advances in technology from large platform vendors, the vision of BPM models becoming fully executable (and capable of simulations and round-trip engineering) is coming closer to reality.

Round-trip engineering (RTE) is a functionality of software development tools that synchronizes two or more related software artifacts, such as, source code, models, configuration files, and other documents.

Round-trip engineering is critical for maintaining consistency among multiple models and between the models and the code in Object Management Group's (OMG) Model-driven architecture.

The need for round-trip engineering arises when the same information is present in multiple artifacts and therefore an inconsistency may occur if not all artifacts are consistently updated to reflect a given change.

Pragmatic MDA blends the literal standards from OMG's MDA with more traditional model driven mechanisms such as round-trip engineering that provides support for adapting implementation artifacts.

In fact, the key characteristic of round-trip engineering that distinguishes it from forward and reverse engineering is the ability to synchronize existing artifacts that evolved concurrently by incrementally updating each artifact to reflect changes made to the other artifacts.

Round-trip engineering refers to the ability of a UML tool to perform code generation from models, and model generation from code (a.k.a., reverse engineering), while keeping both the model and the code semantically consistent with each other.

A more tractable form of round-trip engineering is implemented in the context of framework application programming interfaces (APIs), whereby a model describing the usage of a framework API by an application is synchronized with that application's code.