Management method for decomposing, distributing, tracking and verifying demand data in product research and development process

Abstract

The invention relates to the technical field of product demand data management, and discloses a management method for decomposition, distribution, tracking and verification of demand data in a product research and development process, and the method comprises the steps: for a marketing stage, collecting user demands, and carrying out the refining of the user demands to form demand index data; for the argumentation stage, constructing a product structure, designing product demand directories according to the product structure, and refining demand index data on each product demand directory; establishing association between the demand index data and the product research and development plan, and issuing the product research and development plan and the associated demand index data to a corresponding task principal; the task manager generates a design result according to the design task of the product research and development plan, analyzes and tests the design result, and obtains analysis result data; feeding back demand index data in the design task; and all feedback data are summarized, and the feedback data and the demand index data are compared and analyzed, so that the demand and the research and development process are effectively connected.

Description

Technical Field

[0001] The present invention relates to the technical field of product requirement data management, and specifically provides a management method for decomposing, distributing, tracking, and verifying requirement data during the product R & D process. Background Art

[0002] During the product R & D process, requirement design plays a crucial role, directly determining the product's functions, market adaptability, and R & D efficiency. Clear requirement design can ensure a clear product development goal and reduce rework and resource waste caused by unclear requirements. By combining user requirements in the marketing stage and product requirements in the demonstration stage, it can be ensured that the product meets both market demands and technical feasibility.

[0003] In the traditional R & D process, during the demonstration stage, product requirements are mainly analyzed in depth, and based on this, a product R & D task book or subsystem R & D task book is formulated. These task books are issued together when the R & D work starts. However, the requirement indicators included in the task books are often not fully refined, and designers may not be able to comprehensively capture all requirement indicators when interpreting them. As the design and R & D progress, due to the influence of various complex factors, there may be varying degrees of deviation between the design indicators and requirement indicators at each stage of the product. Especially after the product is finalized, the deviation between the test and verification indicators and the initial requirement indicators may be quite significant, which not only increases the R & D cost but also correspondingly extends the product R & D cycle.

[0004] The present invention proposes a management method for decomposing, distributing, tracking, and verifying requirement data during the product R & D process to solve the problems mentioned in the above background art. Summary of the Invention

[0005] The present invention provides a management method for decomposing, distributing, tracking, and verifying requirement data during the product R & D process, which helps to solve the problems mentioned in the above background art.

[0006] In a first aspect, the present application provides a management method for decomposing, distributing, tracking, and verifying requirement data during the product R & D process, adopting the following technical solution: A management method for decomposing, distributing, tracking, and verifying requirement data during the product R & D process includes: S1. Formulate requirement data in the requirement design stage; The requirement data respectively comes from user requirements in the marketing stage and product requirements in the demonstration stage; For the marketing stage: For the collected user requirements, refine the user requirements to form requirement index data; S2. For the demonstration stage, design product requirements: Build the product structure, design the product requirement catalog according to the product structure, and refine the requirement index data for each product requirement catalog; S3. Start the product R & D project and formulate the product R & D plan using the project template; S4. Establish the association between the requirement index data and the product R & D plan, and issue the product R & D plan and the associated requirement index data to the corresponding task responsible person; S5. The task responsible person receives the product R & D plan, generates design results according to the design tasks in the product R & D plan, analyzes and tests the design results, and obtains the analysis result data; S6. According to the analysis result data, give feedback on the requirement index data in the design tasks; S7. Review the feedback data submitted by the task responsible person, summarize all the feedback data, and conduct a comparative analysis of the feedback data and the requirement index data.

[0007] By formulating requirement data in the requirement design stage, it can ensure that the product development has a clear direction and the requirement sources are clearly traceable. The combination of user requirements in the marketing stage and product requirements in the demonstration stage ensures the balance of the product in terms of market competitiveness and technical feasibility. Refining user requirements and forming specific requirement index data makes the requirements more standardized and structured, which helps with subsequent design and implementation. The construction of the product structure and the design of the product requirement catalog make requirement management more systematic, avoiding the out-of-control or omission of requirements during the R & D process. Establishing the association between the requirement index data and the product R & D plan makes the R & D process closely centered around the requirements, improving the accuracy of the final product implementation effect. After receiving the product R & D plan, the task responsible person completes the design tasks according to the specific requirements and forms design results through analysis and testing to ensure that the product meets the expected requirements. Finally, through the feedback on the design results, a complete closed-loop management system is formed, enabling the effective docking of requirements and the R & D process, reducing rework caused by requirement changes or misunderstandings, and thus improving the R & D efficiency.

[0008] Preferably, for the collected user requirements, refining the user requirements to form requirement index data includes: Obtain the product marketing plan uploaded by the user; According to the product marketing plan, analyze and demonstrate the product functions; Extract the product full-feature index data from the marketing plan book according to the document structure or keywords; Structurally process the product full-feature index data to build the product marketing requirement database; The construction of the product structure, designing the product requirement catalog according to the product structure, and refining the requirement index data for each product requirement catalog include: Construct a product requirement information framework, which includes requirement name, task responsible person, review plan time, business opportunity information, and associated marketing plan; Pull the user requirements of the product marketing plan from the product marketing requirement database according to the business opportunity information as the original product requirements; in the constructed product requirement information framework, associate the user requirements of the product marketing plan, and the associated information includes requirement name, priority, type, specification, etc.; Construct a product structure and generate a product requirement catalog according to the product structure; Set the requirement index data of each component of the product on the product requirement catalog according to the product full-feature index data extracted from the marketing plan book, and the attributes of each component are consistent with the user requirements; The project requirements are composed of product requirements and user requirements; Construct a tracking matrix for product requirements and user requirements to obtain a project requirement matrix, which is used for requirement impact analysis when project requirements change; Release product requirements.

[0009] By obtaining the product marketing plan uploaded by users, it can ensure that product development conforms to market trends and improve the market competitiveness of products. Analyzing and demonstrating product functions based on the marketing plan can accurately position the core value of the product and make the R & D process more focused. The extraction and structured processing of key index data make requirement data more standardized and traceable, facilitating subsequent management and optimization. The construction of the product structure and the formulation of the requirement catalog make requirement management hierarchical, ensuring that the requirements of each link are clearly expressed and correctly implemented. The construction of the product requirement information framework, including key information such as requirement name, task responsible person, review plan time, etc., makes requirement management more orderly and improves the efficiency of information flow. Extracting user requirements from the product marketing requirement database based on business opportunity information ensures the close matching of product development with market demand. By constructing a requirement tracking matrix, it is possible to monitor the impact of requirement changes on the entire project in real time and provide a basis for project adjustment and optimization. Finally, by releasing product requirements, it ensures that all relevant parties reach a consensus on the requirements and lays a solid foundation for subsequent development work.

