An engineering business requirements analysis method and system

Abstract

The present invention discloses a method and system for analyzing engineering business requirements, and the method includes: adaptively generating an RDM requirement analysis method according to a preset business generation principle, converting the brainstorming conceived by business experts based on the RDM requirement analysis method into engineering project business requirements, conducting basic analysis on the engineering project business requirements, mining surrounding businesses for the engineering project business requirements, and conducting overall analysis on the engineering project business requirements based on the mining results. By generating a business requirement training model, business personnel can generate business requirements based on the model to ensure its accuracy and qualification, making the entire business requirement collection process more systematic. The engineering project business requirements can be analyzed in many aspects, which greatly reduces the subjective evaluation of business personnel and ensures the objectivity of the analysis results.

Description

Technical Field

[0001] The present invention relates to the technical field of business analysis, and in particular to an engineering business demand analysis method and system. Background Art

[0002] At present, in financial systems such as banks, in order to better provide services to users and ensure business innovation, it is often necessary to analyze and process the original requirements collected by the business department and generate corresponding requirements analysis results. Generally, requirements development obtains requirements through communication with users, and then analyzes and abstracts various requirements information, and generates "Requirements Specifications". After review with users, the final business requirements are formed. However, the above method has the following problems: 1. The requirements collection process is relatively random, not systematic and engineered, and there is no clear routine for the requirements analysis process; 2. The analysis method is too simple, which is a simple user review, resulting in the analysis results being too subjective. Summary of the invention

[0003] In response to the above-mentioned problems, the present invention provides an engineering business demand analysis method and system for analyzing user business needs based on RDM technology to solve the problems mentioned in the background technology: 1. The demand collection process is relatively arbitrary, not systematic and engineered enough, and there is no clear routine for the demand analysis process; 2. The analysis method is too simple, which is simple user review, resulting in the problem that the analysis results are too subjective.

[0004] An engineering business requirements analysis method includes the following steps:

[0005] Adaptively generate RDM demand analysis method based on preset business generation principle;

[0006] Convert the brainstorming ideas conceived by business experts based on the RDM requirements analysis method into engineering project business requirements;

[0007] Conduct basic analysis on the business requirements of the engineering project;

[0008] Conduct business mining around the business needs of the engineering project, and conduct an overall analysis of the business needs of the engineering project based on the mining results.

[0009] Preferably, the items of the basic analysis include: a general description of the field, three static and two dynamic demand stratification, virtual classification and embedded management system.

[0010] Preferably, the method for adaptively generating RDM demand analysis according to a preset business generation principle includes:

[0011] Form a project requirements group based on the preset business generation principles for different businesses;

[0012] Select a target writing environment according to the formed project requirement group, the target writing environment includes: a remote online writing environment and an offline writing environment;

[0013] If the target writing environment is a remote online writing environment, start the Xmind mind map tool;

[0014] The RDM requirement analysis method is generated according to the basic rules of different business requirements in the project requirement group and combined with the Xmind mind map tool.

[0015] Preferably, the RDM method is used to convert the brainstorming ideas conceived by the business experts based on the business demand training model into engineering project business requirements, including:

[0016] Obtaining basic information of a preset number of business experts, and selecting a plurality of suitable target business experts according to the basic information;

[0017] Inputting the brainstorming results of the target business experts into the business demand training model to obtain output results;

[0018] Based on the output results, the corresponding business project type is determined by using the RDM method and the business requirements of business experts are obtained to be converted into engineering project business requirements;

[0019] Develop a schedule for demand analysis based on the business project type corresponding to the business needs of the engineering project.

[0020] Preferably, the basic analysis of the business requirements of the engineering project includes:

[0021] Determine the business content corresponding to the business requirements of the engineering project by using RDM method;

[0022] Determine the business domain description, business template and embedded management links corresponding to the business requirements of the engineering project based on the business content;

[0023] Draw the business panorama and business process diagram corresponding to the business needs of the engineering project based on the business domain description, business templates and embedded management links corresponding to the business needs of the engineering project;

[0024] The business panorama and business process diagram are structured to obtain a demand analysis table corresponding to the business requirements of the engineering project.

