mradermacher/Qwen3-0.6B-text2mermaid-GGUF
0.6B • Updated • 487
prompt stringlengths 8 593 | output stringlengths 70 2.03k | diagram_type stringclasses 6
values |
|---|---|---|
Produce a flowchart that captures the main student film path plus its revision or recovery loop. | flowchart BT
A([Prepare camera]) --> B[Light scene]
B --> C{Image ready}
C -->|Yes| D[Record take] --> F[Review playback]
C -->|No| E[Relight setup] --> F
F --> H[(Record completion)]
H --> G([Move forward]) | flowchart |
Create a complex state diagram for city snow response combining a guarded response choice, standard and enhanced paths, parallel operational and communication work, a join, final validation, success, and escalation. | stateDiagram-v2
[*] --> CitySnowResponseInitiated
CitySnowResponseInitiated --> CitySnowResponseAssessing: response begins
CitySnowResponseAssessing --> CitySnowResponseResponseChoice: assessment complete
state CitySnowResponseResponseChoice <<choice>>
CitySnowResponseResponseChoice --> CitySnowResponseStanda... | stateDiagram-v2 |
Describe, in Mermaid sequence form, the distributed path used to publish metric. | sequenceDiagram
actor A as Engineer
participant C as Dashboard
participant G as Query API
participant D as Metrics Store
A->>C: Publish metric
C->>+G: Submit request
G->>D: Read publish metric state
D-->>G: Current record
G->>D: Persist publish metric
D-->>G: Commit confirmed
... | sequenceDiagram |
A Billing Manager sends monthly invoices from the Billing Console. The Billing Console asks the Usage Service and Plan Catalog for usage and rates concurrently, calculates each invoice, stores it in the Invoice Store, and uses the Delivery Service to notify each Customer. | sequenceDiagram
actor M as Billing Manager
participant B as Billing Console
participant U as Usage Service
participant P as Plan Catalog
participant I as Invoice Store
participant D as Delivery Service
M->>B: Start monthly invoicing
par Load measured usage
B->>U: Retrieve Custome... | sequenceDiagram |
Trace shared Exhibit objects aggregated by Exhibition, with every item associated to one Collection. | classDiagram
class Exhibition {
+String title
-String status
+open()
+close()
}
class Exhibit {
+String name
-int position
+activate()
+archive()
}
class Collection {
+String code
-String label
+resolve()
}
... | classDiagram |
Turn close stocktake into a sequence | sequenceDiagram
actor A as Operator
participant G as Inventory API
participant Q as Replenishment Queue
participant S as Stock Service
participant D as Inventory DB
A->>G: Close stocktake
G->>Q: Enqueue close stocktake command
G-->>A: Accept request
Q-->>S: Deliver command
S->>D:... | sequenceDiagram |
Using this scenario into stateDiagram-v2: road closure needs normal and priority queues, assignment, requeueing, and completion. Show the entry point, label meaningful events, and connect every final outcome to an end state. | stateDiagram-v2
[*] --> RoadClosureQueued
RoadClosureQueued --> RoadClosurePriority: expedite
RoadClosurePriority --> RoadClosureQueued: downgrade
RoadClosureQueued --> RoadClosureAssigned: worker available
RoadClosurePriority --> RoadClosureAssigned: priority worker available
RoadClosureAssigne... | stateDiagram-v2 |
A Cyclist unlocks a shared bicycle with the Bike App. The Bike App asks the Dock Service to release it and starts billing with the Trip Service. When the Cyclist ends the ride, the Dock Service confirms docking, the Trip Service calculates the fare, and the Bike App shows the receipt. | sequenceDiagram
actor A as Cyclist
participant B as Bike App
participant C as Dock Service
participant D as Trip Service
A->>B: Request bike unlock
B->>C: Release bicycle
C-->>B: Bike unlocked
B->>D: Start trip billing
D-->>B: Trip started
A->>B: End ride
B->>C: Confirm bicyc... | sequenceDiagram |
Charity auction online: bidders place bids on the auction platform, the platform updates the highest bid and outbids notification to the previous high bidder, and at close the platform charges the winner and records the proceeds for the nonprofit. | sequenceDiagram
actor B1 as Bidder 1
actor B2 as Bidder 2
participant AP as Auction Platform
participant PG as Payment Gateway
participant NP as Nonprofit
B1->>AP: Place bid
B2->>AP: Place higher bid
AP-)B1: You have been outbid
Note over AP: Auction closes
AP->>PG: Charge winnin... | sequenceDiagram |
A Customs Broker submits a bond request through the Bond Portal. The Bond Portal asks the Surety Service to assess it. If approved, send the bond number to Customs and confirm to the Customs Broker; if declined, provide the reason without filing. | sequenceDiagram
actor A as Customs Broker
participant B as Bond Portal
participant C as Surety Service
actor D as Customs
A->>B: Submit bond request
B->>C: Assess bond application
alt Bond is approved
C-->>B: Bond number
B->>D: File bond number
D-->>B: Filing accepted
B-->>A:... | sequenceDiagram |
Show a failed direct-debit mandate setup. The customer enters bank details and authorizes the mandate. The bank validates ownership; if validation fails, ask for corrected details and try again. Once valid, activate the mandate, schedule the first debit, and notify the customer. | flowchart TD
A[Enter bank details] --> B[Authorize mandate]
B --> C[Bank validates ownership]
C --> D{Ownership validated?}
D -->|No| E[Request corrected details]
E --> A
D -->|Yes| F[Activate mandate]
F --> G[Schedule first debit]
G --> H[Notify customer] | flowchart |
Given this Gateway scenario, diagram classes where API-key and OAuth strategies implement one authentication interface used by a gateway and constrained by policy. | classDiagram
class GatewayAuthStrategy {
<<interface>>
+authenticate()
}
class GatewayApiKeyAuth {
+authenticate()
}
class GatewayOAuthAuth {
+authenticate()
}
class GatewayGateway {
+authorize()
}
class GatewayAccessPolicy {
+evaluate(... | classDiagram |
Show the mortgage process split by who does the work. The borrower submits an application and supplies documents. The loan officer checks completeness and orders an appraisal. The underwriter assesses risk and issues the approval. Group the steps by these three roles. | flowchart LR
subgraph Borrower
A[Submit application] --> B[Supply documents]
end
subgraph Loan Officer
C[Check completeness] --> D[Order appraisal]
end
subgraph Underwriter
E[Assess risk] --> F[Issue approval]
end
B --> C
D --> E | flowchart |
Describe the steps for joining a local workshop and receiving a registration email. | flowchart TB
A[Browse Workshops] --> B[Choose Session] --> C[Submit Registration] --> D[Pay Fee] --> E[Receive Registration Email] | flowchart |
Our a compact workflow for airport lightning hold that shows both successful handling and the contingency response. | flowchart TB
A(["Lightning alert triggers"]) --> B["Stop ramp activity"]
B --> C{"Strike window expired?"}
C -->|Yes| D["Resume ground handling"]
C -->|No| E["Keep teams sheltered"]
E --> B
D --> F(["Notify operations"]) | flowchart |
Illustrate Dean ownership of ResearchProject records. | classDiagram
class Dean {
+String id
+submit()
}
class ResearchProject {
-String status
+approve()
}
class ResearchProjectEntry {
-int sequence
+validate()
}
Dean "1" --> "0..*" ResearchProject : submits
ResearchProject "1" *-- "1..*" Resea... | classDiagram |
Diagram transient processing errors with delayed retries, eventual success, or failure after the limit. | stateDiagram-v2
[*] --> ApplicationWaiting
ApplicationWaiting --> ApplicationWorking: worker starts
ApplicationWorking --> ApplicationSucceeded: success
ApplicationWorking --> ApplicationRetryDelay: temporary error
ApplicationRetryDelay --> ApplicationWorking: retry
ApplicationRetryDelay --> ApplicationFail... | stateDiagram-v2 |
Produce a repository-oriented class diagram for space exploration. A FlightService depends on SpaceMissionRepository to persist SpaceMission objects; each aggregate contains Experiment entries associated with Spacecraft, while Astronaut can create many aggregates. Include meaningful members and multiplicities. | classDiagram
class Astronaut {
-String id
-String displayName
+requestAction()
#verifyIdentity()
}
class SpaceMission {
-String reference
#Date createdAt
~String status
+submit()
+cancel()
#validate()
}
class Experiment ... | classDiagram |
Represent this scenario as a sequence diagram: preparing a mining blast area. The Blast Supervisor begins readiness checks. At the same time, the Drill Crew confirms hole preparation, the Safety Officer confirms the exclusion zone, and the Control Room confirms nearby equipment is stopped. After all replies, the superv... | sequenceDiagram
participant BS as Blast Supervisor
participant DC as Drill Crew
participant SO as Safety Officer
participant CR as Control Room
BS->>DC: Confirm hole preparation
BS->>SO: Confirm exclusion zone
BS->>CR: Confirm equipment stopped
par Drill readiness
DC-->>BS: Holes prepared
and Safety readiness
SO-->>BS:... | sequenceDiagram |
Simple ETL: extract from API, transform, load to warehouse | flowchart LR
A[Extract from API] --> B[Transform records]
B --> C[(Load to warehouse)] | flowchart |
What does the path through governance exception look like from intake to completion? | flowchart RL
A[Submit exception] --> B[Assess policy impact]
B --> C{Risk tolerable?}
C -->|Pass| D[Approve temporarily] --> F([Set expiry date])
C -->|Revise| E[Reject request]
E -.-> B | flowchart |
Casting defect root cause using fishbone-style branches but as a flowchart: porosity found, check melt temperature, mold venting, and degassing in parallel, then decide corrective action. | flowchart TD
A[Porosity found in casting] --> B[Check melt temperature]
A --> C[Check mold venting]
A --> D[Check degassing]
B --> E[Decide corrective action]
C --> E
D --> E | flowchart |
Encode builder classes assembling Production. | classDiagram
class ProductionBuilder {
-Boolean available
+execute()
+audit()
}
class Production {
+String title
-String status
+open()
+close()
}
class Scene {
+String name
-int position
+activate()
+archive()
... | classDiagram |
A Guest uses the Hotel App to request extra towels. The Hotel App creates a task in Housekeeping Dispatch, which offers it to a Room Attendant. If accepted, notify the Guest of the estimate; after delivery, the Room Attendant closes the task and the Guest receives confirmation. | sequenceDiagram
actor A as Guest
participant B as Hotel App
participant C as Housekeeping Dispatch
actor D as Room Attendant
A->>B: Request extra towels
B->>C: Create delivery task
C->>D: Offer towel task
D-->>C: Accept task
C-->>B: Delivery estimate
B-->>A: Show delivery estimat... | sequenceDiagram |
Show the nondisclosure agreement from Draft to Active. | stateDiagram-v2
[*] --> NondisclosureAgreementDraft
NondisclosureAgreementDraft --> NondisclosureAgreementSigned: parties sign
NondisclosureAgreementSigned --> NondisclosureAgreementActive: effective date arrives
NondisclosureAgreementActive --> [*] | stateDiagram-v2 |
document approval acceptance criteria: use sequenceDiagram syntax, name the business participants, show the request to distribute a released manual, query Document Store, invoke Recipient Directory, and return distribution report; model a recipient address is invalid as the alternative outcome. | sequenceDiagram
autonumber
actor A as Document Controller
participant P as Control Portal
participant S as Distribution Service
participant R as Document Store
participant W as Recipient Directory
A->>P: distribute a released manual
P->>+S: submit request
S->>+R: load authorized reci... | sequenceDiagram |
Acceptance criteria for a vaccination visit: the Patient checks in, the Nurse asks screening questions and administers the vaccine, and the Patient waits 15 minutes for observation. If an adverse reaction appears during observation, the Patient reports symptoms and the Nurse provides immediate care. | sequenceDiagram
participant Patient
participant Nurse
Patient->>Nurse: Check in
Nurse->>Patient: Ask screening questions
Nurse->>Patient: Administer vaccine
Patient->>Patient: Wait 15 minutes for observation
opt Adverse reaction
Patient->>Nurse: Report symptoms
Nurse->>Patien... | sequenceDiagram |
Construct a view of how LearningService implements a port and processes LessonProgress with owned ExerciseAttempt components. | classDiagram
class LearningServicePort {
<<interface>>
+execute()
}
class LearningService {
-Boolean ready
+execute()
}
class Learner {
-String learnerId
+start()
}
class LessonProgress {
-String status
+validate()
}
cla... | classDiagram |
At hospital discharge, the Pharmacist reviews the Patient's medication list and checks for interactions; if a problem is found, the Pharmacist contacts the Prescriber and receives a corrected prescription. Once the list is final, the Pharmacist counsels the Patient on each medication. | sequenceDiagram
participant Pharmacist
participant Prescriber
participant Patient
Pharmacist->>Pharmacist: Review medication list
opt Interaction found
Pharmacist->>Prescriber: Report interaction
Prescriber-->>Pharmacist: Adjusted prescription
end
Pharmacist->>Patient: Counse... | sequenceDiagram |
A Shopper cancels an order in the Store App before shipment. The Store App asks the Fulfillment Service whether packing has started. If not, cancel fulfillment and request a payment void from the Acquirer; if packing has started, deny cancellation and direct the Shopper to the return process. | sequenceDiagram
actor S as Shopper
participant A as Store App
participant F as Fulfillment Service
participant C as Acquirer
S->>A: Cancel order
A->>F: Check packing status
F-->>A: Packing status
alt Packing has not started
A->>F: Cancel fulfillment
F-->>A: Fulfillment ca... | sequenceDiagram |
I need the message flow for warehouse crane move; include Warehouse System, Crane Gateway, Motion Controller, and Stacker Crane. Run operation and response preparation in parallel. | sequenceDiagram
actor A as Warehouse System
participant G as Crane Gateway
participant S as Motion Controller
participant D as Stacker Crane
A->>G: request a pallet move
G->>S: Send request
par Execute operation
S->>D: execute travel and lift
D-->>S: Operation response
an... | sequenceDiagram |
Musicians planning interactive gallery: I need a flowchart that starts with Receive artifact, checks Records complete, and ends with Update database for interactive gallery. | flowchart LR
A[Receive artifact] --> B[Check documentation]
B --> C{Records complete}
C -->|Primary| D[Catalog object]
C -->|Fallback| E[Request missing details]
D --> F[Assign storage]
E --> F
F --> G{Ready to finish}
G -->|Yes| H([Update database])
G -->|No| B | flowchart |
Capture CoAP observe registration as a sequence diagram where Battery Sensor works through CoAP Client, Edge Proxy, and Resource Server. | sequenceDiagram
actor A as Battery Sensor
participant B as CoAP Client
participant C as Edge Proxy
participant D as Resource Server
participant E as Observer Registry
A->>B: subscribe to resource changes
B->>C: send observe request
C->>D: register observation token
D-->>C: validation... | sequenceDiagram |
A Cashier closes a register in Point of Sale. Point of Sale retrieves card totals from Payment Service and cash totals from Cash Drawer, compares them, and shows Cashier whether the register balances. If it does not, Cashier enters a discrepancy note that Point of Sale saves. | sequenceDiagram
actor A as Cashier
participant B as Point of Sale
participant C as Payment Service
participant D as Cash Drawer
A->>B: Start register close
B->>C: Get card totals
C-->>B: Card total
B->>D: Get cash total
D-->>B: Cash total
B->>B: Compare expected and counted total... | sequenceDiagram |
Model the fault-tolerant states of document OCR job, showing preparation, processing, verification, retry backoff, recovery, timeout failure, and a reliability note. | stateDiagram-v2
[*] --> DocumentOCRJobQueued
DocumentOCRJobQueued --> DocumentOCRJobPreparing: worker assigned
DocumentOCRJobPreparing --> DocumentOCRJobProcessing: prerequisites ready
DocumentOCRJobProcessing --> DocumentOCRJobVerifying: processing finished
DocumentOCRJobVerifying --> DocumentOCRJobComplete:... | stateDiagram-v2 |
Password hashing: Represent a factory that creates PasswordHash instances, can return ArgonHash, applies HashPolicy, and registers results through HashRepository. | classDiagram
class PasswordHashFactory {
+PasswordHash create()
}
class PasswordHash {
+String id
}
class ArgonHash {
+specialize()
}
class HashPolicy {
+configure()
}
class HashRepository {
+save()
}
PasswordHash <|-- ArgonHash
Pas... | classDiagram |
Detail parallel checks before create reminder. | sequenceDiagram
actor U as User
participant A as Assistant App
participant C as Account Service
participant P as Policy Service
participant S as Reminder Service
U->>A: Create reminder
par Check account
A->>C: Validate account
C-->>A: Account valid
and Check policy
... | sequenceDiagram |
Could you diagram edit message between Messaging SDK, Message Gateway, and the supporting Delivery Service? | sequenceDiagram
actor A as Sender
participant G as Message Gateway
participant S as Delivery Service
participant D as Message Store
participant O as Telemetry Agent
A->>G: Edit message
G->>+S: Validate request
S->>D: Load policy and state
D-->>S: Validation context
alt Request al... | sequenceDiagram |
Build a state chart for music video take. | stateDiagram-v2
state "Planned" as MusicVideoTakePlanned
state "Rehearsing" as MusicVideoTakeRehearsing
state "Recording" as MusicVideoTakeRecording
state "Reviewing" as MusicVideoTakeReviewing
state "Approved" as MusicVideoTakeApproved
[*] --> MusicVideoTakePlanned
MusicVideoTakePlanned -->... | stateDiagram-v2 |
A Privacy Service receives a deletion request from the Customer Portal. It deletes personal data from the Profile Database and Order Database in parallel, then writes an audit entry to the Audit Database and confirms completion to the portal. | sequenceDiagram
participant Portal as Customer Portal
participant Privacy as Privacy Service
participant Profile as Profile Database
participant Orders as Order Database
participant Audit as Audit Database
Portal->>Privacy: Request personal data deletion
par Delete profile data
Privacy->>Profile: Delete personal record... | sequenceDiagram |
Diagram repeated coordination for museum timed entry, then send a final result to Visitor. | sequenceDiagram
autonumber
actor A as Visitor
participant C as Museum Portal
participant S as Reservation Service
participant B as Capacity Calendar
participant O as Email Service
Note over C,S: Retry transient coordination for museum timed entry
A->>C: book an entry slot
C->>S: requ... | sequenceDiagram |
For the domain team, capture a class diagram where WorkOrder creates AssemblyBatch records composed of AssemblyStep entries referencing WorkCell. | classDiagram
class WorkOrder {
-String id
+release()
}
class AssemblyBatch {
-String status
+close()
+validate()
}
class AssemblyStep {
-String sequence
+assemble()
}
class WorkCell {
-String code
+inspect()
}
cl... | classDiagram |
Frame the school field trip completion route procedure as a Mermaid flowchart for an operations guide. Use a queue based path with success and rework outcomes, label every decision outcome, keep the sequence readable, and connect each normal, retry, or exception path to a clear result. | flowchart RL
A[Receive trip proposal] --> Q[[Completion School Field Trip Queue]]
Q --> B[Review trip budget] --> C{Budget approved?}
C -->|Success| D[Book transport] --> E[Notify families]
C -->|Retry| F[Revise trip plan] --> Q | flowchart |
Can you map photo selection with labeled arrows and the more photos? retry loop in the appropriate place? | flowchart TB
A[Import Photos] --> B[Review Photo]
B --> C[Rate Photo]
C --> D{More Photos?}
D -->|No| B
D -->|Yes| E[Export Favorites] | flowchart |
Cemetery plot purchase through the parks department. Buyer picks a section, staff checks availability. Available plots can be reserved with a deposit, and full payment converts to a deed. Unavailable plots lead to a waiting list. | flowchart TD
A[Buyer chooses section] --> B{Plot available?}
B -->|No| C[Add to waiting list]
B -->|Yes| D[Reserve with deposit]
D --> E[Full payment]
E --> F([Deed issued]) | flowchart |
Given the observability components, show the interaction needed to open trace. | sequenceDiagram
actor A as Engineer
participant G as Query API
participant Q as Ingest Queue
participant S as Telemetry Service
participant D as Metrics Store
A->>G: Open trace
G->>Q: Enqueue open trace command
G-->>A: Accept request
Q-->>S: Deliver command
S->>D: Save open trace... | sequenceDiagram |
Flowchart showing a thick arrow for the critical path in launching a pop-up store: lease signed, then fit-out, then stock delivery, then opening day. A dotted arrow from lease signed to marketing announcement, which also feeds opening day. | flowchart LR
A[Lease signed] ==> B[Fit-out]
B ==> C[Stock delivery]
C ==> D([Opening day])
A -.-> E[Marketing announcement]
E -.-> D | flowchart |
Design the decision path for runway debris report, including the normal action, fallback action, and final closeout. | flowchart LR
A(["Pilot reports debris"]) --> B["Suspend runway arrivals"]
B --> C{"Debris located?"}
C -->|Yes| D["Remove foreign object"]
C -->|No| E["Conduct full runway sweep"]
E --> B
D --> F(["Release runway"]) | flowchart |
Likewise, Describe the interaction flow after Administrator chooses to restore a database backup. | sequenceDiagram
autonumber
actor U as Administrator
participant A as Recovery Console
participant S as Backup Service
participant D as Archive Store
participant W as Database Cluster
U->>A: restore a database backup
A->>S: select recovery point
Note left of S: Coordinate database bac... | sequenceDiagram |
Document the evidence request as a Mermaid state diagram with 9 states. Start in Planned, show the normal review path, include the evidence arrives branch into EvidenceReview, and model the loop back for reconsideration before a terminal outcome. | stateDiagram-v2
[*] --> EvidenceRequestPlanned
EvidenceRequestPlanned --> EvidenceRequestFieldwork: begin
EvidenceRequestFieldwork --> EvidenceRequestEvidencePending: request evidence
EvidenceRequestEvidencePending --> EvidenceRequestEvidenceReview: evidence arrives
EvidenceRequestEvidencePending --... | stateDiagram-v2 |
Robot software hot fix with canary: DevOps Engineer pushes a patch to the Fleet Server. The server deploys to one Canary Robot first and waits for health metrics. If healthy, it deploys to the rest of the Robots. If unhealthy, it rolls back the canary and notifies the engineer. | sequenceDiagram
actor E as DevOps Engineer
participant S as Fleet Server
participant C as Canary Robot
participant R as Other Robots
E->>S: Push patch
S->>C: Deploy patch
C-->>S: Health metrics
alt Healthy
S->>R: Deploy patch
R-->>S: Updated
else Unhealthy
S->... | sequenceDiagram |
Build a TD iterative flowchart for warehouse cycle counting. Loop from review through revision until 'Quantity matches system?', but add a separate limit check that exits to post approved adjustment. | flowchart TD
A(["Count list generated"]) --> B["Count storage bin"] --> C{"Quantity matches system?"}
C -->|Yes| D(["Confirm inventory"])
C -->|No| E["Recount discrepancy"] --> F["Research stock movements"] --> G{"Difference resolved?"}
G -->|No| B
G -->|Yes| H(["Post approved adjustment"]) | flowchart |
Turn insurance policy servicing into a readable class diagram emphasizing a command object. | classDiagram
class Policyholder {
+String id
+invoke()
}
class CreatePolicyChangeCommand {
+String requestId
+execute()
+undo()
}
class PolicyService {
+execute()
}
class PolicyChange {
-String reference
+submit()
}
clas... | classDiagram |
Create a model deployment governance flow. Register the candidate model, attach evaluation results and intended use, and check for prohibited use cases. Prohibited use blocks deployment. Otherwise compare metrics with approval thresholds, request human approval when they pass, and deploy only after approval, followed b... | flowchart TD
A[Register candidate model] --> B[Attach evaluation and intended use]
B --> C{Use case prohibited?}
C -->|Yes| D[Block deployment]
C -->|No| E[Compare approval metrics]
E --> F{Metrics pass?}
F -->|No| G[Return for improvement]
F -->|Yes| H[Request human approval]
H --> I{Ap... | flowchart |
Requirement a sequence diagram for request an official transcript, from the Learning Portal request through the Course Service response. | sequenceDiagram
actor A as Learner
participant U as Learning Portal
participant S as Course Service
participant D as Academic Store
A->>U: request an official transcript
U->>S: Start request
S->>D: Find matching record
alt Record found
D-->>S: Record
S-->>U: transcript or... | sequenceDiagram |
Cobot handover — please trace Assembler's request through Workstation Panel, Handover Service, and Collaborative Robot, ending with handover acknowledgment. Branch on dependency success or failure. | sequenceDiagram
actor A as Assembler
participant G as Workstation Panel
participant S as Handover Service
participant D as Collaborative Robot
A->>G: request the next component
G->>S: Begin processing
S->>D: present the part safely
alt Dependency succeeds
D-->>S: Confirmed
... | sequenceDiagram |
Arrange an observer model for genomics workflow, including status updates, notifications, and publication of VariantReport. | classDiagram
class GenomeStudy {
-String status
+update()
}
class GenomeStudyObserver {
+String channel
+onChanged()
}
class AlignmentService {
+Boolean active
+notifyObservers()
}
class VariantReport {
+String summary
+publish(... | classDiagram |
Month-end close in an accounting system. The Controller starts the close, the Close Manager asks Accounts Payable, Accounts Receivable and Inventory modules to lock their periods in parallel, then runs accruals in the General Ledger and produces the trial balance. Use rect to highlight the lock phase. | sequenceDiagram
actor C as Controller
participant M as Close Manager
participant AP as Accounts Payable
participant AR as Accounts Receivable
participant I as Inventory
participant GL as General Ledger
C->>M: Start month-end close
rect rgb(255, 243, 220)
par Lock AP
M... | sequenceDiagram |
Trace a single remove targeting rule transaction and preserve the ordering of backend effects. | sequenceDiagram
participant G as Flag API
participant S as Evaluation Service
participant D as Flag Store
participant O as Audit Stream
G->>S: Begin remove targeting rule
activate S
S->>D: Update durable state
D-->>S: Update version
S->>O: Emit completion metric
O-->>S: Metric ac... | sequenceDiagram |
Represent home repair visit intake as a flowchart. | flowchart RL
A[Receive repair report] --> Q[[Intake Home Repair Visit Queue]]
Q --> B[Triage reported issue] --> C{Emergency response needed?}
C -->|Success| D[Dispatch repair technician] --> E[Confirm technician arrival]
C -->|Retry| F[Book standard appointment] --> Q | flowchart |
Create a robot battery-management flow. During a mission the robot monitors charge. If charge remains adequate, it continues the mission. If charge is low, it pauses, navigates to the charger, and attempts to dock. A failed dock attempt triggers repositioning and another attempt; successful docking charges the battery ... | flowchart TD
A[Monitor battery during mission] --> B{Charge adequate?}
B -->|Yes| C[Continue mission]
B -->|No| D[Pause mission]
D --> E[Navigate to charger]
E --> F[Attempt docking]
F --> G{Dock successful?}
G -->|No| H[Reposition robot]
H --> F
G -->|Yes| I[Charge battery]
I --... | flowchart |
An Ecologist requests a map layer from the GIS Workbench. The workbench asks the Spatial Database for observations and the Weather Service for rainfall data concurrently. After both arrive, it overlays the data and returns the map to the Ecologist. | sequenceDiagram
participant P1 as Ecologist
participant P2 as GIS Workbench
participant P3 as Spatial Database
participant P4 as Weather Service
P1->>P2: Request map layer
par Load observations
P2->>P3: Query observations
P3-->>P2: Observation coordinates
and Load rainfall
P2->>P... | sequenceDiagram |
Diagram DeliveryMission as a composition of FlightLeg, with DroneService processing it for a DispatchCenter. | classDiagram
class DispatchCenter {
-String id
+launch()
}
class DeliveryMission {
-String status
+confirm()
+validate()
}
class FlightLeg {
-String sequence
+fly()
}
class DeliveryDrone {
-String code
+inspect()
}
... | classDiagram |
Draw a payment link flow with Seller, Payment Link Page, Buyer, and Payment Service. Seller creates a link, Payment Link Page gives it to Seller, Buyer opens it and submits payment, Payment Link Page sends the payment to Payment Service, then both Buyer and Seller receive the successful result. | sequenceDiagram
actor A as Seller
participant B as Payment Link Page
actor C as Buyer
participant D as Payment Service
A->>B: Create payment link
B-->>A: Return shareable link
C->>B: Open link and submit payment
B->>D: Process linked payment
D-->>B: Payment successful
B-->>C: Sho... | sequenceDiagram |
Modify the sequence so subscriber authentication fails returns an error, while success performs accept network registration and updates Subscriber Database. | sequenceDiagram
autonumber
actor A as Mobile Handset
participant B as Radio Access Network
participant C as AMF
participant D as AUSF
Note over A,B: Start 5G registration
A->>B: register on 5G network
loop Until exchange completes
B->>C: send registration request
C->>D: r... | sequenceDiagram |
Create a temporary import process for exhibition equipment. The importer files a temporary admission request and provides a guarantee. Customs verifies both, admits the equipment when acceptable, and later checks that it was re-exported by the deadline. Timely re-export releases the guarantee; failure triggers duties a... | flowchart TD
A[File temporary admission request] --> B[Provide customs guarantee]
B --> C{Request and guarantee acceptable?}
C -->|No| D[Deny temporary admission]
C -->|Yes| E[Admit exhibition equipment]
E --> F{Re-exported by deadline?}
F -->|Yes| G[Release guarantee]
F -->|No| H[Assess dut... | flowchart |
How does our database connection pool serve an application request? The pool hands out a free connection if one is available. If none are free but the pool is still below its maximum size, a new connection is created and used. Otherwise the request waits in the queue until another thread releases its connection, which ... | flowchart TD
A[Application request arrives] --> B{Free connection available?}
B -->|Yes| C[Use connection]
B -->|No| D{Pool below maximum size?}
D -->|Yes| E[Create new connection]
E --> C
D -->|No| F[Wait in queue]
F --> G[Thread releases connection]
G --> C | flowchart |
We are updating an operating procedure for lab equipment calibration. Provide only the Mermaid flowchart, arrange it right-to-left, and ensure that the ordered stages from start to finish is represented with clear connections. | flowchart RL
A[Warm Instrument] --> B[Measure Standard] --> C[Adjust Sensor] --> D[Save Calibration] | flowchart |
Describe WebRTC peer connection as a sequence where Caller performs start video session, validation through Browser B runs beside logging to STUN Server, and the final alt covers success and ICE connectivity checks fail. | sequenceDiagram
actor A as Caller
participant B as Browser A
participant C as Signaling Server
participant D as Browser B
participant E as STUN Server
A->>B: start video session
B->>C: exchange SDP offer
par Verify remote state
C->>D: gather ICE candidates
D-->>C: verific... | sequenceDiagram |
Our debugging session operations team is standardizing its runbook. Provide a clear Mermaid diagram that follows the procedure from bug reproduced to collect evidence, then branch on whether root cause found? before close debug session and ends at the recorded outcome. | flowchart LR
A[Bug Reproduced] --> B[Collect Evidence]
B --> C{Root Cause Found?}
C -->|Yes| D[Implement Fix]
C -->|No| E[Add More Logging]
D --> F[Close Debug Session]
E --> F | flowchart |
Create a BT flowchart for vaccination clinic opening that fans out from clinic day starts into three parallel preparation tasks, then joins at 'Team readiness confirmed' before the final action. | flowchart BT
A(["Clinic day starts"]) --> B["Prepare vaccine stations"]
A --> C["Set up registration"]
A --> D["Review emergency protocol"]
B --> E{"Team readiness confirmed"}
C --> E
D --> E
E --> F(["Admit first patients"]) | flowchart |
A Member asks Social Platform to deactivate an account. Social Platform requests confirmation, then tells Session Service to sign out all devices and Profile Store to hide the profile. Once both finish, Social Platform confirms deactivation to Member. | sequenceDiagram
participant Member as Member
participant Platform as Social Platform
participant Sessions as Session Service
participant Profiles as Profile Store
Member->>Platform: Request account deactivation
Platform-->>Member: Ask for confirmation
Member->>Platform: Confirm deactivation
par End sessions
Platform->>... | sequenceDiagram |
How does our build pipeline use the dependency cache? After the pipeline starts, it checks the cache: on a hit, dependencies are restored from it and the build runs; on a miss, dependencies are downloaded first and saved to the cache before the build runs. Either way, the build finishes by storing the artifact. | flowchart TD
A[Pipeline starts] --> B{Dependency cache hit?}
B -- Yes --> C[Restore dependencies from the cache]
B -- No --> D[Download the dependencies]
D --> E[Save them to the cache]
C --> F[Run the build]
E --> F
F --> G([Store the artifact]) | flowchart |
We need live session track lifecycle states. | stateDiagram-v2
state "Demo" as LiveSessionTrackDemo
state "Tracking" as LiveSessionTrackTracking
state "Mixing" as LiveSessionTrackMixing
state "Mastering" as LiveSessionTrackMastering
state "Released" as LiveSessionTrackReleased
state "Shelved" as LiveSessionTrackShelved
[*] --> LiveSessio... | stateDiagram-v2 |
Food safety: receiving a delivery of chilled goods. | flowchart TD
A[Delivery arrives] --> B[Probe temperature]
B --> C{"At or below 5°C?"}
C -->|Yes| D[Check dates and packaging]
D --> E[Store in walk-in fridge]
C -->|No| F[Reject delivery]
F --> G[Log incident and notify supplier] | flowchart |
Map how we onboard mentors for our youth program. The volunteer submits an application to the program manager, who requests a background check from the screening agency. When the screening comes back clear, the volunteer attends orientation and then receives a first mentee assignment; if it does not come back clear, th... | sequenceDiagram
participant V as Volunteer
participant M as Program Manager
participant S as Screening Agency
V->>M: Submit application
M->>S: Request background check
S->>M: Return screening result
alt Screening clear
V->>M: Attend orientation
M->>V: Assign first mentee
... | sequenceDiagram |
Define a strategy-based class diagram for laboratory automation. Define an interface with fast and robust implementations, then show AutomationService selecting a strategy to run ExperimentProtocol. | classDiagram
class ExperimentProtocolStrategy {
<<interface>>
+apply()
}
class FastExperimentProtocolStrategy {
+int iterations
+apply()
}
class RobustExperimentProtocolStrategy {
+Float tolerance
+apply()
}
class AutomationService {
-S... | classDiagram |
Depict this layered design: Beneficiary calls MembershipFacade, the facade delegates to MembershipNonprofitService, the service updates Membership, and each record owns MembershipEntry entries that refer to exactly one Community. | classDiagram
class Beneficiary {
-String id
+request()
}
class Membership {
-String reference
~String status
+submit()
+validate()
}
class MembershipEntry {
-int sequence
+recalculate()
}
class Community {
+String code
... | classDiagram |
Connect the music lesson booking review cycle workflow in Mermaid using a split workflow that rejoins before completion and concise action labels. | flowchart RL
A[Choose music teacher] --> B[Check teaching calendar]
B --> C{Lesson time available?}
C -->|Proceed| D[Confirm selected lesson]
C -->|Alternate| E[Suggest alternate times]
D --> F[Record review result]
E --> F
F --> G([Send meeting link]) | flowchart |
As launch campaign scenario begins with Marketer using Campaign Console in the advertising workflow. Let Ad Service load context from Campaign DB, consult Auction Engine, persist campaign identifier, and reply through Campaign Console. Keep every request and reply explicit. | sequenceDiagram
actor A as Marketer
participant U as Campaign Console
participant S as Ad Service
participant D as Campaign DB
participant X as Auction Engine
A->>U: Launch a campaign
U->>S: Submit operation
S->>D: Load context
D-->>S: Context
S->>X: Perform auxiliary check
X... | sequenceDiagram |
I need a park-and-ride flow. A driver enters the lot, checks for an open space, and parks if one is available. If the lot is full, display the nearest alternative lot and direct the driver there. After parking, the traveler walks to the platform and boards transit. | flowchart TD
A[Enter park-and-ride lot] --> B{Open space available?}
B -->|Yes| C[Park vehicle]
C --> D[Walk to platform]
D --> E[Board transit]
B -->|No| F[Display nearest alternative lot]
F --> G[Drive to alternative lot]
G --> B | flowchart |
Create a Mermaid state diagram for sports column that can serve as acceptance documentation. It must show normal progress plus any review return, failure, cancellation, postponement, or recovery route in the workflow. | stateDiagram-v2
[*] --> SportsColumnPitch
SportsColumnPitch --> SportsColumnAssigned: editor commissions
SportsColumnAssigned --> SportsColumnDraft: writer begins
SportsColumnDraft --> SportsColumnCopyedit: draft filed
SportsColumnCopyedit --> SportsColumnDraft: substantive revision
SportsColumn... | stateDiagram-v2 |
Show a marketplace order after purchase. The seller either accepts the order or rejects it. Rejection triggers a buyer refund. Acceptance leads to packing and shipping; if the carrier confirms delivery, release the seller payout, but if the parcel is lost, refund the buyer instead. | flowchart TD
A[Seller receives order] --> B{Seller accepts?}
B -->|No| C[Refund buyer]
B -->|Yes| D[Pack order]
D --> E[Ship parcel]
E --> F{Carrier confirms delivery?}
F -->|Yes| G[Release seller payout]
F -->|No, parcel lost| C | flowchart |
Clarify ImagingSession with a configuration object, several ImageFrame elements, and one generated CellMask. | classDiagram
class ImagingSession {
~String state
+execute()
}
class ImagingSessionConfig {
+int seed
+String mode
+validate()
}
class ImageFrame {
+String id
+measure()
}
class CellMask {
+Float score
+summarize()
}... | classDiagram |
The implementation should expose observer relationships for clinical laboratory. LabOrder owns TestPanel, each aggregate composes TestResult, registers several TestPanelObserver objects, and LabService notifies those observers. | classDiagram
class LabOrder {
-String id
+submit()
}
class TestPanel {
-String status
+report()
}
class TestResult {
-String sequence
+validate()
}
class Analyzer {
-String code
+inspect()
}
class TestPanelObserver {
... | classDiagram |
Illustrate our biweekly payroll cycle. HR sends employee changes to the Payroll Team, which runs the payroll batch in the Payroll System. When validation fails, the Payroll System reports the errors and the Payroll Team corrects the data and reruns until validation passes. The Payroll System then sends the direct depos... | sequenceDiagram
participant H as HR
participant P as Payroll Team
participant S as Payroll System
participant B as Bank
participant E as Employees
H->>P: Sends employee changes
P->>S: Runs payroll batch
loop Until validation passes
S-->>P: Reports validation errors
P->>S:... | sequenceDiagram |
Application work may pause and resume. | stateDiagram-v2
[*] --> ApplicationQueued
ApplicationQueued --> ApplicationRunning: start
ApplicationRunning --> ApplicationPaused: pause
ApplicationPaused --> ApplicationRunning: resume
ApplicationRunning --> ApplicationDone: finish
ApplicationDone --> [*] | stateDiagram-v2 |
Deleting an account under GDPR. User requests deletion, the Account Service confirms identity by email, then starts the erasure job that removes posts from Post Service, media from Media Storage, and messages from Messaging Service in parallel. After a 30 day grace period it purges backups. | sequenceDiagram
actor U as User
participant A as Account Service
participant P as Post Service
participant M as Media Storage
participant G as Messaging Service
U->>A: Request account deletion
A-)U: Confirmation email
U->>A: Confirm
par Erase posts
A->>P: Delete user posts
... | sequenceDiagram |
A prosthetics service takes measurements, fabricates a trial socket, and checks fit. If the fit is poor, modify the socket and check it again. Once the fit is acceptable, finish the prosthesis, train the patient, and arrange follow-up. | flowchart TD
A[Take measurements] --> B[Fabricate trial socket]
B --> C[Check fit]
C --> D{Fit acceptable?}
D -->|No| E[Modify socket]
E --> C
D -->|Yes| F[Finish prosthesis]
F --> G[Train patient]
G --> H[Arrange follow-up] | flowchart |
What sequence of components handles update rollout after it reaches Flag API? | sequenceDiagram
participant C as Admin Console
participant G as Flag API
participant S as Evaluation Service
participant D as Flag Store
participant O as Audit Stream
C->>G: Request update rollout
G->>S: Execute update rollout
par Read durable state
S->>D: Fetch required record
... | sequenceDiagram |
Show a Rider requesting an accessible bus stop through the Transit App. The Transit App asks the Stop Registry for accessibility data, shows the result, and optionally lets the Rider report an obstruction, which the Transit App forwards to Transit Operations. | sequenceDiagram
actor A as Rider
participant B as Transit App
participant C as Stop Registry
actor D as Transit Operations
A->>B: Request accessible stop details
B->>C: Look up stop accessibility
C-->>B: Accessibility data
B-->>A: Show stop details
opt Rider reports an obstruction
... | sequenceDiagram |
emergency alert sent to phones | flowchart LR
A[Emergency manager drafts alert] --> B[Supervisor approves]
B --> C[Send via wireless alert system]
C --> D[Phones in area receive alert]
C --> E[Post on social and website] | flowchart |
Draw a Mermaid sequence diagram of event stream processing with a success-versus-failure alternative. Include Producer, Message Broker, Stream Processor, State Store, and activation bars. | sequenceDiagram
actor A as Producer
participant G as Message Broker
participant S as Stream Processor
participant D as State Store
A->>G: Publish business events
G->>+S: Forward partitioned event batch
S->>D: Validate against stored data
D-->>S: Validation context
alt Request can pro... | sequenceDiagram |
Visualize a maintainable class structure for Workflow where API-key and OAuth strategies implement one authentication interface used by a gateway and constrained by policy. | classDiagram
class WorkflowAuthStrategy {
<<interface>>
+authenticate()
}
class WorkflowApiKeyAuth {
+authenticate()
}
class WorkflowOAuthAuth {
+authenticate()
}
class WorkflowGateway {
+authorize()
}
class WorkflowAccessPolicy {
+eval... | classDiagram |
Express a moderately detailed diagram with separate subgraphs for Appeals Office and Faculty Panel. Connect appeal submitted to log appeal, hand off to review evidence, and test appeal upheld. A yes result proceeds through amend decision to notify student; no goes to keep decision and cycles back to log appeal. | flowchart BT
subgraph L1[Appeals Office]
A[Appeal Submitted] --> B[Log Appeal]
end
subgraph L2[Faculty Panel]
C[Review Evidence] --> D{Appeal Upheld?}
D -->|Yes| E[Amend Decision] --> F[Notify Student]
D -->|No| G[Keep Decision]
end
B --> C
G --> B | flowchart |
Annual budgeting works like this: the CFO issues budget targets and FP&A distributes templates to each Department Head, who submits a budget proposal. FP&A consolidates a company-wide draft and presents it to the CFO; the CFO returns it with changes and FP&A incorporates the revisions, repeating until satisfied. Once t... | sequenceDiagram
participant C as CFO
participant F as FP&A
participant D as Department Head
C->>F: Issues budget targets
F->>D: Distributes budget templates
D->>F: Submits budget proposal
F->>F: Consolidates company-wide draft
loop While the CFO requests changes
F->>C: Presents d... | sequenceDiagram |
Describe our path to production: a feature branch opens a pull request and CI builds and tests it; failing tests go back to the developer, who fixes them and pushes, which triggers CI again; on green, the pull request is merged and deployed to staging, and after the release manager approves it, it is released to produc... | flowchart TD
A[Open pull request from feature branch] --> B[CI builds and runs tests]
B --> C{Tests pass?}
C -->|No| D[Developer fixes and pushes]
D --> B
C -->|Yes| E[Merge pull request]
E --> F[Deploy to staging]
F --> G[Release manager approves]
G --> H[Release to production] | flowchart |
Customer reports a missing package. Support checks the carrier tracking: if it shows delivered, they open a claim with the carrier; if it is still in transit, they ask the customer to wait two more days. In both cases, if the package still doesn't turn up, a replacement is shipped; if it is found, the case is closed. | flowchart TD
A[Customer reports missing package] --> B{Tracking status?}
B -->|Delivered| C[Open carrier claim]
B -->|In transit| D[Ask customer to wait two days]
C --> E{Package found?}
D --> E
E -->|No| F[Ship replacement]
E -->|Yes| G[Close case] | flowchart |
Add Reservation composition with StayNight. | classDiagram
class Guest {
#String guestNo
+reserve()
}
class LoyalGuest {
-String level
+authorize()
}
class Reservation {
~String arrival
+extend()
}
class StayNight {
-int rate
+recalculate()
}
class Room {
+S... | classDiagram |
The batch ingestion runbook should depict the process from files arrived into validate files, retrying after quarantine files until files valid?, then continue through load records to write load summary. | flowchart RL
A[Files Arrived] --> B[Validate Files] --> C{Files Valid?}
C -->|No| D[Quarantine Files] --> B
C -->|Yes| E[Load Records] --> F[Write Load Summary] | flowchart |
End of preview. Expand in Data Studio
No dataset card yet
- Downloads last month
- 49