[0010] Preferably, start the product R & D project and use the project template to formulate the product R & D plan, including: Enter the basic information of the project, associate the product requirement information with the project, and complete the approval process for project establishment; Use the task template and plan template in the project template to formulate the product development plan; According to the data template in the project template, formulate the names of the input data and output data required during the execution of each design task of the product R & D plan; The input data and output data are used to obtain the design results of the upstream design task; Call quality procedure documents and checklists to plan quality information for product development plans; Retrieve reference knowledge from the enterprise knowledge base and bind the reference knowledge to the product development plan; The bound reference knowledge will be displayed in context when the task leader performs the design task.

[0011] By entering basic project information and associating product demand information with the project, we can ensure the close integration of demand management and project management and improve overall management efficiency. Use standardized project templates to develop product development plans, making project planning more scientific and reasonable, and reducing arbitrariness and uncertainty in management. The use of data templates clearly defines the input data and output data required for the execution of design tasks in product development plans, which helps to ensure the traceability and consistency of design work. The management of input data and output data enables the results of upstream design tasks to be efficiently transferred to downstream tasks, ensuring the smooth connection of the R&D process. Call quality procedure documents and checklists to formulate clear quality control requirements for product development plans and improve the reliability and stability of the product development process. The retrieval of the enterprise knowledge base and the binding of reference knowledge enable task leaders to draw on existing experience when performing design tasks, improve work efficiency and reduce duplication of work.

[0012] Preferably, the establishing of association between demand indicator data and product development plan, and issuing the product development plan and the associated demand indicator data to the corresponding task leader, includes: Bind the demand indicator data to the product R&D plan. One product demand indicator data is associated with multiple R&D plans. The specific steps are as follows: Demand indicator allocation: Let M be the set of product marketing plans, each marketing plan is represented by x i ; Let R be the set of project requirements, and each requirement item is represented by r i ; but R i For user needs extracted from product marketing plans; Each requirement item r j By multiple demand item indicators I i Composition, I i ={i j1 ,i j2 ,…,i jm}, where i jk Demand item r j The kth demand indicator in ; To bind requirements to a project: Let \(P\) be the set of projects, and each project is represented as \(p\). k , then the mapping relationship from requirement items to projects can be defined as \(\varPhi: R\rightarrow P\); that is, each requirement item \(r\) j is mapped to a specific project \(p\). k : Let \(T\) be the set of tasks, and each task is represented as \(t\). l , and each task is refined and decomposed by the project \(p\). k : \(T\) k = \(g(p\) k ) = \{t\) k1 , \(t\) k2 , \(\cdots\), \(t\) km \}, where \(g(p\) k ) represents the set of tasks generated by the project \(p\). k ; The set of project items that the task \(t\) l needs to satisfy is: \(R\) l = \{r\) l1 , \(r\) l2 , \(\cdots\), \(r\) ln \}; Then the mapping relationship from tasks to requirements can be expressed as \(\varPsi: T\rightarrow R\). Update the status function \(S(t\) l ): \(S(t\) l ) \(\in\) \{not started, in progress, completed\}; Requirement feedback and closed loop: After the task is completed, feedback data \(F\) is generated. l , and stored in the requirement feedback set \(F\). Any \(F\) l = (\(T\) status , \(T\) resList , \(T\) resTime ), where \(T\) status , \(T\) resList , \(T\) resTime are the current status of the task, the remaining unfinished list of the task, and the remaining time of the task respectively. Among them, the final status of the requirement item is determined by the status of its related tasks \(S(r\) j ) = \(\min(S(t\) j1 ), \(S(t\) j2 ), \(\cdots\), \(S(t\) jn ))), which means that the requirement status \(S(r\) j ) depends on the minimum status of all its related tasks, ensuring that the requirement item is marked as completed only after all tasks are completed; Check whether all the requirement index data has been allocated, compile information such as the person in charge of the product R & D plan task and the quality reviewer; issue the product R & D plan.

[0013] By binding the requirement indicator data to the product R & D plan, systematic management of requirements is ensured, avoiding the loss or deviation of requirements from the original goals during the R & D process. The allocation of requirement indicator data enables effective management of requirements at different levels, ensuring that each requirement item can be accurately mapped to the corresponding R & D plan. The definition of the mapping relationship from requirements to projects makes the requirement implementation process more transparent and improves the controllability of requirement management. The definition of the task set and the mapping from tasks to requirements establish a clear corresponding relationship between tasks and requirements, ensuring that R & D tasks are closely centered around requirements. The update function of requirement status enables real-time tracking of the completion status of requirements and improves the transparency of project management. The establishment of the requirement feedback and closed-loop mechanism ensures that the execution status of all tasks can be timely feedback, preventing task deviation caused by requirement changes. Finally, by checking whether all the requirement indicator data have been allocated and compiling the information of relevant responsible persons, the execution of the product R & D plan is made more efficient, ensuring that the R & D work is centered around requirements.

