Nested maps

What is a "nested map"?

A nested map is a visual and structured representation of assets and their hierarchical or logical relationships. It allows you to visualize sets of objects, organized according to traversal rules and filters, in the form of nested blocks.

What is it used for?

• System modeling: Nested maps are used to graphically represent system inclusions, such as applications, business processes, infrastructures, or data repositories.
• Hierarchical navigation: They allow navigation through tree structures (e.g.: an application, its modules, then the components of each module, or a business capability, its child business capabilities and the applications they contain).
• Impact analysis: Visualizing dependencies and relationships between elements facilitates impact analysis during changes.
• Business capability mapping: These maps are particularly effective for modeling and visualizing an organization's business capabilities. They allow representation of each capability, its sub-capabilities, as well as the assets (applications, processes, data, etc.) associated with them.
• Filtering and exploration: Thanks to filters, it's possible to display only certain types of elements or relationships, to focus on a specific aspect of the system.
  

1. Creating a nested map

• Access the section dedicated to nested maps in the application's navigation bar.
• Open the right panel if it is closed, using the button located at the top right of the interface.
  
  

2. Define traversal rules

• Nested maps are defined by a set of traversal rules. This is a set of relationships and filters that will define the assets displayed at each nesting level.
  
  

• You can define multiple traversal rules at each level (e.g.: display applications as well as actors that belong to a business capability)
• You can define up to three maximum nested levels of traversal rules, but you can stop at one or two levels if you wish.

3. Utiliser les filtres

• Filters allow you to restrict the display to certain attributes or properties (e.g.: status, type, creation date).
• They apply to each level of the map, to refine the visualization.
  
  

4. Navigation et interaction

• Click on a block to see its properties and relationships. You can edit it using the "pen" button present at the top of the panel.
• Nested blocks represent the hierarchy or relationships defined by the rules.
• You can hover over or select a block to display additional information.

5. Saving

• Once the map is configured, you can name it and save it with the "Save as" button present above the nested map.