Confirmation system and method based on technology research and development demand closed-loop management

Abstract

The invention discloses a confirmation system and method based on technology research and development demand closed-loop management, and the system and method convert the original demand of a user into the initial demand of a technology developer through a KANO model, QFD and other tools, then convert the initial demand into a technical specification, and achieve the technical specification through the step-by-step decomposition and refining of the technical demand. And conversion and landing from user requirements to technical performance are realized. The invention also defines a closed-loop management process of demand change, namely from demand change confirmation to change influence analysis, change scheme formulation, change scheme verification, change scheme review, change scheme implementation, demand change whole process tracking and demand change acceptance and closure, the demand change management of a technology application party is enhanced; and the cost and the technology research and development quality are effectively controlled. According to the method, the defects of incomplete demand life cycle management, fuzzy demand state circulation standard and high subjectivity in the prior art are overcome, the demand management process is standardized, and the technical research and development design quality is ensured.

Description

Technical Field

[0001] The present invention relates to the field of digital research and development technology, and in particular to a confirmation system and method based on closed-loop management of technology research and development requirements. Background Art

[0002] At present, engineering machinery companies usually manage the demand for technology research and development projects offline, mainly using manual methods to manage technology research and development needs. The technical planning or technical management department is responsible for collecting the demand information of technology users (users), and after preliminary screening and analysis, the demand information is passed to the technical research and development department. The technical research and development department organizes technical research, feasibility analysis and demonstration, and makes a decision on whether to develop the technology research and development project through project review. When the project review is passed, the technical research and development work will begin, responding to user needs through the technology implementation process, and combining simulation analysis, test verification, and user verification to confirm that the research and development results meet user needs and achieve user satisfaction.

[0003] As the needs become more and more diversified, in order to ensure the high efficiency of the system, it is necessary to manage complex needs end-to-end to ensure that the needs are complete and not distorted or lost during the transmission of needs. With the continuous advancement and popularization of technology, the availability of key technologies to achieve functions and performance is no longer an obstacle; therefore, in the actual technology development process, it is not enough to simply realize user needs. The needs of technology application parties (users) involved in the technology development process have not yet been managed in a penetrating manner, and closed-loop management has not been achieved for demand analysis conversion, demand confirmation, demand tracking, and demand changes. The demand lifecycle management is not comprehensive, the granularity of the demand status progress is coarse, and the actual progress still needs to be consulted offline; the demand status flow is vague and subjective because it needs to be manually processed. It is usually difficult for users to accurately and completely put forward the original requirements. At the beginning, they can only put forward a vague functional description, which is gradually clarified only after a long period of repeated understanding, resulting in the fact that user needs are usually dynamic. At present, there are poor correlations in demand disassembly, lack of systematicity, and difficulty in coordinated changes, which makes it difficult to achieve quality control and coordinated implementation of the technology development process.

[0004] Therefore, it is crucial for this field to design a closed-loop management method in the technology R&D business that has a high level of management, fine tracking granularity, and comprehensive demand lifecycle management to ensure timely analysis and conversion of demand, confirmation of technology application (user) needs, tracking of demand, and change of demand. Summary of the invention

[0005] The technical problem to be solved by the present invention is to provide a confirmation system and method based on closed-loop management of technology R&D requirements with a high degree of management, detailed tracking granularity and comprehensive demand lifecycle management in view of the above-mentioned defects of the prior art. The original requirements are converted into initial requirements through tools such as the KANO model and QFD, and then converted into technical specifications. Through the step-by-step decomposition and refinement of technical requirements, the transformation and implementation of user requirements into technical performance are realized; by establishing a systematic mechanism for the disassembly and confirmation of technical application requirements, it is ensured that technology R&D is what is needed.

