Quickly grasp the key points of demand?

Abstract: In the early stage of the project, we often need to quickly grasp the overall requirements of the system and clarify the key points through a simple exchange and several original materials. How can we achieve this effectively? I usually use NotePad to take a note containing the key points. The content of this note is as follows:
Bytes ---------------------------------------------------------------------------------------------------------------------

Name:××× System
E. g.: Online Bookstore System
Customer:××× (Name), ××× (main person in charge), and ××× (contact information)
　　Such as: New Media, Li Si,13888888888, lisi@gmail.com　　
Project objectives:
Develop a ×× application system to enable the customer to ×××.
Note: use one sentence to describe it as concise as possible:,For example, develop an e-commerce website to enable customers to sell books online.
The customer hopes to implement such functions before XXX.
Note: words should be as concise as possible to describe the functions that the customer wants to implement in a short term. For example, the customer wants to provide books for upload and management within one month, and can performBook browsing and query functions.
This is equivalent to describing a short-term goal. The objective of setting short-term goals is to allow us to quickly seize the core and urgent needs and avoid wasting the most valuable resources in the early stage.
The customer hopes to implement functions such as **.
Note: a concise description of the final overall expectations. For example, the customer hopes to implement a simple and easy-to-use book sales website that can manage 1 million books, with millions of daily visits.
This is the final description of the systemVision.
Determine the general direction and principles.
Project role:
1) ×× role: a user from ××× completes the ×× task and ××× through the system.
For example, website visitors come from outsideInternetUsers can browse and query books through the system, and become members after registration. Roles are generally divided into customer roles (end users who use the system) and internal roles (Maintenance roles for system management and configuration ). The clause from XXX usually shows whether the role is an end user or an internal role. Generally, the demand priority of the end user role is higher than that of the internal role (because the customer can see more value)
2) ×× role: a user from ××× completes the ×× task and ××× through the system.
Such as: Member role, from externalInternetAfter registering, you can become a member. You can collect, preview, and purchase books through the system.
3) ×× role: a user from ××× completes the ×× task and ××× through the system.
For example, you can use the system administrator role to manage books, members, and system configurations and maintenance.
4 ).......
Key features:
Note: In my opinion, I only need to list the key points of the short-term objective described above, and only elaborate on the key points of the long-term objective if necessary. I think the user scenario (User Scenarios) Or user stories (User
Story. (Available if necessaryWordWrite this document and add some interface framework sketches to these scenarios or stories, which makes it easier for all the members to have a deep impression)
1)
×× (Role) performs ** × (operation) to ** × (Purpose ).
Note:Who, What, WhyThree elements, sometimes addedWhen, WhereElements.
For example, when a visitor opens a webpage, he can view a list of the latest 10 books and popular 10 books, and search for books through the search function on this page.
For another example, you can go to the system through the "Administrator Logon" page to view the list of existing books, books can be sorted by time, publisher, author, price, sold quantity, and number of databases. You can also search for and filter books based on these fields. You can add new books conveniently and quickly.
At the end of each month, the system administrator needs to collect statistics about the book sales for this month, generate statistical reports, and send emails to the sales manager and general manager.
2 ).......

Other Instructions:

Note: Here are some important things related to the project background.
For example: 1) previously, this customer invited XXX to develop a prototype, but we chose to change it because we were not satisfied, we will try to obtain the existing information to help us analyze ...;
2) The customer attaches great importance to the performance and stress testing of the website, and requires observation and follow-up of the test process..

Bytes ---------------------------------------------------------------------------------------------------------------------

I feel that this method is simple, simple, easy to remember, and easy to share in the team (members of the team can read or share this important note, quickly clarify and remember the system overview and requirements ). I wonder if it is helpful to you?