知识卡片
设计当时留下视图与理由
草图和职责表应在设计时保存,而不是事后凭记忆补写。可拍白板或用工具,但符号需一致并给图例;图本身难以显示替代方案和取舍,还要记录显著决策与原因。文档详略由分析、建设、教育等用途和风险决定,正式完整视图可后续形成,不能把ADD变为先写完巨型文档。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 设计架构 · 查看原书依据
You should develop a discipline of writing down the responsibilities that you allocate to the elements as you create the structures. The reasons for this are simple: As you identify an element, you are determining some responsibilities for that element in your mind.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第20章《设计架构》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch20.html)
- 结论依据:原文解释草图和职责表应在设计时保存,而不是事后凭记忆补写;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。
- 原始内容:You should develop a discipline of writing down the responsibilities that you allocate to the elements as you create the structures. The reasons for this are simple: As you identify an element, you are determining some responsibilities for that element in your mind.