[0006] To achieve the above object, the technical solution adopted by the present invention is as follows: In a first aspect, the present invention provides a confirmation system based on closed-loop management of technology research and development requirements, comprising: The demand analysis module is used to analyze customer needs and convert the original needs from the user's perspective into initial needs described from the technical research and development perspective; and to build a function tree to determine the demand confirmation status; the demand confirmation status includes: not meeting the needs of the technical application party, meeting the needs of the technical application party, and the needs of the technical application party need further explanation; The demand distribution module is used to distribute the demand to the task book and different development stages of the technology research and development project according to the demand analysis results and enter the technical planning after the demand is confirmed; The demand realization module is used to convert user needs into technical R&D design indicators, i.e. component requirements, at different development stages; The requirement verification module is used to verify the technical R&D design indicators generated by the requirement realization module, and to initiate the requirement change process when it is verified that the requirements cannot be met or the requirements have changed; The demand review module is used to review the degree to which the generated design solution satisfies the needs of the technology application party; The demand change module is used to execute the demand change process, which includes: demand change confirmation, change impact analysis, change plan formulation, change plan verification, change plan review, change plan implementation, demand change full process tracking and demand change acceptance and closure.

[0007] Preferably, the demand analysis module is specifically used to: Build a demand collection and analysis model, convert the original requirements from the user's perspective into initial requirements described from the technical research and development perspective and output them, and establish the correlation between the original requirements and the initial requirements.

[0008] Preferably, during the demand conversion process, structural splitting and merging of demands are supported.

[0009] Preferably, the demand analysis module is specifically used to: Use KANO model, QFD method, Maslow model or four-quadrant method to build a demand collection and analysis model.

[0010] Preferably, the demand analysis module is also used to: Customize the requirements collection template to achieve requirements sorting; And build original demand library, initial demand library, technical performance library and common demand database.

[0011] Preferably, the demand distribution module is specifically used to: Distribute medium- and long-term requirements to planning, and distribute new medium- and long-term requirements through the requirements change process during the planning process; Distribute short-term requirements to task orders, and distribute requirements directly to task orders through the requirements distribution or change process; Distribute urgent requirements to technical R&D projects and trigger the requirement change process to ensure that the requirements of technical R&D projects are up to date.

[0012] Preferably, the demand realization module is specifically used to: By calling the QFD integrated tool, the original requirements are decomposed step by step according to initial requirements, system requirements, and component requirements, so as to realize the transformation and implementation of user requirements into components, technical performance, and sample functions; and convert user requirements into technical R&D design indicators.

[0013] Preferably, the requirement verification module is specifically used to: By connecting with simulation collaboration and test collaboration, relevant simulation and test data can be obtained to verify requirements.

[0014] Preferably, the requirement verification module is further used to: During the verification process, when the requirements cannot be met, initiate the requirements change process; When the initial requirements and system requirements change due to the change of the original requirements proposed by the demand proposer or the market environment in different time periods, the demand change process is initiated; When the initially set component and system indicators cannot be met during the technical development process, the demand change process is initiated.

[0015] Preferably, the demand review module is specifically used to: During the technical definition phase, review whether the requirements are clear and comprehensive, and whether the technical definition fully matches the requirements; During the solution design phase, review the changes in requirements and their impact, as well as the degree to which the solution meets the needs of technology users; Review the changes and impact of requirements during the detailed design phase, as well as the degree to which the detailed design output meets the needs of the technology user; During the technical verification phase, review whether the requirements proposed by the technology users are met.

[0016] Preferably, in the demand change module, Change plan formulation includes: creating a requirement baseline. By establishing a requirement baseline, the hierarchical structure, item version, attributes, view, and link information of the requirements form a status snapshot to ensure the completeness of the requirement data at each stage; and comparing the item structure or attribute information in different requirement baselines to provide difference prompts for the requirement baselines.

[0017] Preferably, the demand change module is also used to: When the technical R&D design indicators change, determine whether to initiate changes to the previous level of requirements based on the actual situation. If changes are required, trigger the requirement changes and save them as different versions and status information. Major changes require baseline records.

[0018] In a second aspect, the present invention provides a confirmation method based on closed-loop management of technology research and development requirements, which is implemented based on the above-mentioned confirmation system based on closed-loop management of technology research and development requirements. The method includes: Through demand analysis, we can obtain the original needs from the user's perspective and transform them into initial needs from the perspective of technology development; Enter technical planning and distribute the requirements to different development stages of task orders and technical R&D projects based on the results of demand analysis; By calling the QFD integrated tool to decompose the original demand into initial demand, system demand, and component demand, user demand is converted into technical R&D design indicators; Verify technical R&D design indicators by level and status; Design solutions and review the extent to which the solutions meet the needs of technology users.

