# Mermaid Overtakes PlantUML: Implications for Systems Analysts
Since December 2025, Mermaid has overtaken PlantUML in popularity on Google Trends. draw.io removed PlantUML support from its online version due to security issues, a limited set of diagrams, and server-based architecture. Mermaid runs client-side and supports more diagram types. Microsoft integrated Mermaid rendering into the Visual Studio Markdown editor, and GitHub added preview support in Copilot Chat. Diagrams integrate seamlessly into documentation, specifications, and code.
Changes in Modeling Approach
Systems analysts are shifting from static images to textual models. Mermaid lets you embed diagrams directly into Markdown files alongside requirements, API contracts, and business rules. A sequence diagram sits right next to the integration scenario, a state diagram by the lifecycle description, and an ER diagram by the domain model.
This speeds up iterations: AI generates a Mermaid draft, and the team reviews the preview in their IDE or GitHub. Diagrams are versioned as text and updated weekly without manual redrawing.
Key Shifts in Daily Practice
- Integration into specifications: Diagrams live in the same file as the text, not as separate artifacts.
- Faster discovery: Quick sketches in text or via Copilot to align on ideas.
- Lower barrier to entry: Developers, QA, and team leads edit diagrams without specialized tools.
Visual Studio offers templates for API flows, entity relationships, and task lifecycles. GitHub renders Mermaid in Copilot chats.
New Skills for Analysts
Text-first modeling requires describing structures in text for automatic visualization. Focus shifts to precise wording over graphical interfaces.
Working with AI: Crafting prompts for diagrams with the right level of detail, system boundaries, and actors.
Templating: Standards for naming nodes, arrows, error notations, async operations, and external systems.
What Gets Easier
Common artifacts like integration sequences, lifecycles, context diagrams, and onboarding overviews are created and updated faster. draw.io offers conversion from PlantUML to Mermaid.
Migration makes sense for diagrams that change often in reviews and communications.
Mermaid Limitations
It doesn't replace BPMN or Enterprise Architect for formal modeling and certification. Risk of false sufficiency: AI-generated diagrams look polished but may lack semantic depth.
Overly detailed large diagrams create clutter—layered modeling is needed.
Evolution of the Analyst Role
Analysts become curators of living documentation: maintaining versioned diagrams in docs-as-code. Success measured by reduced misunderstandings, not diagram quantity.
Implementation Recommendations
- Pick scenarios: context diagrams, sequences, states, ER overviews, component overviews.
- Standardize naming, detail levels, and notations.
- Place diagrams next to user stories, API specs, and ADRs.
- Use AI for drafts with analyst review.
- Migrate only diagrams that change frequently.
Key Takeaways
- Mermaid integrates with GitHub, Visual Studio, and draw.io—diagrams as text in the dev workflow.
- Shortens the gap between requirements and code, speeds up updates.
- Demands text-first thinking and templates for quality.
- Not for enterprise modeling, but perfect for living docs.
- draw.io is migrating from PlantUML, accelerating adoption.
— Editorial Team
No comments yet.