从用户故事到序列图 [英] From user stories to sequence diagram

问题描述

我想知道:

如何将用户故事转换为顺序图?

how to convert users stories into sequence diagrams?

(对于客户)最容易理解的图是什么?

and what is the most easy diagram to understand (for customer)?

推荐答案

在我看来，最适合客户的不是用例.即使对于大多数开发人员来说，它们也过于抽象和复杂.而当他们最终获得批准时，您将无法确定客户是否真正正确地理解了他们.

In my opinion, what works best with the customers are not use cases. They are too abstract and complicated even for the most of developers. And when they are finally approved, you're never sure whether the customers actually understood them correctly.

我建议结合使用 UML活动图和用户界面原型(非UML)，这是与非技术业务人员一起进行此分析级别的最佳工具

I suggest the mix of UML activity diagrams and user interface prototypes (non UML) as far the best tool to work on this level of analysis with non technical business people.

活动以直观，易于理解和清晰的方式为业务建模. 还具有UI原型，因此他们可以看到他们如何将业务映射到屏幕.

Activities model their business in an intuitive, easy to understand and clear way. UI Prototypes as well, so they can see how they business maps to screens.

在幕后，我喜欢用正式而准确的领域类模型来支持活动，这些模型当然对客户是不可见的，但对开发人员开放，并为将来的系统打下了良好的技术基础.

Behind the curtains, I like to support activities with a formal and accurate domain class model, invisible to customers of course, but open to developers and making a nice technical backbone of the future system.

用户案例非常适合此建模集中，您甚至可以使它们不那么正式和更高级，因为其余内容将填补信息空白.现在可以使用连接两个视图(客户视图和开发者视图)的域对象来构建序列.

User stories fit perfectly in this modelling set, you can even make them less formal and more high-level, as the rest will fill the information gap. Sequences can now be build using domain objects, connecting 2 views - customers' and developers'.

在可能的情况下，我会尽量避免用例(尽管我个人很喜欢它们).

I avoid use cases strongly, whenever possible (although I personally like them).

这篇关于从用户故事到序列图的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！