0 views collected around this technical thread.
This article introduces a four‑tree framework—WHAT, WHY, HOW, and WHAT‑IF—explaining how each logical tree helps classify issues, uncover root causes, design actionable solutions, and forecast outcomes, while offering refined drawing guidelines and linking the approach to the DEED problem‑type model.
The article explains how product managers should first analyze business architecture and user expectations, then use functional, information, and product architecture diagrams to systematically design and communicate product structure, avoiding premature detail work and ensuring coherent, scalable solutions.
The article explains Domain‑Driven Design as a method for managing software complexity, outlines its meta‑models and limitations, and demonstrates a full problem‑domain analysis for Bilibili’s OGV business—including stakeholder value‑demand analysis, process and use‑case modeling, scenario definition, ubiquitous language creation, and sub‑domain classification—while noting that implementation details will be covered later.
This article explains the concept of a value chain, outlines Michael Porter’s value‑chain model, describes primary and support activities, compares cost‑leadership and differentiation strategies, and provides practical steps and templates for conducting a value‑chain analysis to improve efficiency and profitability.
Becoming a competent IT architect requires a blend of up‑to‑date technical expertise—such as knowledge of AI, big data, cloud computing, networking, databases, security, and programming—deep business understanding of requirements, processes, and data models, and strong leadership skills for team and project management.
This article explores the concept of architecture—from its origins in human societal division of labor to its application in software design—highlighting why recognizing problems, defining boundaries, and splitting responsibilities are essential for building effective, scalable systems that serve human needs.
This article introduces system thinking by defining systems and explaining its three core mindsets—deep, holistic, and dynamic thinking—while detailing causal loop diagram components, common reinforcing and balancing loops, and five foundational models that together help analyze interdependencies, uncover behavior patterns, and support wiser decision‑making.
This guide explains how to plan an application by defining the problem it solves, understanding users and goals, then outlines systematic steps to analyze, improve, and automate business workflows, including practical questions, optimization methods, and a detailed expense‑report case study.
This article presents a step‑by‑step methodology for converting business domain models into robust data models, illustrated with a community group‑buying pre‑scheduling case, and discusses object identification, relationship definition, model refinement, and mapping to database structures to improve scalability and maintainability.
This guide outlines essential steps for planning an application, including defining the problem it solves, identifying target users and goals, understanding current business processes, recognizing key contributors, and creating a project plan to ensure the solution aligns with business needs.
This guide explains how to plan a Power Apps application by identifying the business problem (use case), understanding current processes, estimating the cost of manual work, and creating a project plan that aligns with user goals and organizational value.
The BCG growth‑share matrix, developed by the Boston Consulting Group in the early 1970s, categorizes business units into Stars, Cash Cows, Question Marks, and Dogs based on market growth and relative share, guiding resource allocation while highlighting criticisms such as over‑emphasis on growth and questionable profit assumptions.
The article introduces the Zachman Framework, detailing its historical origins, the six‑row and six‑column matrix of 36 cells, the seven governing rules, and how the framework is applied to model and manage complex enterprise architectures, emphasizing change management and reduction of redundancy.
The article outlines practical business analysis approaches—including flowcharts, sequence diagrams, prototype sketches, business and data model diagrams—and recommends modeling tools, emphasizing the importance of selecting appropriate visualizations to clarify complex requirements and improve communication between stakeholders and technical teams.
This article provides a thorough overview of system architecture methodology, covering core concepts, business and requirement analysis, domain and business modeling, architectural design (logical and physical), high‑level and detailed design, and subsequent development, testing, deployment, and operation phases.
This tutorial explains the concepts of BPMN pools and lanes, demonstrates how to model a distilled‑water ordering process for True Aqua using pools, lanes, and nested lanes, and provides step‑by‑step instructions for creating the diagram in a modeling tool.
This article analyzes ByteDance’s rapid growth by examining its product portfolio, commercial efficiency, algorithmic advantages, and recent expansion into education, gaming, automotive, literature, office tools, and healthcare, revealing why some products thrive while others lag behind.
The article explains the BCG growth‑share matrix, describes its four quadrants—Stars, Cash Cows, Question Marks, and Dogs—illustrates how resources are allocated, discusses its advantages and criticisms, and shares practical experiences of using the matrix for product portfolio decisions.
This article presents a comprehensive guide to solution architecture design, covering its definition, problem classification, a step‑by‑step discovery and design process, key principles, and a toolbox of practical techniques for architects to align solutions with business needs and enterprise capabilities.
This article explains what a business capability is, why it matters, and provides nine practical guidelines to help organizations identify, distinguish, and validate capabilities when building capability maps, emphasizing clear definitions, outcomes, and unique intent.