SAP Business Technology Platform (BTP) Solution Diagrams

This project provides a repository of solution diagrams for the SAP Business Technology Platform (BTP). The diagrams follow official SAP BTP Solution diagram guidelines and are designed according to SAP Fiori Horizon principles and color palettes to ensure a consistent aesthetic. They are intended to visually represent the architecture and components of solutions built on SAP BTP.

You can view the rendered diagrams at: https://sap.github.io/btp-solution-diagrams/

This project provides the visual building blocks for creating SAP Business Technology Platform (BTP) solution diagrams used in SAP community blogs, missions, and the SAP Architecture Center. You can access three types of assets:

1. Editable Examples: Full diagram templates to use as a starting point.
2. draw.io Libraries: XML libraries containing BTP service icons and shapes specifically formatted for use in draw.io.
3. SVG Icons: Individual SVG files for all BTP service icons for use in other design tools.

SAP Business Technology Platform (BTP) Solution Diagrams are high-level, abstract illustrations of technical landscapes. They are used to showcase solution scenarios across IT landscapes by depicting SAP BTP services, systems, environments, and their interdependencies.

Key characteristics:

• Focus: Creating visually compelling, high-level solution architectures.
• Design System: Based on the SAP Fiori Horizon design system.
• Purpose: Helping customers understand the range of BTP Services and Solutions and how they integrate with other SAP products.

An SAP Business Technology Platform solution diagram is a schematic representation of end-to-end solution scenarios on SAP Business Technology Platform. These diagrams are used to illustrate:

• The operation of SAP Business Technology Platform.
• Various SAP BTP services, solutions, and SAP products.
• The specific ways these components are used within a solution architecture.

The provided BTP Solution Diagram examples are organized by granularity levels, which represent different depths of architectural detail:

• L0 (Level 0): High-level overview, typically showing the broadest scope of a solution.
• L1 (Level 1): Intermediate detail, showing more specific components and their relationships.
• L2 (Level 2): Deep dive, showing detailed technical components, connections, and specific service configurations.

Use the appropriate level based on whether you are presenting to business stakeholders (L0) or technical architects/developers (L2).

When designing architectures, distinguish between Technical Architecture Models (TAM) and SAP BTP Solution Diagrams:

In SAP BTP solution diagrams, numbers are used as visual markers to describe specific paths or sequences of flow within a diagram. This helps clarify complex architectural movements or step-by-step processes.

To use these in your diagrams, you must import the associated draw.io library from the project assets.

https://github.com/SAP/btp-solution-diagrams/tree/main/assets/shape-libraries-and-editable-presets/draw.io

Connectors are used in diagrams to represent non-, one-, or bidirectional arrows.

• One-directional arrows: Typically represent a request-response flow from a client to a server.
• Bidirectional solid arrows: May represent mutual trust between components.

To use these in your diagrams, you can find the associated draw.io library in the SAP BTP Solution Diagrams GitHub repository.

In the SAP BTP solution diagramming system, Organisms (also referred to as Component Groups) are higher-level abstractions composed of multiple Molecules.

An Organism can represent:

• A collection of grouped elements (e.g., a specific shape combined with text and connectors).
• A complete, high-level architectural layer or a whole diagram.

Use Organisms when you need to represent complex, logical groupings that go beyond individual atomic components or simple molecules.

To create visual hierarchies and represent different layers (such as nesting a service within a BTP environment), follow these nesting principles:

1. Contrast via Fill: When nesting areas inside each other, alternate between using a background fill and using no fill (outline only). This ensures sufficient visual contrast between the parent and child areas.
2. Parent Layering: The parent layer is typically the BTP layer (using SAP L0 styles).
3. Cardinality: Areas can be shown as stacked to display multiple grouped layers or items. Do not change the standard style to maintain diagram consistency.