用例图作为新功能的需求收集工具 - 特别是在只需要很少用户交互的系统中
我有兴趣追求使用用例图作为收集用户需求的工具的想法。然而，这将是为了新功能，而不是从头开始开发系统。此外，该系统只有一小部分用户交互——大多数参与者将是外部系统。
我想知道人们使用这种收集需求的方法的经验如何。您的客户对这一变化有何反应？是否积极？它对任何人都不起作用吗？
谢谢，
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,
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（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.