Documents and Views
Documents and Views can be created and modeled in MagicDraw and generated to View Editor.
...
Documents and views are built and configured using Viewpoints and Viewpoint Methods. More information can be found in the next view.
Open in View Editor
You may wish to inspect a view after generating it with the MDK, to confirm that it matches your expectations. The "Open in View Editor" feature allows you to easily open a Document of View on View Editor from its element representation in MagicDraw.
...
Note: In the event that Java fails in its attempt to open a link in your default browser, a message will appear in the Notification Window of MagicDraw that includes the web address. This can by copied into your web browser to open the page manually.
...
Viewpoints and Viewpoint Methods
One of the defining moments for widespread adoption of SysML at JPL was when the community created "DocGen" (see DocGen User's Guide), a precursor of the MDK plug-in, which gives MBSE practitioners the ability to produce documents from their models. In order to create these documents, the view and viewpoint method was introduced.
...
Right click a View > DocGen > Validate View
Any not compliant views will appear in the notification window. Right click error > Set Nested Behavior as Viewpoint Method
Select "MDK" from the top ribbon > Validate > Views
Any not compliant views will appear in the notification window. Right click error > Set Nested Behavior as Viewpoint Method
_MMSSync_ Package
The _MMSSync_ package is part of a number of sync solutions for the MMS and View Editor. Its purpose is to allow continual collaboration while a project is consistently being updated by multiple users. It does this by capturing changes between the model and the MMS server and persisting them in the model. The idea is that when an element is updated from the server, whoever is using the syncing options will capture the changes and the MDK will try to update the model itself. However, if there is some non-editable content or errors of any sort that would prevent the MDK from automatically updating, these changes will be saved in the _MMSSync_ package. Once stored, the changes will be tried to be resolved/updated the next time it is run.
...
Every project that is connected to MMS will have an _MMSSync_ package.
References to all changed (categorized as created, updated, and deleted) elements on both MagicDraw and MMS will be persisted in elements in this package.
These changed elements will be analyzed during sync operations to generate the necessary operations to sync the model.
Each element in this package will be categorized and timestamped.
Each element in this package is automatically managed and deleted by the MDK. No user intervention is required or recommended. See version specific implications for more information.
In the case that elements in this package cannot be deleted due to insufficient locks, a second element is created that signifies to sync operations that the first one can be safely ignored as its contents have already been processed.
Holding Bin Package
The "Holding Bin" Package is created for every project. Its purpose is to provide a default place to put elements that were created without an owner specified. This is often the case for Documents and Views that originated in View Editor. Elements in the Holding Bin can be moved to other locations in the project just like other model elements.