3.4.0

Note

• MDK 3.4.0 requires MMS 3.3.0+ and is compatible with View Editor 3.3.0+.

Task

• Creating Viewpoints also creates a <> View() Operation whose method should point to the Viewpoint method. This complies with the SysML 1.4 specification for Viewpoints (Section 7.3.2.8). Additionally, it enables users to build libraries of Viewpoint methods and re-use them in multiple Viewpoints.
  • This change will require a migration of already existing Viewpoints. A validation rule has been added to ensure that all Viewpoints have the Operation. If they do not and an owned Activity is found it offers a quick fix to create the Operation. This validation rule is included in the validation that is automatically done on view generation. There is also a new main menu action "MDK" > "Validate" > "Views" that will run on-demand the validations on all Views in the model. This option can be used to migrate existing Viewpoints in bulk. It is recommended that the whole model is locked by the user applying the fixes to ensure all Views that are being modified are locked.
• The way to define Groups (previously referred to as Sites) has been simplified. The new pattern is documented in the User Guide.
  • This change will require a migration of already existing Groups. There is an automated migration that can be ran from a new main menu action "MDK" > "Migrate" > "Groups". It is recommended that the whole model is locked by the user running the migration to ensure all Groups are locked.
• (Internal) The way in which Diagram images are committed have been updated to support the MMS 3.3.0 Artifacts API changes.

3.4.0-rc7

Note

• MDK 3.4.0 requires MMS 3.3.0+ and is compatible with View Editor 3.3.0+.

Task

• Creating Viewpoints also creates a <> View() Operation whose method should point to the Viewpoint method. This complies with the SysML 1.4 specification for Viewpoints (Section 7.3.2.8). Additionally, it enables users to build libraries of Viewpoint methods and re-use them in multiple Viewpoints.
  • This change will require a migration of already existing Viewpoints. A validation rule has been added to ensure that all Viewpoints have the Operation. If they do not and an owned Activity is found it offers a quick fix to create the Operation. This validation rule is included in the validation that is automatically done on view generation. There is also a new main menu action "MDK" > "Validate" > "Views" that will run on-demand the validations on all Views in the model. This option can be used to migrate existing Viewpoints in bulk. It is recommended that the whole model is locked by the user applying the fixes to ensure all Views that are being modified are locked.
• The way to define Groups (previously referred to as Sites) has been simplified. The new pattern is documented in the User Guide.
  • This change will require a migration of already existing Groups. There is an automated migration that can be ran from a new main menu action "MDK" > "Migrate" > "Groups". It is recommended that the whole model is locked by the user running the migration to ensure all Groups are locked.
• (Internal) The way in which Diagram images are committed have been updated to support the MMS 3.3.0 Artifacts API changes.

3.4.0-rc6

Note

• MDK 3.4.0 requires MMS 3.3.0+ and is compatible with View Editor 3.3.0+.

Task

• Creating Viewpoints also creates a <> View() Operation whose method should point to the Viewpoint method. This complies with the SysML 1.4 specification for Viewpoints (Section 7.3.2.8). Additionally, it enables users to build libraries of Viewpoint methods and re-use them in multiple Viewpoints.
  • This change will require a migration of already existing Viewpoints. A validation rule has been added to ensure that all Viewpoints have the Operation. If they do not and an owned Activity is found it offers a quick fix to create the Operation. This validation rule is included in the validation that is automatically done on view generation. There is also a new main menu action "MDK" > "Validate" > "Views" that will run on-demand the validations on all Views in the model. This option can be used to migrate existing Viewpoints in bulk. It is recommended that the whole model is locked by the user applying the fixes to ensure all Views that are being modified are locked.
• The way to define Groups (previously referred to as Sites) has been simplified. The new pattern is documented in the User Guide.
  • This change will require a migration of already existing Groups. There is an automated migration that can be ran from a new main menu action "MDK" > "Migrate" > "Groups". It is recommended that the whole model is locked by the user running the migration to ensure all Groups are locked.
• (Internal) The way in which Diagram images are committed have been updated to support the MMS 3.3.0 Artifacts API changes.

3.3.6

Bug

• Patched potential source of corrupted elements as a result of Coordinated Sync.

3.4.0-rc5

Note

• MDK 3.4.0 requires MMS 3.3.0+ and is compatible with View Editor 3.3.0+.

Task

• Creating Viewpoints also creates a <> View() Operation whose method should point to the Viewpoint method. This complies with the SysML 1.4 specification for Viewpoints (Section 7.3.2.8). Additionally, it enables users to build libraries of Viewpoint methods and re-use them in multiple Viewpoints.
  • This change will require a migration of already existing Viewpoints. A validation rule has been added to ensure that all Viewpoints have the Operation. If they do not and an owned Activity is found it offers a quick fix to create the Operation. This validation rule is included in the validation that is automatically done on view generation. There is also a new main menu action "MDK" > "Validate" > "Views" that will run on-demand the validations on all Views in the model. This option can be used to migrate existing Viewpoints in bulk. It is recommended that the whole model is locked by the user applying the fixes to ensure all Views that are being modified are locked.
• The way to define Groups (previously referred to as Sites) has been simplified. The new pattern is documented in the User Guide.
  • This change will require a migration of already existing Groups. There is an automated migration that can be ran from a new main menu action "MDK" > "Migrate" > "Groups". It is recommended that the whole model is locked by the user running the migration to ensure all Groups are locked.
• (Internal) The way in which Diagram images are committed have been updated to support the MMS 3.3.0 Artifacts API changes.