Diagram examples
Every diagram here was generated from a plain-language description. Open any one to see its structure live.
Class diagram of a generic repository pattern built around IEntity. It shows IRepository<T> and Repository<T>, with Order and OrderItem as entity examples and OrderRepository as a concrete specialization.
Class diagram of a data access layer using the Repository pattern with a Unit of Work. It shows generic repository interfaces and implementations, domain entities like Customer, Order, and OrderItem, and coordination through DbContext.
Database Selection Guide — flowchart with 12 nodes and 19 connections.
This flowchart is used to map how student records connect to enrollment records, how courses link to each enrollment, and how professors teach courses within a university enrollment model. It helps teams clarify ownership of student, course, professor, and enrollment data, track semester and grade information, and spot relationship gaps when expanding class properties. It is useful for registrars, university admins, developers, and database designers.
This sequence diagram is used to detail the exact request/response flow for a browser login that requires TOTP-based MFA, including challenge creation and session issuance. It helps teams verify responsibilities and data passed between the Browser, Identity Service, TOTP App, and Session Store—from POST /login through creating a pending mfa_challenge, submitting /mfa/totp, validating the code, and returning Set-Cookie session_id. Backend engineers, security engineers, and QA use it to implement, test, and troubles...
A flowchart for feature flag rollout decisions, tracing each user request through a kill switch check, flag status, user-key hashing, rollout percentage evaluation, and final delivery of either the new feature or the existing flow before logging exposure. It is used to plan safer progressive releases, control blast radius, and verify fallback behavior, helping product teams, backend engineers, and SREs manage staged launches and rapid disablement.
This BPMN diagram is used to map insurance claim handling across the Claimant, Agent, Adjuster, and Accounting swimlanes, from loss reported and claim submission through completeness review, requests for more details, damage assessment, approval, payment, or denial. It helps clarify handoffs, decision points, and rework loops, and is used by insurers, operations teams, claims managers, agents, adjusters, and finance staff.
This BPMN Diagram maps FastFoot’s order fulfillment workflow across Sales, Warehouse, and Logistics, from order receipt and stock check to picking, packing, shipment booking, dispatch, and customer notification, with a decision for unavailable stock. It is used to clarify handoffs, responsibilities, and exceptions, helping teams improve coordination, reduce delays, and standardize execution. Sales managers, warehouse supervisors, logistics coordinators, and operations analysts would use it.
This sequence diagram is used to map the checkout path from customer submission through cart validation, card charging, failure handling, inventory reservation, and receipt delivery. It helps teams verify order of operations, error recovery with a retry screen after a failed charge, and service dependencies between Checkout, Payment Gateway, Inventory Service, and Email Service. Product managers, engineers, QA analysts, and solution architects would use it.
An ER Diagram for a university enrollment system, mapping how students with email and status enroll in courses identified by code and credit hours, while professors teach those courses and enrollments store semester and grade. It is used to design and validate the academic database, helping teams manage student registration, teaching assignments, and grade tracking. Typical users include database designers, developers, registrars, and academic operations staff.
This class diagram is used to model the core data and responsibilities in new hire onboarding, clarifying how HR creates a Profile for an Employee, IT provisions one or more Accounts for that Employee, and a Manager manages the Employee and assigns a buddy (another Employee). It also captures that Employees complete day-one Training items via a many-to-many relationship. HR teams, IT admins, and engineering teams use it to align data structures, ownership, and integrations across profile creation, account activati...
This ER diagram is used to design a university database that connects students to courses through enrollments, links each course to the professor who teaches it, and records detailed grade items per enrollment. It helps ensure correct keys and relationships for tracking rosters by term, enrollment status, and grading outcomes (scores and letters). Database designers, campus IT teams, and registrar or academic operations staff would use it to build and validate student information and reporting systems.
This BPMN diagram is used to standardize how a support issue moves from customer submission through support triage, info requests, and a decision to resolve in support or escalate to engineering for a fix and QA validation. It helps teams clarify handoffs, decision points (need more info, can support resolve, tests pass, customer confirms), and the rework loops for failed tests or unresolved outcomes. Support leads, engineering, QA, and customer success teams use it to align responsibilities and reduce resolution...
This flowchart is used to map how IoT devices publish MQTT telemetry to a broker, how a stream processor routes that event data into a telemetry store, analytics warehouse, and alerting webhooks, and how a dashboard reaches registry and telemetry data through an API gateway. It helps teams design ingestion, monitoring, and integration paths, and is useful for IoT architects, backend engineers, platform teams, and technical stakeholders.
This flowchart is used to document an event-driven order processing architecture where order clients send requests through an API gateway to an order service, which writes to the order database and publishes events to Kafka for downstream consumers. It helps teams understand request flow, event handling, failure paths through the dead-letter queue, and archival to S3. Software architects, backend engineers, platform teams, and operations staff would use it.
This Sequence Diagram is used to map how a bank loan application moves from the Applicant through the Loan Portal, Loan DB, Underwriting Engine, and Credit Bureau to an approval outcome. It helps teams understand submission, data storage, credit report retrieval, risk assessment, decision updates, and applicant notification, making handoffs and dependencies clear for product managers, solution architects, developers, QA analysts, and banking operations teams.
This state diagram is used to model how an ATM moves from power on and idle through card reading, PIN entry, menu selection, amount entry, processing, cash dispensing, receipt printing, card ejection, card retention after three failed PIN attempts, and out-of-service recovery. It helps clarify valid transitions, exception handling, and session outcomes for banking software teams, QA testers, ATM product managers, and operations staff.
A State Diagram for a support ticket lifecycle, covering New, Triage, Assigned, In Progress, Escalated, Pending Vendor, Resolved, Closed, and Cancelled, with conditions such as missing details, no response timeouts, SLA breach risk, misrouting, reopen, and vendor dependency. It is used to define allowed status changes, improve handoffs and exception handling, and help support managers, service desk teams, and operations leads standardize ticket handling.
A state diagram for a CI/CD pipeline job maps how work moves from job created to Queued, then Running when a runner is assigned, and finally to Passed, Failed, or Cancelled before completion. It is used to define valid job status changes, helps teams reason about execution outcomes, cancellations, and automation rules, and is useful for DevOps engineers, platform teams, QA, and developers maintaining build and release workflows.
A flowchart for a CI/CD deployment pipeline that starts with a code push, moves through build, unit, integration, staging, smoke testing, manual approval, production release, health monitoring, and rollback on failure. It is used to define release control points, clarify pass or fail paths, and reduce deployment risk. DevOps engineers, software teams, QA leads, and release managers use it to align responsibilities and improve delivery reliability.
A sequence diagram for a CI/CD pipeline where a GitHub commit triggers the build server, which builds and tests the application, pushes a Docker image to the registry, deploys it to staging for verification, and then promotes it to production. It is used to clarify deployment order, handoffs, and acknowledgements, helping teams validate release flow, spot bottlenecks, and align automation. DevOps engineers, platform teams, and developers would use it.
A sequence diagram for a Kafka producer-consumer flow with offset commit, mapping how a Producer publishes a record to a Kafka Broker, how a Consumer Group polls and processes the returned batch, and how offsets are committed to an Offset Store with acknowledgment. It is used to clarify delivery and consumption order, support debugging of acknowledgment and offset handling, and help backend engineers, data platform teams, and architects design reliable event-driven systems.
A BPMN job recruitment pipeline maps how a candidate moves from application submission through HR resume screening, interview scheduling, hiring manager evaluation, legal contract review, and final offer acceptance or closure. It is used to clarify handoffs and decision points, helping teams reduce delays, standardize hiring, and spot bottlenecks. HR teams, hiring managers, recruiters, legal reviewers, and operations leaders would use it.
This ER diagram is used to design and validate a food delivery platform database by mapping how restaurants own menus and menu items, customers place orders, orders contain order items, drivers handle deliveries, and customers leave ratings tied to orders, restaurants, and drivers. It helps teams structure data, enforce relationships, and support ordering, delivery tracking, and feedback features, making it useful for product managers, developers, DBAs, and system architects.