知识卡片
接口随场景逐步细化
外部接口通常是既有约束,应在系统上下文中识别;内部接口来自元素为功能或质量场景的协作。先用时序或状态等行为表示推导交换信息,再形成契约。早期层与层可只标命令和结果,后续相关场景才需细化;互操作技术栈可能已固定部分契约,也不要求每次迭代列出全部内部接口。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 设计架构 · 查看原书依据
The identification of interfaces is usually not performed equally across all design iterations. When you are starting the design of a greenfield system, for example, your first iterations will produce only abstract elements such as layers; these elements will then be refined in later iterations.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第20章《设计架构》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch20.html)
- 结论依据:原文解释外部接口通常是既有约束,应在系统上下文中识别;内部接口来自元素为功能或质量场景的协作;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。
- 原始内容:The identification of interfaces is usually not performed equally across all design iterations. When you are starting the design of a greenfield system, for example, your first iterations will produce only abstract elements such as layers; these elements will then be refined in later iterations.