Skip to main content

Restrictions

Model​

Structural model​

  • Inner class information is imported under the first package found up the parent hierarchy.
  • The following elements defined in Enterprise Architect are imported as classes in Next Design.
    • Data type
    • PrimitiveType
    • Enumeration
  • Constraints set for various Enterprise Architect models (elements, attributes, operations, connections, etc.) cannot be imported.
    • However, constraints represented as notes on the diagram are imported as notes.
  • If there are no user-defined models in the Enterprise Architect project that are set to types such as class attributes and operations, the models imported into Next Design will be untyped.
    • This applies when the following operations are performed in an Enterprise Architect project.
      1. Define class A and class B
      2. Add an attribute X to class A and set the attribute type to class B
      3. Delete class B along with the model
  • Stereotypes set for association end roles of relationships between classes cannot be imported.
  • Navigability information for associations between classes can be imported only if only one of them is navigable and both association ends are not aggregates or composites.
  • The following elements (in composite structures) cannot be imported.
    • object
    • part
  • Assembly connectors are converted and imported in Next Design as follows.
    • Assembly connector between ports: Convert to connector.
    • Assembly connectors between ports and interfaces: convert to realization.
    • Assembly connectors other than the above: Convert to association.
  • Public interfaces (required interfaces/provided interfaces) of components and ports are imported in Next Design with a different model structure.
    • Enterprise Architect: Defined as a child element of the required or provided component/port.
    • Next Design : Imported as an element in the same hierarchy as the component (or its parent component in the case of ports).
  • The following elements defined in Enterprise Architect are imported as nodes in Next Design.
    • device
    • Execution environment
  • The following elements defined in Enterprise Architect are imported as artifacts in Next Design.
    • Placement specification
    • information item
    • image element
    • document deliverables
  • The following elements defined in Enterprise Architect are imported as relationships in Next Design. Also, in this case, the direction of communication (arrow) is not represented.
    • communication path
  • The following relationships defined in Enterprise Architect are imported as dependencies in Next Design.
    • Placement
    • Manifestation
  • You cannot import the contents (Notes) of Enterprise Architect Requirement Properties.
  • The following information that can be defined in Enterprise Architect's extension request, etc. cannot be imported.
    • risk
    • source
    • verifyMethod
  • Models with "unit" and "quantity type" that are not used from Enterprise Architect's value type cannot be imported.
  • "Property" added directly under the package of Enterprise Architect cannot be imported. Only properties added as child elements of blocks are imported.
  • If the block's port direction is undecided, Next Design will import it as an input port.
  • The following values ​​set in the "Unit" model of Enterprise Architect cannot be imported.
    • quantityKind
    • symbols
    • description
    • definitionURI
  • The following values ​​set in the "Quantity type" model of Enterprise Architect cannot be imported.
    • symbols
    • description
    • definitionURI
  • Nested ports cannot be imported.
  • If a class is set as the property type of an Enterprise Architect block, the type information cannot be imported.
  • The following items that can be set in the ports of blocks in Enterprise Architect cannot be imported.
    • read-only
    • Is it a derived attribute?
    • initial value
  • Ports owned by Enterprise Architect Parts cannot be imported.
  • Connections with ports owned by parts are imported as connections with ports of blocks specified in the part type.
  • Properties owned by Enterprise Architect Constraint Properties cannot be imported.
  • The connection with the property owned by the constraint property is imported as the connection with the property of the constraint block specified in the type of the constraint property.
  • If a constraint block is placed under a constraint block in Enterprise Architect, it will be imported into the first parent package found.
  • The extension request below is imported as a request.
    • Extended request
    • Feature request
    • interface request
    • performance requirements
    • physical requirements
    • design constraints
  • The following ports are imported as input ports or output ports according to the set direction.
    • port
    • proxy port
    • full port
  • Valid properties defined as block operations are imported as operations.
  • Import central buffer nodes and datastores in activities as object nodes.
  • Interface blocks are imported as blocks.
  • The following elements are imported as notes.
    • comment
    • element group
    • problem
    • basis
    • allocation
  • Import the following connections as dependencies.
    • tracking
    • Abstraction
    • replace
    • use
  • Use case includes and extends are imported as dependencies.
  • Import delegation connections as dependencies.
  • The following connections in activities are imported as simple flows.
    • control flow
    • object flow
    • exception flow
  • The following elements of a block are imported as part/value/constraint parameters.
    • Part property
    • constraint property
    • flow properties
    • Directed properties
    • connector properties
    • distribution properties
    • Participant properties
    • attached property
    • binding reference
    • endpoint multiplicity
    • classifier behavior properties
    • objective function
    • Effect measurement

