Skip to main content

Restrictions

General​

  • UML/SysML diagrams in Enterprise Architect and Next Design have different internal data structures, which may result in differences between the imported diagram and the resulting diagram. Please be sure to verify that the results of importing using this package are as expected.

Model​

Common to all models​

  • When updating and importing, attribute values updated in Next Design will be lost because they are updated with the information from Enterprise Architect (values are not merged).
  • When updating and importing, if the metaclass of the Next Design model does not match the metaclass of the model being imported, the following models will undergo metaclass conversion, resulting in the loss of unpreservable information.
  • Activity diagram actions (actions/event reception/signal transmission/time events)
  • Activity diagram action pins (input pins/output pins)
  • Block definition diagram ports (input ports/output ports)
  • Block definition diagram proxy ports (input ports/output ports)
  • Block definition diagram complete ports (input ports/output ports)
  • When updating and importing, if the related metaclass in Next Design does not match the related metaclass you are trying to update and import, it will be recreated and all information will be lost.
  • When updating and importing, if the metaclass of a model in Next Design does not match the metaclass of the model you are trying to update and import, updates to that model and any subordinate models may not be performed correctly.
  • When updating and importing, stereotypes do not follow changes (renames) or deletions.
  • When updating and importing, if there is a model imported by importing another Enterprise Architect project under the specified package, that model will be deleted (it will be treated as a model deleted in Enterprise Architect).
  • If multiple diagrams are updated during an update import, only the last diagram will be updated.

Structure Model​

  • Internal class information is imported under the first package found by tracing the parent hierarchy.
  • The following elements defined in Enterprise Architect are imported as classes in Next Design.
  • Data Type
  • Primitive Type
  • Enumeration
  • Constraints set for various Enterprise Architect models (elements, attributes, operations, connections, etc.) cannot be imported.
  • However, constraints expressed as notes on diagrams will be imported as notes.
  • If a user-defined model set for the type of a class attribute, operation, etc. does not exist in the Enterprise Architect project, the type of the model imported in Next Design will be undefined.
  • This applies when the following operations are performed in an Enterprise Architect project:
  1. Define class A and class B
  2. Add attribute X to class A and set the attribute type to class B
  3. Delete class B along with the model
  • Stereotypes set for the association end role of an association between classes cannot be imported.
  • Navigability information for associations between classes can only be imported if it is navigable in one direction and both association ends are not aggregations or composites.
  • The following elements (in composite structures) cannot be imported.
  • Objects
  • Parts
  • Assembly connectors are converted and imported in Next Design as follows:
  • Assembly connectors between ports: Converted to connectors.
  • Assembly connectors between ports and interfaces: Converted to realizations.
  • Assembly connectors other than those listed above: Converted to associations.
  • Public interfaces (required interfaces/provided interfaces) of components and ports are imported in Next Design using a different model structure.
  • Enterprise Architect: Defined as a child element of the requirement or the component/port it provides.
  • Next Design: Imported as an element at the same level as the component (or, in the case of a port, its parent component).
  • The following elements defined in Enterprise Architect are imported as nodes in Next Design.
  • Devices
  • Execution Environments
  • The following elements defined in Enterprise Architect are imported as artifacts in Next Design.
  • Deployment Specifications
  • Information Items
  • Image Elements
  • Document Deliverables
  • The following elements defined in Enterprise Architect are imported as relationships in Next Design. In this case, the direction of communication (Arrows) is not expressed.
  • Communication Paths
  • The following relationships defined in Enterprise Architect are imported as dependencies in Next Design.
  • Deployment
  • Manifestation
  • The contents of Enterprise Architect requirement properties (Notes) cannot be imported.
  • The following information, which can be defined in Enterprise Architect extension requests, cannot be imported.
  • risk
  • source
  • verifyMethod
  • "Unit" and "Quantity Kind" models that are not used in Enterprise Architect value types cannot be imported.
  • "Property" added directly under an Enterprise Architect package cannot be imported. Only properties added as child elements of a block will be imported.
  • If the direction of a block's port is undetermined, Next Design will import it as an input port.
  • The following values set in an Enterprise Architect "Unit" model cannot be imported.
  • quantityKind
  • symbol
  • description
  • definitionURI
  • The following values set in an Enterprise Architect "Quantity Kind" model cannot be imported.
  • symbol
  • description
  • definitionURI
  • Nested ports cannot be imported.
  • If a class is set as the property type of an Enterprise Architect block, type information cannot be imported.
  • The following items that can be set on Enterprise Architect block ports cannot be imported.
  • Read-only
  • Derived attribute
  • Initial value
  • Ports owned by Enterprise Architect parts cannot be imported.
  • Connections to ports owned by parts are imported as connections to ports of the block specified in the part's type.
  • Properties owned by Enterprise Architect constraint properties cannot be imported.
  • Connections to properties owned by constraint properties are imported as connections to properties of the constraint block specified in the constraint property's type.
  • If a constraint block is placed under an Enterprise Architect constraint block, it will be imported into the first parent package found.
  • The following enhancement requests will be imported as requirements.
  • Enhancement requests
  • Functionality requests
  • Interface requirements
  • Performance requirements
  • Physical requirements
  • Design constraints
  • The following ports will be imported as input or output ports according to the set direction.
  • Port
  • Proxy Port
  • Complete Port
  • Effective characteristics defined as block operations are imported as operations.
  • Central buffer nodes and data stores in activities are imported as object nodes.
  • Interface blocks are imported as blocks.
  • The following elements are imported as notes.
  • Comments
  • Element Groups
  • Issues
  • Rationale
  • Assignments
  • The following connections are imported as dependencies.
  • Traces
  • Abstractions
  • Substitutions
  • Uses
  • Use case includes and extends are imported as dependencies.
  • Delegation connections are imported as dependencies.
  • The following connections in activities are imported as simple flows.
  • Control Flows
  • Object Flows
  • Exception Flows
  • The following elements of blocks are imported as part, value, or constraint parameters.
  • Part properties
  • Constraint properties
  • Flow properties
  • Directed characteristics
  • Connector properties
  • Distribution properties
  • Participant properties
  • Attached properties
  • Binding references
  • Terminal point multiplicities
  • Classifier behavior properties
  • Objective functions
  • Effectiveness measurements
    The conditions for determining the import destination are as follows:
  • If the parent element is a block
  • If it is a constraint property: Import as a constraint property.
  • If the property type is a value type: Import as a value.
  • Otherwise: Import as a part.
  • If the parent element is a constraint block
  • If it is a constraint property: Import as a constraint property.
  • Otherwise: Import as a constraint parameter.
  • If the parent element is a part
  • If the property type is a value type: Import as a value.
  • Otherwise: Import as a part.
  • Attribute and operation models of classes, etc. are imported in alphabetical order, regardless of the order displayed in Enterprise Architect.
  • Block-defined constraints are imported in the order they were created, regardless of the order displayed in Enterprise Architect.
  • When updating and importing, changes (renaming) and deletions to constraints defined in constraint blocks are not tracked.

