用例和 SRS 之间的区别？
用例和 SRS 之间有什么区别？
What is the difference between a use case and an SRS?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
用例和 SRS 之间有什么区别？
What is the difference between a use case and an SRS?
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论（5）
SRS 包含一组用例以及非功能性需求
An SRS contains a set of use cases as well as non-functional requirements
在软件和系统工程中，用例是操作或事件步骤的列表，通常定义角色和系统之间的交互，以实现目标，而软件需求规范（SRS）是一个文档，捕获有关如何实现目标的完整描述。系统预计将执行。
In software and systems engineering, a use case is a list of action or event steps, typically defining the interactions between a role and a system, to achieve a goal while software requirements specification (SRS) is a document that captures complete description about how the system is expected to perform.
SRS 和用例对于某些作者来说是相同的，而对于另一些作者来说则是不同的。就您而言，正在要求一个“不同”的地方。
SRS 是：输入、流程描述、输出，这就是每个需求的内容。
用例规格是：TO-BE 设计，可追溯到 SRS 多对一。
问候，
以西结
SRS and Use cases are the same for some authors and different for another. In your case, are requesting the one, where their are "different".
The SRS, is: input, process description, output and that's it for every requirement.
The Use case specs is: the TO-BE design which traces to the SRS many to one.
Regards,
Ezekiel
SRS - 系统需求规范：描述整个系统流程、数据如何流入系统以及系统的整体功能。 SRS 简要介绍了每个模块的功能，但不包括每个页面和模块的深入功能。
SRS 文档包括一组用例，解释用户与软件的所有交互。用例也称为功能需求。除了用例之外，SRS 还包含非功能性需求。
SRS - System Requirement Specification: describes entire system flow, how data is going to flow into the system and overall functionality of the system. SRS says brief about each module's functionality and doesn't include in-depth functionality of each page and module.
SRS documentation includes a set of use cases that explain all the interactions the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the SRS also contain non-functional requirements.
用例仅定义系统角色之间的交互。它没有给出模块的简要知识/描述。
SRS定义了系统和模块将如何执行。它给出了系统角色的详细描述。它让参与开发过程的每个团队都受益匪浅。
Use Case only defines the interaction between the roles of the system. It doesn't give the brief knowledge/description of the modules.
SRS defines how the system and modules are going to be performed.It gives a detailed description of the system roles. It indulges each and every team who is involved in development process.