--- schema_version: "1" id: f8b14785b354c8b62ddf236826f9fea5b535aca971852cf48f45aead85232e3e title: How to Build Salesforce Diagrams collection: architect version: next locale: en-us portal_url: https://docs.salesforce.com/architect/next/en-us/reference-diagrams/guides/introduction.md canonical_url: https://staging.architect.salesforce.com/docs/architect/reference-diagrams/guide/introduction.html source_site: staging.architect.salesforce.com content_type: documentation content_hash: 81aa9f44a2bd6a734831ab4a055afbcfaa3c890f62582329162cbc5ad2adccfd products: - Reference Diagrams - Architect Site Content Repo updated_at: 2024-09-01T00:00:00Z --- ## Introduction Diagrams are an essential tool and a key part of architectural work. They enable us to communicate many different ideas to many different kinds of stakeholders. Diagrams help delivery teams stay aligned, by serving as a single source of truth about the realities of implementations and products. Diagrams are also a critical way to empower business stakeholders to make the right purchasing and technology decisions. **Diagrams should always:** - Read left to right and top to bottom, as closely as possible - Convey a message concisely, with an appropriate scope of information for readability - Utilize [Salesforce Diagrams Standard Components](/docs/architect/reference-diagrams/guide/kit-of-parts), including Cards and a Header with a clear description describing the content, scope and purpose of the diagram ## Diagram Scope The scope of a diagram should be limited to only the critical information to convey for a specific topic. Anything that is not required to capture the message you intend to communicate should be excluded. Multiple diagrams can (and should) be created to capture varying concepts, in order to more clearly communicate and narrow the focus of diagram content. - Define the critical information/message you need to convey to your audience - Classify logical scope(s) in order to focus the information to capture the message - Identify the most appropriate diagram type(s) to use as templates ## Diagram Types Salesforce Diagrams has defined our most useful/popular types of diagrams in order to help you easily utilize templates and understand diagramming conventions. Our current resources are classified as: ### Capability Maps - Capture the property mix and relevant, key capabilities included in a solution - Focus on functionality, business drivers and values ✨ Find Capability Maps in the [Reference Architecture Gallery](/docs/architect/reference-diagrams/guide/section-capability-map) ### System Landscapes - Capture the products and/or technical systems involved in a given implementation - Focus on the properties, specific property aspects, and connections across properties ✨ Find System Landscape examples & templates in the [Reference Architecture Gallery](/docs/architect/reference-diagrams/guide/section-system-landscape) ### Solution Architectures - Include products or technologies with integration, behavior and/or functionality - Focus on the detailed connections and/or communication aspects across properties ✨ Find Solution Architecture examples & templates in the [Reference Architecture Gallery](/docs/architect/reference-diagrams/guide/section-solution-architecture) ### Roadmaps - Help organizations plan and visualize the strategic implementation of capabilities, components, features, and systems over time - Provide a clear view of implementation order, dependencies, and priorities ✨ Find Roadmap examples & templates in the [Reference Architecture Gallery](/docs/architect/reference-diagrams/guide/section-roadmap) ### Interaction / Process / Flows - Capture time-based steps, data flows, or interactions required to support a process - Focus on and clarify (with sequenced numbering) the order of aspects/properties ✨ Find examples & templates of Interaction, Process, and Flow diagrams in the [Reference Architecture Gallery](/docs/architect/reference-diagrams/guide/section-interaction-process-flow) ### Data Models / ERDs - Capture entities (objects), relationships and concepts for metadata implementations ✨ Find Data Model examples & templates in the [Data Model Gallery](https://developer.salesforce.com/docs/platform/data-models/guide/get-started.html) See examples of the Diagram Types in the [Reference Architecture Gallery](/diagrams) or our dedicated [Data Model Gallery](https://developer.salesforce.com/docs/platform/data-models/guide/get-started.html). Utilize a template to quickly/easily create a diagram for your use case. ## Steps to create a diagram: - Define the **scope** of the message you need to convey: - _Think about your audience, what properties/aspects you need to depict, what information is necessary to capture the message, and what can be excluded_ - Ensure there is a **Header** with a clear **Title** and a concise, thoughtfully-worded **Description** that captures the purpose, scope and message of your diagram Ensure there is a Header with a clear Title and a concise, thoughtfully-worded Description that captures the purpose, scope and message of your diagram - Utilize **Cards** to capture the properties (systems, concepts, entities, etc.) - Capture property details or key aspects / capabilities as needed in **Card Attributes** Card Attributes - Depict relationships as needed with **Connectors** between your card properties Connectors - Incorporate **Card Icons** where useful, available and/or appropriate Card Icons - Use **Footers** and **Footer icons** to capture any other key property aspects Footer Icons **Warning:** due to a current limitation with Lucidchart, the footer icons in diagrams that are created from a template become undocked from the card. You will need to re-dock the icons by dragging them into the center of the footer. See the [Standard Components page](/docs/architect/reference-diagrams/guide/kit-of-parts) for more details and best practices. **Have Salesforce Diagrams input or questions?** Please let us know your thoughts [here](https://docs.google.com/forms/d/e/1FAIpQLSe5RmVA2ZtpfGlR2u436FA4QN6QmJGdAWxtZ_AcRLMAH_US9Q/viewform?usp=sf_link).