Architecture diagrams
Drawing the architecture and components of a solution so another person can understand their responsibilities and connections. Shared notation makes diagrams readable across teams.
Overview
Drawing the architecture and components of a solution on BTP so that another person can read the diagram. SAP's solution diagram guideline sets a visual language for this, so a diagram that follows it reads the same whoever drew it.
SAP publishes the visual language as the SAP BTP Solution Diagram GuidelinesSAP BTP Solution Diagram GuidelinesSAP's visual language for BTP solution diagrams, in line with the SAP Fiori Horizon principles and colour palette, with editable templates for draw.io and PowerPoint.sap official, btp, with editable templates for draw.iodraw.ioA diagram editor, on the web and as a desktop app. The BTP diagram skills here write .drawio files, and a person opens and edits them in it. and PowerPoint and a set of service icons for Lucidchart. SAP's reference architectures in SAP/architecture-centerSAP/architecture-centerThe repository the SAP Architecture Center site is built from: SAP's reference architectures, each drawn as editable draw.io diagrams, with Mermaid for flows.sap official, btp carry their diagrams as editable draw.io files, and its site runs an Architecture Validator that checks an uploaded draw.io diagram.
Not covered: It stops at the rules, the templates and a check of a diagram someone has already drawn. Nothing official turns a description into a diagram that follows them.
The community answer is a generator: agent skills and an MCP server that turn a described landscape into a diagram in this style, carrying SAP's icons and reference templates with them. Several also check what they drew before handing it over, either by reading the file or by looking at the rendered picture.
Artifacts
Tasks
Check a BTP solution diagram against the guideline
A BTP solution diagram exists, and before it goes into a document or a review someone wants to know whether it follows SAP's visual language rather than only looking about right.
About a diagram that has already been drawn, whoever or whatever drew it. Drawing one from a description is the rest of this capability and is not assessed here. Whether the architecture the diagram shows is a sound one is a different question that none of these checks answers.
SAP BTP Solution Diagram GuidelinesStates the visual language itself, in line with the SAP Fiori Horizon principles and colour palette. It is what every check here compares a diagram to; it runs no check of its own.
Remaining work: Read the rule and compare the diagram by eye, unless one of the other contributions does it.
btp-solution-diagram-generatorThe plugin states validating a .drawio diagram against the SAP Fiori Horizon guidelines beside generating and editing one, and ships validate_drawio.py as one of three helper scripts.
Remaining work: Install the plugin in Claude Code or Cowork and ask for the check; the README names no version of Python for the scripts.
drawio-btp-diagram-skillsWORKFLOW.md names a structural review Claude runs on the XML it wrote, and a visual review it runs on the screenshot the person pastes back. Both read the project's own rule and style files, which sit under its Japanese summary of SAP's guideline.
Remaining work: A person has to paste the diagram into draw.io and share the screenshot before the second review can happen.
sap-architecturevalidate.py reads the file for bent arrows, clipped labels, off-palette colours, off-grid coordinates, wrong stroke widths and non-Helvetica fonts, autofix.py repairs what it finds, and a second loop renders the diagram and scores the picture against the SAP corpus.
Conditions: Python 3.8 or later on the PATH: without it the validator and the scorer do not run, and the diagram is drafted without the checks
Remaining work: Install the skill and drive it from an agent; the checks run as part of the skill's pipeline rather than against a file someone brings to it.
ARC-DRAWThe maintainer lists a diagram linter that would check an existing .drawio file against the SAP guideline on the roadmap, so the release carries no such check. The guideline reaches the agent as a drawing constitution before the diagram, not as a check after it.
Remaining work: Read the drawn canvas by eye, or run one of the other contributions over the exported file.
Content
Seen working
Details
Coverage
Comparison properties
These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.
For your agent
- Ref
capability:architecture-diagrams- JSON
- /capabilities/architecture-diagrams.json
- MCP
- Connecting an agent