[0025] Preferably, the mining of surrounding businesses for the engineering project business needs and the overall analysis of the engineering project business needs based on the mining results include:

[0026] Explore the related businesses around the engineering project business needs and determine the business relationship between the engineering project business and each related business;

[0027] Selecting an adapted business reference model from a preset model library according to the business relationship between the engineering project business and each associated business;

[0028] Using the business reference model that is adapted to the engineering project business and each associated business, describe the process positioning diagram of the engineering project business and the integration relationship diagram between the engineering project business and the associated business;

[0029] The system division, core documents, key business data, and non-core data information of the engineering project business are obtained, and a data relationship table is generated to describe the relationship between the engineering project business and the above information.

[0030] Preferably, the method further comprises:

[0031] Obtain business reference models related to the business requirements of engineering projects;

[0032] Packaging the engineering project business requirements and the business reference model related thereto into a specific organizational form;

[0033] After packaging is completed, import it into the preset demand base account library;

[0034] Set sample tags and index tags for the engineering project business requirements and their related business reference models in the preset requirement base library.

[0035] Preferably, before generating the RDM requirement analysis method according to the basic rules of different business requirements in the project requirement group in combination with the Xmind mind map tool, the method further includes:

[0036] Obtain the logical parameters of the business process corresponding to each business during the implementation phase;

[0037] Determine the response information of the implementation object corresponding to each business process according to the logical parameters of the business process in the implementation stage;

[0038] Obtaining a sequence of attribute data of the response information;

[0039] Determine the rule parameters corresponding to the attribute data sequence, and construct a mapping relationship between the attribute data sequence and the rule parameters;

[0040] The basic rules for the business requirements of each business are generated according to the mapping relationship between the attribute data sequence of the business and the rule parameters.

[0041] Preferably, the step of obtaining the attribute data sequence of the response information includes:

[0042] Extract metadata from the response information of each implementation object;

[0043] Retrieve the corresponding business description file in real time according to the metadata in the response information of each implementation object;

[0044] Obtaining a preset identifier corresponding to a business description file based on each implementation object;

[0045] Determine the inherent attributes and extended attributes corresponding to the preset identifier of the service description file of each implementation object;

[0046] Merging a first data set of the own attributes and a second data set of the extended attributes of the service description file of each implementation object to obtain a third data set;

[0047] Determine the distribution of elements of the same type in the third data set of the business description file of each implementation object;

[0048] Confirm whether there are iterative elements in the distribution of the same type of elements. If so, remove the redundant number of iterative factors. Otherwise, no subsequent operation is required.

[0049] Constructing multiple data sequences of the same type of elements in the third data set of the business description file of each implementation object;

[0050] Acquire a preset attribute value of each element, and obtain multiple attribute sequences in a third data set of the business description file of each implementation object according to the preset attribute value of each element and the multiple data sequences;

[0051] Combine multiple attribute sequences in the third data set of the business description file of each implementation object to obtain the attribute data sequence in the response information of each implementation object.

[0052] An engineering business demand analysis system, the system comprising:

[0053] A generation module, used to adaptively generate an RDM demand analysis method according to a preset business generation principle;

[0054] A conversion module, used to convert the brainstorming ideas conceived by business experts based on the RDM demand analysis method into engineering project business requirements;

[0055] A first analysis module is used to perform basic analysis on the business requirements of the engineering project;

[0056] The second analysis module is used to mine surrounding businesses for the engineering project business needs, and conduct an overall analysis of the engineering project business needs based on the mining results.

[0057] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the written description and the accompanying drawings.

[0058] The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] The accompanying drawings are used to provide further understanding of the present invention and constitute a part of the specification. They are used to explain the present invention together with the embodiments of the present invention and do not constitute a limitation of the present invention.

[0060] Figure 1 A workflow diagram of an engineering business requirements analysis method provided by the present invention;

[0061] Figure 2 Another workflow diagram of an engineering business requirements analysis method provided by the present invention;

[0062] Figure 3 Another workflow diagram of an engineering business requirements analysis method provided by the present invention;

[0063] Figure 4 This is a screenshot of an embodiment of an engineering business demand analysis method provided by the present invention;