Behavioral Model​

  • Behavioral elements (states, triggers, actions, control nodes, etc.) are imported as child elements of the behavioral diagram model, not under a package.
  • Models representing behavioral elements that are not represented on the diagram are not imported.
  • When updating and importing, changes (renaming) and deletions of triggers are not tracked.
  • When reconfiguring sequence diagram relationships (traceability) during an update import, the relationship end is replaced with a new model that is inferred to be the same model from the previous model. If no model that can be inferred to be the same model is found, that information will be lost. Also, if the inferred model is misidentified, it may be associated with a different model than expected.

Diagram​

Common​

  • The following elements on Enterprise Architect diagrams cannot be imported.
  • Legends
  • Diagram overview
  • Borders
  • Hyperlinks
  • Images
  • Depending on the Enterprise Architect diagram data, connector bend positions may not be laid out correctly.
  • Only connector data with recorded bend positions will be imported.
  • Shape and text styles (background color, line color, line width, text color, font, etc.) cannot be imported.
  • Representations of other diagrams on Enterprise Architect diagrams cannot be imported.
  • Note anchors connected to connectors on Enterprise Architect diagrams cannot be imported.
  • If multiple ports are placed on the same element, the Z-order between the ports cannot be imported.
  • When updating and importing, the position and size information of shapes and connectors updated in ND will be lost. In addition, style information (such as background color) will be lost for some shapes and connectors.

UML​

Class Diagram​

  • UML association qualifier information cannot be imported.
  • UML template information cannot be imported.
  • If an interface is represented as a lollipop in an Enterprise Architect class diagram, it will be converted to class notation in a Next Design class diagram. The size of the interface shape will be the default value of the Next Design shape definition.
  • If an association class is represented in an Enterprise Architect class diagram, the connection between the association class and the association connector will not be represented in the Next Design class diagram.
  • The following Enterprise Architect diagram elements will not be represented in Next Design class diagrams.
  • Artifacts
  • Information Items
  • Image Elements

