Your project may contain one or more framework diagrams and/or a framework matrix, which direct how your project should be built.
- A framework diagram - lets you model a framework with nodes and links, which you can style as necessary.
- Framework matrix - lets you model a framework in a matrix, in which columns usually represent various aspects of the enterprise that can be described or modeled, and the rows represent various viewpoints from which the aspects can be described. Each cell formed by the intersection of a column and a row represents an aspect of the enterprise modeled from a particular viewpoint.
PowerDesigner provides a set of predefined framework diagrams and matrices, and users with framework design rights can also create their own (see Designing Framework Diagrams and Matrices). You complete a framework diagram or matrix by creating (or adding existing) documents in nodes, cells, and additional areas according to predefined rules:
-
Documents — can be of different types and can each be associated with multiple nodes, cells, and additional areas:
-
Model – a PowerDesigner model, such as a BPM or a PDM, created from scratch, based on a template, or generated from another model.
-
Diagram – a PowerDesigner model diagram, such as an OOM use case diagram.
-
Dependency matrix – a grid that displays the links between model objects (see Dependency Matrices).
-
List – a list of PowerDesigner model objects, such as BPM processes, or PDM tables.
-
File – an external file, such as a .doc or .txt file.
-