Diagram examples

Diagram examples — page 8 of 8

Every diagram here was generated from a plain-language description. Open any one to see its structure live.

BPMN Diagram 4/16/2026

Vendor Procurement BPMN Diagram for Requisition, Approval, PO, and Payment

This BPMN diagram is used to manage vendor procurement from a requester’s identified need through requisition review, quote collection, budget approval, purchase order confirmation, receipt of goods or services, invoicing, and payment. It helps teams clarify handoffs, approval points, and rejection or clarification loops across Requester, Procurement, Finance, and Vendor swimlanes, and is used by procurement managers, finance teams, requesters, vendors, and process analysts.

BPMNProcurementPurchase OrderBudget ApprovalVendor Workflow
17 nodes 17 connections 4 lanes
ER Diagram 4/16/2026

Expense Reimbursement ER Diagram: Employee, Manager, Finance & Accounting Flow

This ER diagram is used to map the handoffs in an expense reimbursement case across Employee, Manager, Finance, and Accounting. It helps teams clarify who submits, reviews, approves, requests clarification, rejects, and ultimately pays and closes the case, including rework loops after manager rejection or finance clarification. HR ops, finance teams, accountants, and process owners use it to align responsibilities and reduce delays and compliance issues.

ER DiagramExpense reimbursementApprovalsFinance operationsAccounting
4 nodes 8 connections
ER Diagram 4/16/2026

University System ER Diagram for Courses, Sections, Enrollments, and Grading

This ER diagram is used to design a university academic database by defining how Students, Departments, Courses, Professors, Terms, and CourseSections relate through Enrollments and track learning via Assignments and Submissions. It helps teams enforce referential integrity for course offerings, section scheduling, teaching assignments, prerequisite rules, enrollment status, grades, and submission scoring. It’s used by database designers, developers, and registrar/academic systems analysts.

ER DiagramUniversity databaseCourse enrollmentAcademic recordsSchema design
10 nodes 12 connections
BPMN Diagram 3/30/2026

Loan Origination BPMN Diagram with Swimlanes

A BPMN diagram for loan origination that maps how the Applicant, Loan Officer, Underwriting, and Operations coordinate from application submission through document collection, underwriting, approval or rejection, offer acceptance, and loan booking. It is used to clarify handoffs, decision points, and rework around missing documents, helping teams improve compliance, cycle time, and accountability. Banks, lenders, operations managers, analysts, and process owners would use it.

BPMN DiagramLoan OriginationUnderwritingSwimlanesBanking Process
14 nodes 14 connections 4 lanes
State Diagram 3/20/2026

CI/CD Pipeline Job State Diagram

A state diagram for a CI/CD pipeline job maps how work moves from Queued to Running, then ends as Passed, Failed, or Cancelled, with cancellation possible before or during execution. It is used to define valid job behavior and terminal outcomes, helping teams reason about automation flow, error handling, and interruption rules. DevOps engineers, platform teams, QA leads, and developers would use it to align pipeline design and operations.

CI/CDstate diagrampipeline jobdevopsjob lifecycle
5 nodes 5 connections
BPMN Diagram 3/20/2026

BPMN Loan Application Approval Process with Customer, Bank, and Credit Bureau

A BPMN loan application approval diagram used to map how a customer submits an application, the bank checks completeness and assesses risk, and the credit bureau generates and returns a credit report before approval or rejection. It helps teams clarify responsibilities, decision points, and handoffs, and is used by bank operations staff, business analysts, compliance teams, and lending managers.

BPMNLoan ApprovalBanking ProcessCredit BureauSwimlane Diagram
17 nodes 17 connections 3 lanes
State Diagram 3/20/2026

SaaS Subscription State Diagram for Trial, Billing, Pause, and Cancellation

This State Diagram is used to model a SaaS subscription lifecycle across Trial, Active, Past Due, Paused, and Cancelled states, including key transitions such as trial conversion, payment failure, payment recovery, pause, resume, and cancellation after dunning is exhausted. It helps teams define billing rules, user access behavior, and edge cases clearly, and is used by product managers, engineers, billing teams, and operations staff.

State DiagramSaaS billingSubscriptionsTrial lifecycleDunning
5 nodes 9 connections
BPMN Diagram 3/20/2026

BPMN Online Order Fulfillment: Payment, Inventory, Shipping & Tracking

This BPMN diagram is used to standardize how an online order moves across Customer, Sales, Warehouse, and Shipping—from submitting an order and validating payment, through inventory checks with a backorder/restock path, to pick & pack, shipment creation, carrier handoff, and tracking sent before receipt. It helps teams pinpoint handoffs, decision points, and rework loops (payment retry/cancel) to reduce delays. Operations managers, process analysts, and fulfillment leads would use it.

BPMNOrder fulfillmentEcommerce opsInventoryShipping
17 nodes 18 connections 4 lanes
Sequence Diagram 3/18/2026

Kafka Producer-Consumer Sequence with Consumer Group Join, Fetch, and Offset Commit

This sequence diagram is used to clarify the end-to-end message flow in Kafka from a Producer sending Produce(topic, partition, key, value) to a Kafka Broker acking with an offset, then a Consumer Group joining and receiving partition assignments before fetching records from the last committed offset. It helps teams reason about delivery guarantees, partition ownership, and when offsets are persisted via CommitOffset and the broker’s write to the Offset Store. It’s used by backend engineers, SREs, and platform tea...

KafkaSequence DiagramConsumer GroupOffset CommitEvent Streaming
4 nodes 11 connections
Class Diagram 3/18/2026

Event Sourcing Class Diagram: EventStore, Aggregates, Command Bus, and Projections

This class diagram is used to clarify an event-sourced architecture by showing how CommandBus routes a Command to a CommandHandler, which loads and saves an AggregateRoot through an EventSourcedRepository backed by an EventStore. It helps teams reason about consistency, versioning, and event flow as AggregateRoot emits DomainEvent instances that the EventStore appends, loads, and publishes via an EventBus. Developers and architects use it to design write models and read models, where a Projector subscribes to even...

event sourcingclass diagramCQRSEventStoreprojections
11 nodes 13 connections