[0014] Preferably, the task responsible person receives the product R & D plan, generates design results according to the design tasks in the product R & D plan, analyzes and tests the design results, and obtains analysis result data, including: The task responsible person executes the design task according to the requirement indicator data, input data and reference knowledge, and generates design results; Analyze and test the design results, and extract the analysis result data; When the project requirements change, according to the requirement distribution record, conduct requirement impact analysis and remind the requirement impact stakeholders. The specific steps are as follows: Set the requirement-task association matrix Where, A ij = 0, it is determined that requirement r j and task t i are irrelevant, A ij = 1, it is determined that requirement r j and task t i are relevant; Set the task responsible person set Q, Q = {q1, q2,..., q v}, when task t i is responsible by task responsible person q k , define the mapping relationship: Φ: T → P, Φ(t i ) = p k ; When the project requirement r j changes, define the change vector: ΔR = [δ1, δ2,..., δ n T , where, δ j = 1 indicates that r j has changed; ​Then the set of affected tasks ΔT = A × ΔR, where (ΔT) i = 1, then task t i is affected; The set of task owners corresponding to the affected tasks is ΔQ = {Φ(t i ) | Δ(T) i = 1}; The notification method for notifying the task owners is: Task change notification: where Γ is the notification function; Requirement change cascade analysis: If task t i affects other tasks t l as input data, then the change needs to be further propagated: t l = g(t i ), t l ∈ T, where g(t i ) represents the downstream task of task t i , and continue to analyze t l to ensure that all impacts are propagated to all tasks; Calculate the change propagation depth d: d = max(path(ΔT)), where path is the path length; Set the change propagation depth threshold d max ; If d > d max , then notify the management of the change anomaly.

[0015] By having the task owners execute the design tasks according to the requirement index data, input data, and reference knowledge, it can ensure that the R & D work is carried out based on accurate information and improve the accuracy of task execution. The analysis and testing of the design results scientifically verify the design results and ensure that they meet the product requirements. Through the requirement impact analysis, when the project requirements change, it can timely identify the affected tasks and relevant stakeholders, reducing the negative impacts brought by the change. The setting of the requirement - task association matrix clarifies the relationship between tasks and requirements, improving the efficiency of requirement change management. The definition of the set of task owners makes the execution responsibility of each task clear, ensuring that relevant personnel can be quickly notified during changes. The establishment of the task change notification mechanism enables the efficient transmission of requirement change information, reducing communication costs. The calculation of the change propagation depth quantifies the impact of requirement changes, and by setting the change propagation depth threshold, it avoids abnormal changes from affecting the entire R & D process and improves the stability of project management.

[0016] Preferably, review the feedback data submitted by the task owners, summarize all the feedback data, and conduct a comparative analysis of the feedback data with the requirement index data, including: After the task is completed, for any task t j, obtain the feedback result F j of task t j ; Set the deviation threshold ε of the feedback result k ; Calculate the feedback deviation ΔR k = |R k - F j,k |, and compare ΔR k with ε k ; If ΔR k > ε k , then return task t j , and re - execute the design task; When multiple tasks t1, t2,..., t m give feedback on the same requirement index R k , then conduct weighted integration through the project leader: Among them, w j is the weight of task t j , satisfying the normalization condition Analyze the feedback results of the requirement index R to measure the impact on the system S: Assume the total number of requirements is y, then the implementation situation of each requirement index p j in the subsystem S j is calculated as follows: Among them, e i,j represents the weight of requirement R i in the subsystem S j , and pS j represents the completion degree of requirement R i in the subsystem; Integrate the requirement implementation situations of all subsystems: represents the calculation of the weight of the comprehensive feedback of all tasks in the entire product system.

[0017] Through the feedback mechanism after task completion, ensure that the execution results of each task are effectively evaluated, and avoid the incorrect implementation of requirements caused by task execution deviations. The deviation calculation of the feedback results scientifically evaluates the execution quality of tasks and improves the transparency of the R & D process. When the feedback result of a task exceeds the deviation threshold, the task will be returned for re - execution to ensure that the design results meet the requirement specifications. The feedback results of multiple tasks are weighted and integrated to make the final feedback data more objective and improve the accuracy of the feedback results. The analysis of the feedback results of requirement indicators effectively measures the actual implementation of requirements and ensures that the product functions meet expectations. By calculating the implementation of requirement indicators in subsystems, the various parts of the product can be evaluated in fine - grained manner, improving the system optimization ability. Finally, by integrating the feedback of all tasks, ensure that the overall requirement implementation of the product system reaches the best state, improving the quality and stability of the product.

[0018] Preferably, the feedback data submitted by the person in charge of the review task are aggregated, and all the feedback data are compared and analyzed with the requirement indicator data, including: Set the requirement - task association matrix V to represent the relationship between tasks and requirements: Among them, v ij = 1 indicates that task t j affects requirement R j , v ij = 0 indicates that task t j does not affect requirement R j ; Calculate the requirement impact: Among them, I j represents the impact degree of requirement R j ; Set the requirement impact threshold I0. If I j > I0, then notify the stakeholders for adjustment; compare the current project's requirement implementation situation p now with the similar projects p history in the historical prototype database, and apply linear regression analysis: p' = α×p history +β, where p' is the predicted current requirement implementation situation, and α, β are linear regression analysis parameters, fitted by the least - squares method; If |p now - p'| > χ, then adjust the requirement implementation strategy, where χ is the set difference threshold.

[0019] By setting up the requirement-task association matrix, the impact relationship between tasks and requirements is clearly represented, enhancing the systematicness and transparency of requirement management. The calculation of requirement impact enables the impact of requirement changes on the project to be quantified, providing a scientific basis for adjustment. The setting of requirement impact thresholds makes requirement management more precise, ensuring that only the requirements truly in need of adjustment trigger change notifications and reducing the impact of ineffective changes. By comparing the requirement fulfillment status of the current project with historical data, the existing experience can be utilized to optimize product development and improve R & D efficiency. The application of linear regression analysis makes the prediction of requirement fulfillment more scientific, ensuring the correct direction of product R & D. The calculation of the least squares method fitting parameters makes the requirement prediction model more accurate and improves the intelligent level of requirement management. Finally, by setting the deviation threshold for requirement fulfillment, it is ensured that the actual fulfillment of requirements always meets expectations, and timely adjustments are made when the deviation exceeds the threshold, achieving efficient closed-loop requirement management.

[0020] The present invention has the following beneficial effects: 1. The management method for the decomposition, distribution, tracking, and verification of requirement data during the product R & D process can ensure a clear direction for product R & D by formulating requirement data in the requirement design stage, making the requirement sources clearly traceable. By combining the user requirements in the marketing stage with the product requirements in the demonstration stage, it can ensure a balance between market competitiveness and technical feasibility of the product. By refining user requirements and forming specific requirement index data, the requirements can be made more standardized and structured, facilitating subsequent management and implementation. By constructing the product structure and designing the product requirement catalog, it can ensure clear levels in requirement management, with clear requirement expressions at each link and effective implementation. By establishing the association between requirement index data and the product R & D plan, it can ensure that the R & D process closely revolves around requirements, improving the matching degree of the final product to requirements. By having the task responsible person receive the product R & D plan and complete the design tasks based on specific requirements, it can ensure the accuracy of R & D work. By analyzing and testing the design results, it can ensure that the product meets the requirement expectations. Through the feedback on the design results, a complete closed-loop management system can be formed, enabling effective docking between requirements and the R & D process, thereby reducing rework caused by requirement changes or misunderstandings and improving R & D efficiency.

[0021] 2. The management method for decomposing, distributing, tracking, and verifying requirement data during the product R & D process can ensure that product development meets market demands and enhances the product's market competitiveness by obtaining the product marketing plan uploaded by users. By analyzing and demonstrating product functions based on the marketing plan, it can ensure that the product function design meets user requirements. By extracting key indicator data from the marketing plan and performing structured processing, it can ensure the standardization of requirement data and improve traceability. By constructing the product structure and formulating the product requirement catalog, it can ensure clear and orderly requirement management and avoid requirement omission. By establishing the product requirement information framework, it can ensure the clarity of key information such as requirement names, task responsible persons, and review plan times, and improve the efficiency of requirement management. By extracting user requirements from the product marketing requirement database based on business opportunity information, it can ensure that product development is closely centered around market demands. By constructing the requirement tracking matrix, it can ensure effective impact analysis during requirement changes and improve project controllability. By releasing product requirements, it can ensure that all relevant parties reach a consensus on the requirements and lay a solid foundation for subsequent development work.

[0022] 3. The management method for decomposing, distributing, tracking, and verifying requirement data during the product R & D process can ensure the close integration of requirement management and project management and improve overall management efficiency by entering basic project information and associating product requirement information with the project. By formulating the product development plan using a standardized project template, it can ensure more scientific and reasonable project planning and reduce arbitrariness and uncertainty in management. By using the data template, it can ensure the clear definition of input and output data required during the execution of design tasks in the product R & D plan, and improve the traceability and consistency of design work. By managing input and output data, it can ensure the efficient transfer of the results of upstream design tasks to downstream tasks and improve the smoothness of the R & D process. By invoking quality procedure documents and checklists, it can ensure clear quality control requirements for the product R & D plan and improve the reliability and stability of the product development process. By retrieving the enterprise knowledge base and binding reference knowledge, it can ensure that task responsible persons draw on existing experience when performing design tasks, improve work efficiency, and reduce repetitive labor.

[0023] 4. The management method for the decomposition, distribution, tracking, and verification of the requirement data during the product R & D process can ensure the systematization of requirement management and avoid the loss or deviation of requirements from the original goals by binding the requirement index data to the product R & D plan. Through the allocation of requirement index data, it can ensure the effective management of requirements at different levels and guarantee that each requirement item can be accurately mapped to the corresponding R & D plan. By defining the mapping relationship from requirements to projects, it can ensure the transparency of the requirement implementation process and improve the controllability of requirement management. By defining the task set and the mapping relationship from tasks to requirements, it can ensure a clear correspondence between tasks and requirements and improve the execution efficiency of R & D tasks. By updating the requirement status, it can ensure the real-time traceability of the requirement completion situation and improve the transparency of project management. By establishing a requirement feedback and closed-loop mechanism, it can ensure the timely feedback of the task execution situation and prevent task deviation caused by requirement changes. By checking whether all the requirement index data has been allocated and compiling the information of relevant responsible persons, it can ensure the efficient execution of the product R & D plan and ensure that the R & D work is carried out around the requirements.

[0024] 5. The management method for the decomposition, distribution, tracking, and verification of the requirement data during the product R & D process can ensure that the R & D work is carried out based on accurate information and improve the accuracy of task execution by having the task responsible person execute the design task according to the requirement index data, input data, and reference knowledge. By analyzing and testing the design results, it can ensure that the design results meet the product requirements. Through requirement impact analysis, it can ensure the timely identification of affected tasks and relevant stakeholders when project requirements change and reduce the negative impact brought by the change. By setting up a requirement-task association matrix, it can ensure a clear relationship between tasks and requirements and improve the efficiency of requirement change management. By defining the set of task responsible persons, it can ensure a clear execution responsibility for each task and improve the processing speed of requirement changes. By establishing a task change notification mechanism, it can ensure the efficient transmission of requirement change information and reduce the communication cost. By calculating the change propagation depth, it can ensure that the impact scope of requirement changes is quantified, and by setting a change propagation depth threshold, it can ensure that requirement changes will not abnormally affect the entire R & D process and improve the stability of project management.

[0025] 6. The management method for decomposing, distributing, tracking, and verifying the requirement data during the product R & D process can ensure the effective evaluation of the task execution results through the feedback mechanism after task completion, avoiding the incorrect implementation of requirements due to task execution deviation. By calculating the deviation of the feedback results, the execution quality of tasks can be scientifically measured, and the transparency of the R & D process can be improved. By setting the feedback deviation threshold, timely adjustment can be ensured when the task execution exceeds the reasonable range, improving the accuracy of product development. By weighted integration of the feedback results of multiple tasks, the final feedback data can be made more objective, improving the accuracy of the feedback results. By analyzing the feedback results of requirement indicators, the actual implementation of requirements can be scientifically measured, improving the system optimization ability. By calculating the implementation of requirement indicators in subsystems, the implementation of each part of the product can be evaluated in fine granularity, improving the overall quality of the product. By integrating the feedback of all tasks, the requirement implementation of the product system can be ensured to reach the best state, improving the stability of the product.

[0026] 7. The management method for decomposing, distributing, tracking, and verifying the requirement data during the product R & D process can ensure the clear influence relationship between tasks and requirements by setting the requirement task association matrix, improving the systematicness and transparency of requirement management. By calculating the requirement impact, the impact of requirement changes on the project can be quantified, improving the scientificity of requirement adjustment. By setting the requirement impact threshold, more precise requirement change management can be ensured, reducing the interference of invalid changes. By comparing the requirement implementation of the current project with historical data, the optimization of product development using existing experience can be ensured, improving the R & D efficiency. By applying linear regression analysis, more scientific prediction of requirement implementation can be ensured, improving the intelligent level of requirement management. By calculating the least squares fitting parameters, the requirement prediction model can be made more precise, improving the reliability of requirement management. By setting the deviation threshold of requirement implementation, it can be ensured that the actual implementation of requirements always meets the expectations and timely adjustment can be made when the deviation exceeds the threshold, improving the closed-loop control ability of requirement management. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 It is a schematic diagram of the method flow of the present invention.

[0028] Figure 2 It is a schematic diagram of the itemized decomposition structure of the product requirement indicators of the present invention.

[0029] Figure 3 It is a schematic diagram of the requirement association design structure of the present invention.

[0030] Figure 4 It is a schematic diagram of the database design structure of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0031] The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0032] Embodiment 1. Refer to Figure 1 , a management method for decomposing, distributing, tracking, and verifying requirement data during the product R & D process, including: S1. Formulate requirement data in the requirement design stage; The requirement data are respectively derived from the user requirements in the marketing stage and the product requirements in the demonstration stage; For the marketing stage: For the collected user requirements, refine the user requirements to form requirement index data; S2. For the demonstration stage, design product requirements: Construct a product structure, design a product requirement catalog according to the product structure, and refine the requirement index data on each product requirement catalog; S3. Start a product R & D project and formulate a product R & D plan using a project template; S4. Establish the association between the requirement index data and the product R & D plan, and issue the product R & D plan and the associated requirement index data to the corresponding task responsible person; S5. The task responsible person receives the product R & D plan, generates a design result according to the design task of the product R & D plan, analyzes and tests the design result to obtain analysis result data; S6. According to the analysis result data, give feedback on the requirement index data in the design task; S7. Review the feedback data submitted by the task responsible person, summarize all the feedback data, and conduct a comparative analysis of the feedback data and the requirement index data.