[0019] Preferably, the method further comprises: When it is verified that the requirements cannot be met or the requirements have changed, the requirements change process is initiated; the requirements change process is executed according to the requirements change confirmation, change impact analysis, change plan formulation, change plan verification, change plan review, change plan implementation, full process tracking of requirements changes and acceptance and closure of requirements changes.

[0020] The beneficial effects brought by the technical solution of the present invention are as follows: The present invention provides a confirmation system and method based on closed-loop management of technology research and development requirements, which ensures that technology research and development is what is needed by establishing a system of technology application party requirement specification disassembly and confirmation mechanism. The requirement confirmation status is set based on the function tree, and the function confirmation of the technology application party is performed, and the requirement confirmation status is set: red, yellow, and green, where "red" does not meet the requirements of the technology application party; "green" meets the requirements of the technology application party; "yellow" - the requirements of the technology application party need further explanation; the confirmation method of the technology application party is improved.

[0021] The present invention defines the process of changing technology R&D requirements, manages and controls the changes in technology application requirements, effectively controls the change costs and the quality of technology R&D; implements the tracking of technology application requirements changes to form a closed loop of requirements changes. In technology R&D, the whole process of requirement realization is confirmed, that is, in the technology definition stage, focus on whether the requirements are clearly and comprehensively realized, and whether the technology definition and requirements are completely matched; in the solution design stage, focus on the changes in requirements and their impact, as well as the degree to which the solution satisfies the needs of technology application parties; in the detailed design stage, focus on the changes in requirements and their impact, as well as the degree to which the detailed design output satisfies the needs of technology application parties; in the technology verification stage, focus on the satisfaction of the requirements proposed by technology application parties.

[0022] The present invention targets new requirements that require technology iteration, analyzes and transforms them into technology planning, and ensures timely delivery of requirements, overcoming the defects of incomplete demand lifecycle management, vague demand status flow standards, and strong subjectivity in the prior art. The confirmation method of closed-loop management of technology R&D requirements standardizes the process of demand management and ensures the quality of technology R&D design.

[0023] In the common technology R&D demand development process, the present invention adds demand information collection, analysis and review information from the demand source to improve the entire demand life cycle; it provides new value points for demand tracking for demand value point analysis, demand source analysis, demand change and other scenarios. The present invention realizes the two-way interaction between demand drive and design implementation process, thereby ensuring the goal consistency and work synergy of the design process, and effectively promoting the development of technology R&D business. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 A schematic diagram of a confirmation method flow based on closed-loop management of technology research and development requirements provided by an embodiment of the present invention; Figure 2 A schematic diagram of a demand change process based on closed-loop management of technology R&D demand provided by an embodiment of the present invention; DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the embodiments and the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0026] It should also be noted that, in order to avoid obscuring the present invention due to unnecessary details, only structures and / or processing steps closely related to the solutions according to the present invention are shown in the accompanying drawings, while other details that are not closely related to the present invention are omitted.

[0027] It should be emphasized that the term “include / comprises” when used herein refers to the presence of features, elements, steps or components, but does not exclude the presence or addition of one or more other features, elements, steps or components.

[0028] It should also be noted that, unless otherwise specified, the term “connection” herein may refer not only to a direct connection but also to an indirect connection involving an intermediate.

[0029] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the accompanying drawings, the same reference numerals represent the same or similar components, or the same or similar steps.

[0030] It should be emphasized here that the step marks mentioned below are not intended to limit the order of the steps, but it should be understood that the steps can be executed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be executed simultaneously.

[0031] The embodiment of the present invention provides a confirmation system based on closed-loop management of technology research and development requirements. By establishing a system's technology application party requirement specification disassembly and confirmation mechanism, technology research and development is guaranteed to be what is needed. The requirements are structured and managed in the system, with stages, states, and versions. The stages correspond to the main process of technology development. Status confirmation indicates whether the process approval has been completed, and the requirements modification process is managed through versions. When related to specific user information, customer contact management is supported, including requirement acquisition, confirmation, and verification, and is supported in the system through related functions such as electronic flow and review.

