tag added to ToDo propertyCondition::conditionKind tag was removed, so after the migration it will be added into ToDo property in the Specification window of the Condition element. Changed Property Types
Changes for Condition and EnvironmentIn earlier versions, the Activity Performable Under Condition property (owned by Activity) had the Condition as its value. After the migration, the newly created Actual Condition with the Condition set as a type, replaces this propert The same is valid for : - Environment (owned by Location Holder) value. If the value was . If the value was Condition, the Actual Condition is created.
Changes for DoctrineIn earlier versions, the Doctrine property (owned by Capability Configuration) had Constraint for its value. In UAF 1.1 Constraint is replaced by Standard Operational Activity. After the migration, Capability Configuration is set as constrainedElement to Constraint Except if Constraint is Operational Constraint or Service Policy.
In UAF 1.2, the Security Property is renamed to Operational Information Role and the new Resource Information Role is implemented. The Operational Information Role is used by the Operational Assets and the Resource Information Role is used by the Resource Assets. - Operational Asset - An abstract element used to group the elements of Operational Agent and Operational Information.
- Resource Asset - An abstract element used to group the elements of Resource Performer and Resource Information.
|
If Operational Agent and Operational Information (in UAF 1.2 grouped by Operational Asset) had a Security Property set, after the migration the Security Property will be changed to: - Operational Information Role, if the type of the Security Property was any of the Operational Asset specializations.
- Simple UML property, if the type of the Security Property was Resource Asset.
If Resource Performer and Resource Information (in UAF 1.2 grouped by Resource Asset) had a Security Property set, after the migration the Security Property will be changed to: - Resource Information Role, if the type of the Security Property was Resource Asset.
- Simple UML property, if the type of the Security Property was Operational Asset.
The Known Resource is both: Resource Asset and Operational Asset. After the migration, the Security Property (owned by the Know Resource) is changed depending on its type: - If the type was Resource Information, the Security Property becomes Resource Information Role.
- If the type was Operational Information, the Security Property becomes Operational Information Role.
|
Enduring Task removedEnduring Task element was removed, so after the migration, it become Strategic Phase. Capability For Task removedCapability For Task was removed, so after the migration Capability For Task will be changed to Phases relationship (reverse). Changes for properties of ActualEnterprisePhase- Operational Architecture Of Enterprise Phase property was removed, so after the migration Implements relationship will be created between Actual Enterprise Phase and Operational Architecture element.
- Resource Architecture Of Enterprise Phase property was removed, so after the migration Implements relationship will be created between Actual Enterprise Phase and Resource Architecture element.
- Vision property was removed, so after the migration Phases relationship was created between Actual Enterprise Phase and Enterprise Vision
- Goal property was removed, so after the migration Phases relationship was created between Actual Enterprise Phase and Enterprise Goal
- Concern property was removed, so after the migration Phases relationship was created between Actual Enterprise Phase and Concern
Changes for Concern property- Enterprise Phase property was removed, so after the migration Phases relationship was created between Actual Enterprise Phase and Concern
Changes for property of Enterprise Goal- Enterprise Phase property was removed, so after the migration Phases relationship was created between Actual Enterprise Phase and Enterprise Goal
Changes for property of Enterprise Vision - Enterprise Phase property was removed, so after the migration Phases relationship was created between Actual Enterprise Phase and Enterprise Vision
Changes for properties of Desired Effect and Achieved Effect Consumes renamedIn UAF 1.2 Consumes relationship is renamed to Supports and the direction is reversed. Specializations of Capable Element updatedIn UAF 1.2 Actual Enterprise Phase and Actual Enduring Task are removed as specializations of Capable Element. If these elements have a relationship (Exhibits) with Capability, Exhibits relationship was removed and Phases will be created. Changed Property TypesIn earlier versions, the Benefit property (owned by Enterprise Goal) was String. In UAF 1.2 benefit property has value Item for its value. After migration, the Value Item element will be created based on benefit value. Changed for Whole Life EnterpriseIn the earlier version, Whole Life Enterprise was Class. In UAF 1.2 Whole Life Enterprise will be Instance Specification. After migration, Whole Life Enterprise becomes Strategic Phase. |