知识卡片
用户旅程指导架构取舍
用户旅程描述用户在系统中可能做什么,范围比需求规格更广,且随用户演变,永远不能一次穷尽。先理解最重要场景,用“影响哪段旅程、增加多少价值、是否有更有价值的替代”评估功能和架构决策,防止为容易实现却少人使用的功能浪费投资。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 理解系统设计与架构 · 查看原书依据
The user journey defines what they can and will do with the system. It is not what is written down in the requirement specification. It is everything that can happen. The user journey, however, is never fully defined. It evolves as the user evolves and includes almost unlimited possibilities.
参考来源
- 位置:《Software Architecture and Decision-Making》第2章《理解系统设计与架构》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch02.xhtml)
- 结论依据:原文的定义、比较或例子支持“用户旅程描述用户在系统中可能做什么,范围比需求规格更广,且随用户演变,永远不能一次穷尽”;正文据此说明用途和边界。
- 原始内容:The user journey defines what they can and will do with the system. It is not what is written down in the requirement specification. It is everything that can happen. The user journey, however, is never fully defined. It evolves as the user evolves and includes almost unlimited possibilities.