[0032] Based on this, the confirmation system based on closed-loop management of technology R&D requirements in this embodiment is shown in Figure 1 ,include: The demand analysis module is used to analyze customer needs and convert the original needs from the user perspective into initial needs described from the technical development perspective; and to build a function tree to determine the demand confirmation status; the needs described from the technical development perspective include: medium- and long-term needs, short-term needs, and emergency needs; the demand confirmation status includes: does not meet the needs of the technical application party, meets the needs of the technical application party, and the needs of the technical application party need further explanation; The demand distribution module is used to enter the technical planning after the demand is confirmed according to the demand analysis results, and distribute the demand to the task book, technical research and development project and other development stages; Demand realization module, used to convert user needs into technical R&D design indicators; The requirement verification module is used to verify the technical R&D design indicators generated by the requirement realization module, and to initiate the requirement change process when it is verified that the requirements cannot be met or the requirements have changed; The demand review module is used to review the design solution’s satisfaction with the technology application party’s needs; The demand change module is used to execute the demand change process, which includes: demand change confirmation → change impact analysis → change plan formulation → change plan verification → change plan review → change plan implementation → demand change full process tracking → demand change acceptance and closure.

[0033] In this embodiment, the demand analysis module is specifically used to: Conduct a series of activities including market research and analysis, technical research and analysis, and setting of technical positioning and goals according to the needs of technology users, build a KANO model demand collection and analysis model, enter the original demands into the corresponding demand management system, use the KANO analysis model to transform the original demands and output them as initial demands, and establish the relationship between the original demands and the initial demands. In this process, demands can be structured and split and merged.

[0034] Analyze customer needs, convert the user perspective into descriptions and requirements from the perspective of technical research and development, and build a technical performance structure tree to define the attributes of system functions, such as system function description, main functional points, corresponding system components, system component performance requirements, and system interface requirements. Through the "corresponding system component" attribute of system functions, the structured association of technology maps, technical performance, and systems and components is realized, and the replication, evolution, and rapid generation of function trees are supported.

[0035] Based on the function tree, the confirmation method of the technical application party for the requirements is set to ensure that the analysis and transformation of the requirements are confirmed by the user. Among them, the requirement confirmation status is divided into three colors: red, yellow, and green. "Red" means that it does not meet the requirements of the technical application party; "Green" means that it meets the requirements of the technical application party; "Yellow" means that the requirements of the technical application party need further explanation.

[0036] In this embodiment, the demand distribution module is specifically used to: For new requirements that require technology iteration, after demand analysis and transformation, the requirements enter the technology planning process after confirmation. The technology R&D project undertakes the technology research content in the technology planning to ensure the timely delivery and realization of the requirements. According to the results of the demand analysis, the requirements are distributed to the planning, task book, technology R&D project and other development stages; medium- and long-term requirements are distributed to the planning, and new medium- and long-term requirements are supplemented and distributed through the demand change process during the planning process; short-term requirements are distributed to the task book, and the requirements are directly distributed to the task book through the demand distribution or change process; urgent requirements are distributed to the technology R&D project, and the demand change process is triggered to ensure that the technology R&D project requirements are the latest; this embodiment issues requirements to technology R&D through the task book issuance, requirement issuance and requirement change process; and resolves demand disputes during the demand distribution process.

[0037] In this embodiment, the demand realization module is specifically used to: By calling the QFD integrated tool, we can complete the step-by-step decomposition and refinement of original requirements → initial requirements → system requirements → component requirements, explore user potential needs, and realize the transformation and implementation of user needs into components, technical performance, and sample functions; convert user needs into technical R&D design indicators.

[0038] In this embodiment, the requirement verification module is specifically used to: Verify components, (sub)systems, and samples by level and status; obtain relevant simulation and test data for demand verification by connecting with simulation collaboration, test collaboration and other processes, and achieve system visualization and monitoring of performance indicators, status, defects, etc.; when the requirements cannot be met, initiate the demand change process. When the initial requirements, system requirements, etc. change due to changes in the original requirements proposed by the demand proposer or the market environment in different time periods, initiate the demand change process; when the originally set component and system indicators cannot be met during the technical research and development process, the demand change process can be initiated.

