Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
general:metamodel [2018/05/04 15:49] – emrgeneral:metamodel [2019/04/22 19:18] – emr
Line 3: Line 3:
 The **Metamodel** defines which process elements exist within a [[:general:process|]] and how they are associated with each other. The **Metamodel** defines which process elements exist within a [[:general:process|]] and how they are associated with each other.
  
-In the default configuration, a metamodel TBD+Metamodels are configured on the server by the Stages administrators.
  
-Stages can support multiple metamodels at the same time. Each workspace can have a different metamodel. All process versions within one workspace have the same metamodel.+In the default configuration, a metamodel named **Unified Configuration** is installed, which captures twenty years of customer experience how to best model engineering processes. With the Unified Configuration metamodel, processes are defined by modeling four different perspectives of engineering processes and connecting them with each other: 
 + 
 +{{  :general:metamodel.png?direct&600x276  }} 
 + 
 +Derivatives of this metamodel or completely customer-specific metamodels can be configured, typically in collaboration with Method Park consultants. 
 + 
 +Stages can support multiple metamodels at the same time. Each workspace and every process version within each workspace can have a different metamodel.