知识卡片
用不同视图培训不同问题
新人理解系统时可先借模块视图认识职责与团队分工,借组件连接视图理解运行协作,再借分配视图找到自己的代码在开发或部署环境中的位置。统一架构参照减少只靠局部源码猜全貌的学习成本;培训应按问题切换视图,而非要求新人记完全部文档。
相关:[[共同抽象促成需求协商]]。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 软件架构为何重要 · 查看原书依据
Module views are excellent means of showing someone the structure of a project: who does what, which teams are assigned to which parts of the system, and so forth. Component-and-connector views are excellent choices for explaining how the system is expected to work and accomplish its job. Allocation views show a new project member where their assigned part fits into the project’s development or deployment environment.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第2章《软件架构为何重要》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch02.html)
- 结论依据:原文的定义、机制或比较支持“新人理解系统时可先借模块视图认识职责与团队分工,借组件连接视图理解运行协作,再借分配视图找到自己的代码在开发或部署环境中的位置”;正文保留其条件与取舍。
- 原始内容:Module views are excellent means of showing someone the structure of a project: who does what, which teams are assigned to which parts of the system, and so forth. Component-and-connector views are excellent choices for explaining how the system is expected to work and accomplish its job. Allocation views show a new project member where their assigned part fits into the project’s development or deployment environment.