SRS：场景和流程叙述（UML）有何不同
在软件需求规范中，
每个功能的场景和流程叙述（使用 UML 描述）之间有什么区别？
我理解场景是对系统单个功能的描述。 是否也需要用 UML 来描述场景，或者文本描述就足够了？ 因为我已经必须用 UML 详细描述每个功能（特性）的流程。
两种方法是等效的，对吗？
谢谢，家伙
In Software Requirements Specification,
what is the difference between Scenarios and Process Narratives of each function (described using UML)?
I understand that Scenarios are descriptions of a single feature of the system.
Is it necessary to describe Scenarios also with UML, or are the text descriptions sufficient?
Because I already have to detail Process narrative of each function(feature) with UML.
Both approaches are equivalent, right?
thx, guy
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您不必同时使用两者，您应该使用所有适合传达您正在建模的内容的技术。有些东西传统上可以使用文本更好地表达（用例描述、算法等），有些东西可以更好地以图形方式描述（类层次结构、关系、各种流程......）。因此，由您决定哪种符号最适合您想要描述的事物。
You don't have to use both, you should use all teh techniques that are fit to communicate what are you modeling. There are things which are traditionally better expressed using text (use case descriptions, algorithms, ...) and there are those which are better described graphically (class hierarchy, relations, various flows...). So it is up to you to decide what notation is best for the thing you want to describe.
同时使用 UML 和文本，对于文本，您可以包括表格、段落、非 UML 图表。
两种规范技术是互补的，如果一种技术缺少某些功能，则可以包含另一种技术。
Use both UML and text, and for text you may include tables, paragraphs, non UML charts.
Both specification techniques are complementary, in case some feature is missing in one, the other may included.