The conditions for determining the import destination are as follows.

  • if the parent element is a block
    • In the case of constraint properties: Imported as constraint properties.
    • If the property type is a value type: Imported as a value.
    • Other than the above: Import as a part.
  • if the parent element is a constraint block
    • In the case of constraint properties: Imported as constraint properties.
    • Other than the above: Captured as a constraint parameter.
  • When the parent element is a part
    • If the property type is a value type: Imported as a value.
    • Other than the above: Import as a part.
  • Attributes and operation models of classes are imported in alphabetical order regardless of the order in which they are displayed in Enterprise Architect.
  • Block definition constraints are imported in the order in which they were created, regardless of the order in which they appear in Enterprise Architect.

Behavioral model​

  • Behavioral elements (states, triggers, actions, control nodes, etc.) are imported as child elements of the behavioral diagram model rather than under a package.
  • Models representing behavioral elements that are not represented on the diagram are not imported.

Diagram​

common​

  • The following elements on diagrams in Enterprise Architect cannot be imported.
    • Usage Guide
    • Diagram overview
    • boundaries
    • hyperlink
    • image
  • Depending on the data in the diagram of Enterprise Architect, the bend position of the connector may not be laid out correctly.
    • Only connectors with bend positions recorded are imported.
  • Shapes and text styles (background color, line color, text color, font) cannot be imported.
  • It is not possible to import a representation of another diagram on an Enterprise Architect diagram.
  • Note anchors connected with connectors on Enterprise Architect diagrams cannot be imported.

UML​

Class diagram​

  • Relevant qualifier information in UML cannot be imported.
  • Template information in UML cannot be imported.
  • If an interface is represented in lollipop notation in Enterprise Architect's class diagram, it will be converted to class notation in Next Design's class diagram. At that time, the shape size of the interface will be the default value of Next Design's shape definition.
  • If the related class is represented on the Enterprise Architect class diagram, the connection between the related class and the related connector is not represented on the Next Design class diagram.
  • The following elements on Enterprise Architect diagrams are not represented on Next Design class diagrams.
    • Deliverable
    • information item
    • image element

Component diagram​

  • If an interface is in class notation in Enterprise Architect's component diagram, it will be converted to Lollipop notation in Next Design's component diagram. At that time, the shape size of the interface will be the default value of Next Design's shape definition.
  • The following elements in Enterprise Architect component diagrams cannot be imported.
    • object
    • part
  • The following Enterprise Architect diagram elements are not represented on Next Design component diagrams.
    • Deliverable
    • information item
    • image element

Deployment Plan​

  • The following elements on Enterprise Architect diagrams are not represented on Next Design's deployment diagrams.
    • interface
    • Inheritance relationship
    • Deliverable
    • information item
    • image element

Package diagram​

  • On the package diagram, the relationship that expresses the ownership relationship (Composition) between packages is not expressed.
  • The following Enterprise Architect diagram elements are not represented on Next Design package diagrams.
    • Deliverable
    • information item
    • image element
  • Package merge, package import and profile application are imported as dependencies.

Activity diagram​

  • Elements that correspond to Enterprise Architect partitions will not be imported. However, behavior 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 node
  • Action elements defined in Enterprise Architect are imported as actions in Next Design, except for the following actions.
    • Time event
    • receive signal
    • send signal
  • All Enterprise Architect forks/joins (Synchronization) are imported as parallels in Next Design (even if the intent on the activity diagram is merge).
  • The following Enterprise Architect diagram elements are not represented in Next Design activity diagrams.
    • Deliverable
    • information item
    • image element

Use case diagram​

  • The following relationships are not represented on the use case diagram.
    • actor-to-actor associations (owning/aggregating, etc.)
    • Relation between use cases and use cases (owning/aggregation, etc.)
  • The following Enterprise Architect diagram elements are not represented in Next Design use case diagrams.
    • Deliverable
    • information item
    • image element

State Machine Diagram/State Transition Diagram​

  • Elements that fall within Enterprise Architect's realm will not be imported. However, behavior elements defined under the above elements are imported as child elements of the diagram model.
  • Regions represented by states cannot be imported.
  • Triggers only import models associated with transitions on state transition diagrams. Trigger diagram elements cannot be imported.
  • Enterprise Architect state machines are converted to normal states in Next Design. In addition, the state transition diagrams in Enterprise Architect's state machine are expanded in Next Design as separate state transition diagrams in the parent package and associated as submachines.
  • Enterprise Architect sync states are imported as selection points in Next Design.
  • Stopped states in Enterprise Architect are imported as finished states in Next Design.
  • All Enterprise Architect forks/joins (Synchronization) are imported as parallels in Next Design (even if the intent on the state transition diagram is confluence).
  • The following Enterprise Architect diagram elements are not represented in Next Design state machine diagrams.
    • Deliverable
    • information item
    • image element

