Skip to main content

Constraints

Model​

Structural model​

  • Information on internal classes 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 (DataType)
  • Primitive type (PrimitiveType)
  • Enumeration (Enumeration)
  • Constraints set for various Enterprise Architect models (elements, attributes, operations, connections, etc.) cannot be imported.
  • However, constraints expressed as notes on the diagram are imported as notes.
  • If a user-defined model set for the type of a class attribute or operation does not exist in the Enterprise Architect project, the type of the model imported into Next Design will be unset.
  • 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.
  • Information on the navigability of an association between classes can only be imported if it is navigable to only one side 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 as follows in Next Design.
  • Assembly connectors between ports: Converted to connectors.
  • Assembly connectors between ports and interfaces: Converted to realizations.
  • Assembly connectors other than the above: Converted to associations.
  • Public interfaces (required interfaces/provided interfaces) of components and ports are imported in a different model structure in Next Design.
  • Enterprise Architect: Defined as a child element of the required or provided component/port.
  • Next Design: Imported as an element at the same level as the component (or its parent component in the case of a port).
  • The following elements defined in Enterprise Architect are imported as nodes in Next Design.
  • Devices
  • Execution environment
  • 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 associations in Next Design. In addition, the direction of communication (arrows) is not expressed at this time.
  • Communication paths
  • The following relationships defined in Enterprise Architect are imported as dependencies in Next Design.
  • Placement
  • Manifestation
  • The contents of the properties (Notes) of Enterprise Architect requests cannot be imported.
  • The following information that can be defined in Enterprise Architect extension requests cannot be imported.
  • Risk
  • Source
  • VerifyMethod
  • "Unit" and "Quantity type" 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 are imported.
  • If the direction of a block's port is undecided, Next Design imports it as an input port.
  • The following values ​​set in the Enterprise Architect "Unit" model cannot be imported.
  • quantityKind
  • symbol
  • description
  • definitionURI
  • The following values ​​set in the Enterprise Architect "Quantity type" 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, the type information cannot be imported.
  • The following items that can be set for ports of Enterprise Architect blocks cannot be imported.
  • Read-only
  • 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 the block specified in the part type.
  • Properties owned by Enterprise Architect constraint properties cannot be imported.
  • Connections with properties owned by constraint properties are imported as connections with properties of the constraint block specified in the constraint property 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 extension requests will be imported as requests.
  • Enhancement requests
  • Functionality requests
  • Interface requests
  • Performance requirements
  • Physical requirements
  • Design constraints
  • The following ports are imported as input or output ports according to the configured direction.
  • Ports
  • Delegated ports
  • Complete ports
  • Effective properties 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 flow
  • Object flow
  • Exception flow
  • The following elements of blocks are imported as either parts/values/constraint parameters.
  • Part properties
  • Constraint properties
  • Flow properties
  • Directed characteristics
  • Connector properties
  • Distribution properties
  • Participant properties
  • Attached properties
  • Binding references
  • Terminal point multiplicity
  • Classifier behavior properties
  • Objective functions
  • Effectiveness measurements

The conditions that determine the import destination are as follows.

  • If the parent element is a block
  • If it is a constraint property: It is imported as a constraint property.
  • If the property type is a value type: It is imported as a value.
  • In all other cases: It is imported as a part.
  • If the parent element is a constraint block
  • If it is a constraint property: It is imported as a constraint property.
  • In all other cases: It is imported as a constraint parameter.
  • If the parent element is a part
  • If the property type is a value type: Import as a value.
  • Other than the above: 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 definition constraints are imported in the order they were created regardless of the order displayed in Enterprise Architect.

Behavior model​

  • Behavior elements (states, triggers, actions, control nodes, etc.) are imported as child elements of the behavior diagram model, not under a package.
  • Elements of models that represent behavior elements that are not represented on the diagram are not imported.

Diagram​

Common​

  • The following elements on Enterprise Architect diagrams cannot be imported.
  • Legend
  • Diagram overview
  • Boundaries
  • Hyperlinks
  • Images
  • Depending on the data of the Enterprise Architect diagram, the bend position of the connector may not be laid out correctly.
  • Only those that have the bend position recorded as connector data will be imported.
  • Shape and text styles (background color, line color, text color, font) 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.

UML​

Class diagram​

  • Information on association qualifiers in UML cannot be imported.
  • Information on templates in UML cannot be imported.
  • If an interface is expressed as a lollipop in an Enterprise Architect class diagram, it will be converted to class notation in the Next Design class diagram. In that case, the size of the interface shape will be the default value of the Next Design shape definition.
  • If an association class is expressed on an Enterprise Architect class diagram, the connection between the association class and the association connector will not be expressed in the Next Design class diagram.
  • The following elements on an Enterprise Architect diagram will not be expressed on a Next Design class diagram.
  • Artifacts
  • Information items
  • Image elements

Component diagram​

  • If an interface is expressed as a class in an Enterprise Architect component diagram, it will be converted to lollipop notation in the 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 elements on Enterprise Architect diagrams are not represented on Next Design component diagrams.
  • Artifacts
  • Information items
  • Image elements

Deployment diagram​

  • The following elements on Enterprise Architect diagrams are not represented on Next Design deployment diagrams.
  • Interface
  • Inheritance relationship
  • Artifact
  • Information item
  • Image element

Package diagram​

  • Relationships that represent ownership relationships (Composition) between packages are not represented on package diagrams.
  • The following Enterprise Architect diagram elements are not represented on Next Design package diagrams.
  • Artifact
  • Information item
  • Image element
  • Package merge, package import, and profile application are imported as dependencies.

