1 views collected around this technical thread.
This article explains how modeling, especially Model‑Driven Architecture (MDA), helps software architects identify and manage complexity by abstracting business, logical, and technical concerns into CIM, PIM, and PSM layers, and provides practical principles for prioritizing architectural decisions.
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 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 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.
The article systematically examines Domain‑Driven Design through four discourses—Structure, Process, Language, and Modeling—while contrasting the practical “folk” school with the academic school, linking philosophical ideas, software‑complexity theory, strategic and tactical design, refactoring, agile practices, ubiquitous language, and its parallels to UML/SysML, arguing DDD repackages existing engineering concepts rather than inventing new ones.
This article introduces Data Flow Diagrams (DFD) as a visual tool for modeling system data flows, explains their core components and symbols, and demonstrates their application through a step‑by‑step airline ticket reservation case study, helping readers grasp DFD creation and interpretation.
This article explains the concept, components, and basic symbols of Data Flow Diagrams (DFD) and demonstrates how to draw a complete DFD for a ticket‑booking system, illustrating entities, processes, data stores, and data flows step by step.
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.
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.
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.
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.