This article examines Xiaomi's 2024 business performance and reveals how the company applies mathematical modeling to its pricing, user‑growth, supply‑chain, ecosystem, and new‑retail strategies, illustrating the quantitative logic behind its market‑leading success.
This article explains what modeling means across disciplines, why it is essential for simplifying complex real‑world problems, outlines the three main types of modeling in software engineering, and dives into the practical difficulties of business, domain, and data modeling with concrete examples and diagrams.
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 article walks through business, conceptual, logical, and physical modeling steps to design a recommendation system architecture, detailing value propositions, workflow decomposition, component breakdown, and technology choices to meet reliability, low‑latency, and scalability requirements.
This article walks through a step‑by‑step mathematical modeling process for a night‑market stall, covering product selection, supplier cost comparison, optimal pricing, stall location choice, and promotion strategies to maximize profit and efficiency.
This article explains how to move from business modeling to business and system use case diagrams, covering vision definition, business sequence diagrams, system use case creation, use case specifications, and concludes with a brief promotion for a DevOps certification course, offering practical guidance for software engineers.
The article examines modern software development challenges, explains why thorough design and modeling are essential before coding, and outlines three key practices—business modeling, business process analysis, and system modeling—along with class analysis techniques to improve collaboration, reduce rework, and build robust architectures.
This article guides developers through business modeling, defining a clear vision, creating business and system use‑case diagrams, drawing business sequence diagrams, and refining requirements with use‑case specifications, emphasizing how proper modeling adds real value to software projects.
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.
This article explains how to transform business modeling into concrete requirements by analyzing a face‑recognition payment system for school canteens, covering vision definition, target organization identification, goal measurement, use‑case modeling, and detailed use‑case specifications to ensure valuable, well‑scoped software development.
This article explains how to turn software code from a cost into real product value by systematically modeling the business, identifying the target organization and its decision‑maker, defining a measurable vision, and writing precise, stakeholder‑driven requirements and use‑case specifications.
This article explains why Domain‑Driven Design is needed, critiques traditional development workflows that produce opaque code, and presents various modeling and aggregation strategies—including code examples—to involve non‑developers and bridge the gap between business experts and developers.
The article explains business capability modeling as a technique for creating an organization‑centric capability anchor model, describes how to link process models to capabilities, outlines a step‑by‑step methodology, and highlights practical uses such as strategic planning, resource allocation, and IT transformation support.
The article explains how the evolution from monolithic to microservice architectures created a need for clear business boundaries, why DDD gained traction after the microservice boom, and outlines the strategic and tactical steps to apply DDD for effective service decomposition.
This article explains the distinction between technical and business domains, defines domains and subdomains, describes how to identify core, generic, and supporting subdomains, and outlines practical methods such as domain vision statements and highlighted cores for effective domain‑driven design.
This article explores the communication gaps that hinder software projects, introduces Event Storming as a visual, collaborative workshop technique, walks through its syntax and practical coupon‑distribution example, connects the outcomes to Domain‑Driven Design, and shows how the method improves alignment between product, business, and engineering teams.
This article explores the core purpose of system architecture, identifies technical, business, and project-management challenges, and presents a systematic approach—systemic thinking, decomposition, abstraction, and patterns—to effectively design and implement robust architectures.
The article explains how Alibaba’s TMF 2.0 framework tackles massive transaction‑peak challenges by introducing visual, configurable, and manageable business definitions through a plug‑in architecture, unified business identity, and a clear separation of management and runtime domains.
