知识卡片
用具体职责代替术语争论
把功能笼统分成“做什么”、质量分成“做得怎样”常会失效:控制发动机必须有时序,登录认证又兼具安全职责。需要精确表达时,先列系统必须执行的具体计算职责,再问其时限、预期修改或允许用户。质量要求本身也会引入新职责,不应因被称为非功能就忽略实施。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 理解质量属性 · 查看原书依据
I much prefer using the word “responsibility” to describe computations that a system must perform. Questions such as “What are the timing constraints on that set of responsibilities?”, “What modifications are anticipated with respect to that set of responsibilities?”, and “What class of users is allowed to execute that set of responsibilities?” make sense and are actionable.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第3章《理解质量属性》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch03.html)
- 结论依据:原文的定义、机制或比较支持“把功能笼统分成“做什么”、质量分成“做得怎样”常会失效:控制发动机必须有时序,登录认证又兼具安全职责”;正文保留其条件与取舍。
- 原始内容:I much prefer using the word “responsibility” to describe computations that a system must perform. Questions such as “What are the timing constraints on that set of responsibilities?”, “What modifications are anticipated with respect to that set of responsibilities?”, and “What class of users is allowed to execute that set of responsibilities?” make sense and are actionable.