[0064] Figure 5 This is a workflow diagram of an engineering business demand analysis system provided by the present invention. DETAILED DESCRIPTION

[0065] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0066] At present, in financial systems such as banks, in order to better provide services to users and ensure business innovation, it is often necessary to analyze and process the original needs collected by the business department and generate corresponding demand analysis results. Generally, demand development obtains needs through communication with users, and then analyzes and abstracts various demand information, and generates a "Requirements Specification", which is reviewed with users to form the final business needs. However, the above method has the following problems: 1. The demand collection process is relatively arbitrary, not systematic and engineered, and there is no clear routine for the demand analysis process; 2. The analysis method is too simple, which is a simple user review, resulting in the analysis results being too subjective. In order to solve the above problems, this embodiment discloses an engineering business demand analysis method.

[0067] An engineering business requirements analysis method, such as Figure 1 As shown, the following steps are included:

[0068] Step S101, adaptively generating an RDM demand analysis method according to a preset business generation principle;

[0069] Step S102: converting the brainstorming ideas conceived by the business experts based on the RDM demand analysis method into engineering project business requirements;

[0070] Step S103: Conduct basic analysis on the business requirements of the engineering project;

[0071] Step S104: mining surrounding businesses for the engineering project business needs, and performing overall analysis on the engineering project business needs based on the mining results;

[0072] In this embodiment, the analysis items for basic analysis of the engineering project business requirements include: business panorama analysis, three static and two dynamic demand stratification, virtual classification setting, etc.;

[0073] The above-mentioned business panorama analysis displays the business situation by constructing a business panorama, which includes: an overall description of the field, three static and two dynamic demand stratification, virtual classification, and embedded management system;

[0074] 1. General description of this field

[0075] The general description of this field is for the entire project, and even in order to clarify the business scope of the project, some related businesses of this department will be expanded;

[0076] The overall description of this field includes nine contents: project name, objectives, business lines, functional domains, main stakeholders, legal and regulatory basis, business pain points, glossary, and external services that can be provided.

[0077] 2. Virtual Classification

[0078] When disassembling complex businesses, they can be divided into different business categories. Virtual classification is equivalent to business classification without generating a project proposal catalog;

[0079] 3. Three static and two dynamic needs stratification

[0080] It is used for business classification. When disassembling complex businesses, they need to be divided into different business categories. There are up to 6 levels of business categories. When describing a business, it is necessary to distinguish whether the business is a data business or a process business. If it is a process business, first describe the business (static), then describe each business process of the business in turn (dynamic), confirm whether the business has other dependent business processes, all job operations of this process (static), and describe the operation of the operation (static).

[0081] 4. The embedded management system mainly describes the relationship between the business in this field and the core system;

[0082] When describing embedded business, it is divided into several levels, including overview, model embedding, embedding of each link, and embedded implementation of each link.

[0083] The working principle of the above technical solution is: adaptively generate an RDM demand analysis method according to a preset business generation principle, convert the brainstorming conceived by business experts based on the RDM demand analysis method into engineering project business needs, conduct basic analysis on the engineering project business needs, conduct surrounding business mining for the engineering project business needs, and conduct overall analysis of the engineering project business needs based on the mining results.

[0084] The beneficial effects of the above technical solution are: by generating an RDM demand analysis method, the business needs generated by business personnel based on RDM demand analysis indicators can ensure their accuracy and qualification, making the entire business demand collection process more systematic. Furthermore, by converting users' business needs into engineering project business needs, the engineering of business needs can be achieved, thereby improving stability. Furthermore, by conducting basic analysis and overall analysis of the engineering project business needs, the engineering project business needs can be analyzed from multiple aspects, greatly reducing the subjective evaluation of business personnel and ensuring the objectivity of the analysis results. At the same time, it solves business demand collection and analysis problems in multiple scenarios such as front-end and back-end operation processes, pure back-end operation processes, domain core data, query statistics, monitoring and early warning, thereby improving practicality.

[0085] In one embodiment, Figure 2 As shown, the method for adaptively generating RDM demand analysis according to the preset business generation principle includes:

[0086] Step S201, forming a project requirement group according to preset business generation principles of different businesses;