Sequence diagram​

  • The following elements of sequence diagrams cannot be imported.
    • time constraints
    • duration constraint
    • state invariants
    • continuation
    • message ordering (commonly called GeneralOrdering)
    • lifeline parts/ports and messages that end on them
  • Actors on sequence diagrams are imported as lifelines. Shapes will appear as Actor shapes in Next Design only if the type is set to the model of the actor.
  • Boundaries, controls, and entities on sequence diagrams are imported as lifelines.
  • The following types of compound fragments can only be imported with a single operand. If multiple operands are defined, sequence diagram import fails.
    • Break
    • Loop
    • Neg
    • Opt
  • The response message must have been sent to the execution specification that sent the first message (start message) that the execution specification that sent the message received. Importing a sequence diagram fails if it is answered for different execution specifications.
  • If multiple note anchors are connected to one note on the sequence diagram, only one of them can be imported.
  • Note anchor positions and bend positions cannot be reproduced.
  • Note anchors connecting notes cannot be imported.
  • The position of the message edge (end point of lost message or appearing message) cannot be reproduced.
  • The argument part of the message is kept as a single string in Enterprise Architect. When importing into the Next Design model, the string in the argument part is interpreted as follows.
    • Generates argument models for the number of arguments assuming that there are the number of arguments separated by commas.
    • Set the "Value" field of each argument model to a string separated by commas.
    • Fields other than "Value" in the argument model are left unset.
  • The return value part of the message is kept as a single string in Enterprise Architect. When importing into a Next Design model, the string in the return value part is interpreted as follows.
    • Generates a return value model if the string in the return value part is set.
    • Set the string of the return value part in the "Value" field of the return value model.
    • Fields other than "Value" in the return value model are left unset.
  • Sequence diagrams and stereotypes of sequence diagram elements (such as lifelines and messages) cannot be imported.
  • Contents described in the properties of sequence diagrams and sequence diagram elements (lifelines, messages, etc.) cannot be imported.
  • Return values ​​for messages that are not reply messages are not displayed in the text of the message. .
  • Messages that meet the following conditions cannot be imported.
    • message with frame as endpoint
    • messages with interaction usage as endpoints
  • When importing data such as the following, the sequence diagram execution specification may be imported with a different configuration from the sequence diagram display in Enterprise Architect.
    • Data where execution specifications are continuous on Enterprise Architect's model data, but the execution specifications appear to be disconnected due to Enterprise Architect's display control.
    • Data connecting the destination of messages other than response messages to a started execution specification
    • data starting a new execution specification at the destination of the response message
  • The following Enterprise Architect diagram elements are not represented in Next Design sequence diagrams.
    • Deliverable
    • information item
    • image element

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 deliverables
    • request
    • Deliverable
    • information item
    • image element
    • Generalization
  • The following elements of the block definition diagram are imported as parts or values.
    • Part properties
    • flow properties
    • Directed properties

Internal Block Diagram​

  • Only internal block diagrams placed directly under blocks are imported.
  • The following Enterprise Architect diagram elements are not represented on the Next Design internal block diagram.
    • document deliverables
    • request
    • Deliverable
    • information item
    • image element
  • The following elements of the internal block diagram are imported as parts.
    • connector properties
    • distribution properties
    • Participant properties
    • attached property
    • binding reference
    • endpoint multiplicity
    • classifier behavior properties
  • Connectors in internal block diagrams are imported as directed connectors.

Package Diagram​

Please refer to UML package diagram.

Activity Diagram​

See UML activity diagram.

Usecase Diagram​

See UML use case diagram.

State Machine Diagram/State Transition Diagram​

Please refer to UML state machine diagram/state transition diagram.

Sequence Diagram​

Please refer to UML sequence diagram.

Requirement diagram​

  • Containment relationships between requirements are converted to hierarchical relationships in Next Design and imported. Also, containment relationships are not represented on the Next Design requirement diagram.
    If multiple containment relations are defined, the parent element is determined by the containment relation read last. Also, if the containment relation is cyclic, including the model hierarchy relation on Enterprise Architect, the containment relation will not be imported.
  • Dependencies between requirements are not expressed on the Next Design requirement diagram.
  • If a frame is expressed in Enterprise Architect's requirement diagram, it may be captured as an unintended element in Next Design's requirement diagram.
  • The following elements on the Enterprise Architect diagram are not represented on the Next Design requirements diagram.
    • Deliverable
    • information item
    • image element

Parametric diagram​

  • Only parametric diagrams placed directly under blocks are imported.
  • The following Enterprise Architect diagram elements are not represented on Next Design parametric diagrams.
    • document deliverables
    • request
    • Deliverable
    • information item
    • image element
  • Import the parametric diagram objective function as a constraint property.
  • The following elements of parametric diagrams are imported as value or constraint parameters.
    • Effect measurement
    • Part property
    • connector properties
    • distribution properties
    • flow properties
    • Participant properties
Last updated on