A mind-map demand modeling method and system

The mind map-based demand modeling method solves the problem of low efficiency in software demand modeling in the existing technology by building tree structures and node links, and realizes efficient software demand logic modeling, which improves the quality and efficiency of software engineering. .

CN118862532BActive Publication Date: 2024-12-06NANJING HEDU SOFTWARE TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411349171.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-09-26
Publication Date
2024-12-06
Estimated Expiration
2044-09-26

AI Technical Summary

Technical Problem

The existing software requirements modeling method cannot implement an integrated model of 'one graph to the end', with low reading comprehension efficiency, low modeling efficiency and model change and iteration efficiency, and there are a large number of element layout and alignment work, which reduces the modeling Practicality.

Method used

Using the mind mapped requirements modeling method, the structured, visualized, and digital software requirements logic model is realized by constructing a mind mapped software requirements logic metamodel, including business logic modeling, functional logic modeling and model building view. Use tree structure and node links to achieve integrated display of business logic and functional logic.

Benefits of technology

It greatly improves the reading comprehension efficiency of demand logic, reduces the descriptive workload, improves the efficiency of modeling and iterative models, replaces multiple unstructured demand documents, improves the efficiency and quality of demand definition, and promotes the software engineering Reduce costs, increase efficiency and resolve risks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118862532B_ABST
    Figure CN118862532B_ABST
Patent Text Reader

Abstract

The present invention discloses a mind-map type requirement modeling method and system, the method provides a set of mind-map type software requirement logic meta-model and software requirement logic modeling steps based on the meta-model, so as to construct a software requirement logic model of the target software, namely, a target model. The target model is composed of a plurality of model products and a plurality of model views, each of which is structuredly described in a mind-map manner and linked to each other as required by the description, and can describe the business logic and functional logic of the target software in an integrated and penetrating manner. The method and system are applied in software development and iteration, and can quickly construct and iterate a structured, visualized, and digital software requirement logic model, replacing multiple offline scattered unstructured requirement documents, improving the description efficiency, description quality, and readability of the software requirement definition, and thus improving the software development and iteration efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of software requirement modeling, and in particular to a mind-map type requirement modeling method and system. Background Art

[0002] Software requirements analysis is the process in which the requirements analyst, after in-depth and detailed research and analysis, transforms and iterates the collection of specific requirements put forward by multi-level and different role users for the target software in different forms throughout the life cycle of the target software into a complete, unambiguous, and logically self-consistent software requirements logic model in batches in a timely manner. The software requirements definition continuously iterated by software requirements analysis is an important intermediate product of software development and iteration, and the basis for software design, programming, testing and acceptance, which has a significant impact on the efficiency, quality, cost and delivery of software engineering.

[0003] At present, a large number of software projects still use unstructured documents to describe and iterate software requirements. These unstructured documents have poor description standardization, are time-consuming to read and understand, require laborious revision and iteration, and have low review efficiency, so that the review is often insufficient, resulting in uncontrollable quality of software requirements definition, which is full of errors, omissions, inconsistencies and expired requirements definitions, which in turn leads to a large amount of rework waste, low efficiency and low quality, slow launch and difficult acceptance in the software design, programming and testing process.

[0004] The DFD requirement modeling method is a typical structured requirement analysis modeling method. It was created in the 1970s. It starts from the data flow of the application system and graphically depicts and represents the data processing process and data flow in a specific business system. The requirement model constructed by DFD is too abstract and lacks description of business processes and human-computer interaction.

[0005] The use case requirement modeling method is a typical object-oriented requirement analysis modeling method. The requirement model constructed by this method consists of a use case diagram and a use case specification. The latter describes the use case details in the form of a document, and embeds state diagrams, activity diagrams, and sequence diagrams to assist in the description. The granularity of the use case in the use case requirement modeling method is very flexible and difficult to master. The description of the use case specification is cumbersome and inefficient, and the drawing efficiency of various diagrams is low.

[0006] The above two methods are the main demand modeling methods in the industry, and they have the following common problems:

[0007] 1) There is no integrated model that covers the entire picture, so the reading comprehension efficiency is low.

[0008] It is not possible to construct a network-based software requirement logic model that covers multi-level logic blocks of business logic and functional logic in a unified way and explicitly expresses the relationship between logic blocks. It is also not possible to explicitly penetrate from the top level of multi-level business logic to the bottom level of multi-level functional logic in the model.

[0009] 2) Modeling efficiency is low, and model change iteration efficiency is even lower.

[0010] Using various primitives to express the logic blocks in the model, the layout, alignment, resizing and spacing of a large number of primitives have nothing to do with the description logic, but it takes a lot of time. In particular, the demand model is continuously iterated, and the many carefully arranged primitives need to be rearranged frequently, which greatly reduces the practicality of these modeling methods. Summary of the invention

[0011] Technical purpose:

[0012] In response to the above technical problems, the present invention proposes a mind-mapping requirement modeling method and system, which can quickly build and iterate a structured, visual, and digital software requirement logic model, realize practical and efficient requirement modeling, improve the integration, reading comprehension efficiency, description efficiency and quality of software requirement definition, and promote cost reduction, efficiency improvement and risk mitigation in the software engineering industry.

[0013] Technical solution:

[0014] A mind-map requirement modeling method includes a mind-map software requirement logic meta-model and a software requirement logic modeling step based on the meta-model, thereby constructing a requirement logic model of a target software, namely, a target model;

[0015] The target model is composed of a plurality of model products and a plurality of model views, and each model product and each model view is structuredly described using a mind map;

[0016] The steps of software requirement logic modeling based on the metamodel include:

[0017] Step 1: Business logic modeling:

[0018] A business structure artifact and a corresponding artifact graph are constructed for the target model. The artifact graph includes an artifact definition node of the business structure artifact as a root node. One or more business domain component definition nodes having a hierarchical relationship are extended and added after the artifact definition node of the business structure artifact to define the business domain components.

[0019] Build zero or more business process artifacts for the target model. For each business process artifact, create a corresponding artifact diagram. The artifact diagram contains an artifact definition node of the business process artifact as the root node, a flowchart structure node, and a business scenario structure node. Expand the resource node after the flowchart structure node to link the flowchart uploaded and stored in advance.

[0020] Build zero or more business object artifacts and create zero or more business service artifacts for the target model. For each business service artifact or business service artifact, create a corresponding artifact diagram. The artifact diagram contains an artifact definition node of the business object artifact or business service artifact as the root node, a business rule structure node, a user story structure node, and a business process logic structure node.

[0021] On the product definition nodes of business process products, business object products and business service products, set the information including number, name and business domain respectively; expand the component group nodes with hierarchical relationship after various structure nodes of business process products, business object products and business service products, build the node tree corresponding to the structure node, expand and add component definition nodes after the last node of each node tree, and build the corresponding component diagram; add component link points in the business-related component diagram;

[0022] The business structure artifact, business process artifact, business object artifact and business service artifact constitute the business model artifact of the target model;

[0023] Step 2: Functional logic modeling:

[0024] Construct a functional structure artifact and a corresponding artifact diagram for the target model. The artifact diagram includes an artifact definition node of the functional structure artifact as a root node. One or more functional component definition nodes with a hierarchical relationship are extended after the artifact definition node of the business structure artifact to define the functional module components.

[0025] Build zero or more user interface artifacts for the target model. For each user interface artifact, create a corresponding artifact graph, which includes an artifact definition node of the user interface artifact as a root node, an interface view structure node, a parameter variable structure node, an interface rule structure node, an interface event capability structure node, and an interface basic capability structure node.

[0026] Build zero or more interactive function artifacts for the target model. For each interactive function artifact, create a corresponding artifact diagram. The artifact diagram contains an artifact definition node of the interactive function artifact as the root node, a target structure node, a main use case structure node, and an other use case structure node.

[0027] Construct zero or more timing function products and create zero or more interface products for the target model. For each timing function product or interface product, create a corresponding product graph. The product graph contains a product definition node of the timing function product or interface function product as a root node and a target structure node.

[0028] On the product definition nodes of the functional structure products, user interface products, interactive function products, timing function products and interface function products, set the information including number, name and function module respectively; expand the component group node with hierarchical relationship after the user interface products, interactive function products, timing function products and interface function products, build a node tree corresponding to the structure node, expand and add component definition nodes after the last node of each node tree, and build the corresponding component diagram; add component link points in the business-related component diagram;

[0029] The business structure product, user interface product, interactive function product, timing function product and interface function product constitute the functional model product of the target model;

[0030] Step 3: Build the model view:

[0031] Build a business map based on the constructed business model artifacts;

[0032] Build a functional map based on the constructed functional model artifacts;

[0033] Build the overall model map based on the constructed business map and functional map;

[0034] The business map, function map and model overview map constitute the model view of the target model;

[0035] The business model artifacts, functional model artifacts and model views together constitute the target model.

[0036] Preferably, the model product has a unique number, a name, zero or more parts and a product diagram, wherein the product diagram is a tree-structured description diagram of the model product in the form of a mind map, and is composed of a product definition node and a multi-level sub-node set thereof;

[0037] The component refers to an independent description unit within the model product to which it belongs, and has a unique number, a name, and a component diagram. The component diagram refers to a tree-structured description diagram of the component in the form of a mind map, which is a sub-diagram of the product diagram of the model product to which the component belongs, and is composed of a component definition node and its multi-level sub-node set;

[0038] The model view refers to a mind-map-style classification summary of model products in the target model, including a business map, a functional map and a model overview map;

[0039] The model products and components are collectively referred to as modules. The product diagram and model view include multiple types of nodes: module definition node, module structure node, module group node, module description node, extended description resource node, module link node; among them,

[0040] The module definition node includes a product definition node and a component definition node; the product definition node refers to the root node of the product graph, which contains information including product type, product number, product name and product version number; product definition nodes of different types of products have node styles with different shapes, colors and icons;

[0041] The component definition node refers to the root node of the component diagram, which contains information including component type, component number, component name and component version number; component definition nodes of different types of components have node styles with different shapes, colors and icons;

[0042] The module structure node includes a product structure node and a component structure node; the product structure node refers to an inherent child node of a product definition node, including information such as a node title, and is used to divide a product diagram, and a multi-level child node set of each structure node describes a part of the logic of the model product to which it belongs; the component structure node refers to an inherent child node of a component definition node, including information such as a node title, and is used to divide a component diagram, and a multi-level child node set of each structure node describes a part of the logic of the component to which it belongs;

[0043] The module group node includes a product group node and a component group node; the product group node is used to group products in the model view, and contains information including the group name;

[0044] The module description node refers to the smallest description unit of model products and components, including information such as description type, node title and description content; the multi-level description node set under the model product or component structure node describes part of the logic of the model product or component; description nodes of different description types have different semantics and different node styles;

[0045] The extended description resource nodes include picture nodes, file nodes and hyperlink nodes, which are used for extended description of the module;

[0046] The module link node includes a product link node and a component link node; the product link node refers to a node representing a model product outside the product diagram to which it belongs, and contains information including the product type, product number, product name and product version number. A product is integrated into other product diagrams and model views in the form of a product link node; the node style of the product link node is consistent with the node style of the product definition node of the model product it represents; the component link node refers to a node representing a component outside the component diagram to which it belongs, and contains information including the component type, component number, component name and component version number; a component is integrated into other component diagrams and other product diagrams of the model product to which it belongs in the form of a component link node; the node style of the component link node is consistent with the node style of the component definition node of the component it represents.

[0047] Preferably, the business structure artifact is used to describe a business domain set of a target model; a target model has one and only one business structure artifact, and a business structure artifact includes one or more business domain components with a hierarchical relationship; the business domain component is used to define a business domain of the target model;

[0048] The business process artifact is used to describe the business process of the target model; a target model has zero or more business process artifacts, and a business process artifact includes at least one business scenario component; the business scenario component is used to describe the sub-process of the business process artifact in the selected scenario;

[0049] The business object artifact is used to describe the business requirement logic unit related to business data in the business domain; a target model has one or more business object artifacts, and a business object artifact contains zero or more business rule components, zero or more user story components, and zero or more business processing logic components;

[0050] The business service artifact is used to describe the business requirement logic unit related to the business object within the business domain; a target model has zero or more business service artifacts, and a business service artifact contains zero or more business rule components, zero or more user story components, and zero or more business processing logic components.

[0051] Preferably, the functional structure artifact is used to describe a set of functional modules of a target model; a target model has one and only one functional structure artifact, and a functional structure artifact includes one or more functional module components with a hierarchical relationship; the functional module component defines a functional module of the target model;

[0052] The user interface artifact is used to describe a user interface of a target model; a target model has one or more user interface artifacts, and a user interface artifact includes one or more interface view components, one or more interface rule components, one or more interface event capability components, and zero or more interface basic capability components; wherein the interface view component is used to describe the interface graphic structure of the user interface in a certain mode, and the interface rule component includes a general interface component for describing the interface end processing logic of the topic related to the user interface, and a data control component for describing the input and output data control logic of the user interface artifact; the interface event capability component is used to describe the interface end processing logic and business data processing logic of the user interface artifact in response to human-computer interaction events; the interface basic capability component is used to describe the common interface end processing logic and business data processing logic that appear in the event response logic of multiple interface event components;

[0053] The interactive functional artifact is used to describe the system functional use case of the human-computer interaction type of the target model; a target model has one or more interactive functional artifacts;

[0054] The timing function artifact is used to describe the system function of the target model triggered by time. A target model has one or more timing function artifacts;

[0055] The interface function product is used to describe the system interface opened by the target model to the external system. A target model has one or more interface function products.

[0056] Preferably, the business map refers to a mind-map classification summary of business model products belonging to the final business domain;