[0039] In this embodiment, the demand review module is specifically used to: In the review of each stage, the demand review will be included in the unified review elements for control to ensure the confirmation of the realization of the demand in the whole process. In the technical definition stage, it is reviewed whether the demand realization is clear and comprehensive, and whether the technical definition and demand are completely matched; in the solution design stage, it is reviewed for changes in demand and their impact, as well as the degree to which the solution satisfies the needs of the technology user; in the detailed design stage, it is reviewed for changes in demand and their impact, as well as the degree to which the detailed design output satisfies the needs of the technology user; in the technical verification stage, it is reviewed for the satisfaction of the requirements proposed by the technology user.

[0040] In this embodiment, the demand change module is specifically used to: Based on the demand change process, ensure the systematic management and timely delivery of demand changes to form a closed loop of changes. Figure 2 , including: confirmation of demand changes → analysis of change impacts → formulation of change plans → verification of change plans → review of change plans → implementation of change plans → tracking of the entire process of demand changes → acceptance and closure of demand changes.

[0041] Change impact analysis includes: before the requirements are changed, the requirements personnel can clearly view the direct and indirect impacts of the changed items on the technical R&D data at all levels through the requirements matrix and impact analysis view, to assist in making change decisions; Change plan formulation includes: creating a requirement baseline. By establishing a requirement baseline, the hierarchical structure, item version, attributes, views, links and other information of the requirements are formed into a status snapshot to ensure the completeness of the requirement data at each stage of the project, and compare the item structure or attribute information in different requirement baselines, and provide baseline difference prompts.

[0042] It should be noted that the demand change process can automatically match process nodes and personnel, and automatically collect data affected by the demand change; when technical indicators change, it is manually determined whether to initiate changes to the previous level of demand based on actual conditions. If changes are required, the changes are triggered and saved as different versions, statuses and other information. Major changes require baseline records.

[0043] In this embodiment, the demand change involves the change control of relevant technical information, version change information, etc., the description of the change problem, the establishment of the change order, the execution of the change, and the release of the change are all under continuous control to ensure the correctness, timeliness and completeness of the change. It includes change requests, problem reports, change notifications, change tasks, change object extensions, change tracking and batch changes.

[0044] In this embodiment, the baseline is used to ensure the data status at a specific time, realize the management of technical status, and facilitate data traceability. The baseline data is improved through multi-dimensional comparison and baseline merging; the baseline is automatically formed by signing and reviewing and releasing the change process, and manual recording and archiving of baselines are supported. According to the technical status requirements, it is used to record the technical status released at each stage, and realize the management of the complete life cycle of multi-module baselines.

[0045] Furthermore, in this embodiment, a pre-review link is added to the change plan review activity to strengthen the tracking of changes in technology application requirements. By implementing the tracking of technology application requirements changes, a closed loop of requirements changes is formed; the management of technology application requirements changes is managed and controlled to effectively control change costs and technology research and development quality.

[0046] It should be noted that, in the present invention, the tools used for demand analysis may involve not only the KANO model and QFD, but also the Maslow model and the four-quadrant method (according to importance and urgency).

[0047] It should be noted that, in the present invention, the red, yellow, and green three-color logos and their representative meanings set by the technical application party for confirmation status may be replaced by other three colors respectively and given different meanings.

[0048] It should be noted that, in the present invention, the demand verification method may involve type testing and third-party certification in addition to simulation analysis and experimental verification.

[0049] It should be noted that, in addition to being applied to technology research and development business, the closed-loop management confirmation method of demand is also applicable to product research and development business. The present invention may also be applied to the field of computer application technology, or to the field of management.

[0050] By adopting the above technical solution, this embodiment realizes closed-loop management of demand, realizes structured storage of basic demand information (including demand collection channels, etc.), customer information, and management of demand version, status, baseline, etc., and realizes life cycle management of demand; uses KANO model to customize demand collection template to realize demand sorting; can be integrated with QFD template to support rapid transformation of customer demand; realizes real-time penetration monitoring and management of demand; builds original demand library, initial demand library, technical performance library, etc. Common demands are automatically collected to generate common demand database. A top-down mode is adopted to maintain the demand information architecture through various methods such as manual, PDM integration, and technology map integration. In the system, the demand model solidification at different stages and the electronic flow drive the evolution of demand stages to ensure the standardization of demand analysis and storage; the traceability of demand is realized through the management of demand status and version; the integration of KANO model and QFD tool improves the efficiency and accuracy of demand analysis. Demands at different stages contain different structured information. With the changes in demand analysis, implementation, and verification, the structured information contained in the demand continues to increase, and finally the full control of demand data from the beginning to the end is realized. Support real-time penetration monitoring and management of demand. Function and performance are the underlying logic of demand evolution and the data support for forward systematic design, which are associated with the technology map application and PDM system. This embodiment forms a structured demand database for closed-loop management of the entire life cycle of technology R&D demand through the demand management process, realizes online management of the entire process of technical indicators, and tracks the demand realization process.