[0033] By formulating requirement data in the requirement design phase, it is possible to ensure that product R & D is carried out based on clear requirements, improving the accuracy of product development. By combining user requirements in the marketing phase and product requirements in the demonstration phase, it is possible to ensure a balance between market adaptability and technical feasibility of the product. By refining user requirements and forming requirement index data, it is possible to ensure that requirements are expressed specifically and clearly, improving the executability. By constructing a product structure and designing a product requirement catalog, it is possible to make requirement management hierarchical, contributing to the smooth progress of subsequent R & D work. By establishing the association between requirement index data and the product R & D plan, it is possible to ensure that R & D tasks are consistent with requirements, reducing deviations. By having the task responsible person receive the product R & D plan and complete the design work according to the task requirements, it is possible to ensure the efficient execution of R & D work. By analyzing and testing the design results, it is possible to ensure that the product quality meets the expected standards. By providing feedback on the design results, it is possible to form a complete closed-loop management system, ensuring that problems in the product development process can be discovered and solved in a timely manner, improving R & D efficiency.

[0034] For the collected user requirements, refining the user requirements to form requirement index data includes: Obtain the product marketing plan uploaded by users; According to the product marketing plan, analyze and demonstrate product functions; Extract the product full-feature index data in the marketing plan book according to the document structure or keywords; Structurally process the product full-feature index data to construct a product marketing requirement database; In this embodiment, refer to Figure 2 .