[0057] The functional map refers to a mind-map summary of the user interface products, interactive function products, timing function products, and interface function products belonging to the final functional module;

[0058] The model overview diagram refers to a mind-map summary diagram of all model products of the target model.

[0059] Preferably, the step 1, business logic modeling specifically includes:

[0060] Step 1.1: Build the business structure artifact and the business domain components it contains:

[0061] Step 1.1.1, create a product diagram of a new business structure product, including a product definition node of the business structure product as a root node;

[0062] Step 1.1.2, extending and adding one or more business domain component definition nodes having a hierarchical relationship after the product definition node of the business structure product;

[0063] Step 1.1.3, set the information including the business domain number and name on each business domain component definition node to complete the definition of the business domain component;

[0064] Step 1.2: Build the business process artifact and the business scenario components it contains:

[0065] Step 1.2.1, create a product diagram of a new business process product, including a product definition node of the business process product as the root node, a flowchart structure node, and a business scenario structure node;

[0066] Step 1.2.2: Set the number, name, business domain and other information on the product definition node of the business process product to complete the definition of the business process product.

[0067] Step 1.2.3, add one or more resource nodes after the flowchart structure node, set the storage path of the picture or file of the flowchart of the business process product in the file management system on the resource node, and complete the link of the flowchart. The picture or file of the flowchart is uploaded and stored in the file management system in advance;

[0068] Step 1.2.4, after the business scenario structure node, zero or more component group nodes with a hierarchical relationship are added, and the business scenario structure node and the corresponding component group node constitute a business scenario group node tree;

[0069] After a last-level node in the business scenario group node tree, a business scenario component definition node is added and expanded, and information including a number and a name is set on the business scenario component definition node to complete the definition of the business scenario component;

[0070] Take each business scenario component definition node as the root node and build the corresponding business scenario component graph;

[0071] Step 1.3: Build the business object artifact and its information structure components, common business rule components, user story components, business transaction components, and basic logic components:

[0072] Step 1.3.1, create a product diagram of a new business object product, including a business object product definition node as the root node, a business rule structure node, a user story structure node, and a business process logic structure node;

[0073] Step 1.3.2: Set the information including the number, name, and business domain on the product definition node of the business object product to complete the definition of the business object product.

[0074] Step 1.3.3, after the business rule structure node, zero or more component group nodes with a hierarchical relationship are added, and the business rule structure node and the corresponding component group node constitute a business rule group node tree;

[0075] After a last-level node of the business rule group node tree, expand and add an information structure component definition node or a general business rule component definition node, set the information including number, name, and type on the information structure component definition node to complete the definition of the information structure component, and set the information including number, name, and type on the general business rule component definition node to complete the definition of the general business rule component;

[0076] Taking the information structure component definition node as the root node, the information structure component diagram is extended and constructed; taking the general business rule component definition node as the root node, the general business rule component diagram is extended and constructed;

[0077] Step 1.3.4, add zero or more component group nodes with hierarchical relationships after the user story structure node. The user story structure node and the corresponding component group node constitute a user story group node tree;

[0078] After a last-level node in the user story group node tree, expand and add a user story component definition node, set the information including number, name, and type on the user story component definition node, and complete the definition of the user story component;

[0079] Take the user story component definition node as the root node and expand to build the user story component diagram;

[0080] Step 1.3.5, after the business processing logic structure node, zero or more component group nodes with a hierarchical relationship are added, and the business processing logic structure node and the corresponding component group node constitute a business processing logic group node tree;

[0081] Expand and add a business transaction component definition node after a last-level node of the business processing logic group node tree, set information including number, name, and type on the business transaction component definition node, and complete the definition of the business transaction component;

[0082] Taking the business transaction component definition node as the root node, expand and construct the business transaction component graph;

[0083] In the user story component diagram associated with the business transaction component, add a business transaction component link node;

[0084] Step 1.3.6, expand and add a basic logic component definition node after a last node of the business processing logic group node tree described in step 1.3.5, and set the information including number, name, and type on the basic logic component definition node to complete the definition of the basic logic component;

[0085] Taking the basic logic component definition node as the root node, expand and construct the basic logic component graph;

[0086] Add a basic logic component link node to a business transaction component diagram or other component diagram associated with the basic logic component;

[0087] Step 1.4: Build business service artifacts and their common business rule components, user story components, business transaction components, and basic logic components:

[0088] Step 1.4.1, create an initialization artifact diagram of a new business service artifact, including an artifact definition node of the business service artifact as the root node, a business rule structure node, a user story structure node, and a business process logic structure node;

[0089] Step 1.4.2: Set the number, name, business domain and other information on the product definition node of the business service product to complete the definition of the business service product.

[0090] Step 1.4.3, after the business rule structure node, zero or more component group nodes with a hierarchical relationship are added, and the business rule structure node and the corresponding component group node constitute a business rule group node tree;

[0091] After a last node of the business rule group node tree, expand and add a general business rule component definition node, set the information including number, name, and type on the general business rule component definition node, and complete the definition of the general business rule component;

[0092] Taking the general business rule component definition node as the root node, expand and construct the general business rule component graph;

[0093] Step 1.4.4, add zero or more component group nodes with hierarchical relationships after the user story structure node. The user story structure node and the corresponding component group node constitute a user story group node tree;

[0094] After a last-level node in the user story group node tree, expand and add a user story component definition node, set the information including number, name, and type on the user story component definition node, and complete the definition of the user story component;

[0095] Take the user story component definition node as the root node and expand to build the user story component diagram;

[0096] Step 1.4.5, after the business processing logic structure node, zero or more component group nodes with a hierarchical relationship are expanded and added, and the business processing logic structure node and the corresponding component group node constitute a business processing logic group node tree;

[0097] Expand and add a business transaction component definition node after a last-level node of the business processing logic group node tree, set information including number, name, and type on the business transaction component definition node, and complete the definition of the business transaction component;

[0098] Taking the business transaction component definition node as the root node, expand and construct the business transaction component graph;

[0099] In the user story component diagram associated with the business transaction component, add a business transaction component link node;

[0100] Step 1.4.6, expand and add a basic logic component definition node after a last-level node of the business processing logic group node tree described in step 1.4.5, and set information including number, name, and type on the basic logic component definition node to complete the definition of the basic logic component;

[0101] Taking the basic logic component definition node as the root node, expand and construct the basic logic component graph;

[0102] Add a basic logic component link node to the business transaction component diagram or other component diagram associated with the basic logic component.

[0103] Preferably, the step 2, functional logic modeling, specifically includes:

[0104] Step 2.1: Construct the functional structure product and its functional module components:

[0105] Step 2.1.1, create an initialization artifact graph of a new functional structure artifact, including an artifact definition node of the functional structure artifact as a root node;

[0106] Step 2.1.2, extending and adding one or more function module component definition nodes having a hierarchical relationship after the product definition node of the functional structure product;

[0107] Step 2.1.3, set the information including the function module number and name on each function module component definition node to complete the definition of the function module component;

[0108] Step 2.2: Build the user interface product and its included interface view components, general interface rule components, data control components, interface event capability components and interface basic capability components:

[0109] Step 2.2.1, create a product diagram of a new user interface product, including a product definition node of the user interface product as a root node, an interface view structure node, a parameter variable structure node, an interface rule structure node, an interface event capability structure node, and an interface basic capability structure node, wherein the parameter variable structure node has three child nodes, namely, an input parameter structure node, an output parameter structure node, and an interface variable structure node;

[0110] Step 2.2.2, set the information including number, name, and function module on the product definition node of the user interface product to complete the definition of the user interface product;

[0111] Step 2.2.3, expand and add an interface view component definition node after the interface view structure node, and then set the information including the number and name on the interface view component definition node to complete the definition of the interface view component;

[0112] Taking the interface view component definition node as the root node, expand and construct the interface view component graph;

[0113] Step 2.2.4, add zero or more description nodes after the input parameter structure node to define and describe the input parameters of several user interfaces;

[0114] After the output parameter structure node, zero or more description nodes are added to define and describe the output parameters of several user interfaces;

[0115] Add zero or more description nodes after the interface variable structure node to define and describe several internal variables of the user interface;

[0116] Step 2.2.5, after the interface rule structure node, zero or more component group nodes with a hierarchical relationship are added, and the interface rule structure node and the corresponding component group node constitute an interface rule group node tree;

[0117] After a last node of the interface rule group node tree, expand and add a general interface rule component definition node, set the number, name, type and other information on the general interface rule component definition node, and complete the definition of the general interface rule component; after a last node of the interface rule group node tree, expand and add a data control component definition node, set the number, name, type and other information on the data control component definition node, and complete the definition of the data control component;

[0118] Taking the general interface rule component definition node as the root node, expand and build the general interface rule component diagram; taking the data control component definition node as the root node, expand and build the data control component diagram;

[0119] Step 2.2.6, after the interface basic capability structure node, expand and add zero or more component group nodes with a hierarchical relationship, and the interface basic capability structure node and the corresponding component group node constitute the interface basic capability group node tree;

[0120] After a last node of the interface basic capability group node tree, expand and add an interface basic capability component definition node, set the information including number, name, and type on the interface basic capability component definition node, and complete the definition of the interface basic capability component;

[0121] Take the interface basic capability component definition node as the root node and expand and build the interface basic capability component diagram;

[0122] Step 2.2.7, after the interface event capability structure node, expand and add zero or more component group nodes with a hierarchical relationship, and the interface event capability structure node and the corresponding component group node constitute an interface event capability group node tree;

[0123] After a last node of the interface event capability group node tree, an interface event capability component definition node is added, and information including number, name, and type is set on the interface event capability component definition node to complete the definition of the interface event capability component;

[0124] Taking the interface event capability component definition node as the root node, expand and construct the interface event capability component diagram;

[0125] Step 2.3: Build interactive functional products:

[0126] Step 2.3.1, create an initialization artifact diagram of a new interactive function artifact, including an artifact definition node of the interactive function artifact as a root node, a target structure node, a main use case structure node, and an other use case structure node;

[0127] Step 2.3.2, set the information including number, name, and function module on the product definition node of the interactive function product to complete the definition of the interactive function product;

[0128] Step 2.3.3, adding a description node indicating the execution meaning after the target structure node of the interactive function product, and adding a business transaction component link node after the description node indicating the execution meaning;

[0129] Step 2.3.4, after the main use case structure node, expand and add zero or more description nodes describing user operations, expand and add a description node representing system response after the description node describing each user operation, expand and add an interface event capability component link node, zero or one user interface product link node, and zero or one interface view component link node after each description node representing system response;

[0130] Step 2.3.5, expand and add zero or more description nodes that define use cases after other use case structure nodes, expand and add one or more description nodes that describe user operations after each use case description node, expand and add a description node that represents system response after each description node that describes user operations, expand and add an interface event capability component link node, zero or one user interface artifact link node, and zero or one interface view component link node after each description node that represents system response;

[0131] Step 2.4: Build a timing function product:

[0132] Step 2.4.1, create a product diagram of a new timed function product, including a product definition node of the timed function product as a root node and a target structure node;

[0133] Step 2.4.2, set the information including number, name, and function module on the product definition node of the timing function product;

[0134] Step 2.4.3, after the target structure node of the timing function product, expand and add a description node indicating the execution meaning, and expand and add a business transaction component link node after the description node;

[0135] Step 2.5: Build interface functional products:

[0136] Step 2.5.1, create a product diagram of the new interface function product, including a product definition node of the timing function product as the root node and a target structure node;

[0137] Step 2.5.2, set the information including number, name, and function module on the product definition node of the interface function product;

[0138] Step 2.5.3: After the target structure node of the interface function product, expand and add a description node indicating the execution meaning, and expand and add a business transaction component link node after the description node.

[0139] Preferably, the step 3, constructing the model view specifically includes:

[0140] Step 3.1: Build a business map:

[0141] Step 3.1.1, each final business domain constructs an initialization business map, including a root node and the corresponding component link node of the final business domain component;

[0142] Step 3.1.2, expand and add 0 or more product group nodes with a hierarchical relationship after the business map root node, and the business map root node and the corresponding product group node constitute the business map product group node tree;

[0143] Step 3.1.3, after each last node of the business map product group node tree, expand and add 0 or more business process product link nodes, 0 or more business object product link nodes, and 0 or more business service product link nodes;

[0144] Step 3.2: Build a functional map:

[0145] Step 3.2.1, each final functional module constructs an initialization function map including a root node as a component link node of the corresponding final functional module component;

[0146] Step 3.2.2, after the function map root node, expand and add 0 or more product group nodes with a hierarchical relationship, the function map root node and the corresponding product group node constitute the function map product group node tree;

[0147] Step 3.2.3, after each last level node of the function map product group node tree, expand and add 0 or more interactive function product link nodes, 0 or more timing function product link nodes, 0 or more interface function product link nodes, and 0 or more user interface product link nodes;

[0148] Step 3.3: Build the overall model diagram:

[0149] Step 3.3.1. For each target model, construct an initial model graph with a root node representing the target model.

[0150] Step 3.3.2, expand and add a business structure product link node after the root node of the model general diagram, and according to the hierarchical relationship of the business domain components in the business structure product diagram, expand and add corresponding business domain component link nodes layer by layer after the business structure product link node; the corresponding business domain component link nodes constitute a business domain component node tree;

[0151] Step 3.3.3, after each last node of the business domain component node tree, expand and add the node set of the business map of the corresponding business domain component, excluding its root node;

[0152] Step 3.3.4, expand and add a function structure product link node after the root node of the model general diagram, and expand and add corresponding function module component link nodes layer by layer after the function structure product link node according to the hierarchical relationship of the function module components in the function structure product diagram; the corresponding function module component link nodes constitute a function module component node tree;