Component Diagram​

  • If an interface is represented as a class in an Enterprise Architect component diagram, it will be converted to lollipop notation in a Next Design component diagram. In this case, the size of the interface shape will be the default value of the Next Design shape definition.
  • The following elements of Enterprise Architect component diagrams cannot be imported:
  • Objects
  • Parts
  • The following Enterprise Architect diagram elements are not represented on Next Design component diagrams:
  • Artifacts
  • Information Items
  • Image Elements
  • Public interface shapes are represented in ND using lollipop notation for interfaces and connectors.

Deployment Diagram​

  • The following Enterprise Architect diagram elements are not represented on Next Design deployment diagrams:
  • Interfaces
  • Inheritance Relationships
  • Artifacts
  • Information Items
  • Image Elements

Package Diagram​

  • Associations representing ownership (composition) between packages are not represented on package diagrams.
  • The following Enterprise Architect diagram elements are not represented in Next Design package diagrams.
  • Artifacts
  • Information Items
  • Image Elements
  • Package Merges, Package Imports, and Profile Applications are imported as dependencies.

Activity Diagram​

  • Elements corresponding to Enterprise Architect partitions are not imported. However, behavioral elements defined under the above elements are imported as child elements of the diagram model.
  • The following elements defined in Enterprise Architect are not imported:
  • Activities
  • Loop/Condition Nodes
  • Action elements defined in Enterprise Architect, except for the following actions, are imported as actions in Next Design:
  • Time Events
  • Signal Reception
  • Signal Transmission
  • All Enterprise Architect forks/joins (Synchronizations) are imported as parallel in Next Design (even if the intent on the activity diagram is to merge).
  • The following Enterprise Architect diagram elements are not represented in Next Design activity diagrams.
  • Artifacts
  • Information Items
  • Image Elements

Use Case Diagram​

  • The following relationships are not represented in use case diagrams:
  • Actor-to-actor relationships (such as ownership/aggregation)
  • Use Case-to-use case relationships (such as ownership/aggregation)
  • The following Enterprise Architect diagram elements are not represented in Next Design use case diagrams:
  • Artifacts
  • Information Items
  • Image Elements

State Machine Diagram/State Transition Diagram​

  • Elements that correspond to Enterprise Architect regions are not imported. However, behavioral elements defined under the above elements are imported as child elements of the diagram model.
  • Boundaries (Regions) represented by states cannot be imported.
  • Triggers only import models associated with transitions on state diagrams. Trigger diagram elements cannot be imported.
  • Enterprise Architect state machines are converted to normal states in Next Design. Also, state transition diagrams within Enterprise Architect state machines are expanded into separate state transition diagrams in the parent package in Next Design and associated as submachines.
  • Enterprise Architect stopped states are imported as terminal states in Next Design.
  • Enterprise Architect fork/join (synchronization) are all imported as parallel in Next Design (even if the intent on the state transition diagram is to join).
  • The following Enterprise Architect diagram elements are not represented on Next Design state machine diagrams.
  • Artifacts
  • Information items
  • Image elements