[0051] Based on the same inventive concept, a second embodiment of the present invention provides a confirmation method for closed-loop management of technology research and development requirements based on a confirmation system, comprising: Through demand analysis, we obtain the original needs from the user's perspective and transform them into initial needs from the perspective of technical research and development; define the person responsible for the needs, mark the confirmation status of the needs, and store them in the initial demand library; Enter technical planning and distribute the requirements to development stages such as task books and technical R&D projects based on the results of demand analysis; By calling the QFD integrated tool, the original demand → initial demand → system demand → component demand is decomposed and refined step by step, realizing the transformation and implementation of user demand to technical performance and sample function, and converting user demand into technical R&D design indicators; Verify components, (sub)systems, and samples by level and status; Design solutions and review the extent to which the solutions meet the needs of technology users.

[0052] Terminology explanation: QFD—Quality Function Deployment is a customer-driven product development method. From the perspective of quality assurance, it obtains customer needs through certain market research methods, and uses matrix diagrams to decompose customer needs into various stages and functional departments of product development. By coordinating the work of various departments to ensure the quality of the final product, the designed and manufactured products can truly meet customer needs.

[0053] KANO model - a tool for classifying and prioritizing user needs, based on analyzing the impact of user needs on user satisfaction, reflects the nonlinear relationship between product performance and user satisfaction.

[0054] Original requirements - all requirements from internal and external customers about the company's products and solutions that require the requirements management / analysis team to analyze and review and make decisions. Customer requirements belong to a category of original requirements.

[0055] Initial requirements - After the original requirements are analyzed by the requirements management team, they are re-described in a complete and standard format from the perspective of internal and external customers / markets.

[0056] System requirements - describes the specific requirements that need to be supported to support "system characteristics", which refers to all functional and non-functional requirements that the system presents to the outside and can be tested. Functional requirements are scenario-specific requirements for the functions provided by the system, and non-functional requirements are specific requirements for non-functional aspects such as system cost, global quality attributes, and technical limitations.

[0057] Component requirements - functional or non-functional requirements that are decomposed layer by layer to the component level based on system requirements.

[0058] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A confirmation system based on closed-loop management of technology R&D requirements, characterized in that: include: Demand analysis module, used to analyze customer needs and transform the original needs from the user's perspective into initial needs described from the perspective of technical research and development; And, build a function tree to determine the status of requirement confirmation; The requirement confirmation status includes: not meeting the requirements of the technology application party, meeting the requirements of the technology application party, and the requirements of the technology application party need further explanation; The demand distribution module is used to distribute the demand to the task book and different development stages of the technology research and development project according to the demand analysis results and enter the technical planning after the demand is confirmed; The demand realization module is used to convert user needs into technical R&D design indicators, i.e. component requirements, at different development stages; The requirement verification module is used to verify the technical R&D design indicators generated by the requirement realization module, and to initiate the requirement change process when it is verified that the requirements cannot be met or the requirements have changed; The demand review module is used to review the degree to which the generated design solution satisfies the needs of the technology application party; The demand change module is used to execute the demand change process, which includes: demand change confirmation, change impact analysis, change plan formulation, change plan verification, change plan review, change plan implementation, demand change full process tracking and demand change acceptance and closure.

2. A confirmation system based on closed-loop management of technology R&D requirements according to claim 1, characterized in that: The demand analysis module is specifically used to: Build a demand collection and analysis model, convert the original requirements from the user's perspective into initial requirements described from the technical research and development perspective and output them, and establish the correlation between the original requirements and the initial requirements.

3. A confirmation system based on closed-loop management of technology R&D requirements according to claim 2, characterized in that: During the demand conversion process, structured splitting and merging of demands are supported.