[0153] Step 3.3.5, after each last node of the function module component node tree, expand and add the node set of the function map of the corresponding function module component, excluding its root node.

[0154] A mind-map requirement modeling system with the following modules:

[0155] Model management module, used to create new models, query models, modify models, and delete models;

[0156] Business model product management module, namely:

[0157] The business structure artifact management module is used to generate business structure artifacts for the target model, edit business structure artifact diagrams, and view business structure artifact diagrams;

[0158] The business process artifact management module is used to create new business process artifacts for the target model, edit business process artifact diagrams, query business process artifacts, view business process artifact diagrams, and delete business process artifacts;

[0159] The business object artifact management module is used to create a new business object artifact for the target model, edit the business object artifact diagram, query the business object artifact, view the business object artifact diagram, and delete the business object artifact;

[0160] The business service artifact management module is used to create new business service artifacts for the target model, edit business service artifact graphs, query business service artifacts, view business service artifact graphs, and delete business service artifacts;

[0161] Functional model product management module, namely:

[0162] Functional structure artifact management module, used to generate functional structure artifacts for target models, edit functional structure artifact diagrams, and view functional structure artifact diagrams;

[0163] A user interface artifact management module is used to create a new user interface artifact for a target model, edit a user interface artifact diagram, query a user interface artifact, view a user interface artifact diagram, and delete a user interface artifact;

[0164] An interactive function artifact management module is used to create a new interactive function artifact for a target model, edit an interactive function artifact diagram, query an interactive function artifact, view an interactive function artifact diagram, and delete an interactive function artifact;

[0165] The timing function product management module is used to create a new timing function product for the target model, edit the timing function product diagram, query the timing function product, view the timing function product diagram, and delete the timing function product;

[0166] The interface function artifact management module is used to create a new interface function artifact for the target model, edit the interface function artifact diagram, query the interface function artifact, view the interface function artifact diagram, and delete the interface function artifact;

[0167] Model view management module, namely:

[0168] Business map management module, used to create a new business map for the target model, edit the business map, and view the business map;

[0169] Function map management module, used to create a new function map for the target model, edit the function map, and view the function map;

[0170] The model master diagram management module is used to create a new model master diagram for the target model, edit the model master diagram, and view the model master diagram.

[0171] A computer-readable storage medium stores a computer program, which implements the method when executed by a processor.

[0172] A computer program product comprises a computer program or instructions, and when the computer program or instructions are executed by a processor, the method is implemented.

[0173] A computer device comprising:

[0174] one or more processors;

[0175] A storage device for storing one or more programs;

[0176] When the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method.

[0177] Beneficial effects: Due to the adoption of the above technical solution, the present invention has the following beneficial effects:

[0178] (1) The various model units such as model products and model views constructed by the present invention are uniformly described in the form of a mind map, and the various model units are associated and connected in series through model unit link nodes, so that all business logic and functional logic can be penetrated in one map, which greatly improves the reading and comprehension efficiency of the demand logic.

[0179] (2) The method of the present invention uses mind mapping to draw pictures. Compared with unstructured documents, it saves a lot of description workload by pre-defining visual nodes. Compared with primitive assembly modeling, it does not require layout, alignment, spacing adjustment, and size adjustment. It is convenient to add and remove logic, can be quickly operated by keyboard, and can be operated in batches, which greatly improves the efficiency of building models and iterating models.

[0180] (3) This method and system can be applied in software development and iteration to quickly build and iterate a structured, visual, and digital software requirement logic model, replacing multiple "offline, scattered, unstructured requirement documents", greatly improving the description efficiency, reading efficiency, and iteration efficiency of requirement definition, and greatly improving the efficiency and quality of requirement analysis, thereby achieving agile delivery, reducing costs, mitigating risks, and improving performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0181] Figure 1 A flowchart of a mind-map type demand modeling method proposed by the present invention;

[0182] Figure 2 A schematic diagram of the structure of the software requirement logic model proposed by the present invention;

[0183] Figure 3 A flowchart for modeling the business logic proposed by the present invention;

[0184] Figure 4 A flow chart for modeling the functional logic proposed by the present invention;

[0185] Figure 5 A flowchart of constructing a model view proposed by the present invention;

[0186] Figure 6 An example product diagram of the business structure product proposed by the present invention;

[0187] Figure 7 An example product diagram of the business process product proposed by the present invention;

[0188] Figure 8a An example product diagram of the business object product proposed by the present invention;

[0189] Figure 8b for Figure 8a An example component diagram for a user story component in ;

[0190] Figure 9a An example product diagram of the business service product proposed by the present invention;

[0191] Figure 9b for Figure 9a An example component diagram of a business transaction component in ;

[0192] Fig.10 An exemplary product diagram of a functional structural product proposed by the present invention;

[0193] Fig.11a An example product diagram of a user interface product proposed by the present invention;

[0194] Fig.11b for Fig.11a An example diagram of the middle interface event capability structure node and its child node collection;

[0195] Fig.12a An example product diagram of an interactive product proposed by the present invention;

[0196] Figure 12b for Fig.12a Example diagrams of other use case structure nodes and their child node collections in;

[0197] Fig.13 An exemplary product diagram of a product with a timing function proposed by the present invention;

[0198] Fig.14 An example product diagram of the interface function product proposed by the present invention;

[0199] Fig.15 An example diagram of the business map proposed by the present invention;

[0200] Fig.16 An example diagram of the functional map proposed by the present invention;

[0201] Fig.17a An example diagram of the overall diagram of the model proposed by the present invention;

[0202] Fig.17b for Fig.17a The sample business map added to the model overview is expanded;

[0203] Fig.17c for Fig.17a In the model general diagram, the example function map is expanded and added;

[0204] Fig.18 This is a structural schematic diagram of a mind-map-based demand modeling system proposed by the present invention. DETAILED DESCRIPTION

[0205] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. The described embodiments are only part of the embodiments of the present invention, not all of the embodiments. The embodiments in the present invention and all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0206] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein may be embodied in a wide variety of forms, and any structure and / or function described herein is illustrative only. The present disclosure, those skilled in the art should understand that an aspect described herein may be implemented independently of any other aspect, and two or more of these aspects may be combined in various ways. For example, any number of aspects described herein may be used to implement the device and / or practice the method. In addition, other structures and / or functionalities other than one or more of the aspects described herein may be used to implement this device and / or practice this method.

[0207] Embodiment 1

[0208] This embodiment proposes a mind-map-based requirement modeling method, including a mind-map-based software requirement logic metamodel and a metamodel-based software requirement logic modeling step, so as to construct a requirement logic model of the target software, namely, the target model; the target model refers to a structured description of the business logic and functional logic of the target software.

[0209] The metamodel determines the structural characteristics of the target model, as follows:

[0210] M1) Overall structural features:

[0211] M1.1) The target model consists of several model artifacts and several model views. Each model artifact and each model view is structured using a mind map;

[0212] M1.2) Model product, referred to as product, refers to an independent description unit within the target model; a product has a unique number, a name, 0 or more parts and a product drawing;

[0213] The product diagram is a tree-structured description diagram of the product in the form of a mind map. It consists of a product definition node (product diagram root node) and its multi-level child node set. The multi-level child node set of the product definition node describes the internal structure and logic of the product.

[0214] A component is an independent descriptive unit within a product, with a unique number, a name, and a component drawing;

[0215] A component diagram is a tree-structured description diagram of a component in the form of a mind map. It is a sub-diagram of the product diagram of the product to which the component belongs. It consists of a component definition node and its multi-level child node set. The multi-level child node set of the component definition node describes the internal structure and logic of the component.

[0216] Products and components are collectively referred to as modules;

[0217] M1.3) Mind-map-style product diagrams and model views, consisting of the following types of nodes:

[0218] 1) Module definition node

[0219] Module definition nodes, including product definition nodes and component definition nodes;

[0220] The product definition node refers to the root node of the product graph, which contains information such as product type, product number, product name, and product version number;

[0221] Artifact definition nodes for different types of artifacts have node styles with different shapes, colors, and icons;

[0222] The component definition node refers to the root node of the component diagram, which contains information such as component type, component number, component name, and component version number;

[0223] Component definition nodes for different types of components have node styles with different shapes, colors, and icons;

[0224] 2) Module structure node

[0225] Module structure nodes, including product structure nodes and component structure nodes;

[0226] Artifact structure node refers to the inherent child node of the artifact definition node, which contains information such as node title and is used to divide the artifact graph. The multi-level child node set of each structure node describes a part of the artifact logic;

[0227] Different types of products have different product structure node sets, which have 0 or more product structure nodes;

[0228] A component structure node is an inherent child node of a component definition node. It contains information such as the node title and is used to divide the component graph. The multi-level child node set of each structure node describes a certain part of the logic of the component.

[0229] Different types of components have different component structure node sets, which have 0 or more component structure nodes;

[0230] 3) Module group node

[0231] Module group nodes, including product group nodes and component group nodes;

[0232] Artifact group node, used to group artifacts in the model view, including group name and other information;

[0233] The parent node of an artifact group node can be the root node of a model view or another artifact group node (parent group);

[0234] The child node of an artifact group node can be an artifact link node or another artifact group node (subgroup);

[0235] Component group node, used to group components in the product diagram, including information such as group name;

[0236] The parent node of a component group node can be a product structure node or another component group node (parent group) in the product diagram;

[0237] The child node of a component group node can be a component definition node or another component group node (subgroup);

[0238] 4) Module description node

[0239] Module description node, referred to as description node, refers to the smallest description unit of products and components, including description type and node title (description content) and other information; a multi-level description node set under a product or component structure node, describing the logic of this part of the product or component;

[0240] Description nodes of different description types have different semantics and different node styles;

[0241] 5) Extended description resource node

[0242] Extended description resource node, referred to as resource node, including picture node, file node, hyperlink node, used for extended description of module;

[0243] An image node refers to a node that represents an image, including information such as the node title (image name) and the image storage path;

[0244] A file node refers to a node that represents a file, and contains information such as the node title (file name) and the file storage path;

[0245] A hyperlink node refers to a node that represents an Internet web page, including information such as the node title and hyperlink URL;

[0246] 6) Module link node

[0247] Module link nodes, including product link nodes and component link nodes;

[0248] An artifact link node is a node that represents an artifact outside its artifact diagram, and contains information such as artifact type, artifact number, artifact name, and artifact version number. An artifact can be integrated into other artifact diagrams and model views in the form of an artifact link node.

[0249] The node style of the artifact link node is consistent with the node style of the artifact definition node of the artifact it represents;

[0250] A component link node is a node that represents a component outside its component diagram, and contains information such as component type, component number, component name, and component version number. A component can be integrated into other component diagrams and other product diagrams of the product to which it belongs in the form of a component link node.

[0251] The node style of the component link node is consistent with the node style of the component definition node of the component it represents;

[0252] M1.4) Business model products

[0253] Business model products refer to various model products that describe business logic;

[0254] Business model artifacts and their components include: business structure artifacts and their business domain components, business process artifacts and their business scenario components, business object artifacts and their components (business rule components, user story components, business processing logic components), business service artifacts and their components (business rule components, user story components, business processing logic components);

[0255] M1.5) Functional model products

[0256] Functional model products refer to various types of model products that describe functional logic;

[0257] Functional model products and their components include: functional structure products and their functional module components, user interface products and their components (interface view components, interface rule components, interface event capability components and interface basic capability components), interactive function products, timing function products, and interface function products;

[0258] M1.6) Model View

[0259] Model view refers to a mind-map-like classification summary of the artifacts in the target model, including: business map, functional map and model overview map.

[0260] M2) Structural characteristics of various model products

[0261] M2.1) Business model artifacts

[0262] M2.1.1) Business structure products

[0263] M2.1.1.1) M1.4 Business structure artifact, used to describe the business domain set of the target model;

[0264] A target model has only one business structure artifact; a business structure artifact contains one or more business domain components with hierarchical relationships;

[0265] Business domain components define a business domain of the target model;

[0266] M2.1.1.2) The product diagram of the business structure product is composed of one business structure product definition node (root node), one or more business domain component definition nodes with hierarchical relationships, etc.;

[0267] The component diagram of a business domain component consists of only one business domain component definition node;

[0268] M2.1.2) Business process artifacts

[0269] M2.1.2.1) The business process artifact referred to in M1.4 is used to describe a business process of the target model;

[0270] A target model has 0 or more business process artifacts; a business process artifact contains at least 1 business scenario component;

[0271] Business scenario components are used to describe the sub-process of the business process artifact in a certain scenario and reference one or more user story components (M2.1.3.1);

[0272] M2.1.2.2) The product diagram of a business process product consists of a business process product definition node (root node), a flowchart structure node and its sub-node set, a business scenario structure node and its sub-node set, etc.;

[0273] The sub-node set of the flowchart structure node is composed of 0 or more resource nodes; these resource nodes contain the image storage path or file storage path or webpage URL describing the business process graphic structure of the corresponding business process artifact;

[0274] The sub-node set of the business scenario structure node is composed of 0 or more component group nodes and 1 or more component graphs of business scenario components;

[0275] The component diagram of the business scenario consists of 1 business scenario component definition node (root node), 1 or more description nodes, 0 or more resource nodes, 1 or more component link nodes of user story components (M2.1.3.1), etc.

[0276] M2.1.3) Business object products

[0277] M2.1.3.1) The business object artifact referred to in M1.4 is used to describe the business requirement logic unit related to a business object (a certain type of business data) within a business domain;

[0278] A target model has one or more business object artifacts; a business object artifact contains zero or more business rule components, zero or more user story components, and zero or more business process logic components;

[0279] Business rule components, including general and information structure types;