Sequence diagram​

  • The following sequence diagram elements cannot be imported:
  • Time constraints
  • Duration constraints
  • State invariants
  • Continuations
  • Message ordering (commonly known as GeneralOrdering)
  • Lifeline parts/ports and messages that use them as endpoints
  • Actors on sequence diagrams are imported as lifelines. Shapes are displayed as actor shapes in Next Design only if an actor model is set for the type.
  • Boundaries, controls, and entities on sequence diagrams are imported as lifelines.
  • The following types of composite fragments can only be imported if they have a single operand. If multiple operands are defined, the import of the sequence diagram will fail.
  • Break
  • Loop
  • Neg
  • Opt
  • A response message must be sent to the execution specification that sent the message (invocation message) first received by the execution specification that sent that message. If the response is sent to a different execution specification, the import of the sequence diagram will fail.
  • If multiple note anchors are connected to a single note on a sequence diagram, only one of them can be imported.
  • The position of note anchors and bend positions cannot be reproduced.
  • Note anchors connecting notes cannot be imported.
  • The position of message ends (the end points of disappearing and appearing messages) cannot be reproduced.
  • The argument portion of a message is stored as a single string in Enterprise Architect. When importing into a Next Design model, the string in the argument portion is interpreted as follows:
  • Argument models are generated assuming that there are a number of arguments separated by commas.
  • The "Value" field of each argument model is set to the string separated by commas.
  • Fields other than "Value" in the argument model are left unset.
  • The return value portion of a message is stored as a single string in Enterprise Architect. When importing into a Next Design model, the string in the return value portion is interpreted as follows:
  • If a string in the return value portion is set, a return value model is generated.
  • Set the return value string in the "Value" field of the return value model.
  • Leave all fields other than "Value" of the return value model unset.
  • Stereotypes of sequence diagrams and sequence diagram elements (lifelines, messages, etc.) cannot be imported.
  • Content written in the properties of sequence diagrams and sequence diagram elements (lifelines, messages, etc.) cannot be imported.
  • The return value of messages that are not response messages will not be displayed in the message text.
  • Messages that meet the following conditions cannot be imported.
  • Messages with a frame as an endpoint
  • Messages with an interaction use as an endpoint
  • If the following data is imported, the sequence diagram execution specifications may be imported with a different configuration from the display of the sequence diagram in Enterprise Architect.
  • Data in which the execution specification sections are contiguous in the Enterprise Architect model data, but the execution specifications appear disconnected due to Enterprise Architect display controls.
  • Data that connects the destination of a message other than a response message to an already started execution specification.
  • Data that starts a new execution specification at the destination of a response message.
  • The following Enterprise Architect diagram elements are not represented in Next Design sequence diagrams.
  • Artifacts
  • Information items
  • Image elements
  • If a referenced sequence diagram for an interaction use does not exist, the entire sequence diagram, including that interaction use, cannot be imported. If there are other diagrams to import, the import will continue.

SysML​

Block Definition Diagram​

  • The following Enterprise Architect diagram elements are not represented in Next Design block definition diagrams.
  • Actor
  • Enumeration
  • Interface
  • Flow Specification
  • Document Artifact
  • Requirement
  • Artifact
  • Information Item
  • Image Element
  • Generalization
  • The following elements of a block definition diagram are imported as parts or values.
  • Part Properties
  • Flow Properties
  • Directed Characteristics

Internal Block Diagram​

  • Only internal block diagrams placed directly under a block are imported.
  • The following Enterprise Architect diagram elements are not represented in Next Design internal block diagrams.
  • Document Artifact
  • Requirement
  • Artifact
  • Information Item
  • Image Element
  • The following elements of an internal block diagram are imported as parts.
  • Connector properties
  • Distribution properties
  • Participant properties
  • Attachment properties
  • Binding references
  • Terminal point multiplicity
  • Classifier behavior properties
  • Connectors in internal block diagrams are imported as directed connectors.

Package Diagram​

See UML Package Diagram.

Activity Diagram​

See UML Activity Diagram.

Usecase Diagram​

See UML UseCase Diagram.

Statemachine Diagram/State Transition Diagram​

See UML Statemachine Diagram/State Transition Diagram.

Sequence Diagram​

See UML Sequence Diagram.

Requirement Diagram​

  • Inclusion relationships between requirements are converted into hierarchical relationships in Next Design before import. In addition, inclusion relationships are not represented on Next Design requirement diagrams.
    If multiple inclusion relationships are defined, the parent element is determined by the last inclusion relationship loaded. Also, if there are circular inclusion relationships, including hierarchical relationships in the Enterprise Architect model, the inclusion relationship in question will not be imported.
  • Dependencies between requirements are not represented on Next Design requirement diagrams.
  • If a frame is represented in an Enterprise Architect requirement diagram, it may be included as an unintended element in the Next Design requirement diagram.
  • The following Enterprise Architect diagram elements are not represented on Next Design requirement diagrams.
  • Artifacts
  • Information Items
  • Image Elements

Parametric Diagram​

  • Only parametric diagrams placed directly under a block are imported.
  • The following Enterprise Architect diagram elements are not represented in Next Design parametric diagrams:
  • Document deliverables
  • Requirements
  • Deliverables
  • Information items
  • Image elements
  • Objective functions in parametric diagrams are imported as constraint properties.
  • The following parametric diagram elements are imported as value or constraint parameters:
  • Effectiveness measurements
  • Part properties
  • Connector properties
  • Distribution properties
  • Flow properties
  • Participant properties
Last updated on