[0087] Step S202: selecting a target writing environment according to the formed project requirement group, wherein the target writing environment includes: a remote online writing environment and an offline writing environment;

[0088] Step S203: If the target writing environment is a remote online writing environment, start the Xmind mind map tool;

[0089] Step S204: Generate an RDM requirement analysis method based on the basic rules of different business requirements in the project requirement group and the Xmind mind map tool.

[0090] The beneficial effect of the above technical solution is: by constructing a project requirement group, it can comprehensively include and store most of the business generation principles and then comprehensively generate the RDM requirement analysis method based on its basic rules, so that the generated requirement analysis method is more adaptable and can cope with different types of business needs, thereby improving accuracy and work efficiency.

[0091] In one embodiment, Figure 3 As shown, the RDM method is used to convert the brainstorming ideas conceived by business experts based on the business demand training model into engineering project business requirements, including:

[0092] Step S301, obtaining basic information of a preset number of business experts, and selecting a plurality of suitable target business experts according to the basic information;

[0093] Step S302: input the brainstorming result of the target business expert into the business demand training model to obtain an output result;

[0094] Step S303: Based on the output result, determine the corresponding business project type by using the RDM method and obtain the business requirements of the business experts to convert them into engineering project business requirements;

[0095] Step S304: formulate a schedule for demand analysis according to the business project type corresponding to the engineering project business demand.

[0096] The beneficial effects of the above technical solution are: by selecting appropriate business experts, it can be ensured that the type of business demand is the same as the business type corresponding to the model, thereby improving accuracy. Furthermore, by determining the business project type, the business needs of business experts can be accurately classified into projects and then quickly converted into engineering project business needs, thereby improving work efficiency. Furthermore, by formulating a demand analysis schedule, business experts can subsequently understand the analysis progress of business needs in real time, thereby improving the experience and work efficiency of business personnel.

[0097] In one embodiment, the basic analysis of the engineering project business requirements includes:

[0098] Determine the business content corresponding to the business requirements of the engineering project by using RDM method;

[0099] Determine the business domain description, business template and embedded management links corresponding to the business requirements of the engineering project based on the business content;

[0100] Draw the business panorama and business process diagram corresponding to the business needs of the engineering project based on the business domain description, business templates and embedded management links corresponding to the business needs of the engineering project;

[0101] The business panorama and business process diagram are structured to obtain a demand analysis table corresponding to the business requirements of the engineering project.

[0102] The beneficial effects of the above technical solution are: by drawing the business panorama and business process diagram corresponding to the business needs of the engineering project, the basic content of the engineering project needs can be obtained in an all-round way, avoiding the occurrence of process omissions, and improving accuracy and work efficiency. Furthermore, by structuring the business panorama and business process diagram of the engineering project business needs to obtain the demand analysis table corresponding to the engineering project business needs, the demand data corresponding to the engineering project business can be intuitively determined according to the demand analysis table, providing a reference basis for decision-makers.

[0103] In one embodiment, the mining of surrounding businesses for the engineering project business needs and the overall analysis of the engineering project business needs according to the mining results include:

[0104] Explore the related businesses around the engineering project business needs and determine the business relationship between the engineering project business and each related business;

[0105] Selecting an adapted business reference model from a preset model library according to the business relationship between the engineering project business and each associated business;

[0106] Using the business reference model that is adapted to the engineering project business and each associated business, describe the process positioning diagram of the engineering project business and the integration relationship diagram between the engineering project business and the associated business;

[0107] The system division, core documents, key business data, and non-core data information of the engineering project business are obtained, and a data relationship table is generated to describe the relationship between the engineering project business and the above information.

[0108] The beneficial effect of the above technical solution is that by conducting related business analysis and self-calling data analysis on the engineering project business, the engineering project business work can be analyzed in depth in a more detailed manner, ensuring the rationality and objectivity of the analysis results.

[0109] In one embodiment, the method further comprises:

[0110] Obtain business reference models related to the business requirements of engineering projects;

[0111] Packaging the engineering project business requirements and the business reference model related thereto into a specific organizational form;

[0112] After packaging is completed, import it into the preset demand base account library;

[0113] Set sample tags and index tags for the engineering project business requirements and their related business reference models in the preset requirement base library.