[0280] A general business rule component, referred to as a general business rule component, is used to describe the business rules of a certain topic related to the business object to which it belongs;

[0281] The business rule component of the information structure type, referred to as the information structure component, is used to describe the information structure of the business object to which it belongs;

[0282] The user story component is used to describe a business operation activity of a certain type of user (a certain position / role) related to the business object under certain triggering conditions;

[0283] Business processing logic components, including two types: business transactions and basic logic;

[0284] Business transaction type business processing logic component, referred to as business transaction component, is used to describe the data processing logic of a business data processing task related to the business object; a business data processing task refers to an independently executable step in a business operation activity;

[0285] Basic logic type business processing logic component, referred to as basic logic component, is used to describe a common data processing logic that appears in multiple business transaction components related to the business object to which it belongs;

[0286] One information structure component can reference zero or more other information structure components (regardless of the business objects they belong to) as one or more of its own data elements; one information structure component can be referenced by zero or more other information structure components (regardless of the business objects they belong to);

[0287] A general business rule component can reference 0 or more other general business rule components (regardless of the business objects they belong to) as its own components; a general business rule component can be referenced by 0 or more other general business rule components (regardless of the business objects they belong to);

[0288] A user story component can reference one or more business transaction components (regardless of the business objects they belong to) as steps of the business activity it describes; a business data processing task described by a business transaction component can be referenced by the business activity described by one or more user story components (regardless of the business objects they belong to);

[0289] One business logic processing component (business transaction component or basic logic component) can reference zero or more business rule components (regardless of the business objects they belong to) that need to be followed; one business rule component can be referenced by one or more business logic processing components (regardless of the business objects they belong to);

[0290] One business logic processing component (business transaction component or basic logic component) can reference zero or more other business logic processing components (regardless of the business objects they belong to) as certain steps of the data processing logic described by itself; one business logic processing component can be referenced by zero or more other business logic processing components (regardless of the business objects they belong to);

[0291] M2.1.3.2) The product diagram of the business object product consists of 1 business object product definition node (root node), 1 business rule structure node and its sub-node set, 1 user story structure node and its sub-node set, 1 business process logic structure node and its sub-node set, etc.;

[0292] The sub-node set of the business rule structure node is composed of 0 or more component group nodes, 0 or more component graphs of information structure components, 0 or more component graphs of general business rule components, etc.

[0293] The component diagram of an information structure component consists of one information structure component definition node (root node), one or more description nodes, zero or more resource nodes, zero or more component link nodes of other information structure components, etc.

[0294] The component diagram of the general business rule component is composed of 1 general business rule component definition node (root node), 1 or more description nodes, 0 or more resource nodes, 0 or more component link nodes of other general business rule components, etc.

[0295] The subnode set of the user story structure node consists of 0 or more component group nodes, 1 or more component diagrams of user story components, etc.

[0296] The component diagram of a user story component consists of one user story component definition node (root node), one or more description nodes, zero or more resource nodes, one or more component link nodes of business transaction components, etc.

[0297] The sub-node set of the business processing logic structure node is composed of 0 or more component group nodes, 0 or more component diagrams of business transaction components, 0 or more component diagrams of basic logic components, etc.

[0298] The component diagram of a business transaction component consists of one business transaction component definition node (root node), one or more description nodes, zero or more resource nodes, zero or more component link nodes of business rule components, and zero or more component link nodes of other business processing logic components.

[0299] The component diagram of the basic logic component is composed of 1 basic logic component definition node (root node), 1 or more description nodes, 0 or more resource nodes, 0 or more component link nodes of business rule components, 0 or more component link nodes of other business processing logic components, etc.

[0300] M2.1.4) Business service products

[0301] M2.1.4.1) The business service artifact referred to in M1.4 is used to describe a business requirement logical unit related to multiple business objects within a business domain;

[0302] A target model has 0 or more business service artifacts; a business service artifact contains 0 or more business rule components, 0 or more user story components, and 0 or more business process logic components;

[0303] M2.1.4.2) Business service artifacts are described in the same specification as business objects, except for the following differences:

[0304] Business object artifacts include information structure components, while business service artifacts do not include information structure components;

[0305] M2.2) Functional model products

[0306] M2.2.1) Functional structural products

[0307] M2.2.1.1) The functional structure artifact referred to in M1.5 is used to describe the set of functional modules of the target model;

[0308] One target model has one and only one functional structure product; one functional structure product contains one or more functional module components with hierarchical relationships;

[0309] Functional module component, defines a functional module of the target model;

[0310] M2.2.1.2) The product diagram of the functional structure product is composed of one functional structure product definition node (root node), one or more hierarchical functional module component definition nodes, etc.

[0311] The component diagram of a functional module component consists of only one functional module component definition node;

[0312] M2.2.2) User interface artifacts

[0313] M2.2.2.1) User interface artifacts as described in M1.5, which describe a user interface of the target model;

[0314] One target model has one or more user interface artifacts; one user interface artifact contains one or more interface view components, one or more interface rule components, one or more interface event capability components, and zero or more interface basic capability components;

[0315] The interface view component is used to describe the interface graphic structure of the corresponding user interface in a certain mode;

[0316] Interface rule components, including two types: general and data controls;

[0317] General type interface rule component, referred to as: general interface rule component, is used to describe the interface processing logic of a certain topic related to the user interface, such as: initial query conditions, display conditions of multiple interface views, etc.;

[0318] Business rule components of data control type, referred to as data control components, are used to describe the input and output data control logic of the corresponding user interface product, such as the drop-down options of a selection box control, the control form of the same data control in different interface modes, etc.

[0319] The interface event capability component is used to describe the interface-side processing logic and business data processing logic of the user interface product in response to a certain human-computer interaction event; each user interface product has a fixed initialization interface event capability component, which is used to describe the interface-side processing logic and business data processing logic when the user interface is opened;

[0320] The basic interface capability component is used to describe a common interface processing logic and business data processing logic that appear in the event response logic of multiple interface event components;

[0321] Interface event capability components and interface basic capability components are collectively referred to as interface capability components;

[0322] One general interface rule component can reference zero or more interface view components (belonging to the same user interface product) to describe the display conditions of different interface views; one interface view component can be referenced by zero or more general interface rule components (belonging to the same user interface product);

[0323] One data control component can reference zero or more interface event capability components (belonging to the same user interface product) as the human-computer interaction event response logic of the data control; one interface event capability component can be referenced by zero or one data control component (belonging to the same user interface product);

[0324] One interface capability component can reference zero or more other user interface artifacts as the user interface opened in the processing logic described by it; one user interface artifact can be referenced by the interface capability components of multiple other user interface artifacts;

[0325] An interface capability component can reference 0 or more interface rule components (belonging to the same user interface artifact), 0 or more other interface capability components (belonging to any user interface artifact), and 0 or more business transaction components as some steps in the processing logic it describes;

[0326] One interface rule component can be referenced by zero or more interface capability components (belonging to the same user interface product); one interface capability component can be referenced by zero or more interface capability components (belonging to any user interface product); one business transaction component can be referenced by zero or more interface capability components;

[0327] M2.2.2.2) The product diagram of the user interface product is composed of 1 user interface product definition node (root node), 1 interface view structure node and its sub-node set, 1 parameter variable structure node and its sub-node set, 1 interface rule structure node and its sub-node set, 1 interface event capability structure node and its sub-node set, 1 interface basic capability structure node and its sub-node set, etc.;

[0328] The subnode set of the interface view structure node is composed of 0 or more component group nodes, 1 or more component diagrams of the interface view components, etc.

[0329] The component diagram of the interface view component is composed of one interface view component definition node (root node), one or more resource nodes, etc.; these resource nodes contain the image storage path or file storage path or web page URL that describes the graphical structure of the interface view;

[0330] The sub-node set of the parameter variable structure node is composed of the input parameter structure node and its sub-node set, the output parameter structure node and its sub-node set, the interface variable structure node and its sub-node set, etc.;

[0331] The sub-node set of the input parameter structure node is used to define and describe the input parameters of the corresponding user interface, and is composed of one or more description nodes;

[0332] The sub-node set of the output parameter structure node is used to define and describe the output parameters of the corresponding user interface, and is composed of one or more description nodes;

[0333] The sub-node set of the interface variable structure node is used to define and describe the internal variables of the corresponding user interface, and is composed of one or more description nodes;

[0334] The sub-node set of the interface rule structure node is composed of 0 or more component group nodes, 0 or more component diagrams of common interface rule components, 0 or more component diagrams of data control components, etc.

[0335] The component diagram of the general interface rule component is composed of 1 general interface rule component definition node (root node), 1 or more description nodes, 0 or more resource nodes, 0 or more component link nodes of the interface view component, etc.;

[0336] The component diagram of a data control component consists of one data control component definition node (root node), one or more description nodes, zero or more resource nodes, zero or more component link nodes of interface event capability components, etc.

[0337] The sub-node set of the interface event capability structure node is composed of 0 or more component group nodes, 0 or more component graphs of the interface event capability components, etc.

[0338] The component diagram of the interface event capability component is composed of 1 interface event capability component definition node (root node), 1 or more description nodes, 0 or more resource nodes, 0 or more component link nodes of interface rule components, 0 or more component link nodes of other interface capability components, 0 or more component link nodes of business transaction components, 0 or more product link nodes of user interface products, etc.

[0339] The sub-node set of the interface basic capability structure node is composed of 0 or more component group nodes, 0 or more component diagrams of the interface basic capability components, etc.

[0340] The component diagram of the basic interface capability component is composed of 1 basic interface capability component definition node (root node), 1 or more description nodes, 0 or more resource nodes, 0 or more component link nodes of the interface rule component, 0 or more component link nodes of other interface capability components, 0 or more component link nodes of the business transaction component, 0 or more product link nodes of the user interface product, etc.

[0341] M2.2.3) Interactive products

[0342] M2.2.3.1) The interactive functional artifacts referred to in M1.5 are used to describe the system functional use case of a certain human-computer interaction type of the target model;

[0343] A target model has one or more interactive functional artifacts;

[0344] One interactive function artifact can reference one business transaction component as its implementation goal; one business transaction component can be referenced by 0 or 1 interactive function artifacts;

[0345] One interactive function product can reference one or more interface event capability components as the system processing logic for the function to respond to user operations; one interface event capability product can be referenced by one or more interactive function products;

[0346] One interactive function product can reference one or more user interface products as the newly opened user interface in the system processing logic of the function in response to user operations; one user interface product can be referenced by one or more interactive function products;

[0347] One interactive function product can reference one or more interface view capability components as the new interface view displayed after the system processing logic of the function responds to user operations is executed; one interface view product can be referenced by one or more interactive function products;

[0348] M2.2.3.2) The artifact diagram of the interactive function artifact consists of 1 interactive function artifact definition node (root node), 1 target structure node and its sub-node set, 1 main use case structure node and its sub-node set, 1 other use case structure node and its sub-node set, etc.;

[0349] The sub-node set of the target structure node is composed of a description node representing the execution meaning and a component link node of the business transaction component;

[0350] The subnode set of the main use case structure node is composed of one or more user operation description nodes and their subnode sets; the subnode set of the user operation description node is composed of one system response description node and its subnode set; the subnode set of the system response description node is composed of one component link node of the interface event capability component, 0 or 1 product link nodes of the user interface product, 0 or 1 component link node of the interface view component, etc.;

[0351] The subnode set of other use case structure nodes is composed of one or more function use case description nodes and their subnode sets; the subnode set of function use case description nodes is composed of one or more user operation description nodes and their subnode sets; the subnode set of user operation description nodes is composed of one system response description node and its subnode set; the subnode set of system response description nodes is composed of one component link node of interface event capability component, 0 or 1 product link nodes of user interface product, 0 or 1 component link node of interface view component, etc.;

[0352] M2.2.4) Timing function products

[0353] M2.2.4.1) The timed functional artifacts referred to in M1.5 are used to describe the time-triggered system functions of the target model;

[0354] A target model has one or more timed function artifacts;

[0355] One timed function artifact can reference one business transaction component as its implementation target; one business transaction component can be referenced by 0 or 1 timed function artifacts;

[0356] M2.2.3.2) The product diagram of the timing function product consists of a timing function product definition node (root node), a target structure node and its child node set;

[0357] The sub-node set of the target structure node is composed of a description node representing the execution meaning and a component link node of the business transaction component;

[0358] M2.2.4) Interface functional products

[0359] M2.2.4.1) The interface functional artifact referred to in M1.5 is used to describe the system interface opened by the target model to the external system;

[0360] A target model has one or more interface functional artifacts;

[0361] One interface function artifact can reference one business transaction component as its implementation target; one business transaction component can be referenced by 0 or 1 interface function artifacts;

[0362] M2.2.3.2) The product diagram of the interface function product consists of an interface function product definition node (root node), a target structure node and its sub-node set;

[0363] The child node set of the target structure node is composed of a description node representing the execution meaning and a component link node of the business transaction component.

[0364] M3) Structural characteristics of various model views

[0365] M3.1) The business map referred to in M1.6 refers to a mind-map classification summary of business model artifacts (business process artifacts, business object artifacts, business service artifacts) belonging to a certain end-level business domain;

[0366] 1 business map, consisting of a component link node (root node) of a terminal business domain component defined in the business structure artifact diagram, 0 or more artifact group nodes, 0 or more artifact link nodes of business process artifacts, 0 or more artifact link nodes of business object artifacts, and 0 or more artifact link nodes of business service artifacts;

[0367] Each final business domain component of the target model has one business map;

[0368] M3.2) The functional map referred to in M1.6 refers to a mind-map summary of the user interface products, interactive function products, timing function products, and interface function products belonging to a certain final function module;

