About Views Global Update

The following section helps you identifying the impacts in a diagram when it has been initialized from another diagram and if an element has been removed, added or replaced by a new version in the source diagram.

This page discusses:

Update Conditions

When updating a target view according to the modifications made on the source view:

  • The source and target views must be opened without filter.
  • The source and target diagrams must be up-to-date with the main view.
  • The update applies only to diagrams loaded in session.
    Note: The RFLP Linked Objects panel provides information on the impacting and impacted diagrams and allows you to load them in session if needed.
  • The update is only done on the diagram for which the Global update command has been launched. Other impacted diagrams are not updated.
  • The update must be launched from the parent level of the diagram.

Update a Diagram View from the Main View

An update of the diagram view is possible in the following cases:

  • In the main view, a function or logical instance is deleted or not loaded
  • in the main view, a function or logical connector is deleted or created on a function or logical instance
  • In the diagram view, the version of a function or logical instance is not the latest version, in session or saved
  • In the diagram view, the version of a function or logical connector is not the latest version, in session or saved
  • Connected instances of a particular function or logical instance is in the main view but not placed in the diagram view
  • In the main view, new connections between instances of a function or logical instance are added
  • In the main view, connections between instances of function or logical instance are broken

Update Implementing Sequence Diagram from Implemented Sequence Diagram

When you update an implementing sequence diagram from an implemented sequence diagram, the following information must be taken into consideration:

  • Actor:
    • Removed: Removing an actor removes all the linked entities such as activation, messages, time and duration constraints.
    • Added: Only mapped actors are taken into account.
    • Replaced: Implementing and implemented views are up-to-date with the main view.
  • Message:
    • Removed: Removing a message removes time and duration constraints linked to the message.
    • Added: By default, the position of the added message is the same as in the source diagram with spacing between messages if several are added.
Note: Message Flow is a message in the source diagram and Message Type is a message in the target diagram.
  • Duration constraints: Messages from the Message section are used to create the duration constraints.
  • Guard: All the blocks are considered. If a block is added or removed, the guard is seen as removed or added.

Update Implementing Sequence Diagram from Implemented Use Case Diagram

When you update an implementing sequence diagram from an implemented use case, the following information must be taken into consideration:

  • Actor: Only external actors can be removed or added.
  • Message
    • Removed: Flows from both directions are managed (actor to use case and use case to actor).
    • Added: When messages are added, flow interfaces and connections are created if not existing.

Update Implemented Use Case Diagram from Implementing Sequence Diagrams

When you update an implemented use case diagram from an implementing sequence diagram, the following information must be taken into consideration:

  • Actor
    • Removed: The actor is removed only if not represented in all the sequence diagrams implementing the use case placed in the use case diagram.
    • Added: If there is no association between the use case actor and the use case, it is created even though there is no message between the two sequence diagram actors.

Update Implementing Context Diagram from Implemented Use Case Diagrams

When you update an implemented context diagram from an implementing use case, the following information must be taken into consideration:

  • Actor
    • Removed: A context actor can be removed only if the use case actor has been removed from the use case diagram linked to the context diagram.
    • Added: When a context actor is created, a route is also created in the context diagram. In the main view, flow interfaces and a system are created, based on the cardinality.
      Note: Since a flow association in a use case diagram does not create any object, some updates can trigger the creation of corresponding objects.
  • Flow:
    • Removed: A Flow can be removed only if it has been removed from all the use case diagrams. Interfaces are not removed.
    • Added: According to the direction of the use case association, corresponding flow interfaces are created on the actor and the system in the main view.

Update Implementing Context Diagram from Implemented Context Diagrams

When you update an implemented context diagram from an implementing context diagram, the following information must be taken into consideration:

  • Removed Actor: An actor can be removed only if it has been removed from the implemented context diagram.
  • Flow:
    • Removed: PLM interfaces are not removed.
    • Added: PLM interfaces are created if necessary.