API Application

The the above diagram is a Component diagram, which is used to “decompose each container further to identify the major structural building blocks and their interactions”.

Mapping

Surroundings -> selectors

Similar to the container diagram, diagram elements representing the surroundings of the “API Application” are mapped to semantic elements defined on the higher level diagrams using selectors. The system context diagram defines the surrounding nodes and this diagram references them.

This is a selector of the “Single-Page Application”:

getDocument().getModelElementById('single-page-application')

The loading logic “carries over” tooltips from the System Context Diagram to this diagram.

API Application

The “API Application” container maps to the same semantic element as on the Container diagram because:

• The “API Application” element on the Container diagram links to this diagram page.
• The “API Application” element on this diagram has page-element property set to true.

Semantic elements of the child elements of the “API Application” element are mapped to the elements reference and ordered with the right-down comparator:

container:
  self:
    elements:
      path: 1
      comparator: right-down

Components

All components within the container are mapped to c4.Components.

The “Mainframe Banking System Facade” is linked to the “Mainframe Banking System Facade Code” page. As such, its semantic element is mapped to the “Mainframe Banking System Facade Code” page element as well allowing further mapping on that page.

This diagram element defines base-uri property as %id%/. Because “Placeholders” is checked, %id%/ expands to mainframe-banking-system-facade/ during loading. doc-ref is set to readme.md, which in combination with base-uri of this element and its containing element resolves to api-appliction/mainframe-banking-system-facade/readme.md.