[0369] 1 functional map, consisting of a component link node (root node) of a terminal functional module component defined in the functional structure artifact diagram, 0 or more artifact group nodes, 0 or more artifact link nodes of user interface artifacts, 0 or more artifact link nodes of interactive function artifacts, 0 or more artifact link nodes of timing function artifacts, and 0 or more artifact link nodes of interface function artifacts;

[0370] Each final functional module component of the target model has one functional map;

[0371] M3.3) The model master diagram referred to in M1.6 refers to a mind map summary diagram of all artifacts of the target model, which is composed of the root node representing the target software, the business logic model sub-diagram, the functional logic model sub-diagram, etc.;

[0372] The business logic model subgraph is composed of 1 business structure product link node (the root node of the subgraph), 0 or more non-last-level business domain component link nodes of the hierarchical structure, 1 or more business maps, etc.

[0373] The functional logic model subgraph is composed of 1 functional structure artifact link node (the root node of the subgraph), 0 or more non-final functional module component link nodes of the hierarchical structure, 1 or more functional maps, etc.

[0374] The target model has 1 model overview drawing.

[0375] like Figure 1 As shown, this method can construct a software requirement logic model consisting of business model artifacts, functional model artifacts and model views for the target software through business logic modeling, functional logic modeling and building model views.

[0376] Figure 2 Provides a software requirement logical model structure diagram for the target software.

[0377] The demand modeling method proposed in this embodiment includes the following modeling steps:

[0378] S1) Business logic modeling

[0379] Figure 3 Provides a sample flowchart for business logic modeling.

[0380] S1.1) Build business structure products

[0381] Each model builds a business structure product, the steps are as follows:

[0382] S1.1.1) New business structure products

[0383] Creating a new business structure product refers to the initialization product graph of the new business structure product. The graph has one root node (the product definition node of the business structure product).

[0384] S1.1.2) Construct a hierarchical set of business domain components

[0385] S1.1.2.1) Add one or more business domain component definition nodes with a hierarchical relationship after the product definition node of the business structure product.

[0386] The term "adding a certain B node set" after a certain A node means adding a certain B node set as a subnode set of a certain A node in a product diagram or a model view;

[0387] S1.1.2.2) Define business domain components

[0388] Defining a business domain component refers to setting the business domain number, name and other information on each business domain component definition node.

[0389] Figure 6 An example of a business structure artifact diagram is provided.

[0390] S1.2) Build business process artifacts

[0391] Each model builds zero or more business process artifacts.

[0392] Each business process artifact is constructed as follows:

[0393] S1.2.1) Create new business process artifacts

[0394] S1.2.1.1) Initialization artifact diagram for creating a new business process artifact

[0395] The initialization artifact diagram of the business process artifact has 1 root node (the artifact definition node of the business process artifact), 1 flowchart structure node, and 1 business scenario structure node.

[0396] S1.2.1.2) Define business process artifacts

[0397] Defining a business process artifact refers to setting information such as the number, name, and business domain on the artifact definition node of the business process artifact.

[0398] S1.2.2) Setting flow chart

[0399] S1.2.2.1) Upload flow chart

[0400] Uploading a flowchart means uploading a picture or file of the flowchart of a business process product and storing it in the file management system.

[0401] S1.2.2.2) Linking flow chart

[0402] Linking a flowchart means adding one or more resource nodes after the flowchart structure node, and setting the storage path of the corresponding flowchart image or file in the file management system on these resource nodes.

[0403] S1.2.3) Define business scenario component groups

[0404] Defining a business scenario component group means expanding and adding zero or more component group nodes with a hierarchical relationship after the business scenario structure node. The business scenario structure node and these component group nodes constitute a business scenario group node tree.

[0405] S1.2.4) Build business scenario components

[0406] Each business process artifact constructs one or more business scenario components.

[0407] Each business scenario component is constructed as follows:

[0408] S1.2.4.1) Create new business scenario components

[0409] To create a new business scenario component is to expand and add a business scenario component definition node after a certain last-level node in the business scenario group node tree.

[0410] S1.2.4.2) Define business scenario components

[0411] Defining a business scenario component refers to setting information such as number and name on the business scenario component definition node.

[0412] S1.2.4.3) Describe business scenario components

[0413] Describing a business scenario component means taking the business scenario component definition node as the root node and extending and building a business scenario component graph. Extending and building a component graph means extending and adding various nodes according to structural characteristics to build a component graph.

[0414] Figure 7 An example of a business process artifact diagram is provided.

[0415] S1.3) Build business object artifacts

[0416] Each target model builds zero or more business object artifacts.

[0417] Each business object artifact is constructed as follows:

[0418] S1.3.1) Create new business object artifacts

[0419] S1.3.1.1) Initialization artifact diagram for new business object artifact

[0420] The initialization artifact diagram of the business object artifact has 1 root node (the artifact definition node of the business object artifact), 1 business rule structure node, 1 user story structure node, and 1 business process logic structure node.

[0421] S1.3.1.2) Define business object artifacts

[0422] Defining a business object artifact refers to setting information such as the number, name, and business domain to which the artifact belongs on the artifact definition node of the business object artifact.

[0423] S1.3.2) Define business rule component groups

[0424] Defining a business rule component group means expanding and adding zero or more component group nodes with a hierarchical relationship after the business rule structure node. The business rule structure node and these component group nodes constitute the business rule group node tree.

[0425] S1.3.3) Construct information structure components

[0426] Each business object artifact builds one or more information structure components.

[0427] Each information structure component is constructed as follows:

[0428] S1.3.3.1) Create new information structure components

[0429] To create a new information structure component means to expand and add an information structure component definition node after a certain last-level node in the business rule group node tree.

[0430] S1.3.3.2) Define information structure components

[0431] Defining an information structure component refers to setting information such as number, name, type, etc. on the information structure component definition node.

[0432] S1.3.3.3) Describe the information structure components

[0433] Describing an information structure component means taking the information structure component definition node as the root node and expanding and constructing an information structure component graph.

[0434] S1.3.4) Build common business rule components

[0435] Each business object artifact builds zero or more common business rule components.

[0436] Each common business rule component is constructed as follows:

[0437] S1.3.4.1) Create a new general business rule component

[0438] To create a new general business rule component is to expand and add a general business rule component definition node after a certain last-level node in the business rule group node tree.

[0439] S1.3.4.2) Define common business rule components

[0440] Defining a general business rule component refers to setting information such as number, name, type, etc. on the general business rule component definition node.

[0441] S1.3.4.3) Describe the common business rule components

[0442] Describing a general business rule component means taking the general business rule component definition node as the root node and extending and constructing a general business rule component graph.

[0443] S1.3.5) Define user story component groups

[0444] Defining a user story component group means adding zero or more component group nodes with a hierarchical relationship after the user story structure node. The user story structure node and these component group nodes constitute the user story group node tree.

[0445] S1.3.6) Build user story components

[0446] Each business object artifact builds one or more user story components.

[0447] Each user story component is constructed as follows:

[0448] S1.3.6.1) Create a new user story component

[0449] Creating a new user story component means adding a user story component definition node after a certain last-level node in the user story group node tree.

[0450] S1.3.6.2) Define the user story components

[0451] Defining a user story component means setting the number, name, type and other information on the user story component definition node.

[0452] S1.3.6.3) Describe the user story components

[0453] Describing user story components means taking the user story component definition node as the root node and expanding and building a user story component diagram.

[0454] S1.3.6.4) Integrate user story components

[0455] Integrating user story components means adding user story component link nodes to the component diagram of related business scenario components.

[0456] S1.3.7) Define business processing logic component groups

[0457] Defining a business processing logic component group means expanding and adding zero or more component group nodes with a hierarchical relationship after the business processing logic structure node. The business processing logic structure node and these component group nodes constitute a business processing logic group node tree.

[0458] S1.3.8) Build business transaction components

[0459] Each business object artifact builds one or more business transaction components.

[0460] Each business transaction component is constructed as follows:

[0461] S1.3.8.1) Create a new business transaction component

[0462] To create a new business transaction component is to expand and add a business transaction component definition node after a certain last-level node in the business processing logic group node tree.

[0463] S1.3.8.2) Define business transaction components

[0464] Defining a business transaction component refers to setting information such as number, name, type, etc. on the business transaction component definition node.

[0465] S1.3.8.3) Describe the business transaction components

[0466] Describing a business transaction component means taking the business transaction component definition node as the root node and extending and building a business transaction component graph.

[0467] S1.3.8.4) Integrate business transaction components

[0468] Integrating business transaction components means adding business transaction component link nodes to the component diagram of related user story components.

[0469] S1.3.9) Construct basic logic components

[0470] Each business object artifact builds zero or more basic logical components.

[0471] Each basic logic component is constructed as follows:

[0472] S1.3.9.1) Create new basic logic components

[0473] Creating a new basic logic component means expanding and adding a basic logic component definition node after a certain last-level node in the business processing logic group node tree.

[0474] S1.3.9.2) Define basic logical components

[0475] Defining a basic logic component refers to setting information such as number, name, type, etc. on the basic logic component definition node.

[0476] S1.3.9.3) Describe the basic logical components

[0477] Describing a basic logic component means taking the basic logic component definition node as the root node and expanding and constructing a basic logic component diagram.

[0478] S1.3.9.4) Integrate basic logic components

[0479] Integrating basic logic components refers to adding basic logic component link nodes to the component diagrams of related business transaction components or other basic logic components.

[0480] Figure 8a Provides an example of a business object artifact diagram. Figure 8b An example component diagram for one of the user story components.

[0481] S1.4) Build business service products

[0482] Each target model builds zero or more business service artifacts.

[0483] Each business service artifact is built as follows:

[0484] S1.4.1) Create new business service products

[0485] S1.4.1.1) Initialization artifact diagram for new business service artifact

[0486] The initialization artifact diagram of the business service artifact has 1 root node (artifact definition node of the business service artifact), 1 business rule structure node, 1 user story structure node, and 1 business process logic structure node.

[0487] S1.4.1.2) Define business service artifacts

[0488] Defining a business service product refers to setting information such as the number, name, and business domain on the product definition node of the business service product.

[0489] S1.4.2) Define business rule component groups

[0490] Same as described in S1.3.2.

[0491] S1.4.3) Build common business rule components

[0492] Each business service artifact builds zero or more common business rule components.

[0493] The steps for constructing each common business rule component are the same as the steps for constructing the common business rule component in the business object described in S1.3.4.

[0494] S1.4.4) Define user story component groups

[0495] Same as described in S1.3.5.

[0496] S1.4.5) Build user story components

[0497] Each business service artifact builds one or more user story components.

[0498] The steps for building each user story component are the same as the steps for building the user story component in the business object described in S1.3.6.

[0499] S1.4.6) Define business processing logic component groups

[0500] Same as S1.3.7.

[0501] S1.4.7) Build business transaction components

[0502] Each business service artifact builds one or more business transaction components.

[0503] The steps for constructing each business transaction component are the same as the steps for constructing the business transaction component in the business object described in S1.3.8.

[0504] S1.4.8) Construct basic logic components

[0505] Each business service artifact builds zero or more basic logical components.

[0506] The steps for constructing each basic logic component are the same as the steps for constructing the basic logic components in the business object described in S1.3.9.

[0507] Figure 9a An example of a business service artifact diagram is provided. Figure 9b The following is an example component diagram for one of the business transaction components.

[0508] S2) Functional logic modeling

[0509] Figure 4 A sample flow chart for functional logic modeling is provided.

[0510] S2.1) Construct functional structural products

[0511] Each target model builds a functional structure product, the steps are as follows:

[0512] S2.1.1) New functional structural products

[0513] Creating a new functional structure artifact refers to the initialization artifact diagram of the new functional structure artifact, which has one root node (the artifact definition node of the functional structure artifact).

[0514] S2.1.2) Construct a hierarchical structure of functional module components

[0515] S2.1.2.1) Add one or more hierarchical functional module component definition nodes after the product definition node of the functional structure product.

[0516] S2.1.2.2) Define functional module components

[0517] Defining a functional module component refers to setting the functional module number, name and other information on each functional module component definition node.

[0518] Fig.10 An example of a functional structure artifact diagram is provided.

[0519] S2.2) Build user interface artifacts

[0520] Each target model builds zero or more user interface artifacts.

[0521] Each user interface artifact is built as follows:

[0522] S2.2.1) Create new user interface artifacts

[0523] S2.2.1.1) Initialization artifact diagram for new user interface artifact

[0524] The initialization artifact diagram of the user interface artifact has 1 root node (artifact definition node of the user interface artifact), 1 interface view structure node, 1 parameter variable structure node and its 3 child nodes (input parameter structure node, output parameter structure node, interface variable structure node), 1 interface rule structure node, 1 interface event capability structure node, and 1 interface basic capability structure node.

[0525] S2.2.1.2) Define user interface artifacts

[0526] Defining a user interface product refers to setting information such as number, name, and function module on the product definition node of the user interface product.

[0527] S2.2.2) Constructing interface view components

[0528] Each user interface artifact builds zero or more interface view components.

[0529] Each interface view component is constructed as follows:

[0530] S2.2.2.1) Create new interface view components

[0531] Creating a new interface view component means expanding and adding an interface view component definition node after the interface view structure node.

[0532] S2.2.2.2) Define interface view components

[0533] Defining an interface view component refers to setting information such as number and name on the interface view component definition node.

[0534] S2.2.2.3) Describe the interface view components

[0535] Describing an interface view component means taking the interface view component definition node as the root node and expanding and constructing an interface view component diagram.

[0536] S2.2.3) Define and describe parameter variables

[0537] S2.2.3.1) Define and describe input parameters