[0114] The beneficial effects of the above technical solution are: by importing the business requirements of the engineering project and the related business reference models into the preset demand base library, the business requirements can be reused and shared, and there is no need to rebuild the model later, which further improves work efficiency and the experience of business experts. Furthermore, by setting sample tags and index tags, business personnel can quickly retrieve models and business requirements later, further improving work efficiency.

[0115] In one embodiment, before generating the RDM requirement analysis method according to the basic rules of different business requirements in the project requirement group in combination with the Xmind mind map tool, the method further includes:

[0116] Obtain the logical parameters of the business process corresponding to each business in the implementation stage;

[0117] Determine the response information of the implementation object corresponding to each business process according to the logical parameters of the business process in the implementation stage;

[0118] Obtaining a sequence of attribute data of the response information;

[0119] Determine the rule parameters corresponding to the attribute data sequence, and construct a mapping relationship between the attribute data sequence and the rule parameters;

[0120] The basic rules for the business requirements of each business are generated according to the mapping relationship between the attribute data sequence of the business and the rule parameters.

[0121] The beneficial effect of the above technical solution is that by constructing a mapping relationship to generate real-time rules for each business, basic rules can be quickly determined by matching according to the mapping relationship, thereby improving the stability and ideal efficiency of determining the basic rules.

[0122] In one embodiment, the step of obtaining the attribute data sequence of the response information includes:

[0123] Extract metadata from the response information of each implementation object;

[0124] Retrieve the corresponding business description file in real time according to the metadata in the response information of each implementation object;

[0125] Obtaining a preset identifier corresponding to a business description file based on each implementation object;

[0126] Determine the inherent attributes and extended attributes corresponding to the preset identifier of the service description file of each implementation object;

[0127] Merging a first data set of the own attributes and a second data set of the extended attributes of the service description file of each implementation object to obtain a third data set;

[0128] Determine the distribution of elements of the same type in the third data set of the business description file of each implementation object;

[0129] Confirm whether there are iterative elements in the distribution of the same type of elements. If so, remove the redundant number of iterative factors. Otherwise, no subsequent operation is required.

[0130] Constructing multiple data sequences of the same type of elements in the third data set of the business description file of each implementation object;

[0131] Acquire a preset attribute value of each element, and obtain multiple attribute sequences in a third data set of the business description file of each implementation object according to the preset attribute value of each element and the multiple data sequences;

[0132] Combine multiple attribute sequences in the third data set of the business description file of each implementation object to obtain the attribute data sequence in the response information of each implementation object.

[0133] The beneficial effect of the above technical solution is: by obtaining the inherent attributes and extended attributes of the description file of the response information of each implementation object to comprehensively extract the attribute data sequence in the response information of each implementation object, it is possible to achieve full extraction of the attribute data sequence of the response information, thereby ensuring the stable progress of subsequent work and the rationality of constructing rules, laying a solid foundation for subsequent work.

[0134] In one embodiment, Figure 4 As shown, including:

[0135] 1. Planning and preliminary preparation for demand analysis:

[0136] Prepare for the requirements analysis of this iteration. Select relevant business experts and technical experts, provide them with method training, and develop a schedule for requirements analysis;

[0137] 2. Panoramic business analysis:

[0138] Organize business experts and technical experts to brainstorm together. Use the RDM method to systematically obtain the user's business needs, and through continuous communication with business experts, jointly complete the overall and systematic analysis of business needs;

[0139] 3. Business reference model:

[0140] Based on the results of the business panorama analysis, the RDM method is used to further explore the relationship between the business needs of this project and various existing surrounding needs, so as to jointly achieve the integrity and synergy of business needs;

[0141] 4. Demand base account

[0142] Import the results of business panorama analysis and business reference model into the demand base library according to a specific organizational form, laying a solid foundation for further demand analysis, statistics and demand tracing.

[0143] The beneficial effects of the above technical solution are: collecting and analyzing users' business needs in an engineering and systematic way; facilitating seamless communication between business experts and between business experts and technical experts, and facilitating the reuse and sharing of business needs.

[0144] This embodiment also discloses an engineering business demand analysis system, such as Figure 5 As shown, the system includes:

