The goal is to capture user needs and define product requirements through surveys and analysis, including: demand acquisition, demand analysis, and requirements definition. The goal is to establish a common understanding of the product between the user and the project team.

1. Demand acquisition The purpose of demand acquisition is to obtain the user's demand information through various channels, and output the "Product Requirements Specification" in combination with its own development environment. Sources of demand, access technologies include but are not limited to: industry standards; product specifications, technical specifications, brochures, etc. of competitors; user interviews and user surveys; may be organized, implemented, and fed back to the R&D department by the product group of the company's marketing department.

2. Demand Analysis After completing the analysis and sorting of the required data, the project manager organizes the demand analysis of the product. Establish relationships between requirements and clearly define the requirements assigned to the product (including embedded software, hardware, and structure).

3. Change in requirements Regardless of how clear the initial needs analysis is, changes in demand during the development process are inevitable.

4. Demand Tracking The purpose of demand tracking is to ensure that every requirement is realized during the product development process, and that other work products of the project are consistent with the requirements.