[0538] Defining input parameters means adding zero or more description nodes after the input parameter structure node to define and describe the input parameters of several user interfaces.

[0539] S2.2.3.2) Define and describe output parameters

[0540] Defining output parameters means adding zero or more description nodes after the output parameter structure node to define and describe the output parameters of several user interfaces.

[0541] S2.2.3.3) Define and describe interface variables

[0542] Defining interface variables means adding 0 or more description nodes after the interface variable structure node to define and describe several internal variables of the user interface.

[0543] S2.2.4) Define interface rule component groups

[0544] Defining an interface rule component group means expanding and adding zero or more component group nodes with a hierarchical relationship after the interface rule structure node. The interface rule structure node and these component group nodes constitute the interface rule group node tree.

[0545] S2.2.5) Build common interface rule components

[0546] Each user interface artifact builds zero or more common interface rule components.

[0547] Each common interface rule component is constructed as follows:

[0548] S2.2.5.1) Create a new general interface rule component

[0549] To create a new general interface rule component is to expand and add a general interface rule component definition node after a certain last-level node in the interface rule group node tree.

[0550] S2.2.5.2) Define common interface rule components

[0551] Defining a general interface rule component refers to setting information such as number, name, type, etc. on the general interface rule component definition node.

[0552] S2.2.5.3) Describe common interface rule components

[0553] Describing a general interface rule component means taking the general interface rule component definition node as the root node and extending and constructing a general interface rule component graph.

[0554] S2.2.6) Construct data control components

[0555] Each user interface artifact builds one or more data control components.

[0556] Each data control is constructed as follows:

[0557] S2.2.6.1) Create a new data control component

[0558] To create a new data control component means to expand and add a data control component definition node after a certain last-level node in the interface rule group node tree.

[0559] S2.2.6.2) Define data control components

[0560] Defining a data control component means setting the number, name, type and other information on the data control component definition node.

[0561] S2.2.6.3) Describe the data control components

[0562] Describing a data control component means taking the data control component definition node as the root node and expanding and building a data control component diagram.

[0563] S2.2.7) Define the interface basic capability component groups

[0564] Defining the basic interface capability component group means expanding and adding zero or more component group nodes with a hierarchical relationship after the basic interface capability structure node. The basic interface capability structure node and these component group nodes constitute the basic interface capability group node tree.

[0565] S2.2.8) Build basic interface capabilities

[0566] Each user interface artifact builds zero or more basic interface capability components.

[0567] Each interface basic capability is constructed according to the following steps:

[0568] S2.2.8.1) Create new interface basic capability components

[0569] To create a new basic interface capability component is to expand and add a basic interface capability component definition node after a certain last-level node of the basic interface capability group node tree.

[0570] S2.2.8.2) Define basic interface capabilities

[0571] Defining basic interface capability components refers to setting information such as number, name, type, etc. on the basic interface capability component definition node.

[0572] S2.2.8.3) Describe the basic capabilities of the interface

[0573] Describing the basic interface capability components means taking the basic interface capability component definition node as the root node and expanding and constructing the basic interface capability component diagram.

[0574] S2.2.9) Define interface event capability component groups

[0575] Defining an interface event capability component group means expanding and adding 0 or more component group nodes with a hierarchical relationship after the interface event capability structure node. The interface event capability structure node and these component group nodes constitute an interface event capability group node tree.

[0576] S2.2.10) Build interface event capability components

[0577] Each user interface artifact builds one or more interface event capability components.

[0578] Each interface event capability is constructed as follows:

[0579] S2.2.10.1) Create new interface event capability components

[0580] To create a new interface event capability component is to expand and add an interface event capability component definition node after a certain last-level node of the interface event capability group node tree.

[0581] S2.2.10.2) Define interface event capability components

[0582] Defining an interface event capability component refers to setting information such as number, name, type, etc. on the interface event capability component definition node.

[0583] S2.2.10.3) Describe the interface event capability component

[0584] To describe an interface event capability component is to use the interface event capability component definition node as a root node and expand and construct an interface event capability component graph.

[0585] Fig.11a An example of a user interface artifact diagram is provided. Fig.11b Shown in Fig.11a An example diagram showing multiple hierarchical child nodes extending after the interface event capability structure node.

[0586] S2.3) Build interactive functional products

[0587] Each target model builds zero or more interactive functional artifacts.

[0588] Each interactive feature artifact is built as follows:

[0589] S2.3.1) Create new interactive products

[0590] S2.3.1.1) Initialization artifact diagram for newly created interactive artifacts

[0591] The initialization artifact diagram of the interactive function artifact has 1 root node (artifact definition node of the interactive function artifact), 1 target structure node, 1 main use case structure node, and 1 other use case structure node.

[0592] S2.3.1.2) Define interactive functional products

[0593] Defining an interactive function product refers to setting information such as number, name, and function module on the product definition node of the interactive function product.

[0594] S2.3.2) Describe the implementation goals of the interactive function

[0595] Describing the realization goal of the interactive function means extending and adding a description node indicating the execution meaning after the target structure node of the interactive function product, and extending and adding a business transaction component link node after the description node.

[0596] S2.3.3) Describe the main use cases for interactive functions

[0597] The main use case that describes the interactive function refers to adding one or more description nodes that describe user operations after the main use case structure node of the interactive function product, adding one description node that represents the system response after each user operation description node, and adding one interface event capability component link node, 0 or 1 user interface product link nodes, and 0 or 1 interface view component link nodes after each system response description node.

[0598] S2.3.4) Describe other use cases for interactive functionality

[0599] Other use cases that describe interactive functions refer to adding 0 or more description nodes that define use cases after the other use case structure nodes of the interactive function artifact, adding 1 or more description nodes that describe user operations after each use case description node, adding 1 description node that represents system response after each user operation description node, and adding 1 interface event capability component link node, 0 or 1 user interface artifact link nodes, and 0 or 1 interface view component link nodes after each system response description node.

[0600] Fig.12a An example of an interactive feature product diagram is provided. Figure 12b For Fig.12a An example diagram of expanding multiple hierarchical subnodes under other use case structure nodes.

[0601] S2.4) Build a timed function product

[0602] Each target model builds zero or more timed function artifacts.

[0603] Each timed function product is constructed as follows:

[0604] S2.4.1) Create a new timer function product

[0605] S2.4.1.1) Initialization product diagram for newly created timing function product

[0606] The initialization product graph of the timing function product has one root node (the product definition node of the timing function product) and one target structure node.

[0607] S2.4.1.2) Define timed functional products

[0608] Defining a timed function product refers to setting information such as number, name, and function module on the product definition node of the timed function product.

[0609] S2.4.2) Describe the implementation objectives of the timing function

[0610] The realization goal of describing the timing function refers to extending and adding a description node indicating the execution meaning after the target structure node of the timing function product, and extending and adding a certain business transaction component link node after the description node.

[0611] Fig.13 An example of a timing function artifact diagram is provided.

[0612] S2.5) Build interface functional products

[0613] Each target model builds zero or more interface functional artifacts.

[0614] Each interface function artifact is constructed as follows:

[0615] S2.5.1) Create new interface function products

[0616] S2.5.1.1) Initialization artifact diagram of new interface function artifact

[0617] The initialization artifact graph of the interface function artifact has 1 root node (the artifact definition node of the interface function artifact) and 1 target structure node.

[0618] S2.5.1.2) Define interface functional artifacts

[0619] Defining an interface function product refers to setting information such as number, name, and function module on the product definition node of the interface function product.

[0620] S2.5.2) Describe the implementation goals of the interface functions

[0621] Describing the realization goal of the interface function means adding a description node indicating the execution meaning after the target structure node of the interface function product, and adding a business transaction component link node after the description node.

[0622] Fig.14 An example of an interface functional artifact diagram is provided.

[0623] S3) Build model view

[0624] Figure 5 Provides a sample flow chart for building a model view.

[0625] S3.1) Build a business map

[0626] A business map is constructed for each final-level business domain.

[0627] Each business map is constructed using the following steps:

[0628] S3.1.1) Create a new and initialized business map

[0629] Initialize the business map, which has one root node: the component link node of the final business domain component.

[0630] S3.1.2) Define business map product groups

[0631] Defining a business map product group means expanding and adding 0 or more product group nodes with a hierarchical relationship after the business map root node. The business map root node and these product group nodes constitute the business map product group node tree.

[0632] S3.1.3) Grouping business model artifacts

[0633] Grouping business model products means expanding and adding 0 or more business process product link nodes, 0 or more business object product link nodes, and 0 or more business service product link nodes after each last-level node in the business map product group node tree.

[0634] Fig.15 An example of a business map is provided.

[0635] S3.2) Constructing functional maps

[0636] Each final-level functional module constructs a functional map.

[0637] Each functional map is constructed by following the steps below:

[0638] S3.2.1) Create a new initialization function map

[0639] Initialize the function map, which has one root node: the component link node of the final function module component.

[0640] S3.2.2) Define functional map product groups

[0641] Defining a function map product group means expanding and adding 0 or more product group nodes with a hierarchical relationship after the function map root node. The function map root node and these product group nodes constitute the function map product group node tree.

[0642] S3.2.3) Grouping and aggregating functional model products

[0643] Grouping and aggregating functional model products means expanding and adding 0 or more interactive functional product link nodes, 0 or more timing functional product link nodes, 0 or more interface functional product link nodes, and 0 or more user interface product link nodes after each last-level node of the functional map product group node tree.

[0644] Fig.16 An example of a functional map is provided.

[0645] S3.3) Build the overall model diagram

[0646] Each target model constructs a model overview diagram, the steps are as follows:

[0647] S3.3.1) Create a new initialization model overview

[0648] Initialize the model overview, with a root node representing the target software.

[0649] S3.3.2) Expand and increase business structure

[0650] Expanding and adding business structure means expanding and adding business structure artifact link nodes after the root node of the model general diagram, and expanding and adding corresponding business domain component link nodes layer by layer after the business structure artifact link nodes according to the hierarchical relationship of the business domain components in the business structure artifact diagram. These business domain component link nodes constitute the business domain component node tree.

[0651] S3.3.3) Expand and add business map

[0652] Expanding and adding a business map refers to expanding and adding a set of nodes (excluding its root node) of the business map of the business domain component after each last-level node of the business domain node tree described in S3.3.2.

[0653] S3.3.4) Expand and add functional structure

[0654] Expanding and adding functional structures means expanding and adding functional structure artifact link nodes after the root node of the model general diagram, and expanding and adding corresponding functional module component link nodes layer by layer after the functional structure artifact link nodes according to the hierarchical relationship of the functional module components in the functional structure artifact diagram. These functional module component link nodes constitute the functional module component node tree.

[0655] S3.3.5) Expand and add functional map

[0656] Expanding and adding a function map refers to expanding and adding a node set (excluding its root node) of the function map of the function module component after each last-level node of the function module node tree described in S3.3.4.

[0657] Fig.17a An example of a model overview is provided. Fig.17b and Fig.17c The business map and functional map expanded and added in the model overall diagram are shown respectively.

[0658] The present invention can greatly improve the practicability of software requirement modeling technology in software engineering practice, which is conducive to changing the industry pain point that "a large number of actual software projects are still using scattered unstructured requirement documents". By structuring, visualizing and digitizing the requirement analysis and modeling process, it can promote software engineering to improve quality, resolve risks, shorten delivery time, reduce costs and increase efficiency.

[0659] Embodiment 2

[0660] like Fig.18 As shown, this embodiment proposes a mind-map demand modeling system, including the following modules:

[0661] 1. Model management module

[0662] The requirement modeling for the target software starts with the user using the new model function of this module, and then building the model artifacts and model views of this new model through other modules.

[0663] 2. Business model product management

[0664] 2.1) Business structure product management module

[0665] When a model is newly created, this module automatically generates a unique business structure artifact for the model.

[0666] Users use the function of editing business structure product diagram in this module to build a collection of business domain components with a hierarchical structure.

[0667] 2.2) Business process product management module

[0668] Users use the new business process artifact function of this module to generate an initialization artifact diagram for the business process artifact, and set the business process artifact number, name, business domain and other information.

[0669] Users use the editing business process product diagram function of this module to set up flowcharts, define business scenario component groups, and build business scenario components.

[0670] Users use this module to view the business process product diagram: they can load / unload the module diagram of any module on demand after linking the node in the product diagram, so as to display the entire logical chain in a penetrating manner.

[0671] 2.3) Business object product management module

[0672] The user uses the new business object artifact function of this module to generate an initialization artifact diagram for the business object artifact, and set the business object artifact number, name, business domain, and other information.

[0673] Users use the business object product diagram editing function of this module to: define business rule component groups, build information structure components, build common business rule components, define user story component groups, build user story components, define business processing logic component groups, build business transaction components, and build basic logic components.

[0674] Users use the function of viewing business object product diagrams in this module: they can load / unload the module diagram of any module on demand after linking nodes in the product diagram, thereby being able to display the entire logical chain in a penetrating manner.

[0675] 2.4) Business service product management module

[0676] The user uses the new business service product function of this module to generate an initialization product diagram for the business service product and set the number, name, business domain and other information of the business service product.

[0677] Users use the business service product diagram editing function of this module to: define business rule component groups, build common business rule components, define user story component groups, build user story components, define business processing logic component groups, build business transaction components, and build basic logic components.

[0678] Users use the function of viewing business service product diagrams in this module: they can load / unload the module diagram of any module on demand after linking nodes in the product diagram, thereby displaying the entire logical chain in a penetrating manner.

[0679] 3. Functional model product management

[0680] 3.1) Functional structure product management module

[0681] When a new model is created, this module automatically generates a unique functional structural product for the model.

[0682] Users use the editing function of this module to create a structural product diagram: a collection of functional module components that construct a hierarchical structure.