[0035] For the construction of the product structure, design a product requirement catalog according to the product structure, and refine the requirement index data on each product requirement catalog, including: Construct a product requirement information framework, where the product requirement information framework includes requirement name, task responsible person, review plan time, business opportunity information, and associated marketing plan; According to the business opportunity information, retrieve the user requirements of the product marketing plan in the product marketing requirement database as the original product requirements; in the constructed product requirement information framework, associate the user requirements of the product marketing plan, and the associated information includes requirement name, priority, type, specification, etc.; Construct a product structure and generate a product requirement catalog according to the product structure; According to the extracted product full-feature index data in the marketing plan book, set the requirement index data for each component of the product on the product requirement catalog, and the attributes of each component are consistent with the user requirements; The project requirements are composed of product requirements and user requirements; Construct a tracking matrix for product requirements and user requirements to obtain a project requirements matrix, which is used for requirement impact analysis when project requirements change; Release product requirements.

[0036] By obtaining the product marketing plan uploaded by users, it is possible to ensure that product development meets market needs and improve the market competitiveness of the product. By analyzing and demonstrating product functions based on the marketing plan, the rationality of product functions can be ensured. By extracting key indicator data from the marketing plan and performing structured processing, it is possible to ensure the standardization of requirement data and improve traceability. By constructing a product structure and formulating a product requirements catalog, it is possible to ensure orderly requirement management and avoid omissions. By establishing a product requirement information framework, it is possible to ensure that key information such as requirement names, task responsible persons, and review plan times is clear and improve management efficiency. By extracting user requirements from the product marketing requirements database based on business opportunity information, it is possible to ensure that product development is closely centered around market needs. By constructing a requirements tracking matrix, it is possible to ensure effective impact analysis when requirements change and improve project controllability. By releasing product requirements, it is possible to ensure that all relevant parties reach a consensus on the requirements and lay a solid foundation for subsequent development work.

[0037] Start the product R & D project and use the project template to formulate a product R & D plan, including: Enter the basic information of the project, associate the product requirement information with the project, and complete the approval process for project establishment; Use the task template and plan template in the project template to formulate a product development plan; According to the data template in the project template, determine the names of the input data and output data required for each design task in the product R & D plan during execution; The input data and output data are used to obtain the design results of upstream design tasks; Call the quality procedure document and checklist to plan the quality information of the product R & D plan; Retrieve reference knowledge from the enterprise knowledge base and bind the reference knowledge to the product R & D plan; The bound reference knowledge will be associated and displayed when the task responsible person executes the design task.

[0038] By entering the basic project information and associating the product requirement information with the project, it is possible to ensure the close integration of requirement management and project management, improving management efficiency. By using a standardized project template to formulate the product development plan, it is possible to ensure the scientific and reasonable project planning, reducing the arbitrariness and uncertainty in management. By using a data template, it is possible to ensure that the input and output data required in the execution of the design tasks in the product R & D plan are clearly defined, improving the traceability of the design work. By managing the input data and output data, it is possible to ensure the efficient transfer of the results of the upstream design tasks to the downstream tasks, improving the smoothness of the R & D process. By invoking the quality procedure documents and checklists, it is possible to ensure the clear quality control requirements of the product R & D plan, improving the reliability of product development. By retrieving the enterprise knowledge base and binding reference knowledge, it is possible to ensure that the task responsible person can draw on existing experience when executing the design task, improving work efficiency and reducing repetitive labor.

