1. Introduction

1. Basic information about Requirements

Product Manager:

Priority:

1. Change Log

1. Glossary

For infrequent words or newly created words, it is necessary to define and describe them so that the reader can understand them quickly.

1. Requirements Review Records

2022年3月24日, 周四2022年3月24日  Requirements Review Meeting

Attendees: you can ype "@+ name" to refer to the people participating in the review

Conclusion：

Todo：

2. Requirements Background

1. Problem to Be Solved

Describe the problem to be solved as simply as possible so that the document reader can quickly get to the point.

1. User Research

Brief description of the survey methods, samples and key conclusions, can be entered "@+ file name" attached to a detailed shimo cloud file.

1. Data Analysis

Only in this document to list the key findings, there are more detailed data analysis report can enter "@+ filename" attached to the graphite cloud file.

1. Competitive Analysis

Set out the main information and key conclusions of the relevant capabilities of the competition, which can be focused on the motivation and objectives behind their design, and then compared with the problem we want to solve.

3. Requirements Objectives

Requirement Objectives: Objectives should be measurable and assist us in determining whether the objectives have been achieved afterwards. For instance, supporting XX capability within XX time frame, allowing users to directly XXXXXX within XX time frame.

Measurement Criteria: The measurement approach can be quantitative or qualitative. For example, one month after the feature's launch, the usage rate of the feature (XX feature UV / XX product UV) should reach X%.

4. Requirements Range

Organized list of requirements scope or information architecture。

5. Function Detailed Description

1. Product Flowchart

You can insert the product flowchart here.

1. Interactive Prototype

You can copy the webpage link and directly paste it into the document.

1. Function Descriptions

6. Non-Functional Requirements

You can enumerate product marketing needs, operational needs, financial needs, legal needs, use of help, problem feedback, etc.

7. Data Requirements

Consider in advance what data you want to see after the feature is launched and what kind of user insights you hope to gain from each data point.

8. Project Time Planning

You can type "@+ filename" to insert the relevant shimo cloud file or insert a table directly into the document

9. Appendix

You can type "@+ filename" to insert the relevant shimo cloud file, or other requirements-related description links attached here for reference.

1. Data Analysis Report

2. User Research Reports

3. Design Analysis Report

4. ......