厘清设计中的核心需求，避免因理解偏差导致失败
A Deep Dive into Axiomatic Design -- Part I: Problem Formulation
- 明确第一层功能需求的定义与边界，确保独立性
- 相同需求下不同设计师应得出一致的功能需求
- 适合初学者和需要严谨设计流程的工程师
问题定义——将客户需求和约束转化为最少且相互独立的第一层功能需求——是所有设计框架（包括公理化设计）中最关键的步骤，但实践中常被误解或低估。本文聚焦公理化设计中的问题定义，阐明第一层功能需求的本质（及非本质），解释为何在相同需求和约束下，功能需求不应因设计师而异，并揭示导致设计失败的内在难点与常见陷阱。论述主要基于苏南·P·Suh的三部著作：《设计原理》《公理化设计进展与应用》《复杂性理论》，并提供实用指导，帮助设计者制定恰当的第一层功能需求。最后简要回顾大语言模型时代的问题定义，探讨此类工具在第一层所能提供的支持及其局限。
原文摘要 · Abstract (English)
Problem formulation translating customer needs and constraints into a minimum set of independent first-level functional requirements, is arguably the most critical step in every design framework, including axiomatic design yet it is frequently misunderstood or underestimated in practice. This paper focuses exclusively on problem formulation in axiomatic design it clarifies what first-level FRs are (and are not), explains why they should not legitimately vary across designers given the same needs and constraints, and highlights intrinsic difficulties and recurring pitfalls that lead to design failure. The discussion is grounded primarily in Nam P.Suh's three books. The Principles of Design, Axiomatic Design Advances and Applications, and Complexity Theory, and it offers practical guidance to help designers formulate well-posed first-level FRs. Finally, the paper briefly revisits problem formulation in the era of large language models and discusses what such tools can (and cannot) contribute at the first level.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品；中文卡片由大模型生成，请以原文为准。