Chapter 3 Projects and Framework Matrices

Completing a Framework Matrix

Your project may contain a framework matrix, which directs how the project should be built.

In the following example of the FEAF framework matrix template, the content of the cells in the Planner's View row specifies the scope of the enterprise and identifies what should be modeled:

A framework matrix is a grid in which each cell must be completed according to predefined rules. PowerDesigner provides a set of predefined framework matrices, and users with framework matrix rights can also create their own (see Designing Framework Matrices).

You complete the framework matrix by creating (or adding existing) documents in cells and additional areas:

Documents — can be of different types and can each be associated with multiple 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" in the Diagrams and Symbols chapter).
- 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.

Cells — [when active] must be completed by particular kinds of documents.
Additional areas — can be defined outside of the grid (for example, the global view in the FEAF framework matrix that is created at the end of the enterprise architecture implementation).