知识卡片
用例描述交互需求
用例是比用户故事更偏重文档的需求表达方式,用于描述使用者与系统交互以完成目标。本章脚注指出其与UML和RUP的历史关联。它与用户故事的格式不同,但二者都不能自然装下所有系统品质要求,性能和安全仍需要适当跨功能表达。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- To Practice Architecture Is to Decide · 查看原书依据
Use cases were commonly used before extreme programming (XP) popularized user stories. First proposed by Ivar Jacobson at OOPSLA 1987, use cases were core to diagramming notation UML and the rational unified process (RUP). They are a more heavyweight, documentation-driven way of capturing user requirements for software. 9 The problem is that some of them
参考来源
- 位置:《Facilitating Software Architecture》第02章《To Practice Architecture Is to Decide》(来源项目book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch02.html)
- 结论依据:原文脚注说明use case的历史及heavyweight documentation-driven性质,正文说明其不足以承载全部品质。
- 原始内容:Use cases were commonly used before extreme programming (XP) popularized user stories. First proposed by Ivar Jacobson at OOPSLA 1987, use cases were core to diagramming notation UML and the rational unified process (RUP). They are a more heavyweight, documentation-driven way of capturing user requirements for software. 9 The problem is that some of them