知识卡片
架构术语需约定可检验的含义
同一个架构词可能有不同含义。原书举“互操作性”与“兼容性”:前者偏系统集成与接口,后者偏行业或领域标准;“易学性”甚至可指用户学习软件,也可指系统自动学习环境。
若只写抽象标签,团队可能以为达成共识,实施和验收却各用自己的定义。应在当前项目中说明对象、度量或可观察结果,形成共同语言;这种写法是应用推断,不声称存在统一词典。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Architectural Characteristics Defined · 查看原书依据
The absence of a standard leads companies to define their own terms for common things. This often leads to industry-wide confusion, because architects either use opaque terms or, worse yet, the same terms for wildly different meanings.
参考来源
- 位置:《Fundamentals of Software Architecture》第06章《Architectural Characteristics Defined》(源文件:`OEBPS/ch04.html`,Cross-Cutting Architectural Characteristics、The Many Ambiguities in Software Architecture)
- 结论依据:原文明确不同术语间的细微区别、同名术语的不同含义及组织使用共同语言的建议;操作化写法是应用推断。
- 原始内容:The absence of a standard leads companies to define their own terms for common things. This often leads to industry-wide confusion, because architects either use opaque terms or, worse yet, the same terms for wildly different meanings.