Preconditions

• Process updates need to preserve the element identities. Do not use the “adopt elements” option when importing a core process.
• The scrope of the phase to freeze needs to be defined.
• Children of a process element are paths of their parent and therefore must be part of the same phase as the parent element.
• Metrics cannot be frozen, as they can have arbitrary data sources.
• Roles cannot be frozen, as they are responsible for permission management and freezing them would prevent e.g. revoking permissions. However you can freeze a role association.
• It is not possible to freeze process enactments.
• Resources that are inlined in process element descriptions (e.g. images, arbitrary descriptions) are automatically frozen as long as they reside in the local process. Otherwise it is not ensured that the description of a frozen element remains unchanged.
• It is not possible to freeze parts of a reference model.

Rules

• The tailoring state of frozen elements cannot be modified any longer.
• Freezing an element will also freeze the dependent project data like project attributes and files. For CM managed files, the referenced revision number is frozen.
• Associations can be either frozen, converted to comments, or not frozen at all.
  • If an association is frozen, the source element will keep the exact amount of associations of that type. This might result in suppressing new associations at unfrozen elements in case the source and target element are not part of the same phase.
  • If an association is converted to a comment, the source element looks the same (apart from the comment has no link). This might result in deleting associations at the target element.
  • If an association is not frozen, the source element might get additional associations or it might lose some even if it is frozen itself.
• Process elements that are part of multiple phases will get duplicated when one of those phases is frozen, as each phase needs a different version of the element. The duplicate is moved to an element folder called “Duplicaes for <phase name>”.
• Frozen process elements are marked by a little check mark taht provides a link to the owning phase.
• Frozen core process elements are separated from the core process because they will not be updated anymore when the current valid version and the working revision are merged into a new valid version.
• The process freeze operation will lock the process including the working revision and the valid version as long as the operation is running to ensure a consistent freeze result. This also means that only one freeze operation can be executed at a time in a single workspace.