← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 1958.x.3

架构过程形成反馈闭环

理解等级:中级

少数明确负责的架构师与技术负责人保持概念一致性,并与实现团队紧密协作。以有优先级的质量需求驱动设计,用视图交流,尽早评价并在变化后重评,再通过先跑通通信的骨架系统逐步生长功能。骨架先具备初始化、通信、数据共享、资源访问和错误日志;可先用低保真原型或按目标速率收发的替身,再逐步增加功能。这样减少纸上设计与最终实施脱节,并提前发现集成和性能问题。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 2 处

    • 什么是软件架构 · 查看原书依据

      The architecture should lend itself to incremental implementation, to avoid having to integrate everything at once (which almost never works) as well as to discover problems early. One way to do this is via the creation of a “skeletal” system in which the communication paths are exercised but which at first has minimal functionality. This skeletal system can be used to “grow” the system incrementally, refactoring as necessary.

    • 软件架构为何重要 · 查看原书依据

      The first increment can be a skeletal system in which at least some of the infrastructure—how the elements initialize, communicate, share data, access resources, report errors, log activity, and so forth—is present, but much of the system’s application functionality is not.

    参考来源

    - 位置:《Software Architecture in Practice, 4th Edition》第1章《什么是软件架构》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch01.html) - 结论依据:原文的定义、机制或比较支持“少数明确负责的架构师与技术负责人保持概念一致性,并与实现团队紧密协作”;正文保留其条件与取舍。 - 原始内容:The architecture should lend itself to incremental implementation, to avoid having to integrate everything at once (which almost never works) as well as to discover problems early. One way to do this is via the creation of a “skeletal” system in which the communication paths are exercised but which at first has minimal functionality. This skeletal system can be used to “grow” the system incrementally, refactoring as necessary.