Restrictions
General
- If you are using Next Design V1.1, you can use only the functions of the old package: UML/SysML Sample.
- About update from old package
- When updating the profile of the old package, it is necessary to prepare for package migration. If you proceed with the update without preparing for it, some information may be lost. For details, please refer to Migration Guide > Migration from Old Package.
- The language of the updated profile is determined by the display language of Next Design. If you want to migrate English profile data, please set the display language of Next Design to "English" before migrating the data.
- If you make the following changes to the profile package [UML/SysML] provided by this package, you will not be able to use all the functions of this package. (In that state, the UML tab does not appear on the ribbon)
- Change the package name of [UML/SysML] to something other than
UMLSysML. - [UML/SysML] is not placed directly under the root package
- Example not placed directly under
- Example not placed directly under
- Change the package name of [UML/SysML] to something other than
- If you have modified the view definition of each diagram, an error may occur when you undo the change after changing the display settings on the [UML Diagram] tab of the inspector. No design information is lost in the event of an error. There is no problem in continuing editing as it is.
- If you are using profile references, you can customize UML/SysML profile elements, but if you disable some classes or fields, the extensions included in the UML/SysML package may behave in an unintended manner. For example, the extension may display information about the disabled fields.
Constraint digest for each figure
Below is a digest of the constraints for each diagram. For details, refer to the restrictions described at the end of each figure page.
| Target | Classification | Picture | Restrictions |
|---|---|---|---|
| UML | Structure | Class Diagram | ・Related classes and inner classes cannot be defined. |
| Component Diagram | ・Parts cannot be defined. | ||
| Deployment Diagram | - | ||
| Package Diagram | - | ||
| Object diagram | (not supported) | ||
| Profile diagram | (not supported) | ||
| Composite structure drawing | (not supported) | ||
| Behavior | Activity Diagram | ・Swimlanes cannot be defined. | |
| Usecase Diagram | ・ Use case extension points cannot be defined. | ||
| State machine diagram | ・Concurrent states cannot be defined. | ||
| Sequence Diagram | ・State invariants and duration constraints cannot be defined. | ||
| Communication diagram | (not supported) | ||
| Interaction overview diagram | (not supported) | ||
| Timing diagram | (not supported) | ||
| SysML | Structure | Block definition diagram | ・Input/output ports of blocks cannot be placed as shapes. Write in compartments. |
| Internal Block Diagram | ・The block type is a rectangular label notation. | ||
| Package Diagram | (similar to UML package diagram) | ||
| behavior | Activity Diagram | (similar to activity diagram in UML) | |
| Usecase Diagram | (similar to UML usecase diagram) | ||
| State machine diagram | (similar to UML state machine diagram) | ||
| Sequence Diagram | (Similar to UML sequence diagram) | ||
| Requirement | Requirement Diagram | ・Requirement stereotypes cannot be represented on the diagram. Check and edit in the inspector. | |
| Parametric | Parametric Diagram | ・ Constraint content and constraint parameter type display are different from SysML standard. |