系统需求规范:用户需求？

Question

我目前正在为一个系统编写一个SRS，并且我很难弄清楚用户的需求在哪里。我会给你我现在的内容：

Table of Contents
Revision History
1. Document Introduction
    1.1 Purpose
    1.2 Scope
    1.3 Word List
    1.4 References
    1.5 Overview
2. System Description
    2.1 Product Description
    2.2 Project Stakeholders
    2.3 System Characteristics
    2.4 Context Diagram
        2.4.1 Frontend
        2.4.2 Backend
        2.4.3 Database  
        2.4.4 API
     2.5 User Requirements // <---- is this the correct place and naming?
     2.6 User Assumptions and Dependencies  
     2.7 User Documentation
3. User Requirements // <---- or is this more appropriate?
4. Functional Requirements
    4.1 Frontend
        4.1.1 Stop
        4.1.2 Quicklist
        4.1.3 Journey
        4.1.4 Settings
        4.1.5 System
        4.2.6 JSON
    4.2 Backend
        4.2.1 JSON
        4.2.2 System
5. Other Non-Functional Requirements
    5.1 Software Interface
    5.2 Performance Requirements
    5.3 Security Requirements
    5.4 Software Quality Attributes
    5.5 Platform Requirements

用户需求将容纳如下(这只是一个例子)：

The user needs the application to be responsive at all times.
The user must not be confused as to what is a button and what is not.
The user must be able to save personal preferences within area A of the application.
The user must be able to use the application offline.
The user must be able to retain their personal preferences if they log in on any device.

如果这不是正确的地方放置他们，那么我应该把他们放在哪里，也如果有任何其他看起来不对劲的SRS只是说，我一直在寻求提高我的技能！

Answer 1

我会将用户需求保持在2.5的位置，因为接下来的信息流是用户依赖/假设。但是，如果信息足够大，需要自己的部分，那就更有意义了。如果不知道每个部分都代表了什么，就很难回答这个问题。我通常假设用户的需求将在项目的范围和目的中定义，而不是需要一个章节来进一步解释用户需要什么，或者项目的“为什么”。