[0145] A generation module 501 is used to adaptively generate an RDM demand analysis method according to a preset business generation principle;

[0146] A conversion module 502, used to convert the brainstorming ideas conceived by the business experts based on the RDM demand analysis method into engineering project business requirements;

[0147] The first analysis module 503 is used to perform basic analysis on the business requirements of the engineering project;

[0148] The second analysis module 504 is used to mine surrounding businesses for the engineering project business requirements and conduct an overall analysis of the engineering project business requirements based on the mining results.

[0149] The working principle and beneficial effects of the above technical solution have been described in the method claims and will not be repeated here.

[0150] Those skilled in the art should understand that the first and second in the present invention merely refer to different application stages.

[0151] Other embodiments of the present disclosure will be readily apparent to those skilled in the art after considering the specification and practicing the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0152] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. An engineering business requirements analysis method, characterized in that: The following steps are involved: Adaptively generate RDM demand analysis method based on preset business generation principle; Convert the brainstorming ideas conceived by business experts based on the RDM requirements analysis method into engineering project business requirements; Conduct basic analysis on the business requirements of the engineering project; Conduct business mining around the business needs of the engineering project, and conduct an overall analysis of the business needs of the engineering project based on the mining results; The method for adaptively generating RDM demand analysis according to a preset business generation principle includes: Form a project requirements group based on the preset business generation principles for different businesses; Select a target writing environment according to the formed project requirement group, the target writing environment includes: a remote online writing environment and an offline writing environment; If the target writing environment is a remote online writing environment, start the Xmind mind map tool; Generate an RDM requirement analysis method based on the basic rules of different business requirements in the project requirement group and the Xmind mind map tool; Before generating the RDM requirement analysis method according to the basic rules of different business requirements in the project requirement group in combination with the Xmind mind map tool, the method further includes: Obtain the logical parameters of the business process corresponding to each business in the implementation stage; Determine the response information of the implementation object corresponding to each business process according to the logical parameters of the business process in the implementation stage; Obtaining a sequence of attribute data of the response information; Determine the rule parameters corresponding to the attribute data sequence, and construct a mapping relationship between the attribute data sequence and the rule parameters; Generate basic rules for the business requirements of each business based on the mapping relationship between the attribute data sequence and the rule parameters of the business; The step of obtaining the attribute data sequence of the response information includes: Extract metadata from the response information of each implementation object; Retrieve the business description file corresponding to each implementation object according to the metadata in the response information of the implementation object; Obtaining a preset identifier corresponding to a business description file based on each implementation object; Determine the inherent attributes and extended attributes corresponding to the preset identifier of the service description file of each implementation object; Merging a first data set of the own attributes and a second data set of the extended attributes of the service description file of each implementation object to obtain a third data set; Determine the distribution of elements of the same type in the third data set of the business description file of each implementation object; Confirm whether there are iterative elements in the distribution of the same type of elements. If so, remove the redundant number of iterative factors. Otherwise, no subsequent operation is required. Constructing multiple data sequences of the same type of elements in the third data set of the business description file of each implementation object; Acquire a preset attribute value of each element, and obtain multiple attribute sequences in a third data set of the business description file of each implementation object according to the preset attribute value of each element and the multiple data sequences; Combine multiple attribute sequences in the third data set of the business description file of each implementation object to obtain the attribute data sequence in the response information of each implementation object.

2. The engineering business requirements analysis method according to claim 1 is characterized in that: The basic analysis items include: general description of the field, three static and two dynamic demand stratification, virtual classification and embedded management system.

3. The engineering business requirements analysis method according to claim 1 is characterized in that: The process of converting the brainstorming ideas conceived by business experts based on the RDM requirements analysis method into engineering project business requirements includes: Obtaining basic information of a preset number of business experts, and selecting a plurality of suitable target business experts according to the basic information; Inputting the brainstorming results of the target business experts into the business demand training model to obtain output results; Based on the output results, the corresponding business project type is determined by using the RDM method and the business requirements of business experts are obtained to be converted into engineering project business requirements; Develop a schedule for demand analysis based on the business project type corresponding to the business needs of the engineering project.