Activity diagram​

  • Elements that correspond 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.
  • Activity
  • Loop/Condition node
  • Action elements defined in Enterprise Architect, except for the following actions, are imported as actions in Next Design.
  • Time event
  • Signal reception
  • Signal transmission
  • Fork/Join (Synchronization) in Enterprise Architect is imported as parallel in Next Design (even if the intent in the activity diagram is confluence).
  • The following elements on Enterprise Architect diagrams are not represented on Next Design activity diagrams.
  • Artifacts
  • Information items
  • Image elements

Use case diagram​

  • The following relationships are not represented on use case diagrams.
  • Actor-actor relationships (ownership/aggregation, etc.)
  • Use case-use case relationships (ownership/aggregation, etc.)
  • The following elements on Enterprise Architect diagrams are not represented on Next Design use case diagrams.
  • Artifacts
  • Information items
  • Image elements

State machine diagram/state transition diagram​

  • Elements that fall under the Enterprise Architect area 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 are imported only as models associated with transitions on the state transition diagram. 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 as separate state transition diagrams in the parent package in Next Design and associated as submachines.
  • Enterprise Architect synchronization states are imported as choice points in Next Design.
  • Enterprise Architect stop states are imported as end states in Next Design.
  • Enterprise Architect forks/joins (Synchronization) are all imported as parallel in Next Design (even if the intent on the state transition diagram is to merge).
  • The following Enterprise Architect diagram elements are not represented on Next Design state machine diagrams.
  • Artifacts
  • Information items
  • Image elements

Sequence diagram​

  • The following elements of sequence diagrams cannot be imported.
  • Time constraints
  • Duration constraints
  • State invariants
  • Continuations
  • Message ordering (commonly called GeneralOrdering)
  • Lifeline parts/ports and messages with them as endpoints
  • Actors on sequence diagrams are imported as lifelines. Shapes are displayed as actor shapes in Next Design only if the type has an actor model.
  • 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 is the sender of the message (start message) that the execution specification that sent the message first receives. If the response is sent to a different execution specification, importing the sequence diagram will fail.
  • If multiple note anchors are connected to one note on a sequence diagram, only one of them can be imported.
  • The position of the note anchor and the bend position cannot be reproduced.
  • Note anchors that connect notes cannot be imported.
  • The position of the message end (the end point of a disappearing message or an appearing message) cannot be reproduced.
  • The argument part of the message is stored as a single string in Enterprise Architect. When importing into a Next Design model, the string of the argument part is interpreted as follows.
  • Generates argument models for the number of arguments as if there were a comma-separated number of arguments.
  • Sets the comma-separated string in the "Value" field of each argument model.
  • Fields other than "Value" in the argument model are left unset.
  • The return value part of a message is held 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:
  • If a string in the return value part is set, a return value model is generated.
  • The string in the return value part is set in the "Value" field of the return value model.
  • Fields other than "Value" in the return value model are left 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 a message that is not a response message is not displayed in the message text. .
  • Messages that meet the following conditions cannot be imported.
  • Messages with frames as endpoints
  • Messages with interaction usage as endpoints
  • When importing the following data, the execution specifications of the sequence diagram may be imported in a different configuration from the display of the sequence diagram in Enterprise Architect.
  • Data in which the execution specification partitions are continuous in the Enterprise Architect model data, but the execution specifications appear to be disconnected due to the display control of Enterprise Architect
  • 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 elements on Enterprise Architect diagrams are not represented on Next Design sequence diagrams.
  • Deliverables
  • Information items
  • Image elements
  • If a sequence diagram referenced by an interaction usage does not exist, the entire sequence diagram including that interaction usage cannot be imported. If there are other diagrams to be imported, the import will continue.

SysML​

Block definition diagram​

  • The following elements on Enterprise Architect diagrams are not represented on Next Design block definition diagrams.
  • Actor
  • Enumeration
  • Interface
  • Flow specification
  • Document artifact
  • Requirement
  • Artifact
  • Information item
  • Image element
  • Generalization
  • The following elements on block definition diagrams 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 elements on Enterprise Architect diagrams are not represented on Next Design internal block diagrams.
  • Document artifacts
  • Requirements
  • Artifacts
  • Information items
  • Image elements
  • The following elements in internal block diagrams 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 to hierarchical relationships in Next Design and imported. In addition, inclusion relationships are not displayed on Next Design requirement diagrams.
    If multiple inclusion relationships are defined, the parent element is determined by the inclusion relationship last loaded. In addition, if the inclusion relationship is circular, including the hierarchical relationship of the model on Enterprise Architect, the relevant inclusion relationship will not be imported.
  • Dependencies between requirements are not displayed on Next Design requirement diagrams.
  • If a frame is displayed in the Enterprise Architect requirement diagram, it may be imported as an unintended element in the Next Design requirement diagram.
  • The following elements on the Enterprise Architect diagram are not displayed on the Next Design requirement diagram.
  • Artifacts
  • Information items
  • Image elements

Parametric diagram​

  • Only parametric diagrams placed directly under blocks are imported.
  • The following elements on Enterprise Architect diagrams are not represented on Next Design parametric diagrams.
  • Document artifacts
  • Requirements
  • Artifacts
  • Information items
  • Image elements
  • Objective functions on parametric diagrams are imported as constraint properties.
  • The following elements on parametric diagrams are imported as value or constraint parameters.
  • Effect measurements
  • Part properties
  • Connector properties
  • Distribution properties
  • Flow properties
  • Participant properties
Last updated on