知识卡片
架构特征界定成功
领域需求描述软件解决什么业务问题;架构特征描述支撑成功所需的性能、伸缩性、模块性等能力。“非功能需求”“质量属性”在这里指同类关注点。功能正确不表示系统整体可用,架构设计必须同时识别领域需求与这些特征,并为后者确定保护机制。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 架构特征界定成功
原书出处 · 1 处
- Evolving Software Architecture · 查看原书依据
The requirements shown in Figure 1-1 represent whatever problem domain the software solution addresses. The other parts are variously known as architecture characteristics (our preferred term), nonfunctional requirements, system quality attributes, cross-cutting requirements, and a host of other names. Regardless of the name, they represent critical capabilities required for project success, both for initial release and long-term maintainability. For example, architecture characteristics such as scale
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第01章《Evolving Software Architecture》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch01.html;段落定位:The requirements shown in Figure 1-1)
- 结论依据:原文对“架构特征界定成功”的定义或案例,支撑“领域需求描述软件解决什么业务问题;架构特征描述支撑成功所需的性能、伸缩性、模块性等能力”的归纳。据其上下文,“非功能需求”“质量属性”在这里指同类关注点。
- 原始内容:The requirements shown in Figure 1-1 represent whatever problem domain the software solution addresses. The other parts are variously known as architecture characteristics (our preferred term), nonfunctional requirements, system quality attributes, cross-cutting requirements, and a host of other names. Regardless of the name, they represent critical capabilities required for project success, both for initial release and long-term maintainability. For example, architecture characteristics such as scale