Each of the three UML Designer semantic models (requirements, analysis, and design) represents a different level of abstraction, and each has its own set of model elements. Although these elements represent distinct objects, in many cases there is a logical correspondence between an element at one level of abstraction and an element at the next level. For example, a Thing element (requirements model) typically corresponds to a Protocol element (analysis model), which in turn corresponds to a class (design and implementation model).
UML Designer provides transform capabilities that can map between model elements at a different levels of abstraction. Transforming takes the selected element, creates its corresponding element or elements, and automatically creates a traceability link between them.
Transforms exist for both the "forward" mapping (requirements > analysis > design) and the "backward" mapping (reverse engineering). "Forward" transforms include: