简体繁体 English

用例图作为新功能的需求收集工具-特别是在只需要很少用户交互的系统中

[英]Use Case diagrams as a requirements gathering tool for new functionality - particularly in systems that only require very little user interaction

原文 2010-05-14 13:18:27 3 1 requirements/ use-case/ real-time-systems

I'm interested in persuing the idea of using Use Case Diagrams as a tool for collecting user requirements. 我对说服使用用例图作为收集用户需求的工具的想法很感兴趣。 However, it will be for new features as opposed to developing a system from scratch. 但是，这将是新功能，而不是从头开始开发系统。 Also, the system only has a small level of user interaction - most of the actors will be external systems. 而且，系统仅具有少量的用户交互-大多数参与者将是外部系统。

I want to know what people's experiances have been with using this method of gathering requirements. 我想知道人们使用这种收集需求的方法的经历。 How did your customers respond to the change and was it positive? 您的客户如何应对这一变化，并且是积极的吗？ Did it just not work for anybody? 只是对任何人都行不通吗？

Thanks, 谢谢，

1 个解决方案

One of the main benefits of use-cases is they help communicate ideas clearly, so that you and end-users can get on the same wavelength. 用例的主要好处之一是它们可以帮助您清晰地传达想法，从而使您和最终用户可以使用相同的波长。 They can provoke discussion and reveal subtleties that users (or you) might take for granted. 他们可以引起讨论并揭示用户（或您）可能认为理所当然的微妙之处。

On the other hand interaction between systems is concrete, so you can dispense with discussion and instead seek to document hard facts; 另一方面，系统之间的交互是具体的，因此您可以省去讨论，而寻求记录事实。 what data will be transmitted, what volumes, what form will it take, what happens when garbage is received, and so on. 什么数据将被传输，什么卷，它将采取什么形式，接收到垃圾时会发生什么，等等。