[0683] 3.2) User interface product management module

[0684] The user uses the new user interface product function of this module to generate an initialization product diagram of the user interface product, and set the number, name, functional module and other information of the user interface product.

[0685] Users use the editing user interface product diagram function of this module to: build interface view components, define and describe parameter variables, define interface rule component groups, build common interface rule components, build data control components, define interface basic capability component groups, build interface basic capability components, define interface event capability component groups, and build interface event capability components.

[0686] Users use the user interface product diagram viewing function of this module: they can load / unload the module diagram of any module on demand after linking nodes in the product diagram, so as to display the entire logical chain in a penetrating manner.

[0687] 3.3) Interactive Function Product Management Module

[0688] The user uses the new interactive function product function of this module to generate an initialization product diagram of the interactive function product, and set the number, name, functional module and other information of the interactive function product.

[0689] Users use this module's editing interactive function product diagram function: describe the implementation goals of the interactive function, describe the main use cases of the interactive function, and describe other use cases of the interactive function.

[0690] Users use the interactive viewing function of this module, the product diagram function: they can load / unload the module diagram of any module on demand after linking the node of any module in the product diagram, so as to display the entire logical chain in a penetrating manner.

[0691] 3.4) Timing function product management module

[0692] The user uses the new timing function product function of this module to generate the initialization product diagram of the timing function product, and set the number, name, functional module and other information of the timing function product.

[0693] Users use this module to edit the timing function product diagram function: describe the implementation goals of the timing function.

[0694] Users use the module's timing function to view product diagrams: they can load / unload the module diagram of any module on demand after linking nodes in the product diagram, thereby displaying the entire logic chain in a penetrating manner.

[0695] 3.5) Interface function product management module

[0696] The user uses the new interface function product function of this module to generate the initialization product diagram of the interface function product, and set the number, name, functional module and other information of the interface function product.

[0697] Users use the editing interface function of this module to draw the product diagram function: describe the implementation goals of the interface function.

[0698] Users use the viewing interface function of this module to view the product diagram function: they can load / unload the module diagram of any module on demand after linking the node of any module in the product diagram, so as to display the entire logical chain in a penetrating manner.

[0699] 4. Model view management

[0700] 4.1) Business map management module

[0701] Users use the new business map function of this module to generate an initialization business map for a certain business domain.

[0702] Users use the business map editing function of this module to define business map product groups and group business model products.

[0703] Users use the business map viewing function of this module: they can load / unload the module diagram of any module on demand after linking the node of any module in the business map, so as to display the entire logical chain in a penetrating manner.

[0704] 4.2) Functional map management module

[0705] Users use the new function map function of this module to generate an initialization function map for a certain function module.

[0706] Users use the editing function map function of this module to define functional map product groups and group and collect functional model products.

[0707] Users use the function of viewing the functional map of this module: they can load / unload the module diagram of any module on demand after linking the node of any module in the functional map, so as to display the entire logical chain in a penetrating manner.

[0708] 4.3) Model master diagram management module

[0709] Used to create a new model diagram, edit the model diagram, and view the model diagram for a model.

[0710] When a new model is created, this module automatically generates a unique model overview diagram (initialized state) for the model.

[0711] Users use this module's editing model master map function to: expand and add business structure, expand and add business map, expand and add functional structure, and expand and add functional map.

[0712] Users use the function of viewing the overall model diagram of this module: they can load / unload the module diagram of any module on demand after linking the node of any module in the function map, so as to display the entire logical chain in a penetrating manner.

[0713] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the system can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0714] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. In this understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium. Of course, there are other forms of readable storage media, such as quantum memory, graphene memory, etc. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media does not include electrical carrier signals and telecommunication signals.

[0715] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0716] Although the present application provides method operation steps as described in the embodiments or flow charts, conventional or non-creative means may include more or fewer operation steps. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent a unique execution order. When the system or terminal product in practice is executed, it can be executed in sequence or in parallel according to the method shown in the embodiments or the drawings (for example, in an environment of parallel processors or multi-threaded processing, or even in a distributed data processing environment).

[0717] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A system that specifies the functions of a box or multiple boxes.

[0718] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction system, which is implemented in the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0719] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0720] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0721] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, electronic device, and readable storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0722] The above description is only a preferred embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A mind-map demand modeling method, characterized in that: It includes a set of mind-map-style software requirement logic meta-model and software requirement logic modeling steps based on the meta-model, so as to construct a requirement logic model of the target software, namely, a target model; The target model is composed of a plurality of model products and a plurality of model views, and each model product and each model view is structuredly described using a mind map; The model product has a unique number, a name, zero or more parts and a product diagram. The product diagram is a tree-structured description diagram of the model product in the form of a mind map, which is composed of a product definition node and its multi-level child node set; The component refers to an independent description unit within the model product to which it belongs, and has a unique number, a name, and a component diagram. The component diagram refers to a tree-structured description diagram of the component in the form of a mind map, which is a sub-diagram of the product diagram of the model product to which the component belongs, and is composed of a component definition node and its multi-level sub-node set; The model view refers to a mind-map-style classification summary of model products in the target model, including a business map, a functional map and a model overview map; The model products and components are collectively referred to as modules. The product diagram and model view include multiple types of nodes: module definition node, module structure node, module group node, module description node, extended description resource node, module link node; among them, The module definition node includes a product definition node and a component definition node; the product definition node refers to the root node of the product graph, which contains information including product type, product number, product name and product version number; product definition nodes of different types of products have node styles with different shapes, colors and icons; The component definition node refers to the root node of the component diagram, which contains information including component type, component number, component name and component version number; component definition nodes of different types of components have node styles with different shapes, colors and icons; The module structure node includes a product structure node and a component structure node; the product structure node refers to an inherent child node of a product definition node, including information such as a node title, and is used to divide a product diagram, and a multi-level child node set of each structure node describes a part of the logic of the model product to which it belongs; the component structure node refers to an inherent child node of a component definition node, including information such as a node title, and is used to divide a component diagram, and a multi-level child node set of each structure node describes a part of the logic of the component to which it belongs; The module group node includes a product group node and a component group node; the product group node is used to group products in the model view, and contains information including the group name; The module description node refers to the smallest description unit of model products and components, including information such as description type, node title and description content; the multi-level description node set under the model product or component structure node describes part of the logic of the model product or component; description nodes of different description types have different semantics and different node styles; The extended description resource nodes include picture nodes, file nodes and hyperlink nodes, which are used for extended description of the module; The module link node includes a product link node and a component link node; the product link node refers to a node representing a model product outside the product diagram to which it belongs, and includes information including product type, product number, product name and product version number. A product is integrated into other product diagrams and model views in the form of a product link node; the node style of the product link node is consistent with the node style of the product definition node of the model product represented; the component link node refers to a node representing a component outside the component diagram to which it belongs, and includes information including component type, component number, component name and component version number; a component is integrated into other component diagrams and other product diagrams of the model product to which it belongs in the form of a component link node; the node style of the component link node is consistent with the node style of the component definition node of the component represented; The steps of software requirement logic modeling based on the metamodel include: Step 1: Business logic modeling: A business structure artifact and a corresponding artifact graph are constructed for the target model. The artifact graph includes an artifact definition node of the business structure artifact as a root node. One or more business domain component definition nodes having a hierarchical relationship are extended and added after the artifact definition node of the business structure artifact to define the business domain components. Build zero or more business process artifacts for the target model. For each business process artifact, create a corresponding artifact diagram. The artifact diagram contains an artifact definition node of the business process artifact as the root node, a flowchart structure node, and a business scenario structure node. Expand the resource node after the flowchart structure node to link the flowchart uploaded and stored in advance. Build zero or more business object artifacts and create zero or more business service artifacts for the target model. For each business service artifact or business service artifact, create a corresponding artifact diagram. The artifact diagram contains an artifact definition node of the business object artifact or business service artifact as the root node, a business rule structure node, a user story structure node, and a business process logic structure node. On the product definition nodes of business process products, business object products and business service products, set the information including number, name and business domain respectively; expand the component group nodes with hierarchical relationship after various structure nodes of business process products, business object products and business service products, build the node tree corresponding to the structure node, expand and add component definition nodes after the last node of each node tree, and build the corresponding component diagram; add component link points in the business-related component diagram; The business structure artifact, business process artifact, business object artifact and business service artifact constitute the business model artifact of the target model; Step 2: Functional logic modeling: Construct a functional structure artifact and a corresponding artifact diagram for the target model. The artifact diagram includes an artifact definition node of the functional structure artifact as a root node. One or more functional component definition nodes with a hierarchical relationship are extended after the artifact definition node of the business structure artifact to define the functional module components. Build zero or more user interface artifacts for the target model. For each user interface artifact, create a corresponding artifact graph, which includes an artifact definition node of the user interface artifact as a root node, an interface view structure node, a parameter variable structure node, an interface rule structure node, an interface event capability structure node, and an interface basic capability structure node. Build zero or more interactive function artifacts for the target model. For each interactive function artifact, create a corresponding artifact diagram. The artifact diagram contains an artifact definition node of the interactive function artifact as the root node, a target structure node, a main use case structure node, and an other use case structure node. Construct zero or more timing function products and create zero or more interface products for the target model. For each timing function product or interface product, create a corresponding product graph. The product graph contains a product definition node of the timing function product or interface function product as a root node and a target structure node. On the product definition nodes of the functional structure products, user interface products, interactive function products, timing function products and interface function products, set the information including number, name and function module respectively; expand the component group node with hierarchical relationship after the user interface products, interactive function products, timing function products and interface function products, build a node tree corresponding to the structure node, expand and add component definition nodes after the last node of each node tree, and build the corresponding component diagram; add component link points in the business-related component diagram; The business structure product, user interface product, interactive function product, timing function product and interface function product constitute the functional model product of the target model; Step 3: Build the model view: Build a business map based on the constructed business model artifacts; Build a functional map based on the constructed functional model artifacts; Build the overall model map based on the constructed business map and functional map; The business map, function map and model overview map constitute the model view of the target model; The business model artifacts, functional model artifacts and model views together constitute the target model.

2. A mind-map demand modeling method according to claim 1, characterized in that: The business structure artifact is used to describe the business domain set of the target model; a target model has and only has one business structure artifact, and a business structure artifact contains one or more business domain components with a hierarchical relationship; the business domain component is used to define a business domain of the target model; The business process artifact is used to describe the business process of the target model; A target model has zero or more business process artifacts, and a business process artifact contains at least one business scenario component; the business scenario component is used to describe the sub-process of the business process artifact under the selected scenario; The business object artifact is used to describe the business requirement logic unit related to the business data in the business domain; A target model has one or more business object artifacts. A business object artifact contains zero or more business rule components, zero or more user story components, and zero or more business process logic components. The business service artifact is used to describe the business requirement logic unit related to the business object in the business domain; A target model has zero or more business service artifacts, and a business service artifact contains zero or more business rule components, zero or more user story components, and zero or more business process logic components.

3. A mind-map demand modeling method according to claim 1, characterized in that: The functional structure artifact is used to describe the functional module set of the target model; a target model has and only has one functional structure artifact, and a functional structure artifact includes one or more functional module components with a hierarchical relationship; the functional module component defines a functional module of the target model; The user interface artifact is used to describe a user interface of the target model; A target model has one or more user interface artifacts, and a user interface artifact includes one or more interface view components, one or more interface rule components, one or more interface event capability components, and zero or more interface basic capability components; wherein the interface view component is used to describe the interface graphic structure of the user interface in a certain mode, the interface rule component includes a general interface component used to describe the interface end processing logic of the topic related to the user interface, and a data control component used to describe the input and output data control logic of the user interface artifact; the interface event capability component is used to describe the interface end processing logic and business data processing logic of the user interface artifact in response to human-computer interaction events; the interface basic capability component is used to describe the common interface end processing logic and business data processing logic that appear in the event response logic of multiple interface event components; The interactive functional artifact is used to describe the system functional use case of the human-computer interaction type of the target model; a target model has one or more interactive functional artifacts; The timing function artifact is used to describe the system function of the target model triggered by time. A target model has one or more timing function artifacts; The interface function product is used to describe the system interface opened by the target model to the external system. A target model has one or more interface function products.

4. The mind-map requirement modeling method according to claim 1, characterized in that: The business map refers to a mind-map classification summary of business model products belonging to the final business domain; The functional map refers to a mind-map summary of the user interface products, interactive function products, timing function products, and interface function products belonging to the final functional module; The model overview diagram refers to a mind-map summary diagram of all model products of the target model.

