返回主题:状态与活动建模

此卡片不在当前主题的阅读序列中,可返回主题继续阅读。

知识卡片

普通读书笔记卡 · 2314.m

视图围绕需要管理复杂性

理解等级:中级

视图是特定类型元素及其关系的表示,不是把所有东西画在同一张图上。模块、运行连接、分配等视图各暴露不同性质,应按读者与质量分析目标选择,并让收益抵偿创建维护成本。架构结构是系统中实际元素关系,视图则是其表示;层次视图不应被误当运行服务或数据模型的完整说明。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 记录架构文档 · 查看原书依据

      A view is a representation of a set of system elements and relations among them—not all system elements, but those of a particular type. For example, a layered view of a system would show elements of type “layer”; that is, it would show the system’s decomposition into layers, along with the relations among those layers.

    参考来源

    - 位置:《Software Architecture in Practice, 4th Edition》第22章《记录架构文档》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch22.html) - 结论依据:原文解释视图是特定类型元素及其关系的表示,不是把所有东西画在同一张图上;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。 - 原始内容:A view is a representation of a set of system elements and relations among them—not all system elements, but those of a particular type. For example, a layered view of a system would show elements of type “layer”; that is, it would show the system’s decomposition into layers, along with the relations among those layers.