4. A confirmation system based on closed-loop management of technology R&D requirements according to claim 2, characterized in that: The demand analysis module is specifically used to: Use KANO model, QFD method, Maslow model or four-quadrant method to build a demand collection and analysis model.

5. According to claim 2, a confirmation system based on closed-loop management of technology R&D requirements is characterized in that: The demand analysis module is also used to: Customize the requirements collection template to achieve requirements sorting; And build original demand library, initial demand library, technical performance library and common demand database.

6. A confirmation system based on closed-loop management of technology R&D requirements according to claim 2, characterized in that: The demand distribution module is specifically used to: Distribute medium- and long-term requirements to planning, and distribute new medium- and long-term requirements through the requirements change process during the planning process; Distribute short-term requirements to task orders, and distribute requirements directly to task orders through the requirements distribution or change process; Distribute urgent requirements to technical R&D projects and trigger the requirement change process to ensure that the requirements of technical R&D projects are up to date.

7. A confirmation system based on closed-loop management of technology R&D requirements according to claim 6, characterized in that: The demand realization module is specifically used for: By calling the QFD integrated tool, the original requirements are decomposed step by step according to initial requirements, system requirements, and component requirements, so as to realize the transformation and implementation of user requirements into components, technical performance, and sample functions; and convert user requirements into technical R&D design indicators.

8. A confirmation system based on closed-loop management of technology R&D requirements according to claim 7, characterized in that: The requirement verification module is specifically used to: By connecting with simulation collaboration and test collaboration, relevant simulation and test data can be obtained to verify requirements.

9. A confirmation system based on closed-loop management of technology R&D requirements according to claim 8, characterized in that: The requirement verification module is also used to: During the verification process, when the requirements cannot be met, initiate the requirements change process; When the initial requirements and system requirements change due to the change of the original requirements proposed by the demand proposer or the market environment in different time periods, the demand change process is initiated; When the initially set component and system indicators cannot be met during the technical development process, the demand change process is initiated.

10. A confirmation system based on closed-loop management of technology R&D requirements according to claim 8, characterized in that: The demand review module is specifically used to: During the technical definition phase, review whether the requirements are clear and comprehensive, and whether the technical definition fully matches the requirements; During the solution design phase, review the changes in requirements and their impact, as well as the degree to which the solution meets the needs of technology users; Review the changes and impact of requirements during the detailed design phase, as well as the degree to which the detailed design output meets the needs of the technology user; During the technical verification phase, review whether the requirements proposed by the technology users are met.

11. A confirmation system based on closed-loop management of technology R&D requirements according to claim 10, characterized in that: In the demand change module, Change plan formulation includes: creating a requirement baseline. By establishing a requirement baseline, the hierarchical structure, item version, attributes, view, and link information of the requirements form a status snapshot to ensure the completeness of the requirement data at each stage; and comparing the item structure or attribute information in different requirement baselines to provide difference prompts for the requirement baselines.

12. A confirmation system based on closed-loop management of technology R&D requirements according to claim 11, characterized in that: The demand change module is also used to: When the technical R&D design indicators change, determine whether to initiate changes to the previous level of requirements based on the actual situation. If changes are required, trigger the requirement changes and save them as different versions and status information. Major changes require baseline records.

13. A confirmation method based on closed-loop management of technology R&D requirements, characterized in that: The confirmation system based on closed-loop management of technology R&D requirements according to any one of claims 1 to 12 is implemented, and the method comprises: Through demand analysis, we can obtain the original needs from the user's perspective and transform them into initial needs from the perspective of technology development; Enter technical planning and distribute the requirements to different development stages of task orders and technical R&D projects based on the results of demand analysis; By calling the QFD integrated tool to decompose the original demand into initial demand, system demand, and component demand, user demand is converted into technical R&D design indicators; Verify technical R&D design indicators by level and status; Design solutions and review the extent to which the solutions meet the needs of technology users.

14. A confirmation method based on closed-loop management of technology R&D requirements according to claim 13, characterized in that: The method further comprises: When it is verified that the requirements cannot be met or the requirements have changed, the requirements change process is initiated; the requirements change process is executed according to the requirements change confirmation, change impact analysis, change plan formulation, change plan verification, change plan review, change plan implementation, full process tracking of requirements changes and acceptance and closure of requirements changes.

Images