Day 21 ties together six software‑engineering pillars—development models, requirements engineering, UML, design principles & patterns, testing, and CMMI—explains their interrelations, illustrates them with an e‑commerce order‑system case, teaches a memory‑palace recall method, and provides a 20‑question exam with answers.
The article introduces fireworks‑tech‑graph, an open‑source AI‑driven diagram skill that turns natural‑language descriptions into fully styled SVG diagrams, offering seven built‑in visual themes, support for 14 UML types, an extensive icon library, and concise command‑line usage, dramatically cutting the time engineers spend on manual drawing.
fireworks-tech-graph is an open‑source Claude Code skill that turns natural‑language prompts into professional SVG/PNG architecture diagrams, offering seven visual styles plus an AI‑hand‑drawn style, full support for 14 UML diagram types, built‑in AI/Agent patterns, product icons, and a quick‑start installation process.
This article explains the meaning of each UML line style—solid, dashed, hollow triangle, hollow diamond, and solid diamond—covers class‑diagram relationships, use‑case include/extend, activity vs. state diagrams, component vs. deployment diagrams, and provides exam‑style practice questions with concrete examples.
This article explains why learning UML should begin with clarifying the system aspect you want to convey, outlines the five core activities of requirement engineering, and details the purpose and typical use cases of the seven most common UML diagram types with concrete e‑commerce examples.
The article explains the standards for high‑quality architecture diagrams, outlines common UML diagram types, compares a range of online, professional, and cloud‑native UML tools with pros and cons, and offers practical tips and a step‑by‑step process for creating clear, visually appealing diagrams.
This article demonstrates how SVG can be used to create precise sequence diagrams, flowcharts, and architecture diagrams, explains the standards behind each diagram type, provides concrete examples such as a user‑login flow and a typical web‑app architecture, and shares best‑practice guidelines to turn complex logic into instantly understandable visuals.
The article introduces the open‑source fireworks‑tech‑graph project, a Claude Code skill that turns natural‑language prompts into production‑grade SVG/PNG diagrams, offering seven visual styles, 14 UML types, built‑in AI/Agent semantics, and a seamless workflow that outperforms Mermaid and draw.io for technical documentation and presentations.
Webminal, a free online Linux learning platform, has survived for fifteen years on a single 8 GB CentOS server, serving over half a million users by using a minimalist stack—including Python 2.7, Flask, Shellinabox, User Mode Linux and eBPF—while deliberately avoiding modern container orchestration and commercial monetisation.
This article presents a comprehensive, practice‑tested methodology that combines C4, UML, DDD, micro‑service decomposition and other techniques into a standardized set of diagrams—context, architecture, deployment, domain/data models, sequence, state, concurrency and data‑flow—to improve communication and thinking across diverse system types.
This article explains what UML state diagrams are, why they matter for modeling dynamic system behavior, outlines their core components, and walks through a practical e‑commerce product‑management example with detailed steps and visual illustrations to help developers design robust state‑based models.
This article walks through using large language models such as Claude, Gemini, DeepSeek, and Kimi to generate accurate, colorful UML diagrams via Mermaid syntax, covering model selection, prompt engineering, step‑by‑step demonstrations, and practical tips for reliable AI‑driven diagram creation.
This article explains UML class diagrams, covering their purpose, core elements, how classes, interfaces, and various relationships are represented, and provides a practical example of a simple music‑streaming system to illustrate the concepts.
This article explains the purpose and components of UML use case diagrams, illustrates how they capture system actors and interactions, and provides a concrete example of a mobile recharge app, while also inviting readers to follow the author's architecture notes for deeper learning.
This comprehensive guide explores the evolution of object‑oriented programming, clarifies its core concepts, and walks readers through use‑case modeling, static and dynamic modeling, responsibility‑driven design patterns, and advanced modeling techniques, providing a complete knowledge framework for software engineers and architects.
This article analyzes how modern AI coding assistants like Gemini‑CLI and Claude Code can overcome the maintenance costs of traditional modeling, making RUP, the 4+1 view and UML viable again as powerful tools for high‑quality, AI‑augmented software development.
This article explains how mastering business modeling, requirements analysis, and UML techniques—rather than focusing solely on code—helps developers create software that truly solves real business problems and drives profit, using lessons from the classic book “Software Method”.
This guide introduces PlantUML, an open‑source text‑based diagram tool, covering its core features, IDE plugins, basic and advanced sequence‑diagram syntax, color customization, grouping, notes, and a complete Google‑login example, helping developers create clear, version‑controlled diagrams efficiently.
This tutorial introduces PlantUML, explains its core features, shows how to install plugins for popular IDEs, and provides detailed syntax examples for participants, messages, lifelines, activation bars, groups, notes, and colors, culminating in a complete login flow diagram.
This article introduces the basics of software modeling and design documentation, explaining UML diagram types such as class, sequence, component, and deployment diagrams, and outlines how architects use these models throughout requirement analysis, high‑level design, and detailed design, while also promoting a community and related resources.
This article introduces PlantUML, explains its core features, walks through quick setup with IDE plugins, demonstrates basic and advanced sequence diagram syntax—including participants, messages, lifelines, activation bars, groups, notes, and colors—and provides a complete Google‑login example for practical reference.
This article introduces PlantUML, explains its text‑based diagramming approach, walks through quick setup, IDE plugins, core sequence‑diagram syntax—including participants, message types, lifelines, activation bars, grouping, notes, and color customization—while providing complete code examples and best‑practice tips.
This article introduces the basics of software design documentation, explaining how software modeling and UML diagrams such as class, sequence, component, deployment, use case, state, and activity charts are used to capture domain problems and system architecture throughout requirement analysis, high‑level design, and detailed design phases.
This article explains the fundamentals of software design documentation, covering why modeling is essential, how UML diagrams such as class, sequence, component, deployment, use‑case, state and activity charts are used across requirement analysis, conceptual design, and detailed design phases, and how architects tailor documents for different stakeholders.
This article explains the purpose, components, and relationships of UML deployment diagrams, illustrates a basic deployment example with client, web, application, and database nodes, and provides visual references while also promoting additional architecture resources from the author.
This article explains why architecture diagrams are essential for software engineers, introduces the seven most common UML diagram types, and provides practical guidance on selecting and applying each diagram during requirements analysis, high‑level design, and detailed design phases.
The article explains the main UML architecture diagram types—class, sequence, component, deployment, use‑case, state, and activity—outlines how to choose the appropriate diagram, and details when each should be applied during requirement analysis, high‑level design, and detailed design phases of software development.
The guide walks readers through clarifying vision, modeling business use case diagrams that capture external value, then translating those insights into detailed system use case diagrams and specifications—including actors, pre/postconditions, and paths—emphasizing that solid requirements, not code alone, drive enterprise profit.
The article distills the book “Software Method,” outlining a disciplined approach that starts with industry‑specific business modeling—defining vision, use‑case and sequence diagrams, and improvement patterns—then moves to precise requirements gathering, detailed analysis class diagrams, and finally design, emphasizing that true software value comes from meeting real demand.
This article explains how programmers can overcome the hassle of writing documentation by using ChatGPT to automatically generate PlantUML code, covering the basics of PlantUML, prompt engineering, and step‑by‑step examples for class and sequence diagrams.
This article introduces PlantUML, explains its core features, walks through quick installation and plugin setup, demonstrates basic and advanced sequence diagram syntax with code examples, and provides a complete login flow illustration, helping developers create clear, version‑controlled diagrams efficiently.
This guide explains the seven core UML diagrams—class, sequence, component, deployment, use‑case, state, and activity—detailing when and how to use each across requirement analysis, architecture design, and detailed design to produce clear, actionable software design documentation.
Design patterns and algorithms remain external to official language specifications because they need universal applicability, flexibility for innovation, and manageable maintenance, and developers can visualize them with UML diagrams—such as the Observer pattern class diagram—to better understand and implement these core software concepts.
The article explains how business and domain modeling—using UML diagrams, RUP‑based workflows, and DDD principles—help engineers bridge the gap between business problems and technical solutions, enabling clearer requirements, stakeholder alignment, and improved system design across complex industries such as finance, logistics, and e‑commerce.
This article introduces PlantUML, explains how to install its plugins for IDEs, demonstrates various diagram types such as activity, class, component, and sequence, and provides a practical code example for modeling authentication flows, making it a comprehensive guide for creating UML diagrams efficiently.
This article explores how large language models like ChatGPT can be leveraged to transform natural‑language requirements into UML diagrams using PlantUML, demonstrating the workflow, prompt engineering, iterative training, and the resulting efficiency gains for developers.
This article introduces PlantUML, an open‑source tool that lets developers generate various UML diagrams directly from text, explains how to install the IntelliJ IDEA plugin, and provides step‑by‑step code examples for sequence, use‑case, class, activity, and mind‑map diagrams, complete with visual outputs.
This article explores the fundamentals of software architecture, discussing entropy, the dual value of behavior and structure, core design principles such as SOLID, DRY, layering, orthogonality, component coupling, boundary definition, communication patterns, and modeling tools, while also offering practical guidance for building maintainable systems.
This article introduces the fundamentals of software modeling and design documentation, explaining how UML diagrams such as class, sequence, component, deployment, use‑case, state and activity charts are used across requirement analysis, conceptual design, and detailed design phases to create clear architectural blueprints.
This article explains the Bridge design pattern, a structural pattern that separates abstraction from implementation to avoid class explosion, provides detailed Java code examples, UML diagrams, advantages, disadvantages, and typical scenarios for applying the pattern in software development.
This article provides a comprehensive overview of the five creational design patterns—Singleton, Abstract Factory, Factory Method, Builder, and Prototype—explaining their concepts, UML structures, implementation details, typical use cases, advantages, disadvantages, and includes Java code examples and diagrams.
This article explains the Factory Method design pattern, covering its definition, UML diagram, key participants, the problems it solves compared to the Simple Factory, step‑by‑step Java implementation with code examples, advantages, disadvantages, application scenarios, and differences from the Simple Factory pattern.
This article explains the purpose, key elements, and appropriate usage scenarios of the main UML model diagrams—including class, sequence, component, deployment, use‑case, state, and activity diagrams—to help software engineers select and apply the right diagram at each stage of system design.
This article explains the Single Responsibility Principle, its core idea, why it should be followed, its three main benefits, and provides UML class diagrams and Java code examples that demonstrate how to split responsibilities into dedicated classes for clearer, more maintainable software.
This article explains the logical framework of software analysis and design, outlines practical methods and principles, introduces essential UML tools, and demonstrates the concepts with two concrete case studies—a logging framework and a task‑scheduling framework—providing a complete guide for developers.
This article explains the importance of architecture visualization for clear communication, compares wireframe, UML, and sketch approaches, and details how the C4 model’s layered abstractions—system, container, component, and code—provide a low‑cognitive‑load, consistent way to document software systems.
This comprehensive guide explains software methods—including business modeling, requirement analysis, domain modeling, UML relationships, and design principles—illustrating how systematic modeling improves product quality, reduces costs, and enhances engineers' professional growth.
The article shows how developers can describe desired UML, flowchart, SVG icon, or mind‑map in natural language and use AI to generate PlantUML or Mermaid code instantly, streamlining diagram creation, reducing manual effort, and illustrating broader AI‑assisted productivity tips for software development.
This article demonstrates how to leverage ChatGPT's ability to produce textual code snippets together with PlantUML to automatically create various UML diagrams—such as sequence, class, flow, state, and use‑case diagrams—from Java‑style pseudocode, providing a step‑by‑step workflow and example prompts.
The article explains how enterprise applications have evolved to web‑based distributed environments, describes the three‑tier architecture, and shows how UML/EAP and Archimate can be used to model and visualize the deployment of hardware and application components in a networked infrastructure.
The article explains how environment and location diagrams map applications to physical sites, defines key UML/BPMN EAP elements such as headquarters, site locations, servers, workstations, applications, interactive components, and class relationships, and illustrates these concepts with an Archimate diagram while also providing community links.
The article explains how to create data‑security diagrams that map which participants can access specific enterprise data, recommends breaking large diagrams into role‑based views, and illustrates the approach with UML/BPMN and ArchiMate models while addressing compliance and trust considerations.
The article explains the purpose and benefits of data publication diagrams for visualizing relationships among data entities, services, and application components, introduces UML/BPMN EAP profile components with illustrative images, and outlines Archimate modeling elements, highlighting how data is localized within repositories or entity application components.
The article explains the purpose and structure of application communication diagrams, describes SOA‑oriented component layering, introduces the UML/BPMN EAP profile and Archimate concepts, and provides a detailed list of application component types for enterprise architecture modeling.
The article explains how organization decomposition diagrams illustrate the links between participants, roles, and locations, define responsibilities, show information flows, and map goals to stakeholders using UML/BPMN and Archimate models, providing a comprehensive view of enterprise structure and governance.
This article explains the SOLID principles, various UML relationship types, and provides detailed descriptions of 22 classic design patterns, illustrating their intents, applicability, and implementation considerations for building clean, maintainable software architectures.
This guide explains how Java developers can install Graphviz and the PlantUML plugin in IntelliJ IDEA, configure environment variables, and create UML sequence and class diagrams directly within the IDE, including code examples and troubleshooting tips.
This article explains core object-oriented design concepts including the SOLID principles, UML relationship types, and a comprehensive overview of common design patterns such as Factory Method, Singleton, Adapter, and Observer, providing clear definitions, intents, and applicability for software architects.
This article explores how structured domain model metadata, derived from domain‑driven design principles, can standardize business component descriptions, enable visual UML modeling, support low‑code and no‑code generation, and ultimately reduce development costs while accelerating delivery of enterprise support systems.
This tutorial introduces PlantUML, an open‑source tool for generating UML, mind‑map, and activity diagrams directly from code, covering installation, key syntax, and step‑by‑step examples for sequence, use‑case, mind‑map, and activity diagrams.
This article explains the fundamentals of software design documentation, showing how UML modeling—class, sequence, component, deployment, use‑case, state, and activity diagrams—captures domain problems and system structure across requirement, high‑level, and detailed design phases, enabling architects to communicate intent to diverse stakeholders.
This article explains how software architects use modeling techniques and UML diagrams to create clear, stakeholder‑focused design documents that capture domain problems, system structure, and implementation details across requirement analysis, conceptual design, and detailed design phases.
This article explains the basic concepts of software modeling, the role of UML diagrams, and how to organize those models into a coherent software design document that guides architects, developers, testers, and stakeholders throughout the development lifecycle.
This article explains how to select and use appropriate UML diagrams throughout a software project's lifecycle—covering project initiation, requirements analysis, system design, and detailed modeling—illustrated with electronic procurement and hospital admission case studies.
This comprehensive guide walks you through selecting and applying the right UML diagrams at each project stage—from initial scope and feasibility studies, through requirement analysis and use‑case modeling, to system design, domain modeling, and detailed interaction diagrams—illustrated with two practical case studies.
This guide explains how to install the PlantUML plugin and Graphviz, configure environment variables and IntelliJ IDEA, and use PlantUML to quickly create UML diagrams and flowcharts directly within the IDE, including a sample code snippet and alternative browser options.
The article explains how a project context diagram maps work packages to organizational elements and describes UML/BPMN EAP profile elements and an Archimate model centered on a DiscountTravelOrderingSite, while also providing contact information for further discussion.
The article explains processing diagrams that focus on deployable code and configuration units, detailing how to group application components into deployment units, their interactions, capacity considerations, and illustrates these concepts using UML/BPMN EAP profiles and Archimate diagrams.
The article explains how enterprise applications have evolved to web‑centric, three‑layer architectures and describes the purpose and components of network computing hardware diagrams using UML/BPMN EAP Profile and Archimate to map logical application components to physical deployment nodes.
This article explains how environment and location diagrams depict where applications run, defines headquarters, site, server, workstation, and application components, and illustrates these concepts using UML/BPMN EAP profile and Archimate diagrams, while also providing community links for further architectural discussion.
This article guides Java developers on installing the PlantUML plugin for IntelliJ IDEA, setting up Graphviz, configuring environment variables, and creating UML diagrams directly from text, including sample code and alternative Chrome viewer options.
The article explains how data lifecycle diagrams model business data independently of processes, define stable entity states and transitions, and illustrate these concepts with a UML/BPMN EAP profile example of an order entity, while also providing community and resource links.
The article explains how application and user location maps illustrate the geographic distribution of software usage, development, and hosting, outlines their purposes for capacity planning and support, describes typical user interactions, and introduces UML/BPMN EAP and Archimate profiles for modeling these relationships in enterprise architecture.
System use case diagrams illustrate how participants and application services interact, enriching functional descriptions with technical details and supporting architecture design, while the article also explains UML/BPMN EAP profiles, Archimate representations, and provides community resources for further enterprise architecture discussion.
The article explains how application migration diagrams map components from baseline to target systems, describes UML/BPMN EAP profile elements such as system, application, entity and process components, and illustrates migration strategies using Archimate with a multi‑version Travel example.
The article explains the purpose and structure of application communication diagrams, describes SOA‑oriented application components, outlines the UML/BPMN EAP profile and Archimate modeling elements, and provides guidance on layering interaction, process, and entity components within logical enterprise architectures.
The article explains that business event diagrams (also called business process diagrams) illustrate how events like order receipt or fiscal quarter end trigger workflows, showing processes, trigger events, products, and participating roles, and then lists various community and social media resources for further learning.
This guide shows Java developers how to install Graphviz and the PlantUML plugin in IntelliJ IDEA, configure environment variables, and use PlantUML syntax to generate flowcharts and class diagrams directly within the IDE, plus alternatives like Chrome extensions for quick diagram rendering.
This guide introduces PlantUML, an open‑source text‑based UML tool, shows how to install its IntelliJ IDEA plugin, and provides step‑by‑step examples for creating sequence, use‑case, class, activity, and mind‑map diagrams, highlighting key syntax and the efficiency of code‑driven diagramming.
Learn how to quickly set up PlantUML in IntelliJ IDEA, configure Graphviz, and create UML diagrams directly within the IDE, including step-by-step installation, environment variable setup, and sample code for generating sequence and class diagrams.
This guide explains what PlantUML is, its advantages, how to install the PlantUML plugin and Graphviz on Windows, configure IntelliJ IDEA, write PlantUML code to generate diagrams, and alternative browser‑based options, providing a complete workflow for developers.
This article explains UML relationship types—including association, aggregation, composition, generalization and specialization—by describing their definitions, visual notations, multiplicity, role names, and real‑world examples, helping readers distinguish each concept and apply them in software modeling.
This guide explains what PlantUML is, its advantages, and provides step‑by‑step instructions for installing the PlantUML plugin and Graphviz on Windows, configuring IntelliJ IDEA, and creating UML diagrams directly within the IDE, including sample code and alternative Chrome extension options.
This article explains how software architects can conduct effective software design by building abstract models and textual specifications, using UML diagrams such as class, sequence, component, deployment, use‑case, state, and activity diagrams to communicate functional and non‑functional requirements throughout requirement analysis, conceptual design, and detailed design phases.
This article explains how software architects can use UML modeling and design documentation to capture both functional and non‑functional requirements, communicate with stakeholders, and guide developers through requirement analysis, high‑level design, and detailed design phases.
Learn how to set up PlantUML in IntelliJ IDEA by installing the PlantUML plugin, configuring Graphviz, adding environment variables, and using simple code snippets to generate UML and flowcharts, with step‑by‑step screenshots and tips for alternative browser‑based usage.
This article explains how software architects can use UML modeling—covering class, sequence, component, deployment, use‑case, state, and activity diagrams—to analyze domain problems, design abstract models, and produce clear documentation that guides development from requirements through detailed design.
This article explains how software architects can conduct effective software design through modeling, documentation, and UML diagrams to satisfy functional, non‑functional, and cost requirements while ensuring clear communication among developers, testers, and operations teams.
This article explains the essence of software architecture, its core elements, why clear diagrams are crucial for communication and quality, and presents practical principles, patterns like UML, 4+1, C4, arc42, and tools such as draw.io and PlantUML to help engineers create accurate, consistent, and maintainable architectural documentation.
This article explains the purpose, definition, and step‑by‑step process of creating domain models for e‑commerce shopping flows, covering concept identification, relationship mapping, state modeling, class and state diagrams, model review, and introduces the accompanying conceptual architecture visuals.
This guide shows how to install and configure the PlantUML plugin and Graphviz on Windows, enabling Java developers to draw flowcharts and UML class diagrams directly within IntelliJ IDEA, with optional Chrome extension for browser‑based editing.
This article provides a comprehensive overview of UML, explaining its purpose, core elements, diagram classifications, static and dynamic models, and the typical modeling process, enabling readers to understand, create, and interpret UML diagrams across software development stages.
This guide shows how to install and configure the PlantUML plugin and Graphviz on Windows, set up environment variables, and use simple text syntax to generate UML sequence and class diagrams directly within IntelliJ IDEA, plus an alternative Chrome extension.
This article explains the concept of domain models, why they are crucial business assets, how to create and use them with UML diagrams and simple examples, highlights common misconceptions, and shows how explicit modeling improves communication, code readability, and software adaptability.
The article explains why architects need to master mind maps, UML diagrams (class, sequence, activity, state) and architecture diagrams, outlines key principles for each, provides concrete examples and visual illustrations, and shares practical insights on using these diagrams to improve design communication and business alignment.
This article introduces the Builder design pattern, explains its role in separating object construction from representation, provides UML class diagrams and Java code examples, outlines typical application scenarios, and discusses its advantages and disadvantages.
The article analyses the rise and fall of UML, tracing its origins in the 1990s, the impact of CASE tools, the shift toward agile development, and the technical and cultural reasons for its decline, while also exploring emerging lightweight modeling alternatives such as C4 and masala diagrams.
The article explains how software‑engineering’s planning‑to‑maintenance lifecycle benefits from UML, then demonstrates using the open‑source textual tool PlantUML to quickly create version‑controlled use‑case, activity (swimlane), state, sequence, and class diagrams, detailing each syntax element and illustrating real‑world examples.
This article explains the concept, purpose, and essential practices of domain modeling, covering UML relationship types, code examples, model simplification tips, and common pitfalls to help developers create clear, business‑focused class diagrams.
This article explains the purpose, elements, and notation of major UML diagram types—including sequence, collaboration, activity, state, component, and deployment diagrams—illustrated with examples such as a data‑center billing system, helping readers understand how to model and communicate software architecture effectively.
