Business Process Model
(BPM)

A Business Process Model (BPM) helps you identify, describe, and decompose business processes. You can analyze your system at various levels of detail, and focus on control flow (the sequence of execution) or data flow (the exchange of data). You can choose from a number of process languages, including BPEL and BPMN.

Data Movement Model
(DMM)

A Data Movement Model (DMM) provides a global view of the movement of information in your organization. You can analyze and document where your data originates, where it moves to, and how it is transformed along the way, including replications and ETL.

Using a Data Movement Model, you can generate SQL scripts to replicate data via a Replication Server. You can create a data movement model from the mappings between PDMs.

Prior to PowerDesigner 15.3, the Data Movement Model was called the Information Liquidity Model (ILM).

Enterprise Architecture Model
(EAM)

An Enterprise Architecture Model (EAM) helps you analyze and document your organization and its business functions, along with the applications and systems that support them, and the physical architecture on which they are implemented.

Free Model
(FEM)

A Free Model (FEM) provides a context-free environment for modeling any kind of objects or systems. It is generally associated with a set of extensions that allow you to define your own concepts and graphical symbols.

Impact and Lineage Model
(IAM)

An Impact And Lineage Model (IAM) is a permanent graphical record of dependencies between model objects. When you perform an action on a model object, you can use:

Impact Analysis – to analyze the effect of the action on the objects that depend on the initial object

Lineage Analysis – to identify the objects that influence the initial object

The use of analysis rule sets allows you to tailor the information that is presented for model objects.

Multimodel Report
(MMR)

A Multimodel Report (MMR) is a PowerDesigner report that can document any number of models together and show the links between them. To create such a report, you must have at least one model open in the workspace, and you can add additional models at any time.

Object-Oriented Model
(OOM)

An Object-Oriented Model (OOM) helps you analyze an information system through use cases, structural and behavioral analyses, and in terms of deployment, using the Unified Modeling Language (UML). You can reverse-engineer, model, and generate for XML, Java, .NET and other languages.

Requirements Model
(RQM)

A Requirements Model (RQM) helps you analyze any kind of written requirements and link them to the users and groups who will implement them, and with analysis and design objects in other models. You can use an RQM to represent any structured document (e.g. functional specification, test plan, business goals, etc.) and import and export hierarchies of requirements as MS Word documents.

You can import objects from other types of models as requirements, and also generate different objects, such as entities, from requirements into other types of models.

XML Model
(XSM)

An XML Model (XSM) helps you analyze an XML Schema Definition (.XSD), Document Type Definition (.DTD), or XML-Data Reduced (.XDR) file. You can model, reverse-engineer, and generate each of these file formats.