There are as many SRS templates as there are software architects so it's a little hard to give a good answer, but I think you're on the right track with an overview (perhaps in use case form) in the Definition section and more details in the Detailed section.
When it comes to elaborating use cases, I usually steer clear of state charts. I feel they're better suited for describing design rather than specifying functionality. I like Activity diagrams for this purpose, but again it depends on the type of system you are specifying.
发布评论
评论（1）
有多少个软件架构师就有多少个 SRS 模板，因此很难给出一个好的答案，但我认为您在定义部分中的概述（可能以用例形式）和更多详细信息中处于正确的轨道上详细部分。
在详细阐述用例时，我通常会避开状态图。我觉得它们更适合描述设计而不是指定功能。我喜欢用于此目的的活动图，但这又取决于您指定的系统类型。
There are as many SRS templates as there are software architects so it's a little hard to give a good answer, but I think you're on the right track with an overview (perhaps in use case form) in the Definition section and more details in the Detailed section.
When it comes to elaborating use cases, I usually steer clear of state charts. I feel they're better suited for describing design rather than specifying functionality. I like Activity diagrams for this purpose, but again it depends on the type of system you are specifying.