5. The mind-map requirement modeling method according to claim 1, characterized in that: The step 1, business logic modeling specifically includes: Step 1.1: Build the business structure artifact and the business domain components it contains: Step 1.1.1, create a product diagram of a new business structure product, including a product definition node of the business structure product as a root node; Step 1.1.2, extending and adding one or more business domain component definition nodes having a hierarchical relationship after the product definition node of the business structure product; Step 1.1.3, set the information including the business domain number and name on each business domain component definition node to complete the definition of the business domain component; Step 1.2: Build the business process artifact and the business scenario components it contains: Step 1.2.1, create a product diagram of a new business process product, including a product definition node of the business process product as the root node, a flowchart structure node, and a business scenario structure node; Step 1.2.2: Set the number, name, business domain and other information on the product definition node of the business process product to complete the definition of the business process product. Step 1.2.3, add one or more resource nodes after the flowchart structure node, set the storage path of the picture or file of the flowchart of the business process product in the file management system on the resource node, and complete the link of the flowchart. The picture or file of the flowchart is uploaded and stored in the file management system in advance; Step 1.2.4, after the business scenario structure node, zero or more component group nodes with a hierarchical relationship are added, and the business scenario structure node and the corresponding component group node constitute a business scenario group node tree; After a last-level node in the business scenario group node tree, a business scenario component definition node is added and expanded, and information including a number and a name is set on the business scenario component definition node to complete the definition of the business scenario component; Take each business scenario component definition node as the root node and build the corresponding business scenario component graph; Step 1.3: Build the business object artifact and its information structure components, common business rule components, user story components, business transaction components, and basic logic components: Step 1.3.1, create a product diagram of a new business object product, including a business object product definition node as the root node, a business rule structure node, a user story structure node, and a business process logic structure node; Step 1.3.2, set the information including number, name, and business domain on the product definition node of the business object product to complete the definition of the business object product; Step 1.3.3, after the business rule structure node, zero or more component group nodes with a hierarchical relationship are added, and the business rule structure node and the corresponding component group node constitute a business rule group node tree; After a last-level node of the business rule group node tree, expand and add an information structure component definition node or a general business rule component definition node, set the information including number, name, and type on the information structure component definition node to complete the definition of the information structure component, and set the information including number, name, and type on the general business rule component definition node to complete the definition of the general business rule component; Taking the information structure component definition node as the root node, the information structure component diagram is extended and constructed; taking the general business rule component definition node as the root node, the general business rule component diagram is extended and constructed; Step 1.3.4, add zero or more component group nodes with hierarchical relationships after the user story structure node. The user story structure node and the corresponding component group node constitute a user story group node tree; After a last-level node in the user story group node tree, expand and add a user story component definition node, set the information including number, name, and type on the user story component definition node, and complete the definition of the user story component; Take the user story component definition node as the root node and expand to build the user story component diagram; Step 1.3.5, after the business processing logic structure node, zero or more component group nodes with a hierarchical relationship are added, and the business processing logic structure node and the corresponding component group node constitute a business processing logic group node tree; Expand and add a business transaction component definition node after a last-level node of the business processing logic group node tree, set information including number, name, and type on the business transaction component definition node, and complete the definition of the business transaction component; Taking the business transaction component definition node as the root node, expand and construct the business transaction component graph; In the user story component diagram associated with the business transaction component, add a business transaction component link node; Step 1.3.6, expand and add a basic logic component definition node after a last node of the business processing logic group node tree described in step 1.3.5, and set the information including number, name, and type on the basic logic component definition node to complete the definition of the basic logic component; Taking the basic logic component definition node as the root node, expand and construct the basic logic component diagram; Add a basic logic component link node to a business transaction component diagram or other component diagram associated with the basic logic component; Step 1.4: Build business service artifacts and their common business rule components, user story components, business transaction components, and basic logic components: Step 1.4.1, create an initialization artifact diagram of a new business service artifact, including an artifact definition node of the business service artifact as the root node, a business rule structure node, a user story structure node, and a business process logic structure node; Step 1.4.2: Set the number, name, business domain and other information on the product definition node of the business service product to complete the definition of the business service product. Step 1.4.3, after the business rule structure node, zero or more component group nodes with a hierarchical relationship are added, and the business rule structure node and the corresponding component group node constitute a business rule group node tree; After a last node of the business rule group node tree, expand and add a general business rule component definition node, set the information including number, name, and type on the general business rule component definition node, and complete the definition of the general business rule component; Taking the general business rule component definition node as the root node, expand and construct the general business rule component graph; Step 1.4.4, add zero or more component group nodes with hierarchical relationships after the user story structure node. The user story structure node and the corresponding component group node constitute a user story group node tree; After a last-level node in the user story group node tree, expand and add a user story component definition node, set the information including number, name, and type on the user story component definition node, and complete the definition of the user story component; Take the user story component definition node as the root node and expand to build the user story component diagram; Step 1.4.5, after the business processing logic structure node, zero or more component group nodes with a hierarchical relationship are expanded and added, and the business processing logic structure node and the corresponding component group node constitute a business processing logic group node tree; Expand and add a business transaction component definition node after a last-level node of the business processing logic group node tree, set information including number, name, and type on the business transaction component definition node, and complete the definition of the business transaction component; Taking the business transaction component definition node as the root node, expand and construct the business transaction component graph; In the user story component diagram associated with the business transaction component, add a business transaction component link node; Step 1.4.6, expand and add a basic logic component definition node after a last-level node of the business processing logic group node tree described in step 1.4.5, and set information including number, name, and type on the basic logic component definition node to complete the definition of the basic logic component; Taking the basic logic component definition node as the root node, expand and construct the basic logic component diagram; Add a basic logic component link node to the business transaction component diagram or other component diagram associated with the basic logic component.

6. A mind-map demand modeling method according to claim 1, characterized in that: The step 2, functional logic modeling specifically includes: Step 2.1: Construct the functional structure product and its functional module components: Step 2.1.1, create an initialization artifact graph of a new functional structure artifact, including an artifact definition node of the functional structure artifact as a root node; Step 2.1.2, extending and adding one or more function module component definition nodes having a hierarchical relationship after the product definition node of the functional structure product; Step 2.1.3, set the information including the function module number and name on each function module component definition node to complete the definition of the function module component; Step 2.2: Build the user interface product and its included interface view components, general interface rule components, data control components, interface event capability components and interface basic capability components: Step 2.2.1, create a product diagram of a new user interface product, including a product definition node of the user interface product as a root node, an interface view structure node, a parameter variable structure node, an interface rule structure node, an interface event capability structure node, and an interface basic capability structure node, wherein the parameter variable structure node has three child nodes, namely, an input parameter structure node, an output parameter structure node, and an interface variable structure node; Step 2.2.2, set the information including number, name, and function module on the product definition node of the user interface product to complete the definition of the user interface product; Step 2.2.3, expand and add an interface view component definition node after the interface view structure node, and then set the information including the number and name on the interface view component definition node to complete the definition of the interface view component; Taking the interface view component definition node as the root node, expand and construct the interface view component graph; Step 2.2.4, add zero or more description nodes after the input parameter structure node to define and describe the input parameters of several user interfaces; After the output parameter structure node, zero or more description nodes are added to define and describe the output parameters of several user interfaces; Add zero or more description nodes after the interface variable structure node to define and describe several internal variables of the user interface; Step 2.2.5, after the interface rule structure node, zero or more component group nodes with a hierarchical relationship are added, and the interface rule structure node and the corresponding component group node constitute an interface rule group node tree; After a last node of the interface rule group node tree, expand and add a general interface rule component definition node, set the number, name, type and other information on the general interface rule component definition node, and complete the definition of the general interface rule component; after a last node of the interface rule group node tree, expand and add a data control component definition node, set the number, name, type and other information on the data control component definition node, and complete the definition of the data control component; Taking the general interface rule component definition node as the root node, expand and build the general interface rule component diagram; taking the data control component definition node as the root node, expand and build the data control component diagram; Step 2.2.6, after the interface basic capability structure node, expand and add zero or more component group nodes with a hierarchical relationship, and the interface basic capability structure node and the corresponding component group node constitute the interface basic capability group node tree; After a last node of the interface basic capability group node tree, expand and add an interface basic capability component definition node, set the information including number, name, and type on the interface basic capability component definition node, and complete the definition of the interface basic capability component; Take the interface basic capability component definition node as the root node and expand and build the interface basic capability component diagram; Step 2.2.7, after the interface event capability structure node, expand and add zero or more component group nodes with a hierarchical relationship, and the interface event capability structure node and the corresponding component group node constitute an interface event capability group node tree; After a last node of the interface event capability group node tree, an interface event capability component definition node is added, and information including number, name, and type is set on the interface event capability component definition node to complete the definition of the interface event capability component; Taking the interface event capability component definition node as the root node, expand and construct the interface event capability component graph; Step 2.3: Build interactive functional products: Step 2.3.1, create an initialization artifact diagram of a new interactive function artifact, including an artifact definition node of the interactive function artifact as a root node, a target structure node, a main use case structure node, and an other use case structure node; Step 2.3.2, set the information including number, name, and function module on the product definition node of the interactive function product to complete the definition of the interactive function product; Step 2.3.3, adding a description node indicating the execution meaning after the target structure node of the interactive function product, and adding a business transaction component link node after the description node indicating the execution meaning; Step 2.3.4, after the main use case structure node, expand and add zero or more description nodes describing user operations, expand and add a description node representing system response after the description node describing each user operation, expand and add an interface event capability component link node, zero or one user interface product link node, and zero or one interface view component link node after each description node representing system response; Step 2.3.5, expand and add zero or more description nodes that define use cases after other use case structure nodes, expand and add one or more description nodes that describe user operations after each use case description node, expand and add a description node that represents system response after each description node that describes user operations, expand and add an interface event capability component link node, zero or one user interface artifact link node, and zero or one interface view component link node after each description node that represents system response; Step 2.4: Build a timing function product: Step 2.4.1, create a product diagram of a new timed function product, including a product definition node of the timed function product as a root node and a target structure node; Step 2.4.2, set the information including number, name, and function module on the product definition node of the timing function product; Step 2.4.3, after the target structure node of the timing function product, expand and add a description node indicating the execution meaning, and expand and add a business transaction component link node after the description node; Step 2.5: Build interface functional products: Step 2.5.1, create a product diagram of the new interface function product, including a product definition node of the timing function product as the root node and a target structure node; Step 2.5.2, set the information including number, name, and function module on the product definition node of the interface function product; Step 2.5.3: After the target structure node of the interface function product, expand and add a description node indicating the execution meaning, and expand and add a business transaction component link node after the description node.

7. A mind-map demand modeling method according to claim 1, characterized in that: The step 3, constructing the model view specifically includes: Step 3.1: Build a business map: Step 3.1.1, each final business domain constructs an initialization business map, including a root node and the corresponding component link node of the final business domain component; Step 3.1.2, expand and add 0 or more product group nodes with a hierarchical relationship after the business map root node, and the business map root node and the corresponding product group node constitute the business map product group node tree; Step 3.1.3, after each last node of the business map product group node tree, expand and add 0 or more business process product link nodes, 0 or more business object product link nodes, and 0 or more business service product link nodes; Step 3.2: Build a functional map: Step 3.2.1, each final functional module constructs an initialization function map including a root node as a component link node of the corresponding final functional module component; Step 3.2.2, after the function map root node, expand and add 0 or more product group nodes with a hierarchical relationship, the function map root node and the corresponding product group node constitute the function map product group node tree; Step 3.2.3, after each last level node of the function map product group node tree, expand and add 0 or more interactive function product link nodes, 0 or more timing function product link nodes, 0 or more interface function product link nodes, and 0 or more user interface product link nodes; Step 3.3: Build the overall model diagram: Step 3.3.

1. For each target model, construct an initial model graph with a root node representing the target model. Step 3.3.2, expand and add a business structure product link node after the root node of the model general diagram, and according to the hierarchical relationship of the business domain components in the business structure product diagram, expand and add corresponding business domain component link nodes layer by layer after the business structure product link node; the corresponding business domain component link nodes constitute a business domain component node tree; Step 3.3.3, after each last node of the business domain component node tree, expand and add the node set of the business map of the corresponding business domain component, excluding its root node; Step 3.3.4, expand and add a function structure product link node after the root node of the model general diagram, and expand and add corresponding function module component link nodes layer by layer after the function structure product link node according to the hierarchical relationship of the function module components in the function structure product diagram; the corresponding function module component link nodes constitute a function module component node tree; Step 3.3.5, after each last node of the function module component node tree, expand and add the node set of the function map of the corresponding function module component, excluding its root node.

8. A mind-map requirement modeling system, executing a mind-map requirement modeling method according to any one of claims 1 to 7, characterized in that: The mind-map requirement modeling system has the following modules: Model management module, used to create new models, query models, modify models, and delete models; Business model product management module, namely: The business structure artifact management module is used to generate business structure artifacts for the target model, edit business structure artifact diagrams, and view business structure artifact diagrams; The business process artifact management module is used to create new business process artifacts for the target model, edit business process artifact diagrams, query business process artifacts, view business process artifact diagrams, and delete business process artifacts; The business object artifact management module is used to create a new business object artifact for the target model, edit the business object artifact diagram, query the business object artifact, view the business object artifact diagram, and delete the business object artifact; The business service artifact management module is used to create new business service artifacts for the target model, edit business service artifact graphs, query business service artifacts, view business service artifact graphs, and delete business service artifacts; Functional model product management module, namely: Functional structure artifact management module, used to generate functional structure artifacts for target models, edit functional structure artifact diagrams, and view functional structure artifact diagrams; A user interface artifact management module is used to create a new user interface artifact for a target model, edit a user interface artifact diagram, query a user interface artifact, view a user interface artifact diagram, and delete a user interface artifact; An interactive function artifact management module is used to create a new interactive function artifact for a target model, edit an interactive function artifact diagram, query an interactive function artifact, view an interactive function artifact diagram, and delete an interactive function artifact; The timing function product management module is used to create a new timing function product for the target model, edit the timing function product diagram, query the timing function product, view the timing function product diagram, and delete the timing function product; The interface function artifact management module is used to create a new interface function artifact for the target model, edit the interface function artifact diagram, query the interface function artifact, view the interface function artifact diagram, and delete the interface function artifact; Model view management module, namely: Business map management module, used to create a new business map for the target model, edit the business map, and view the business map; Function map management module, used to create a new function map for the target model, edit the function map, and view the function map; The model master diagram management module is used to create a new model master diagram for the target model, edit the model master diagram, and view the model master diagram.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method described in any one of claims 1 to 7 is implemented.

10. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

11. A computer device, characterized in that: It includes: one or more processors; A storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors are enabled to implement the method described in any one of claims 1 to 7.