University enrollment
University enrollment — bpmn diagram with 11 nodes and 10 connections.
Diagram examples
Every diagram here was generated from a plain-language description. Open any one to see its structure live.
University enrollment — bpmn diagram with 11 nodes and 10 connections.
Conference Talk Submission Workflow — flowchart with 10 nodes and 11 connections.
Flowchart of an end-to-end ML pipeline showing data sources flowing into a raw data lake, ingestion, and a feature store, then training to a model registry and serving API for apps and users, with monitoring and drift feedback loops.
Stripe Checkout Payment Flow — sequence diagram with 4 nodes and 11 connections.
CDN Cache Miss and Origin Fetch — sequence diagram with 3 nodes and 7 connections.
SaaS Multi-Tenant ERD — er diagram with 8 nodes and 9 connections.
Hospital Patient Intake — bpmn diagram with 13 nodes and 15 connections.
Swimlane diagram of the airport check-in process across Passenger, Airline, Security, and Ground Crew roles. It follows document verification, boarding pass issuance, baggage check, parallel security screening, and the outcomes of boarding or denied check-in.
Flowchart of an on-call alert routing system, showing alerts moving from monitoring tools through ingestion, severity triage, and routing to responders. It also includes escalation paths, notification channels, incident tracking, and ticket creation.
BPMN swimlane diagram of a hospital patient intake process across Reception, Triage, Doctor, and Pharmacy. It follows the path from patient arrival and registration through vitals assessment, examination, medication dispensing, instructions, or emergency referral.
Sequence diagram of the OAuth 2.0 Authorization Code Flow, showing how the user, browser, client app, and authorization server interact during sign-in and code exchange.
BPMN diagram of a hospital patient intake workflow across Reception, Triage, Doctor, and Pharmacy lanes, from patient arrival and registration through vitals assessment, consultation, prescription, dispensing, and visit completion.
Class diagram of a payment system using the Strategy pattern: OrderService calls PaymentProcessor, which delegates to a PaymentGateway interface implemented by StripeGateway and PayPalGateway.
Entity-relationship diagram for a SaaS subscription database, showing organizations, users, plans, subscriptions, invoices, and payments and how billing records connect to customers and pricing plans.
Flowchart of a microservices platform where a client app sends requests through an API gateway to user, order, catalog, and payment services. It also shows separate databases, a message bus, and a notification service for asynchronous events.
Entity-relationship diagram for a food delivery platform, showing customers, restaurants, menus, menu items, drivers, orders, order items, and ratings. It maps how orders connect users, merchants, delivery, and feedback data.
BPMN workflow showing how a sales contract moves from drafting and legal review through finance and executive approval to signature and storage, with rejection paths when any approval fails.
BPMN workflow for a SaaS subscription renewal across Customer, CRM, Billing, and Support. It traces notice and offer review through payment success, activation, confirmation, or issue resolution leading to completion or cancellation.
BPMN diagram of a job recruitment pipeline with lanes for Candidate, HR, Hiring Manager, and Legal, tracing the process from application receipt and screening through interviews, selection, offer review, and issuing or closing the application.
BPMN swimlane diagram of an order fulfillment process across Customer, Sales, Warehouse, and Shipping. It covers checkout, payment verification, stock availability, picking and packing, dispatch, tracking, delivery, and cancellation if payment fails.
Flowchart of a CI/CD pipeline from GitHub commits through a webhook-triggered build, container image push to a Docker registry, deployment to staging, manual release approval, and promotion to production.
Flowchart of an e-commerce checkout process from cart review through payment and order confirmation, including decision points for cart validation, payment failure, retries, and checkout ending.
Recipe Data Model (ERD) — er diagram with 6 nodes and 10 connections.
ERD showing a recipe app data model, with entities for foodRecipe and ingredientInfo plus a recipe collection. It also includes code-related nodes like variable declaration and functions addRecipe() and displayRecipe(recipes) linked to the data flow.