Book a Demo
Prev Next

Generate Robustness Diagram

When you create a scenario on an element and then generate a Robustness diagram, a Collaboration is created as a child of the selected element to act as a container for the Robustness diagram.


On a diagram or in the Browser window, click on the element and select one of these access methods to display the Scenarios view, then click on Scenario Generation Dialog and select 'Robustness'.


Start > Application > Edit > Responsibilities > Structured Scenarios

Context Menu

Inspector window > Details | Right-click on 'Scenarios' | New Scenario

Inspector window > Details | Scenarios | right-click on existing scenario | Structured Scenario Editor

Keyboard Shortcuts

Alt+2 > Responsibilities > Structured Scenarios


On the 'Scenarios' tab of the Responsibility window, click on the Edit button against a scenario (see the Scenarios Tab - Responsibility Window Help topic)

On the 'Scenarios' tab of the element 'Properties' dialog, click on the Structure Editor button (see the Scenarios Tab - Properties Dialog Help topic)


Showing a structured scenario for a robustness diagram.
The Robustness that represents a structured scenario.


  • All the elements involved in the scenario should be identified in the 'Context Reference' tab; that is, relationships must already exist between the scenario parent element and the other elements named in the scenario
  • Any values in the 'Uses', 'Results' and 'State' columns are ignored and not represented in the diagram
  • Each UI element in a step becomes a Boundary element; a Dependency relationship is created from this Boundary element to the UI element (this connector is not shown on the diagram)
  • Each Actor referenced in a step is dropped into the Robustness diagram as a simple link
  • Each Class referenced in a step is dropped into the Robustness diagram as a simple link, and is given the stereotype entity
  • Each step with a System trigger becomes a Controller; alternate/exception path Controllers are displayed with a red background color
  • Each step with a User trigger becomes the name of the Association between Controllers

Learn more