[0039] The establishment of the association between the requirement index data and the product R & D plan, and the issuance of the product R & D plan and the associated requirement index data to the corresponding task responsible person, includes: Binding the requirement index data to the product R & D plan, where one product requirement index data is associated with multiple R & D plans. The specific steps are as follows: Requirement index allocation: Set M as the set of product marketing plans, and each marketing plan is represented as x i ; Set R as the set of project requirements, and each requirement item is represented as r i ; Then R i is the user requirement extracted from the product marketing plan; Each requirement item r j is composed of multiple requirement item indicators I i , I i ={i j1 , i j2 ,…, i jm}, where i jk represents the kth requirement index in the requirement item r j ; Binding the requirement to the project: Set P as the set of projects, and each project is represented as p k , then the mapping relationship from the requirement item to the project can be defined as Φ:R→P; that is, each requirement item r j is mapped to a specific project p k : Set the task set T, and each task is represented as t l , and each task is refined and decomposed by the project p k : T k = g(p k ) = {t k1 , t k2 , …, t km}, where g(p k ) represents the set of tasks generated by item p k ; The set of item sets that task t l needs to satisfy is: R l = {r l1 , r l2 , …, r ln}; Then the mapping relationship from task to requirement can be expressed as Ψ: T → R, Update status function S(t l ) : S(t l ) ∈ {Not started, In progress, Completed}; Requirement feedback and closed loop: After the task is completed, feedback data F l is generated and stored in the requirement feedback set F; Any F l = (T status , T resList , T resTime ), where T status , T resList , T resTime are the current state of the task, the remaining uncompleted list of the task, and the remaining time of the task respectively. Among them, the final state of the requirement item is determined by its related task states S(r j ) = min(S(t j1 ), S(t j2 ), …, S(t jn ))), indicating that the requirement state S(r j ) depends on the minimum state of all its related tasks, ensuring that the requirement item is marked as completed only after all tasks are completed; Check whether all the requirement index data has been allocated, compile information such as the person in charge of the product R & D plan and the quality reviewer; issue the product R & D plan.

[0040] In this embodiment, refer to Figure 2 and Figure 3 .

[0041] By binding the requirement indicator data to the product R & D plan, it is possible to ensure the systematic management of requirements, avoiding the loss or deviation of requirements during the R & D process. Through the allocation of requirement indicator data, it is possible to ensure the effective management of requirements at different levels, ensuring that each requirement item is accurately mapped to the corresponding R & D plan. By defining the mapping relationship from requirements to projects, it is possible to ensure the transparency of the requirement implementation process and improve the controllability of requirement management. By defining the task set and the mapping relationship from tasks to requirements, it is possible to ensure a clear correspondence between tasks and requirements and improve the execution efficiency of R & D tasks. By updating the requirement status, it is possible to ensure that the completion status of requirements is traceable in real time and improve the transparency of project management. By establishing a requirement feedback and closed-loop mechanism, it is possible to ensure that the task execution status is promptly feedback and prevent task deviation caused by requirement changes. By checking whether all the requirement indicator data has been allocated and compiling the information of relevant responsible persons, it is possible to ensure the efficient execution of the product R & D plan and ensure that the R & D work is carried out around the requirements.