4. The engineering business requirements analysis method according to claim 1 is characterized in that: The basic analysis of the business requirements of the engineering project includes: Determine the business content corresponding to the business requirements of the engineering project by using RDM method; Determine the business domain description, business template and embedded management links corresponding to the business requirements of the engineering project based on the business content; Draw the business panorama and business process diagram corresponding to the business needs of the engineering project based on the business domain description, business templates and embedded management links corresponding to the business needs of the engineering project; The business panorama and business process diagram are structured to obtain a demand analysis table corresponding to the business requirements of the engineering project.

5. The engineering business requirements analysis method according to claim 1 is characterized in that: The mining of surrounding businesses for the engineering project business needs and the overall analysis of the engineering project business needs based on the mining results include: Explore the related businesses around the engineering project business needs and determine the business relationship between the engineering project business and each related business; Selecting an adapted business reference model from a preset model library according to the business relationship between the engineering project business and each associated business; Using the business reference model that is adapted to the engineering project business and each associated business, describe the process positioning diagram of the engineering project business and the integration relationship diagram between the engineering project business and the associated business; The system division, core documents, key business data, and non-core data information of the engineering project business are obtained, and a data relationship table is generated to describe the relationship between the engineering project business and the above information.

6. The engineering business requirements analysis method according to claim 1 is characterized in that: The method further comprises: Obtain business reference models related to the business requirements of engineering projects; Packaging the engineering project business requirements and the business reference model related thereto into a specific organizational form; After packaging is completed, import it into the preset demand base account library; Set sample tags and index tags for the engineering project business requirements and their related business reference models in the preset requirement base library.

7. An engineering business demand analysis system, characterized in that: The system includes: A generation module, used to adaptively generate an RDM demand analysis method according to a preset business generation principle; A conversion module, used to convert the brainstorming ideas conceived by business experts based on the RDM demand analysis method into engineering project business requirements; A first analysis module is used to perform basic analysis on the business requirements of the engineering project; The second analysis module is used to mine surrounding businesses for the engineering project business needs, and conduct an overall analysis of the engineering project business needs based on the mining results; The method for adaptively generating RDM demand analysis according to a preset business generation principle includes: Form a project requirements group based on the preset business generation principles for different businesses; Select a target writing environment according to the formed project requirement group, the target writing environment includes: a remote online writing environment and an offline writing environment; If the target writing environment is a remote online writing environment, start the Xmind mind map tool; Generate an RDM requirement analysis method based on the basic rules of different business requirements in the project requirement group and the Xmind mind map tool; Before generating the RDM requirement analysis method according to the basic rules of different business requirements in the project requirement group in combination with the Xmind mind map tool, the system is also used to: Obtain the logical parameters of the business process corresponding to each business during the implementation phase; Determine the response information of the implementation object corresponding to each business process according to the logical parameters of the business process in the implementation stage; Obtaining a sequence of attribute data of the response information; Determine the rule parameters corresponding to the attribute data sequence, and construct a mapping relationship between the attribute data sequence and the rule parameters; Generate basic rules for the business requirements of each business based on the mapping relationship between the attribute data sequence and the rule parameters of the business; The step of obtaining the attribute data sequence of the response information includes: Extract metadata from the response information of each implementation object; Retrieve the business description file corresponding to each implementation object according to the metadata in the response information of the implementation object; Obtaining a preset identifier corresponding to a business description file based on each implementation object; Determine the inherent attributes and extended attributes corresponding to the preset identifier of the service description file of each implementation object; Merging a first data set of the own attributes and a second data set of the extended attributes of the service description file of each implementation object to obtain a third data set; Determine the distribution of elements of the same type in the third data set of the business description file of each implementation object; Confirm whether there are iterative elements in the distribution of the same type of elements. If so, remove the redundant number of iterative factors. Otherwise, no subsequent operation is required. Constructing multiple data sequences of the same type of elements in the third data set of the business description file of each implementation object; Acquire a preset attribute value of each element, and obtain multiple attribute sequences in a third data set of a business description file of each implementation object according to the preset attribute value of each element and the multiple data sequences; Combine multiple attribute sequences in the third data set of the business description file of each implementation object to obtain the attribute data sequence in the response information of each implementation object.

Images