The article explains the purpose and components of process/system realization diagrams, introduces the UML/BPMN EAP profile and Archimate examples, and includes references and promotional links for enterprise architecture communities.
The article explains the purpose and structure of application communication diagrams, describes SOA‑oriented component layering, outlines the UML/BPMN EAP profile and Archimate concepts, and provides a detailed list of component types used in enterprise architecture modeling.
This article explains how software architects can use UML modeling to capture domain problems and system designs, produce clear design documents, and communicate functional, non‑functional, and cost requirements across all stakeholders throughout the development lifecycle.
This article explains the six core UML relationship types—Dependency, Association, Aggregation, Composition, Generalization, and Realization—detailing their semantics, visual notations, code representations in Java/C++, and practical distinctions such as lifecycle ownership and usage contexts.
This guide explains what PlantUML is, why it’s useful for fast diagram creation, how to install the required Graphviz engine, set up the PlantUML plugin in IntelliJ IDEA, create UML files, and includes sample code for sequence diagrams and role definitions.
This tutorial explains how to use IntelliJ IDEA's built‑in Diagram plugin to automatically generate UML class diagrams for Java classes, covering configuration steps, shortcut keys, example screenshots, and the tool's limitations for software design documentation.
Software design, essential for architects, involves modeling domain problems and the resulting system using UML diagrams such as class, sequence, component, deployment, use‑case, state, and activity charts, applied across requirement, conceptual, and detailed design phases to communicate functional, non‑functional, and cost requirements.
This article explains how software architects can use UML‑based modeling and a series of design documents to capture domain problems and system solutions, communicate functional and non‑functional requirements, and guide development across requirement analysis, architectural design, and detailed implementation.
This article explains the six fundamental UML relationship types—Dependency, Association, Aggregation, Composition, Generalization, and Realization—detailing their semantics, visual notations, code examples in Java/C++, and the distinctions among them, helping developers model object interactions accurately.
This article explains how to correctly draw UML class diagrams by describing the six main relationship types—generalization, realization, aggregation, composition, association, and dependency—using clear examples and visual illustrations to help readers understand and apply each relationship in software modeling.
Learn how the Command pattern separates request issuance from execution, introducing roles like Command, ConcreteCommand, Receiver, Invoker, and Client, and see real‑world analogies and examples such as Hystrix and Java’s ThreadPoolExecutor that illustrate its widespread use in modern software.
The article explains why diagrams are essential in software development, describes the problems they solve, and details nine common diagram types—use‑case, robustness, mind‑map, data‑flow, flowchart, UML class, state, ER, and sequence—showing their appropriate scenarios, advantages, and drawbacks to help architects and developers select the most suitable visual tool for each stage of the development lifecycle.
This article introduces UML as a standardized visual modeling language, focusing on commonly used class, sequence, and state diagrams, and explains the symbols and relationships—such as dependency, generalization, association, aggregation, and composition—along with practical examples and tool recommendations for effective software design.
The article explains a software architect's core duties, contrasts them with developers, outlines how to become an architect, and provides practical advice on topics such as UML, Spring Cloud vs Dubbo, distributed tasks, high concurrency, rate limiting, data synchronization, and large‑scale data updates.
This article explains how software architects can use UML‑based modeling to translate functional and non‑functional requirements into clear design documents, covering the essential steps, key concepts, and the seven major UML diagram types across requirement, conceptual, and detailed design phases.
This article explains the six core UML class diagram relationships—generalization, realization, aggregation, composition, association, and dependency—illustrating each with clear diagrams and practical examples, and also recommends popular UML tools for creating these models.
This article explains the essential steps of requirement analysis, covering how to decompose and refine business needs, choose appropriate modeling structures, create effective UML diagrams, and avoid common mistakes that can lower requirement quality and increase change risk.
Drawing the right diagrams—such as use‑case, robustness, mind‑map, DFD, flowchart, class, state, E‑R, and sequence charts—helps software architects clarify requirements, design solutions, and communicate across teams, turning vague ideas into concrete visual references that guide development from inception to coding.
The article explains why software architects need to create clear diagrams, describes the problems they solve, lists nine typical diagram types—including use case, robustness, mind map, DFD, flowchart, class, state, E‑R, and sequence diagrams—with their appropriate scenarios, advantages, and drawbacks, and outlines a step‑by‑step workflow for applying them in real projects.
UML class diagrams feature six primary relationships—Generalization, Realization, Dependency, Association, Aggregation, and Composition—each with distinct visual notations and semantics, and this guide explains their definitions, code representations in Java, and practical examples to help developers model system structures accurately.
This guide explains UML's core relationship notations, the nine essential diagram types and their purposes, detailed insights into class, object, use‑case, sequence, collaboration, state, activity, component, and deployment diagrams, and how they map to fundamental object‑oriented concepts such as boundary, entity, and control classes.
This article examines the evolution of a web crawler architecture across three versions, highlighting the importance of completeness, standardization with UML, clear goals, accuracy, and maintainability to build a scalable and cost‑effective backend system.
This article explains the fundamental ideas of Domain‑Driven Design, showing how to build expressive domain models, use a ubiquitous language, map bounded contexts, apply strategic and tactical patterns, and implement the concepts with C# code, UML sketches, and architectural guidelines.
This article reviews UML modeling basics, then dives into deployment and activity diagrams—explaining their elements, relationships, and practical B2C system examples—to help readers understand how to represent component placement and dynamic behavior in software architecture.
This article reviews UML basics, corrects earlier mistakes, and provides a practical guide on when and how to apply sequence, component, and state diagrams for effective system architecture modeling.
This article introduces UML modeling fundamentals, explains the purpose and types of UML diagrams, and provides step‑by‑step guidance on creating use‑case and class diagrams, helping readers build clear abstract models for system architecture and design.
This article explains software architecture as the composition and interaction of components, outlines its ANSI/IEEE definition, describes UML diagrams for modeling, discusses validation through testing, and shares practical development rules, offering a concise learning summary for engineers.
This article presents a curated list of essential Java books ranging from beginner fundamentals and agile testing to advanced architecture, software development processes, and project management, offering download links and concise commentary to help Java developers systematically improve their skills.
This article reviews UML modeling basics and provides a detailed, example‑driven explanation of deployment diagrams and activity diagrams, covering their elements, relationships, and a concrete B2C system illustration to help readers grasp how to model system structure and dynamic behavior.
This article reviews UML basics, corrects earlier mistakes, and explains how and when to apply sequence, component, and state diagrams—covering their elements, modeling rules, and practical examples—to help architects build clear abstract models.
This article introduces UML modeling fundamentals, covering the purpose and elements of use‑case and class diagrams, their relationships, and step‑by‑step guidance on building abstract models to improve system architecture design and communication.
This article explains software architecture as the arrangement and interaction of components, outlines its standards, discusses UML diagrams for modeling, describes the role of architects, and shares practical rules for effective system design and development.
This article explains UML as a modeling language, detailing its semantics and notation, and introduces the nine core diagram types—use case, class, object, static, behavior, interaction, implementation, component, and deployment—highlighting their purposes, differences, and how they support static and dynamic system modeling.
This article presents a curated list of essential books covering software architecture fundamentals, design patterns, domain‑specific frameworks, RUP/UML methodologies, and additional leisure reads, along with practical reading strategies for developers and architects.
Software architecture is described as a set of critical decisions about system organization, including the selection of components, their interfaces, and collaborative behavior, and as a compositional style that progressively assembles these elements into larger subsystems, a definition comprehensively presented by Booch, Rumbaugh, and Jacobson in the UML User Guide.