[0042] The task responsible person receives the product R & D plan, generates design results based on the design tasks in the product R & D plan, analyzes and tests the design results, and obtains analysis result data, including: The task responsible person executes the design task according to the requirement indicator data, input data, and reference knowledge, and generates design results; Analyze and test the design results, and extract the analysis result data; When the project requirements change, according to the requirement distribution record, conduct a requirement impact analysis and remind the requirement impact stakeholders. The specific steps are as follows: Set up a requirement-task association matrix Among them, A ij = 0, it is determined that the requirement r j and the task t i are irrelevant, A ij = 1, it is determined that the requirement r j and the task t i are relevant; Set up a set of task responsible persons Q, Q = {q1, q2,..., q v}, when the task t i is responsible by the task responsible person q k , define the mapping relationship: Φ: T → P, Φ(t i ) = p k ; When the project requirement r j changes, define the change vector: ΔR = [δ1, δ2,..., δ n T , where, δ j = 1 indicates that r j has changed; ​The set of affected tasks ΔT = A × ΔR, where (ΔT) i = 1, then task t i is affected; The set of task owners corresponding to the affected tasks is ΔQ = {Φ(t i )|Δ(T) i = 1}; The notification method for notifying task owners is: Task change notification: where Γ is the notification function; Requirement change cascade analysis: If task t i affects other tasks t l as input data, then the change needs to be further propagated: t l = g(t i ), t l ∈ T, where g(t i ) represents the downstream tasks of task t i , and continue to analyze t l to ensure that all impacts are propagated to all tasks; Calculate the change propagation depth d: d = max(path(ΔT)), where path is the path length; Set the change propagation depth threshold d max ; If d > d max , then notify the management of the change anomaly.

[0043] By having the task owners execute the design tasks based on the requirement index data, input data, and reference knowledge, it can ensure that the R & D work is carried out based on accurate information and improve the accuracy of task execution. By analyzing and testing the design results, it can ensure that the design results meet the product requirements. By conducting requirement impact analysis, it can ensure that when project requirements change, the affected tasks and relevant stakeholders can be identified in a timely manner, reducing the negative impacts brought by the change. By setting the requirement-task association matrix, it can ensure that the relationship between tasks and requirements is clear and improve the efficiency of requirement change management. By defining the set of task owners, it can ensure that the execution responsibility of each task is clear and improve the processing speed of requirement changes. By establishing a task change notification mechanism, it can ensure the efficient transmission of requirement change information and reduce communication costs. By calculating the change propagation depth, it can ensure that the impact scope of requirement changes is quantified, and by setting the change propagation depth threshold, it can ensure that requirement changes will not abnormally affect the entire R & D process and improve the stability of project management.

[0044] Review the feedback data submitted by the task owners, summarize all the feedback data, and conduct a comparative analysis of the feedback data with the requirement index data, including: When the task is completed, for any task t j, obtain the feedback result F of task t j ; j Set the deviation threshold ε of the feedback result ; k Calculate the feedback deviation ΔR = |R k -F k |, and compare ΔR j,k with ε k ; k If ΔR > ε k , then return task t k , and re - execute the design task; j When multiple tasks t1, t2,..., t give feedback on the same requirement index R m , then weighted integration is carried out by the project leader: k Among them, w is the weight of task t j , satisfying the normalization condition j Analyze the feedback results of the requirement index R to measure the impact on the system S: Suppose the total number of requirements is y, then the implementation situation of each requirement index p in the subsystem S j is calculated as follows: j Among them, e represents the weight of requirement R i,j in the subsystem S i , p j represents the completion degree of requirement R Sj in the subsystem; i Integrate the requirement implementation situations of all subsystems: represents the calculation of the weight of the comprehensive feedback of all tasks in the entire product system.

[0045] ​Through the feedback mechanism after task completion, it is possible to ensure that the task execution results are effectively evaluated, avoiding the inability to correctly implement requirements due to task execution deviations. By calculating the deviation of the feedback results, it is possible to ensure that the execution quality of the tasks is scientifically measured, improving the transparency of the R & D process. By setting a feedback deviation threshold, it is possible to ensure timely adjustment when the task execution exceeds the reasonable range, improving the accuracy of product development. By weighted integration of the feedback results of multiple tasks, it is possible to ensure that the final feedback data is more objective, improving the accuracy of the feedback results. By analyzing the feedback results of the requirement indicators, it is possible to ensure that the actual implementation of the requirements is scientifically measured, improving the system optimization ability. By calculating the implementation of the requirement indicators in the subsystems, it is possible to ensure a fine-grained evaluation of the implementation of each part of the product, improving the overall quality of the product. By integrating the feedback of all tasks, it is possible to ensure that the requirement implementation of the product system reaches the best state, improving the stability of the product.

[0046] The feedback data submitted by the person in charge of the review task is summarized, and all the feedback data is compared and analyzed with the requirement indicator data, including: Set the requirement task association matrix V to represent the relationship between tasks and requirements: where, v ij = 1 indicates that task t j affects requirement R j , v ij = 0 indicates that task t j does not affect requirement R j ; Calculate the requirement impact: where, I j represents the impact degree of requirement R j ; Set the required impact threshold I0. If I j > I0, then notify the stakeholders to make adjustments; compare the requirement implementation situation p now of the current project with the similar project p history in the historical prototype database, and apply linear regression analysis: p' = α × p history + β, where, p' is the predicted current requirement implementation situation, and α, β are the linear regression analysis parameters, which are fitted by the least squares method; If |p now - p'| > χ, then adjust the requirement implementation steps, where, χ is the set difference threshold.

[0047] By setting up the requirement-task association matrix, the impact relationship between tasks and requirements can be made clear, improving the systematicness and transparency of requirement management. By calculating the requirement impact, the impact of requirement changes on the project can be quantified, improving the scientific nature of requirement adjustment. By setting the requirement impact threshold, accurate management of requirement changes can be ensured, reducing the interference of ineffective changes. By comparing the requirement fulfillment situation of the current project with historical data, the optimization of product development using existing experience can be ensured, improving the R & D efficiency. By applying linear regression analysis, the prediction of requirement fulfillment can be made more scientific, improving the intelligence level of requirement management. By calculating the least squares fitting parameters, the requirement prediction model can be made more accurate, improving the reliability of requirement management. By setting the deviation threshold for requirement fulfillment, it can be ensured that the actual requirement fulfillment situation always meets the expectations, and timely adjustment can be made when the deviation exceeds the threshold, improving the closed-loop control ability of requirement management.

[0048] It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements not only includes those elements but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or device.

[0049] The above are only the preferred embodiments of the present invention. It should be pointed out that for those of ordinary skill in the art, without departing from the technical principle of the present invention, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present invention.

Claims

1. A management method for decomposing, distributing, tracking and verifying demand data in the product development process, characterized in that: include: S1. Formulate demand data during the demand design phase; The demand data are derived from user demand in the marketing stage and product demand in the demonstration stage; For the marketing stage: Collect user needs and refine them to form demand indicator data; S2. Design product requirements for the demonstration phase: Build product structure, design product demand catalog according to product structure, and refine demand indicator data for each product demand catalog; S3. Start a product development project and use the project template to develop a product development plan; S4. Establish the association between demand indicator data and product development plan, and issue the product development plan and the associated demand indicator data to the corresponding task leader; S5. The task leader receives the product development plan, generates design results according to the design tasks of the product development plan, analyzes and tests the design results, and obtains analysis result data; S6. Provide feedback on the demand indicator data in the design task based on the analysis result data; S7. Review the feedback data submitted by the task leader, summarize all the feedback data, and compare and analyze the feedback data with the demand indicator data.

2. The management method for decomposing, distributing, tracking and verifying demand data in the product development process according to claim 1 is characterized in that: The collected user needs are refined to form demand indicator data, including: Get product marketing plans uploaded by users; Analyze and demonstrate product functions according to product marketing plan; Extract all product feature index data in the marketing plan based on document structure or keywords; Structural processing of product full characteristic index data to build a product marketing demand database; The product structure is constructed, a product demand catalog is designed according to the product structure, and demand indicator data is refined on each product demand catalog, including: Building a product demand information framework, wherein the product demand information framework includes demand name, task leader, review plan time, business opportunity information, and associated marketing plan; Pull out the user requirements of the product marketing plan from the product marketing requirements database based on the business opportunity information as the original product requirements; associate the user requirements of the product marketing plan in the constructed product requirements information framework, and the associated information includes the requirement name, priority, type, specification, etc.; Build product structure and generate product demand catalog based on product structure; According to the product full characteristic index data extracted from the marketing plan, the demand index data of each component of the product is set in the product demand catalog, and the attributes of each component are consistent with user needs; Project requirements are composed of product requirements and user requirements; Construct a tracking matrix of product requirements and user requirements to obtain a project requirements matrix, which is used to perform demand impact analysis when project requirements change; Release product requirements.

3. The management method for decomposing, distributing, tracking and verifying demand data in the product development process according to claim 2 is characterized in that: The product development project is initiated and a product development plan is developed using a project template, including: Enter the basic information of the project, associate the product demand information with the project, and complete the approval process for project establishment; Use the task template and plan template in the project template to develop a product development plan; According to the data template in the project template, formulate the names of the input data and output data required for each design task in the product development plan during execution; The input data and output data are used to obtain the design results of the upstream design task; Call quality procedure documents and checklists to plan quality information for product development plans; Retrieve reference knowledge from the enterprise knowledge base and bind the reference knowledge to the product development plan; The bound reference knowledge will be displayed in context when the task leader performs the design task.

4. The management method for decomposing, distributing, tracking and verifying demand data in the product development process according to claim 1 is characterized in that: The establishment of the association between demand indicator data and product development plan, and the issuance of product development plan and associated demand indicator data to the corresponding task leaders, includes: Bind the demand indicator data with the product R&D plan. One product demand indicator data is associated with multiple R&D plans. The specific steps are as follows: Demand indicator allocation: Let M be the set of product marketing plans, each marketing plan is represented by x i ; Let R be the set of project requirements, and each requirement item is represented by r i ; but R i = {r i1 ,r i2 ,…,r in }, R i For user needs extracted from product marketing plans; Each requirement item r j By multiple demand item indicators I i Composition, I i ={i j1 ,i j2 ,…,i jm }, where i jk Demand item r j The kth demand indicator in ; To bind requirements to a project: Let P be the set of items, each item is denoted by p k , then the mapping relationship from demand items to projects can be defined as Φ:R→P; That is, each demand item r j times is mapped to a specific item p k : Φ(r j )=p k ; Set the task set T, each task is represented by t l , each task consists of project p k Detailed breakdown: T k =g(p k )={t k1 ,t k2 ,…,t km }, where g(p k ) indicates item p k The generated task set; Task l The set of project items that need to be satisfied is: R l = {r l1 ,r l2 ,…,r ln }; Then the mapping relationship from task to requirement can be expressed as Ψ:T→R, Ψ(t l )=R l ; Update state function S(t l ): S(t l )∈{not started, in progress, completed}; Demand feedback and closed loop: After the task is completed, feedback data F is generated l , stored in the demand feedback set F; Any F l =(T status ,T resList ,T resTime ), where T status ,T resList ,T resTime They are the current status of the task, the remaining unfinished list of the task, and the remaining time of the task. The final status of the requirement item is determined by its related task status S(r j )=min(S(t j1 ),S(t j2 ),…,S(t jn )), indicating the demand state S(r j ) depends on the minimum status of all its related tasks, ensuring that the requirement is marked as completed only after all tasks are completed; Check whether the demand indicator data has been fully allocated, and compile information such as the person in charge of the product development plan and the quality auditor; Issue product development plans.

5. The management method for decomposing, distributing, tracking and verifying demand data in the product development process according to claim 4 is characterized in that: The task leader receives the product development plan, generates design results according to the design tasks of the product development plan, analyzes and tests the design results, and obtains analysis result data, including: The task leader performs the design task based on the demand indicator data, input data and reference knowledge to produce design results; Analyze and test the design results and extract the analysis result data; When project requirements change, perform requirement impact analysis based on requirement distribution records and remind stakeholders of the requirements. The specific steps are: Set up the requirement task association matrix Among them, A ij =0, identify demand r j and task t i No relation, A ij =1, identify demand r j and task t i related; Set the task responsible person set Q, Q = {q1, q2, ..., q v }, when task t i By task leader q k When responsible, define the mapping relationship: Φ:T→P,Φ(t i )=p k ; When the project requires j When a change occurs, define the change vector: ΔR = [δ1, δ2, …, δ n ] T , where δ j =1 means r j Changes occur; Then the affected task set ΔT = A × ΔR, where (ΔT) i =1, then task t i affected; The set of task leaders corresponding to the affected tasks is ΔQ = {Φ(t i )|Δ(T) i =1}; The notification method for notifying the task leader is: Mission change notification: Among them, Γ is the notification function; Requirement change cascade analysis: If task t i As input data to influence other tasks t l , the change needs to be further propagated: l =g(t i ),t l ∈T, where g(t i ) represents task t i The downstream task of t l Conduct analysis to ensure all impacts are propagated to all tasks; Calculate the change propagation depth d: d = max(path(ΔT)), where path is the path length; Set the change propagation depth threshold d max ; if d>d max , then notify management of the abnormal change.

6. The management method for decomposing, distributing, tracking and verifying demand data in the product development process according to claim 1 is characterized in that: The feedback data submitted by the audit task leader, all feedback data are summarized, and the feedback data is compared and analyzed with the demand indicator data, including: When the task is completed, for any task t j , get task t j Feedback results F j ; Set the deviation threshold ε of the feedback result k ; Calculate feedback deviation ΔR k =|R k -F j,k |, compare ΔR k and ε k ; If ΔR k >ε k , then return task t j , re-execute the design task; When multiple tasks t1, t2, …, t m For the same demand index R k Feedback is provided, and the project leader conducts weighted integration: Among them, w j For task t j The weight of satisfies the normalization condition Analyze the feedback results of the demand indicator R to measure the impact on the system S: Assume that the total demand is y, then each demand index p j In subsystem S j The implementation is calculated as follows: Among them, e i,j Indicates the demand R i In subsystem S j The weight in, p S j Indicates the demand R i The degree of completion of the subsystem; Integration of all subsystems requirements: Represents the weight calculation of the comprehensive feedback of all tasks in the entire product system.

7. The management method for decomposing, distributing, tracking and verifying demand data in the product development process according to claim 1 is characterized in that: The feedback data submitted by the audit task leader, all feedback data are summarized, and the feedback data is compared and analyzed with the demand indicator data, including: Set the demand-task association matrix V to represent the relationship between tasks and requirements: Among them, v ij =1 indicates task t j Impact Demand R j , v ij =0 means task t j Does not affect demand R j ; Calculate the impact of demand: Among them, I j Indicates the demand R j Impact; Set the threshold I0 that needs to be affected. If I j >I0, notify stakeholders to make adjustments; compare the current project demand realization status p now Similar items in the historical prototype database history , using linear regression analysis: p' = α × p history +β, where p' is the predicted current demand realization, α, β are linear regression analysis parameters, fitted by the least squares method; If |p now -p'|>χ, then adjust the demand implementation steps, where χ is the set difference threshold.

Images