Skip to main content

Constraints

Model​

Common to all models​

  • When updating and importing, attribute values updated in Next Design will be lost because they are updated with information from Enterprise Architect (values are not merged).
  • When updating and importing, if the metaclass of the model in Next Design does not match the metaclass of the model to be updated and imported, the following models will undergo metaclass conversion and information that cannot be maintained will be lost.
  • Actions in activity diagrams (actions/event reception/signal transmission/time events)
  • Action pins in activity diagrams (input pins/output pins)
  • Ports in block definition diagrams (input ports/output ports)
  • Proxy ports in block definition diagrams (input ports/output ports)
  • Complete ports in block definition diagrams (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 the model in Next Design does not match the metaclass of the model you are trying to update and import, updates to that model and updates to 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).
  • When multiple diagrams are updated during update import, the display will not be updated except for the diagram that is updated last.

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 (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 will be 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 to Next Design will be unset.
  • This applies when the following operations are performed in the 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 an association 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 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 requirement or the component/port it provides.
  • 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.
  • Deployment
  • Manifestation
  • The contents of Enterprise Architect requirement properties (Notes) 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 type of a property in an Enterprise Architect block, 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 are imported as requirements.
  • Extension requests
  • Functionality requests
  • Interface requirements
  • Performance requirements
  • Physical requirements
  • Design constraints
  • The following ports are imported as input or output ports according to the set direction.
  • Ports
  • Delegated Ports
  • Complete Ports
  • Validity 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 flows
  • Object flows
  • Exception flows
  • The following elements in blocks are imported as part/value/constraint parameters.
  • Part properties
  • Constraint properties
  • Flow properties
  • Directed characteristics
  • Connector properties
  • Distribution properties
  • Participant properties
  • Attached properties
  • Binding references
  • End 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: Import as a constraint property.
  • If the property type is a value type: Import as a value.
  • In other cases: Import as a part.
  • If the parent element is a constraint block
  • If it is a constraint property: Import as a constraint property.
  • In other cases: Import as a constraint parameter.
  • If the parent element is a part
  • If the property type is a value type: Import as a value.
  • In other cases: Import as a part.
  • Attribute and operation models of classes, etc. 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 are displayed in Enterprise Architect.
  • When updating and importing, the constraints defined in the constraint block are not followed up to changes (renames) or deletions.

Behavior model​

  • Behavior elements (states, triggers, actions, control nodes, etc.) are imported as child elements of the behavior diagram model, not under a package.
  • Among the models that represent behavior elements, elements that are not represented on the diagram are not imported.
  • When updating and importing, triggers are not followed up to changes (renames) or deletions.
  • When updating and importing, when reconfiguring the relationship (traceability) of the sequence diagram, the relationship end is replaced with a new model that is inferred to be the same model from the model before the re-creation, so if a model that can be inferred to be the same model is not found, that information is lost. Also, if the model you inferred is misidentified, it may be associated with a different model than expected.

Diagram​

Common​

  • The following elements on Enterprise Architect diagrams cannot be imported.
  • Legend
  • Diagram overview
  • Boundary
  • Hyperlink
  • Image
  • Depending on the Enterprise Architect diagram data, the connector bend position may not be laid out correctly.
  • Only those 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 (background color, etc.) for some shapes and connectors will also be lost.

UML​

Class diagram​

  • UML related qualifier information cannot be imported.
  • UML template information cannot be imported.
  • If an interface is expressed as a lollipop in an Enterprise Architect class diagram, it will be converted to a class notation in a Next Design class diagram. In that case, the size of the interface shape will be the default value of the shape definition in Next Design.
  • If an associated class is expressed on an Enterprise Architect class diagram, the connection between the associated class and the associated connector will not be expressed on the Next Design class diagram.
  • The following elements on Enterprise Architect diagrams are not expressed on Next Design class diagrams.
  • Deliverables
  • 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 a lollipop notation in a Next Design component diagram. In that case, the size of the interface shape will be the default value of the shape definition in Next Design.
  • 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
  • The shapes of public interfaces are represented in ND with interfaces and connectors in lollipop notation.

Deployment diagram​

  • The following elements on Enterprise Architect diagrams are not represented on Next Design deployment diagrams.
  • Interfaces
  • Inheritance relationships
  • Artifacts
  • Information items
  • Image elements

Package diagram​

  • Associations that represent ownership relationships (Composition) between packages are not represented on package diagrams.
  • The following elements on Enterprise Architect diagrams are not represented on Next Design package diagrams.
  • Artifacts
  • Information items
  • Image elements
  • Package merges, package imports, and profile applications 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.
  • 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
  • Forks/joins (Synchronization) in Enterprise Architect are all imported as parallel in Next Design (even if the intent on the activity diagram is to join).
  • The following Enterprise Architect diagram elements are not represented on Next Design activity diagrams.
  • Deliverables
  • Information items
  • Image elements

Use case diagram​

  • The following relationships are not represented on use case diagrams.
  • Actor-to-actor relationships (ownership/aggregation, etc.)
  • Use case-to-use case relationships (ownership/aggregation, etc.)
  • The following Enterprise Architect diagram elements are not represented on Next Design use case diagrams.
  • Deliverables
  • 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 transition diagrams. Trigger diagram elements cannot be imported.
  • State machines in Enterprise Architect are converted to normal states in Next Design. Also, state transition diagrams in Enterprise Architect state machines are expanded as separate state transition diagrams in the parent package in Next Design and related as submachines.
  • Stopped states in Enterprise Architect are imported as end states in Next Design.
  • Forks/Joins in Enterprise Architect are all imported as parallel in Next Design (even if the intent on the state transition diagram is to join).
  • The following elements on Enterprise Architect diagrams are not represented on state machine diagrams in Next Design.
  • 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, the import of 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 connecting notes cannot be imported.
  • The position of the message end (end point of disappearing message or appearing message) cannot be reproduced.
  • The argument part of the message is stored as a single string in Enterprise Architect. When importing to a Next Design model, the string of the argument part is interpreted as follows.
  • It is assumed that there are arguments of the number separated by commas, and an argument model is generated for that number.
  • The string separated by commas is set in the "Value" field of each argument model.
  • Fields other than "Value" of the argument model are left unset.
  • The return value part of the message is stored as a single string in Enterprise Architect. When importing to a Next Design model, the string of the return value part is interpreted as follows.
  • If a string of the return value part is set, a return value model is generated.
  • Set the string of the return value in the "Value" field of the return value model.
  • Fields other than "Value" of 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 that use a frame as an end point
  • Messages that use an interaction as an end point
  • If you import data like the following, the execution specifications of the sequence diagram may be imported with a configuration that differs from the display of the sequence diagram in Enterprise Architect.
  • Data in which the partitions of the execution specification are continuous in the Enterprise Architect model data, but the execution specification appears 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 the response message.
  • The following elements on Enterprise Architect diagrams are not represented on Next Design sequence diagrams.
  • Deliverables
  • Information items
  • Image elements
  • If the referenced sequence diagram does not exist in the use of an interaction, the entire sequence diagram including the use of that interaction 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 of a block definition diagram are imported as parts or values.
  • Part property
  • Flow property
  • Directed characteristic

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 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 use case diagram.

State machine diagram/state transition diagram​

See UML state machine diagram/state transition diagram.

Sequence Diagram​

See UML sequence diagram.

Requirement diagram​

  • Inclusion relationships between requirements are converted to hierarchical relationships in Next Design before being imported. In addition, inclusion relationships are not shown on Next Design requirement diagrams.
    If multiple inclusion relationships are defined, the parent element is determined by the inclusion relationship that was last loaded. In addition, if there is a circular inclusion relationship, including the hierarchical relationship of the model on Enterprise Architect, the inclusion relationship in question will not be imported.
  • Dependencies between requirements are not shown on Next Design requirement diagrams.
  • If a frame is shown in the Enterprise Architect requirement diagram, it may be included as an unintended element in the Next Design requirement diagram.
  • The following elements on Enterprise Architect diagrams are not shown on Next Design requirement diagrams.
  • Deliverables
  • 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 elements in parametric diagrams are imported as value or constraint parameters.
  • Effectiveness measurements
  • Part properties
  • Connector properties
  • Distribution properties
  • Flow properties
  • Participant properties
Last updated on