Management Method of Financial Products

Abstract

The present disclosure provides a management method for financial products, which relates to the technical field of big data intelligent analysis. The method includes: configuring product basic information through a first node, storing the product basic information in a database, and sending the product identifier of the product basic information to a second node; configuring at least one product requirement information by the second node according to the product identifier, associating and storing the product requirement information with the product identifier in the database, and sending the requirement identifier of the product requirement information to a third node; obtaining, by the third node according to the requirement identifier, an execution code adapted to the product requirement information, executing the execution code to obtain execution information, and associating and storing the code information with the requirement identifier in the database; generating, by a fourth node when the product requirement information and the code information meet the closing requirements, a financial product based on the product basic information, the product requirement information, and the code information. Thus, the degree of manual participation in product management can be reduced, and the product quality can be improved.

Description

Technical Field

[0001] The present disclosure relates to the technical field of big data intelligent analysis, and particularly to a management method for financial products. Background Art

[0002] In the management of traditional financial products, the management of multiple process links of the entire product (such as the project establishment link, the planning link, the execution link, and the project closing link) is mainly achieved through manual control. For example, through manual offline communication methods (such as the method of sending paper documents offline), the management of each process link is realized.

[0003] The above-mentioned manual control method is prone to errors, resulting in difficult control of the product generation quality and high labor costs. Summary of the Invention

[0004] The present disclosure aims to at least partly solve one of the technical problems in the related art.

[0005] One aspect of the present disclosure proposes a management method and system for financial products to reduce the degree of manual participation in financial product management, reduce labor costs, and improve the generation quality of financial products.

[0006] An embodiment of the first aspect of the present disclosure proposes a management method for financial products, including:

[0007] In response to a product configuration operation by a first node, configuring product basic information, storing the product basic information in a database, and sending a product identifier of the product basic information to a second node;

[0008] The second node receives the product identifier, queries the product basic information associated with the product identifier from the database, in response to a demand configuration operation, configures at least one product demand information according to the product basic information, and stores the product demand information associated with the product identifier in the database, and sends a demand identifier of the product demand information to a third node;

[0009] The third node receives the demand identifier, queries the product demand information associated with the demand identifier from the database, obtains an execution code adapted to the product demand information, executes the execution code to obtain execution information, and stores the code information (where the code information includes the execution code and the corresponding execution information) associated with the demand identifier in the database;

[0010] Obtain the product identifier through the fourth node, query the product basic information and product requirement information associated with the product identifier, and the code information associated with the requirement identifier of the product requirement information from the database, and when the product requirement information and the code information meet the closing requirements, generate a financial product associated with the product identifier based on the product basic information, the product requirement information, and the code information.

[0011] The second aspect embodiment of the present disclosure proposes a management system for financial products, including:

[0012] A first node, configured to, in response to a product configuration operation, configure product basic information, store the product basic information in a database, and send the product identifier of the product basic information to a second node;

[0013] A second node, configured to receive the product identifier, query the product basic information associated with the product identifier from the database, in response to a requirement configuration operation, configure at least one product requirement information according to the product basic information, and store the product requirement information associated with the product identifier in the database, and send the requirement identifier of the product requirement information to a third node;

[0014] A third node, configured to receive the requirement identifier, query the product requirement information associated with the requirement identifier from the database, obtain an execution code adapted to the product requirement information, execute the execution code to obtain execution information, and store the code information associated with the requirement identifier in the database; wherein, the code information includes the execution code and the corresponding execution information;

[0015] A fourth node, configured to obtain the product identifier, query the product basic information and product requirement information associated with the product identifier, and the code information associated with the requirement identifier of the product requirement information from the database, and when the product requirement information and the code information meet the closing requirements, generate a financial product associated with the product identifier based on the product basic information, the product requirement information, and the code information.

[0016] The third aspect embodiment of the present disclosure proposes an electronic device, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the program, it implements the management method of the financial product proposed in the first aspect embodiment of the present disclosure.

[0017] The fourth aspect embodiment of the present disclosure proposes a non-transitory computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, it implements the management method of the financial product proposed in the first aspect embodiment of the present disclosure.

[0018] Embodiments of the fifth aspect of the present disclosure propose a computer program product. When the instructions in the computer program product are executed by a processor, they perform the method for managing financial products proposed in the embodiments of the first aspect of the present disclosure.

[0019] The technical solutions provided in the above embodiments of the present disclosure have at least the following beneficial effects:

[0020] 1. Only identification information is transmitted between nodes, which can improve the data transmission efficiency, and avoid the situation of data leakage caused by transmitting important information related to financial products, thereby enhancing the security of information related to financial products. Moreover, after each node processes or manages the process stage of the financial product it is responsible for, it automatically transmits the information required by the next node, so that the next node can process or manage the process stage of the financial product it is responsible for according to the information it needs, which can reduce the degree of manual participation in financial product management. In addition, the last node in the system generates the final financial product based on the processing result (or management result) of the previous node only when it verifies that the processing result (or management result) of the previous node meets the closing requirements, which can improve the generation quality of financial products and meet the actual application requirements.

[0021] 2. Two coding algorithms and encryption algorithms are simultaneously used to encrypt the data transmitted between nodes, which can reduce the probability of encrypted data being cracked, and thus enhance the security of data transmission between nodes. Moreover, the modulus N in the encryption algorithm is greater than the first set threshold, which can further avoid the situation of encrypted data being cracked, thereby further enhancing the security of the data transmitted between nodes.

[0022] 3. The management node (denoted as the fifth node in the present disclosure) can manage the data involved in each node (including but not limited to index information, product information, requirement information, code information, task information, personnel information (such as the person in charge of each node), etc.) based on the interface visualization method. It can not only meet the actual management needs and know the actual situation of each process link of the financial product, but also trace the person in charge of each process link of the financial product and the development records, etc., further meeting the actual management needs of the management personnel. In addition, in the case of not reaching the planned date, the product requirement information and code information can be dynamically adjusted according to the actual situation, so as to achieve the purpose of improving the timely response of the management of each process link of the financial product.

[0023] Additional aspects and advantages of the present disclosure will be given in part in the following description, become apparent in part from the following description, or be understood through the practice of the present disclosure. Description of the Drawings

[0024] The above and / or additional aspects and advantages of the present disclosure will become apparent and be readily understood from the following description of embodiments in conjunction with the accompanying drawings, wherein:

[0025] Figure 1 It is a schematic flowchart of a method for managing a financial product provided by an embodiment of the present disclosure;

[0026] Figure 2 It is a schematic diagram of a configuration page for product basic information provided by an embodiment of the present disclosure;

[0027] Figure 3 It is a schematic diagram of a configuration page for product requirement information provided by an embodiment of the present disclosure;

[0028] Figure 4 It is a schematic flowchart of another method for managing a financial product provided by an embodiment of the present disclosure;

[0029] Figure 5 It is a schematic diagram of an encryption principle provided by an embodiment of the present disclosure;

[0030] Figure 6 It is a schematic diagram of a decryption principle provided by an embodiment of the present disclosure;

[0031] Figure 7 It is a schematic flowchart of another method for managing a financial product provided by an embodiment of the present disclosure;

[0032] Figure 8 It is a schematic flowchart of another method for managing a financial product provided by an embodiment of the present disclosure;

[0033] Figure 9 It is a schematic diagram of the principle of dynamically adjusting product requirement information for the second node provided by an embodiment of the present disclosure;

[0034] Figure 10 It is a schematic flowchart of another method for managing a financial product provided by an embodiment of the present disclosure;

[0035] Figure 11 It is a schematic diagram of the structure of a financial product management system provided by an embodiment of the present disclosure;

[0036] Figure 12 It is a schematic diagram of the structure of another financial product management device provided by an embodiment of the present disclosure;

[0037] Figure 13 It is a schematic diagram of the structure of an electronic device shown in an exemplary embodiment of the present disclosure. Detailed implementation manners

[0038] Embodiments of the present disclosure will be described in detail below. Examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to explain the present disclosure, but should not be construed as limiting the present disclosure.

[0039] Currently, in the management of traditional financial products, the management of multiple process links (such as project establishment, planning, execution, and project closure) of the entire product is mainly achieved through manual control. For example, data is exported manually from the support systems corresponding to each process link and the exported data is managed. Moreover, for the developed financial products, only basic information such as batch numbers, verification dates, and release dates can be recorded.

[0040] For example, different support systems are used to store data in each process link such as project establishment, planning, execution, and project closure. Data can be exported manually from the support systems corresponding to each process link and the exported data can be managed.

[0041] The above management method lacks a complete system to automatically converge and perceive the data in the support systems of each process link, and is even less able to display the index data involved in each process link through the analysis of a visualization interface. In addition, the product quality problems in each process link cannot be timely controlled. Often, in order to meet the project schedule, a large amount of manpower needs to be invested endlessly to ensure the delivery time of the project, but the product quality after delivery cannot be guaranteed.

[0042] Moreover, the manual management or operation method at least has the following obvious disadvantages: it is prone to errors; the labor cost is relatively high, and once overly relying on human control, when personnel flow, it will have a great impact on the production of products; it is impossible to trace the operators and development records of each process link of financial products, and the problems that occur during the release of financial products cannot be traced back.

[0043] In view of at least one of the above problems, one aspect of the present disclosure proposes a management method and system for financial products.

[0044] The management method and system for financial products according to embodiments of the present disclosure will be described below with reference to the accompanying drawings.

[0045] Figure 1 It is a flowchart of a management method for a financial product provided by an embodiment of the present disclosure.

[0046] As Figure 1 shown, the management method for the financial product includes the following steps S101 to S104:

[0047] Step S101: In response to a product configuration operation by the first node, configure the product basic information, store the product basic information in the database, and send the product identifier of the product basic information to the second node.

[0048] Among them, the first node is also called the project establishment node.

[0049] In the embodiments of the present disclosure, the product basic information includes but is not limited to the following information: product name, product number, product person in charge, department to which the product person in charge belongs, product classification, sub-classification, product description, note information, etc.

[0050] Among them, classified by trading venue, the product classification of financial products includes: on-exchange financial products and over-the-counter financial products; classified by income method, the product classification of financial products includes: fixed-income products and floating-income products; classified by asset category, the product classification of financial products mainly includes: cash and short-term assets, fixed-income securities, equity assets, etc.

[0051] Among them, different financial products correspond to different sub-classifications. Taking insurance products as an example of financial products, the sub-classifications include life insurance, property insurance, medical insurance, accidental injury insurance, etc.; taking funds as an example of financial products, the sub-classifications include money funds, bond funds, stock funds, etc.

[0052] In the embodiments of the present disclosure, the first node configures the product basic information of financial products in response to a product configuration operation triggered by relevant personnel. For example, relevant personnel click the new button on the operation page to enter the Figure 2 configuration page (or entry page) of the new product as shown, and enter the product basic information of the new product on this configuration page.

[0053] In the embodiments of the present disclosure, the first node obtains the product identifier of the product basic information (such as the product ID (Identity, the unique identifier of the financial product)). For example, this product identifier can be automatically generated when configuring the product basic information. After that, the first node associates and stores the product basic information and the product identifier in the database, and sends the product identifier of the product basic information to the second node.

[0054] Step S102: The second node receives the product identifier, queries the product basic information associated with the product identifier from the database, configures at least one product requirement information according to the product basic information in response to a requirement configuration operation, associates and stores the product requirement information and the product identifier in the database, and sends the requirement identifier of the product requirement information to the third node.

[0055] Among them, the second node is also called the planning node.

[0056] Among them, the product requirement information includes, but is not limited to, the following information: requirement name, requirement number, product version, requirement type (requirements proposed by users, requirements identified through product comparison, etc.), module to which the requirement belongs (such as front-end display, back-end storage, etc. modules), requirement source, requirement category (such as new functions, defect repair, additional testing, etc.), requirement reviewer, requirement priority, planned cycle, planned man-hours, requirement description information, and requirement documents (used to describe the detailed requirement information), etc.

[0057] In an embodiment of the present disclosure, the second node receives the product identifier sent by the first node, queries the product basic information associated with the product identifier from the database, and then, in response to the requirement configuration operation triggered by the relevant personnel by the second node, configures at least one product requirement information according to the product basic information.

[0058] For example, the relevant personnel enter the configuration page as shown in Figure 3 by clicking the add button on the operation page, and enter the product requirement information of the financial product on this configuration page.

[0059] In an embodiment of the present disclosure, the second node may also associate and store each product requirement information with the product identifier in the database, and send the requirement identifier (such as requirement ID) of each product requirement information to the third node.

[0060] Step S103, the third node receives the requirement identifier, queries the product requirement information associated with the requirement identifier from the database, obtains the execution code adapted to the product requirement information, executes the execution code to obtain the execution information, and associates and stores the code information with the requirement identifier in the database.

[0061] Among them, the code information includes the execution code and the corresponding execution information.

[0062] In an embodiment of the present disclosure, the third node receives the requirement identifier sent by the second node and queries the product requirement information associated with the requirement identifier from the database.

[0063] In an embodiment of the present disclosure, after the third node obtains the product requirement information associated with the requirement identifier, it can display the product requirement information so that the relevant personnel can write the execution code that matches or adapts to the product requirement information according to the product requirement information. Then, the third node executes the execution code to obtain the execution information and submits the code information, where the code information includes the execution code and the execution information corresponding to the execution code.

[0064] In an embodiment of the present disclosure, the third node may also associate and store the code information with the requirement identifier in the database.

[0065] Step S104: Obtain the product identifier through the fourth node, query the product basic information and product requirement information associated with the product identifier from the database, query the code information associated with the requirement identifier of the product requirement information, and generate a financial product associated with the product identifier based on the product basic information, product requirement information, and code information when the product requirement information and code information meet the requirements for project completion.

[0066] In the embodiments of the present disclosure, the product identifier can be passed to the fourth node by any one of the nodes, or can also be manually input by relevant personnel or managers. The embodiments of the present disclosure do not limit this.

[0067] In the embodiments of the present disclosure, through the fourth node, according to the product identifier, query the product basic information and product requirement information associated with the product identifier from the database, and according to the requirement identifier of the product requirement information, query the code information associated with the requirement identifier from the database. Then, the fourth node can determine whether the product requirement information and code information meet the requirements for project completion. If so, a financial product associated with the product identifier is generated based on the product basic information, product requirement information, and code information.

[0068] In the method for managing financial products according to the embodiments of the present disclosure, only identification information is transmitted between nodes, which can improve the data transmission efficiency, avoid the situation of data leakage caused by transmitting important information related to financial products, and enhance the security of information related to financial products. Moreover, after each node processes or manages the data in the process stage of the financial product it is responsible for, it automatically transmits the information required by the next node to enable the next node to process or manage the data in the process stage of the financial product it is responsible for according to the information it needs, which can reduce the degree of manual participation in financial product management. In addition, the last node in the system generates the final financial product based on the processing results (or management results) of the previous nodes only when it verifies that the processing results (or management results) of the previous nodes meet the requirements for project completion, which can improve the generation quality of financial products and meet the actual application requirements.

[0069] In any one of the embodiments of the present disclosure, in order to improve the security of data transmission, the data transmitted between nodes can be encrypted data. The following combines Figure 4 , and details the data encryption process and decryption process.

[0070] Figure 4 It is a schematic flowchart of another method for managing financial products provided by the embodiments of the present disclosure.

[0071] As Figure 4 shown, the method for managing financial products may include the following steps S401 to S412:

[0072] Step S401: In response to a product configuration operation by the first node, configure the product basic information and store the product basic information in the database.

[0073] For the explanation of step S401, reference can be made to the relevant descriptions in any embodiment of the present disclosure, which will not be elaborated here.

[0074] Step S402: By the first node, use the public key of the second node to perform an encryption process on the product identifier to obtain the encrypted data of the first node.

[0075] In the embodiments of the present disclosure, in order to improve the security of the data transmitted between the first node and the second node, when the first node sends data to the second node, the first node can use the public key of the second node to encrypt the data to be transmitted. That is, the data sent by the first node to the second node is the data encrypted using the public key of the second node.

[0076] That is to say, in the present disclosure, an asymmetric encryption algorithm is used to encrypt the data transmitted between nodes. The asymmetric encryption algorithm includes two different keys, one of which is the public key and the other is the private key. The asymmetric encryption algorithm enables decryption without directly transmitting the key, which can ensure the security of data transmission and avoid the risk of the encrypted data being cracked due to the direct transmission of the key. Specifically, the public key is used to encrypt the data, and the private key is used to decrypt the encrypted data. Among them, the encrypted data can only be decrypted using the private key to obtain the correct data, otherwise incorrect data will be obtained.

[0077] Specifically, by the first node using the public key of the second node to perform an encryption process on the product identifier to obtain the encrypted data of the first node, so that the encrypted data of the first node can be sent to the second node through the first node subsequently.

[0078] Among them, the public key of the second node is transmitted from the second node to the first node. For example, after the second node generates a pair of keys (public key and private key), the second node keeps the private key for itself (i.e., does not disclose the private key), and only discloses the public key (for example, any node can obtain the public key). The second node transmits its own public key to the first node, so that the first node encrypts the data to be transmitted (i.e., the product identifier) using the public key of the second node, obtains the encrypted data of the first node, and sends the encrypted data of the first node to the second node. Correspondingly, subsequently, after the second node receives the encrypted data of the first node, it decrypts the encrypted data of the first node using its own private key to obtain the product identifier. In this process, there are only two data transmission processes. The first time is that the second node transmits the public key to the first node, and the second time is that the first node transmits the encrypted data to the second node. Even if the public key and the encrypted data are intercepted, the encrypted data cannot be cracked because only the private key of the second node can decrypt the encrypted data, preventing the leakage of data content.

[0079] Among them, there is a mathematical relationship between the public key and the private key in the key pair, and the difficulty of factoring large prime numbers is used to ensure the security of information transmission. Although the computing power of a computer is very strong and it can easily find the product of two large prime numbers, if this product is very large, it is very difficult to factor it into prime factors. Usually, an individual keeps the private key, and the public key is public (possibly held by multiple people at the same time).

[0080] For example, a 200-digit decimal number requires 300 million years to factorize, and this time exceeds the limit of human beings. Therefore, as long as the present disclosure uses a modulus N that is long enough, it can be ensured that it cannot be factored.

[0081] In any embodiment of the present disclosure, the public key of the second node includes a public key exponent E and a modulus N, where the modulus N is greater than a first set threshold to avoid the occurrence of the situation where the encrypted data is cracked and further improve the security of the data transmitted between nodes. At this time, the first node can adopt the steps S501 to S503 as Figure 5 shown to perform the encryption process:

[0082] Step S501: Based on a first coding algorithm by the first node, perform coding processing on the product identifier to obtain a target value.

[0083] In the embodiment of the present disclosure, based on a set first coding algorithm by the first node, perform coding processing on the product identifier to obtain a target value for representing or characterizing the product identifier.

[0084] For example, the first node uses a mapping dictionary to encode the product identifier to obtain a target value representing or characterizing the product identifier; wherein, the mapping dictionary includes the mapping relationship between the original text before encoding and the encoded value.

[0085] At this time, the target value is the encoded value in the mapping dictionary that has a mapping relationship with the product identifier.

[0086] Step S502: The first node uses the public key exponent E and the modulus N to encrypt the target value to obtain an encrypted value.

[0087] For example, the first node calculates the E-th power of the target value to obtain a first intermediate value, and performs a modulo operation on the first intermediate value with N to obtain the encrypted value.

[0088] That is, the specific implementation method of the asymmetric encryption algorithm is as follows: the ciphertext is the result of taking the modulo of N of the E-th power of the number representing the plaintext (taking the first node executing the encryption process as an example, the plaintext is the product identifier, and the number representing the plaintext is the target value). In other words, it is to multiply the number representing the plaintext by itself E times, and then divide the result by N to obtain the remainder, and this remainder is the ciphertext (denoted as the encrypted value in this disclosure). Among them, the combination of E and N is the public key.

[0089] For example, assume that the number representing the plaintext (subsequently referred to as the original data, marked as m) is 5. The public key E, N (13, 77) of the second node can be obtained from the database, and the original data 5 is encrypted using the public key E, N (13, 77). First, perform an encryption calculation on the original data 5 and the public key to become the ciphertext m^E mod N = 5^13 mod 77 = 26.

[0090] Step S503: The first node encodes the encrypted value based on the second encoding algorithm to obtain the encrypted data of the first node.

[0091] In the embodiment of the present disclosure, the first node encodes the encrypted value based on the set second encoding algorithm to obtain the encrypted data of the first node.

[0092] Still taking the above example, assume that the second encoding algorithm is the Base64 encoding algorithm. After base64 encoding and encrypting the encrypted string 26, the encrypted data of the first node obtained is: MjY.

[0093] In summary, by simultaneously adopting two encoding algorithms and encryption algorithms to encrypt the data transmitted between nodes, the probability of the encrypted data being cracked can be reduced, thereby enhancing the security of data transmission between nodes. Moreover, when the modulus N in the encryption algorithm is greater than the first set threshold, the situation of the encrypted data being cracked can be further avoided, thus further enhancing the security of the data transmitted between nodes.

[0094] Step S403: Send the encrypted data of the first node to the second node through the first node.

[0095] Step S404: Receive the encrypted data of the first node through the second node.

[0096] Step S405: Use the private key of the second node to perform a decryption process on the encrypted data of the first node to obtain the product identifier.

[0097] In the embodiment of the present disclosure, after receiving the encrypted data of the first node, the second node can use the private key of the second node to perform a decryption process on the encrypted data of the first node to obtain the product identifier.

[0098] Wherein, the private key of the second node includes a private key exponent D and a modulus N. The second node can perform the decryption process by using steps S601 to S603 as follows: Figure 6 As shown:

[0099] Step S601: Decode the encrypted data of the first node through the second node based on the second encoding algorithm to obtain an encrypted value.

[0100] Step S602: Use the private key exponent D and the modulus N to decrypt the encrypted value through the second node to obtain a target value.

[0101] Wherein, the modulus N used for decryption is the same as the modulus N used for encryption. The combination of D and N is the decryption key (i.e., the private key). Only by knowing these two numbers D and N can the decryption operation be completed.

[0102] As an example, the second node calculates the D-th power of the encrypted value to obtain a second intermediate value, and performs a modulo operation on the second intermediate value with N to obtain a target value.

[0103] That is, the process of the second node decrypting the encrypted data transmitted by the first node is: taking the D-th power of the ciphertext (i.e., the encrypted value) and then taking the modulus with N, to obtain the number representing the plaintext (i.e., the target value). That is, multiply the encrypted value by itself D times, and then divide the result by N to take the remainder, to obtain the target value.

[0104] It should be noted that since N is part of the public key and is public, D can also be referred to as the private key alone. Among them, the numbers D and E are closely related. Otherwise, the mechanism of decrypting the result encrypted by E with D cannot be realized. Among them, the forms of encryption and decryption are the same, that is, encryption is to calculate "mod N of the E-th power", and decryption is to calculate "mod N of the D-th power".

[0105] Still taking the above example, the private key D, N(37, 77) of the second node can be obtained from the database, and the encrypted data MjY can be decrypted using the private key D, N(37, 77). First, use the Base64 encoding algorithm to perform Base64 transcoding and decryption on the encrypted data MjY to obtain the ciphertext (i.e., the encrypted value) 26. Then, use the transcoded and decrypted number 26 and the private key to perform a decryption calculation once to obtain the number representing the plaintext: ciphertext^D mod N = 26^37 mod 77 = 5.

[0106] Step S603: The second node decodes the target value based on the first encoding algorithm to obtain the product identifier.

[0107] For example, the second node uses a mapping dictionary to decode the target value to obtain the product identifier; among them, the mapping dictionary includes the mapping relationship between the original text before encoding and the encoding value.

[0108] At this time, the product identifier is the original text before encoding in the mapping dictionary that has a mapping relationship with the target value (i.e., the encoding value).

[0109] In summary, using the same encoding algorithm as the encryption process to decrypt the encrypted data transmitted between nodes can improve the accuracy of cracking the encrypted data.

[0110] Step S406: The second node queries the product basic information associated with the product identifier from the database, configures at least one product requirement information according to the product basic information in response to the demand configuration operation, and stores the product requirement information associated with the product identifier in the database.

[0111] For the explanation of step S406, reference can be made to the relevant descriptions in any embodiment of the present disclosure, and details are not described here.

[0112] Step S407: The second node uses the public key of the third node to perform an encryption process on the demand identifier to obtain the encrypted data of the second node.

[0113] It should be noted that the implementation principle of step S407 is similar to that of step S402, and details are not described here.

[0114] Step S408: Send the encrypted data of the second node to the third node through the second node.

[0115] Step S409: Receive the encrypted data of the second node through the third node.

[0116] Step S410: Use the private key of the third node to perform a decryption process on the encrypted data of the second node through the third node to obtain a requirement identifier.

[0117] It should be noted that the implementation principle of step S410 is similar to that of step S405, and will not be elaborated here.

[0118] Step S411: Query product requirement information associated with the requirement identifier from the database through the third node, obtain an execution code adapted to the product requirement information, execute the execution code to obtain execution information, and store the code information and the requirement identifier associated in the database.

[0119] Among them, the code information includes the execution code and the corresponding execution information.

[0120] Step S412: Obtain a product identifier through the fourth node, query product basic information, product requirement information associated with the product identifier, and code information associated with the requirement identifier of the product requirement information from the database, and generate a financial product associated with the product identifier based on the product basic information, product requirement information, and code information when the product requirement information and the code information meet the closing requirements.

[0121] For the explanations of steps S411 to S412, reference can be made to the relevant descriptions in any embodiment of the present disclosure, and will not be elaborated here.

[0122] The financial product management method according to the embodiments of the present disclosure encrypts the data transmitted between nodes based on an asymmetric encryption algorithm, which can improve the security of data transmission.

[0123] To clearly illustrate any of the above embodiments, the present disclosure also proposes a financial product management method.

[0124] Figure 7 It is a schematic flowchart of another financial product management method provided by the embodiments of the present disclosure.

[0125] As Figure 7 shown, the financial product management method includes the following steps S701 to S708:

[0126] Step S701: In response to a product configuration operation through the first node, configure product basic information, store the product basic information in the database, and send the product identifier of the product basic information to the second node.

[0127] Step S702: Receive the product identifier through the second node, query the product basic information associated with the product identifier from the database, and in response to the demand configuration operation, configure multiple product demand information according to the product basic information.

[0128] For the explanatory notes of steps S701 to S702, reference can be made to the relevant descriptions in any embodiment of the present disclosure, which will not be elaborated here.

[0129] Step S703: Determine the first demand identifier from the demand identifiers of multiple product demand information through the second node.

[0130] Among them, the first demand identifier is manually selected or specified by the relevant personnel on the second node side.

[0131] Step S704: Associatively store the first demand identifier, product identifier, and task information in the database through the second node.

[0132] Among them, the task information is also manually selected or specified by the relevant personnel, and the task information includes a reference execution code adapted to the reference demand information and execution information obtained by running the reference execution code.

[0133] Among them, the reference demand information includes product demand information shared among the generated or developed financial products and / or default product demand information (pre-configured product demand information).

[0134] Step S705: Send the second demand identifier other than the first demand identifier among the multiple demand identifiers to the third node through the second node, and associatively store the product demand information associated with the second demand identifier, the second demand identifier, and the product identifier in the database.

[0135] In the embodiments of the present disclosure, the second node only sends the remaining demand identifiers other than the first demand identifier among the multiple demand identifiers (denoted as the second demand identifier in the present disclosure) to the third node, and associatively stores the product demand information associated with the second demand identifier, the second demand identifier, and the product identifier in the database.

[0136] Step S706: Receive the second demand identifier through the third node, query the product demand information associated with the second demand identifier from the database, obtain the execution code adapted to the product demand information associated with the second demand information, execute the execution code to obtain the execution information, and associatively store the code information and the second demand identifier in the database.

[0137] Among them, the code information includes the execution code and the corresponding execution information.

[0138] In an embodiment of the present disclosure, first, a third node receives a second requirement identifier, queries product requirement information associated with the second requirement identifier from a database, then, the third node obtains execution code adapted to the product requirement information associated with the second requirement identifier, and executes the execution code to obtain execution information, and then, the third node stores the code information associated with the second requirement identifier in the database.

[0139] Step S707, a fourth node obtains a product identifier, and queries product basic information, product requirement information and task information associated with the product identifier, and code information associated with a second requirement identifier associated with the product requirement information from a database.

[0140] In an embodiment of the present disclosure, a fourth node obtains a product identifier, queries product basic information and a first requirement identifier associated with the product identifier from a database, and queries task information associated with the first requirement identifier from a database. Then, the fourth node queries multiple pieces of product requirement information associated with the product identifier from the database, and queries code information associated with a second requirement identifier other than the first requirement identifier among the requirement identifiers of the multiple pieces of product requirement information.

[0141] Step S708, when the product requirement information, the code information and the task information meet the closing requirements, the fourth node generates a financial product associated with the product identifier based on the product basic information, the product requirement information, the code information and the task information.

[0142] In an embodiment of the present disclosure, the fourth node determines whether the product requirement information, the code information and the task information meet the closing requirements. If so, the fourth node generates a financial product associated with the product identifier based on the product basic information, the product requirement information, the code information and the task information.

[0143] For the management method of the financial product in the embodiment of the present disclosure, if the currently developed financial product shares the same product requirement information (denoted as reference requirement information in the present disclosure) with the existing developed financial product, the reference execution code adapted to the reference requirement information of the existing developed financial product and the execution information obtained by running the reference execution code are directly used to generate the currently developed financial product, without re-developing the corresponding execution code, which can reduce the development cost of the financial product. Or, for common or default product requirement information, there is no need to re-develop the corresponding execution code, which can further reduce the development cost of the financial product.

[0144] In any one of the embodiments of the present disclosure, the project closing requirements are determined based on the planned date and requirement description information in the product requirement information. For example, the project closing requirements are used to indicate that when the planned date is reached, the number of defects in the execution information of the code information or task information adapted to the product requirement information that must be completed must be lower than the second set threshold. At this time, in order to clearly illustrate steps S104, S412, or steps S707 to S708 in the above embodiments, the present disclosure also proposes a management method for financial products.

[0145] Figure 8 It is a schematic flowchart of another management method for financial products provided by the embodiments of the present disclosure.

[0146] As Figure 8 shown, based on any one of the above embodiments, steps S104, S412, or steps S707 to S708 may specifically include the following steps S801 to S805:

[0147] Step S801, determine whether the planned date is reached through the fourth node, and when the planned date is reached, query the product basic information, product requirement information, and task information associated with the product identifier from the database, as well as the code information associated with the requirement identifier of the product requirement information.

[0148] Among them, the product requirement information includes a planned period, and the planned period includes a start date (StartDate) and an end date (EndDate), and the planned date may be the end date in the planned period.

[0149] In the embodiments of the present disclosure, determine whether the current date or current time reaches the planned date in the product requirement information through the fourth node, and when the planned date in the product requirement information is reached, query the product basic information, product requirement information, and task information associated with the product identifier from the database, as well as the code information associated with the requirement identifier of the product requirement information.

[0150] Step S802, determine the target requirement information that must be completed from multiple product requirement information through the fourth node according to the requirement description information.

[0151] Among them, each product requirement information includes requirement description information, and the requirement description information is at least used to indicate whether the product requirement information is a requirement information that must be completed.

[0152] For example, the requirement description information is used to indicate that the product requirement information with a requirement priority higher than the set level is the product requirement information that must be completed. Or, the requirement description information is used to indicate that all product requirement information is the product requirement information that must be completed.

[0153] Step S803: When the requirement status of the target requirement information is the completed status through the fourth node, determine whether the number of defects in the execution information in the code information or task information associated with the requirement identifier of the target requirement information is lower than the second set threshold.

[0154] For example, when the execution code adapted to the target requirement information is completed, the requirement status of the target requirement information is set to the completed status through the third node. However, when the execution code adapted to the target requirement information is not completed, the requirement status of the target requirement information cannot be set to the completed status.

[0155] Step S804: When the number of defects is lower than the second set threshold through the fourth node, determine that the product requirement information, code information, and task information meet the requirements for project closure.

[0156] Step S805: Based on the product basic information, product requirement information, code information, and task information through the fourth node, generate a financial product associated with the product identifier.

[0157] Furthermore, when the requirement status of the target requirement information is the uncompleted status, or when the number of defects is greater than or equal to the second set threshold, it is determined through the fourth node that the product requirement information, code information, and task information do not meet the requirements for project closure. At this time, the fourth node can further determine the reason for not meeting the requirements for project closure. For example, when the requirement status of the target requirement information is the uncompleted status, the fourth node can determine the reason for not meeting the requirements for project closure, which is used to indicate that the code writing of the target requirement information is not completed; when the number of defects is greater than or equal to the second set threshold, the fourth node can determine the reason for not meeting the requirements for project closure, which is used to indicate that the code writing quality of the target requirement information does not meet the expected requirements.

[0158] After that, the fourth node can also display this reason, and / or send this reason to the third node.

[0159] In summary, it is possible to timely remind relevant personnel in the case where the code writing progress or code writing quality is not ideal or does not meet the standards, so that relevant personnel can timely write or adjust the code information or task information adapted to the target requirement information, and improve the development progress of financial products.

[0160] In any one of the embodiments of the present disclosure, when the planned date has not been reached, the second node can also dynamically adjust the product requirement information according to the actual situation, so as to achieve the purpose of improving the timely response of the management of each process link of financial products.

[0161] Specifically, the second node can execute steps S901 to S903 as Figure 9 shown to dynamically adjust the product requirement information:

[0162] S901. When the planned date has not been reached, receive, through the second node, a modification instruction for product requirement information associated with a third requirement identifier among requirement identifiers of multiple product requirement information.

[0163] In an embodiment of the present disclosure, when the planned date has not been reached, a modification instruction triggered by relevant personnel for product requirement information associated with a third requirement identifier among requirement identifiers of multiple product requirement information can be received through the second node.

[0164] Wherein, the modification instruction is used to modify the product requirement information associated with the third requirement identifier, and the third requirement identifier is input or selected by relevant personnel.

[0165] S902. In response to the modification instruction through the second node, update the product requirement information associated with the third requirement identifier in the database.

[0166] For example, update requirement description information, requirement priority, planned cycle, etc. in the product requirement information.

[0167] S903. Send the third requirement identifier to the third node through the second node.

[0168] Correspondingly, after receiving the third requirement identifier, the third node can query the updated product requirement information associated with the third requirement identifier from the database, and update the code information or task information associated with the third requirement identifier according to the updated product requirement information, so that the fourth node can generate a financial product that meets the latest business requirements based on the updated code information or task information in the database.

[0169] The management method of the financial product in the embodiment of the present disclosure generates a financial product only based on code information and task information with qualified code quality, which can further improve the generation quality of the financial product.

[0170] To clearly illustrate the above embodiments, the present disclosure also proposes a management method of a financial product.

[0171] Figure 10 It is a schematic flowchart of another management method of a financial product provided by the embodiment of the present disclosure.

[0172] As Figure 10 shown, the management method of the financial product may include the following steps:

[0173] Step S1001. In response to a product configuration operation through the first node, configure product basic information, store the product basic information in the database, and send the product identifier of the product basic information to the second node.

[0174] Step S1002: Receive the product identifier through the second node, query the product basic information associated with the product identifier from the database, in response to the requirement configuration operation, configure at least one product requirement information according to the product basic information, and store the product requirement information associated with the product identifier in the database, and send the requirement identifier of the product requirement information to the third node.

[0175] Step S1003: Receive the requirement identifier through the third node, query the product requirement information associated with the requirement identifier from the database, obtain the execution code adapted to the product requirement information, execute the execution code to obtain the execution information, and store the code information associated with the requirement identifier in the database.

[0176] Among them, the code information includes the execution code and the corresponding execution information.

[0177] For the explanatory notes of Steps S1001 to S1003, reference can be made to the relevant descriptions in any embodiment of the present disclosure, and details are not described herein.

[0178] In any embodiment of the present disclosure, the code information further includes at least one of the requirement category of the product requirement information, the code theme information of the execution code, and the code function description information, so that relevant personnel (such as management personnel) can know the role and function of the execution code in the code information without browsing the meaning of each line of the code line by line, and there is no need for relevant personnel to consult the code writer offline to understand the actual role of the code, further improving the convenience of product management.

[0179] In the present disclosure, the code information can also be associated and stored in the database with at least one of the requirement identifier, the task information, the submission times of the code information, the code defects in the execution information, the code scale of the execution code, the code complexity of the execution code, the code equivalent of the execution code, and the test coverage rate of the execution code through the third node, so as to facilitate the management of the code information by relevant personnel.

[0180] Step S1004: Obtain the product identifier through the fourth node, query the product basic information and product requirement information associated with the product identifier from the database, and the code information associated with the requirement identifier of the product requirement information, and generate a financial product associated with the product identifier based on the product basic information, product requirement information, and code information when the product requirement information and the code information meet the closing requirements.

[0181] For the explanatory notes of Step S1004, reference can be made to the relevant descriptions in any embodiment of the present disclosure, and details are not described herein.

[0182] In any of the embodiments of the present disclosure, when the product requirement information and the code information meet the requirements for project closure, the fourth node can also perform project closure processing on the financial product, update the product status of the financial product to the project closure status, generate a requirement file associated with the requirement category in the product requirement information according to the product requirement information, and generate a code file associated with the requirement category according to the execution code, so as to store the requirement category, the requirement file, and the code file in the database in an associated manner, facilitating relevant personnel to manage the requirement files and code files under each requirement category.

[0183] Step S1005: Obtain the product identifier of the financial product through the fifth node.

[0184] Among them, the fifth node is used to manage the first node, the second node, the third node, the fourth node, and the database.

[0185] Among them, the manner in which the fifth node obtains the product identifier is similar to the manner in which the fourth node obtains the product identifier, and will not be elaborated here.

[0186] Step S1006: Query the target information associated with the product identifier from the database through the fifth node.

[0187] Among them, the target information includes at least one of the following: product basic information associated with the product identifier; product requirement information associated with the product identifier; requirement files and code files associated with the requirement category in the product requirement information; code information associated with the requirement identifier in the product requirement information; task information associated with the requirement identifier in the product requirement information; code defects in the execution information of the code information; code scale of the execution code; code complexity of the execution code; code equivalent of the execution code; test coverage rate of the execution code.

[0188] Step S1007: Visualize and display the target information through the fifth node.

[0189] In the embodiments of the present disclosure, the fifth node can obtain the product identifier of the financial product, query the target information associated with the product identifier from the database, and then display the target information in the form of interface visualization.

[0190] For example, the fifth node can display the target information in the form of a chart (for example, display the target information in the form of a bar chart, a line chart, a report, etc.), and display the target information in a hierarchical structure and relationship visualization manner (for example, display the target information in the form of a tree chart, a network chart, etc.).

[0191] In summary, through the fifth node, based on the interface visualization method, the data involved in each node (including but not limited to index information, product information, requirement information, code information, task information, personnel information (such as the person in charge of each node), etc.) is managed. This can not only meet the actual management needs and understand the actual situation of each process link of the financial product, but also trace the person in charge of each process link of the financial product and the development records, further meeting the actual management needs of the management personnel.

[0192] To implement the above embodiments, the present disclosure also proposes a management system for financial products.

[0193] Figure 11 It is a schematic structural diagram of a management system for a financial product provided by an embodiment of the present disclosure.

[0194] As Figure 11 shown, the management system for the financial product includes: a first node 1110, a second node 1120, a third node 1130, and a fourth node 1140.

[0195] Among them, the first node 1110 (or called the project establishment node) is used to respond to the product configuration operation, configure the product basic information, store the product basic information in the database, and send the product identifier of the product basic information to the second node 1120.

[0196] The second node 1120 (or called the plan node) is used to receive the product identifier, query the product basic information associated with the product identifier from the database, respond to the requirement configuration operation, configure at least one product requirement information according to the product basic information, and store the product requirement information associated with the product identifier in the database, and send the requirement identifier of the product requirement information to the third node 1130.

[0197] The third node 1130 is used to receive the requirement identifier, query the product requirement information associated with the requirement identifier from the database, obtain the execution code adapted to the product requirement information, execute the execution code to obtain the execution information, and store the code information associated with the requirement identifier in the database; wherein, the code information includes the execution code and the corresponding execution information.

[0198] The fourth node 1140 is used to obtain the product identifier, query the product basic information and product requirement information associated with the product identifier from the database, and the code information associated with the requirement identifier of the product requirement information, and generate a financial product associated with the product identifier based on the product basic information, product requirement information, and code information when the product requirement information and the code information meet the closing requirements.

[0199] It should be noted that the explanations of the management method of financial products in any of the above embodiments are also applicable to this embodiment, and their implementation principles are similar, so they will not be elaborated here.

[0200] It should be noted here that the management system of financial products provided by the embodiments of the present disclosure can implement all the functions achieved by the management method of financial products in any of the above embodiments, and can achieve the same technical effects. Therefore, the same parts and beneficial effects as those in the method embodiments in this embodiment will not be specifically elaborated here.

[0201] The embodiments of the present disclosure provide another management system of financial products. Figure 12 It is a schematic structural diagram of another management system of financial products provided by the embodiments of the present application.

[0202] It should be noted that the functions of each node in the management system of financial products can be executed independently, or can be executed in combination with any one of the embodiments in the present application or the possible implementation manners in the embodiments. The embodiments of the present application do not limit this.

[0203] As Figure 12 shown, the management system of financial products includes: a first node 1110, a second node 1120, a third node 1130, a fourth node 1140, and a fifth node 1150.

[0204] Among them, the first node 1110 is used to configure product basic information in response to a product configuration operation, store the product basic information in a database, and send the product identifier of the product basic information to the second node 1120.

[0205] The second node 1120 is used to receive the product identifier, query the product basic information associated with the product identifier from the database, configure at least one product requirement information according to the product basic information in response to a requirement configuration operation, and store the product requirement information associated with the product identifier in the database, and send the requirement identifier of the product requirement information to the third node 1130.

[0206] The third node 1130 is used to receive the requirement identifier, query the product requirement information associated with the requirement identifier from the database, obtain the execution code adapted to the product requirement information, execute the execution code to obtain execution information, and store the code information (including the execution code and the corresponding execution information) associated with the requirement identifier in the database.

[0207] The fourth node 1140 is used to obtain a product identifier, query product basic information and product requirement information associated with the product identifier, and code information associated with the requirement identifier of the product requirement information from a database. When the product requirement information and the code information meet the requirements for project closure, a financial product associated with the product identifier is generated based on the product basic information, the product requirement information, and the code information.

[0208] It should be noted that the explanations of the first node 1110, the second node 1120, the third node 1130, and the fourth node 1140 can refer to the relevant descriptions in the above embodiments and will not be elaborated here.

[0209] The fifth node 1150 is used to manage the first node 1110, the second node 1120, the third node 1130, the fourth node 1140, and the database.

[0210] In addition, the fifth node 1150 is further used to obtain the product identifier of the financial product, query the target information associated with the product identifier from the database, and then display the target information in the form of interface visualization. For example, the target information is displayed in a chart (such as in the form of a bar chart, a line chart, a report, etc.), or the target information is displayed in a hierarchical structure and relationship visualization (such as in the form of a tree chart, a network chart, etc.).

[0211] The target information includes at least one of the following: product basic information associated with the product identifier; product requirement information associated with the product identifier; requirement files and code files associated with the requirement category in the product requirement information; code information associated with the requirement identifier of the product requirement information; task information associated with the requirement identifier of the product requirement information; code defects in the execution information of the code information; code scale of the executed code; code complexity of the executed code; code equivalent of the executed code; test coverage of the executed code.

[0212] In summary, the fifth node 1150 can manage the data involved in each node (including but not limited to metric information, product information, requirement information, code information, task information, personnel information (such as the person in charge of each node), etc.) based on the interface visualization method, which can not only meet the actual management needs and know the actual situation of each process link of the financial product, but also trace the person in charge of each process link of the financial product and the development records, further meeting the actual management needs of the management personnel.

[0213] In any one of the embodiments of the present disclosure, the management system of the financial products provided by the present disclosure can break down the barriers between various nodes (or service modules), enabling designers, managers, developers, testers, operation and maintenance personnel, etc. of financial products to timely know the current situation of financial products and make corresponding adjustments according to the actual situation, so as to achieve the purpose of comprehensively improving the timely response of the management of each process stage of financial products. In addition, encrypted data transmission is carried out between each node to ensure the security of data transmission.

[0214] As an example, the functions of each node in the management system of financial products are specifically as follows:

[0215] 1. The first node (or called the project establishment node) is used to input the product basic information of the financial product, generate the product ID of the financial product, save the input product basic information into the database, and after encrypting the product ID, transmit it to the next node for use to associate the first node with other nodes.

[0216] Among them, the product basic information includes but is not limited to the information shown in Figure 2 : product name, product number, product responsible person, department to which the product responsible person belongs, product classification, sub-classification, product description, remarks information, etc.

[0217] For example, relevant personnel enter the configuration page (or input page) of the new product shown in Figure 2 by clicking the new button on the operation page, and input the product basic information of the new product on this configuration page.

[0218] Among them, the first node (or called the project establishment node) encrypts the product ID according to the public key of the second node.

[0219] 2. The second node (or called the planning node) is used to decrypt the encrypted data transmitted by the first node to obtain the product ID, query the product basic information from the database based on the product ID, and display the product basic information, so that relevant personnel can input the product requirement information associated with the financial product based on this product basic information, generate the requirement ID (requirement unique identification code), and save the product ID and the input product requirement information into the database together. Among them, when multiple product requirement information corresponds to the same financial product, the product ID of the same financial product will be saved.

[0220] Among them, the second node can also encrypt the requirement ID and transmit it to the third node for use.

[0221] Among them, the product requirement information includes but is not limited to Figure 3The information shown in the figure: requirement name, requirement number, product version, requirement type, module to which the requirement belongs, requirement source, requirement category, requirement reviewer, requirement priority, planned cycle, planned man-hours, requirement description information, requirement documents, etc.

[0222] 3. The third node (or called the execution node) is used to decrypt the encrypted data transmitted by the second node to obtain the requirement ID, query the product requirement information from the database based on the requirement ID, and according to the product requirement information, generate the execution code and run the execution code to obtain the execution information. After completing the execution of the code, one way is to record the code information (also called the code submission information), and the code submission information includes the decrypted requirement ID, so that the requirement information and the code submission information can be associated. Another way is to record the code submission information without including the requirement ID, and through the second node, select the already submitted task information for association.

[0223] 3.1) The execution code is associated with the product requirement information.

[0224] After completing the generation of the execution code according to the product requirement information, associate the information of the submission log with the code information (or called the code submission information). Standardize the code submission information by stipulating the code submission specification. For example, the code submission information must include the requirement type and the code topic (a short description of the execution code) information.

[0225] Adding a purpose description to the code submission information is to explicitly display the function of the execution code through text. For example, relevant personnel can know that this execution code is for developing a new requirement function just by looking at the code submission information, rather than having to browse the code line by line to understand its meaning. A further approach is to directly establish an association between the submission of the execution code and requirements, tasks, or defects, etc.

[0226] Taking GitHub (a hosting platform for open-source and private software projects) as an example, the product requirement information can be associated through the log. Just input the requirement ID (requirementId) in the code submission (commit) information each time. For example: git commit -m "{'requirementId':'12', 'type': 'add', note: 'User information query interface'}"

[0227] It is also possible to modify the requirement status by inputting instructions such as Done in the code submission (commit) information. For example: git commit -m "{'requirementId':'12', 'type': 'done', note: 'Development of user information query interface completed'}"

[0228] It should be noted that the execution code is an unstructured data information and cannot be directly associated with the products or requirements that managers are concerned about. Without a good data management and measurement mechanism, from the perspective of managers, they can only obtain some subjective descriptive information from front-line engineers through means such as meetings and communications, such as data on the workload of requirements and tasks, code quality and risks refined to the dimensions of requirements and tasks. These data are very important reference bases in links such as product review, resource assessment, quality and risk assessment.

[0229] By associating the requirement ID in the code submission information, the data shown in Table 1 can be obtained:

[0230] Table 1 Relationship between code submission information and requirement categories identified by requirement IDs

[0231] Requirement Category Submission Times Code Size (lines) Number of Defects Requirement A 12 5125 50 Requirement B 23 3089 21

[0232] The above is the summary calculation of basic data. In addition, data such as code complexity, code equivalent, and test coverage in the dimensions of requirements and tasks can also be introduced.

[0233] 3.2) Associate product requirement information with the execution code.

[0234] After completing the production of the execution code according to the product requirement information and submitting the code submission information, if the product requirement information is modified, the code submission records are associated by selecting the requirement ID. For example, use the command "git log--pretty=oneline--abbrev-commit" to view the commit records of a certain project. Optionally, the serial number used to identify the commit can only display the first 7 digits. For example, using a 7-digit hexadecimal number can represent approximately 270 million different numbers, which is sufficient to identify a commit.

[0235] That is, the --abbrev-commit option will shorten the hash value of each commit. Usually, the commit hash value of Git is a SHA-1 value with an original length of 40 characters. Using --abbrev-commit to shorten it to fewer characters, such as the first 7 digits.

[0236] 4. The fourth node (also known as the project establishment node) is used to perform the closing process on the financial product based on the information of the above several nodes, and modify the product status of the financial product to the closed status. Make the product requirement information of the financial product into a requirement document, save the execution code in the execution stage of the financial product as a code document, make all the information associated with the financial product into an artifact for saving, and complete the submission of the artifact.

[0237] To implement the above embodiments, the present disclosure further provides an electronic device. The electronic device can be any device with computing capabilities and includes: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, it implements the financial product management method proposed in any of the foregoing embodiments of the present disclosure.

[0238] As an example, Figure 13 is a schematic structural diagram of an electronic device 1300 shown in an exemplary embodiment of the present disclosure. As Figure 13 shown, the above-mentioned electronic device 1300 may further include:

[0239] A memory 1310 and a processor 1320, a bus 1330 connecting different components (including the memory 1310 and the processor 1320). The memory 1310 stores a computer program, and when the processor 1320 executes the program, it implements the financial product management method described in the embodiments of the present disclosure.

[0240] The bus 1330 represents one or more of several types of bus structures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any bus structure in a variety of bus structures. By way of example, these architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

[0241] The electronic device 1300 typically includes a variety of electronic device-readable media. These media can be any available media accessible by the electronic device 1300, including volatile and non-volatile media, removable and non-removable media.

[0242] The memory 1310 may further include a computer system-readable medium in the form of volatile memory, such as random access memory (RAM) 1340 and / or cache memory 1350. The server 1300 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, a storage system 1360 can be used to read and write non-removable, non-volatile magnetic media ( Figure 13 not shown, commonly referred to as a "hard disk drive"). Although Figure 13Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (such as a "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (such as a CD-ROM, DVD-ROM, or other optical medium) can be provided. In these cases, each drive can be connected to the bus 1330 through one or more data medium interfaces. The memory 1310 may include at least one program product having a set (such as at least one) of program modules configured to perform the functions of the embodiments of the present disclosure.

[0243] A program / utility 1380 having a set (at least one) of program modules 1370 can be stored, for example, in the memory 1310. Such program modules 1370 include - but are not limited to - an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include the implementation of a network environment. The program modules 1370 generally perform the functions and / or methods in the embodiments described in the present disclosure.

[0244] The electronic device 1300 can also communicate with one or more external devices 1390 (such as a keyboard, a pointing device, a display 1391, etc.), and can also communicate with one or more devices that enable a user to interact with the electronic device 1300, and / or communicate with any device that enables the electronic device 1300 to communicate with one or more other computing devices (such as a network card, a modem, etc.). Such communication can be carried out through the input / output (I / O) interface 1392. Also, the electronic device 1300 can communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through the network adapter 1393. As shown in the figure, the network adapter 1393 communicates with other modules of the electronic device 1300 through the bus 1330. It should be understood that although not shown in the figure, other hardware and / or software modules can be used in combination with the electronic device 1300, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0245] The processor 1320 executes various functional applications and data processing by running the programs stored in the memory 1310.

[0246] It should be noted that for the implementation process and technical principle of the electronic device in this embodiment, refer to the explanation of the management method of the financial product in any of the foregoing embodiments of the present disclosure, which will not be elaborated here.

[0247] To implement the above embodiments, the present disclosure also provides a non-transitory computer-readable storage medium having stored thereon a computer program, which when executed by a processor, implements the method for managing financial products as proposed in any of the foregoing embodiments of the present disclosure.

[0248] To implement the above embodiments, the present disclosure also provides a computer program product, which when the instructions in the computer program product are executed by a processor, executes the method for managing financial products as proposed in any of the foregoing embodiments of the present disclosure.

[0249] In the description of this specification, the descriptions with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples", etc., mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms are not necessarily directed to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, without contradiction, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples.

[0250] In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of such features. In the description of the present disclosure, "a plurality" means at least two, such as two, three, etc., unless otherwise specifically defined.

[0251] Any process or method description in the flowchart or described in other ways herein may be understood to represent a module, segment, or portion of code including one or more executable instructions for implementing a customized logical function or process, and the scope of the preferred embodiments of the present disclosure includes additional implementations, where the functions may be executed in a manner not shown or discussed, including substantially concurrently or in a reverse order according to the functions involved, which should be understood by those skilled in the art to which the embodiments of the present disclosure pertain.

[0252] The logic and / or steps represented in the flowchart or otherwise described herein can, for example, be considered as a definitional sequence list of executable instructions for implementing logical functions, which can be embodied specifically in any computer-readable medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other systems that can fetch and execute instructions from the instruction execution system, apparatus, or device), or in conjunction with these instruction execution systems, apparatuses, or devices. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium include the following: an electrical connection part with one or more wirings (electronic device), a portable computer disk cartridge (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium can even be paper or other suitable media on which the program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpretation, or otherwise processing as appropriate, and then storing it in a computer memory.

[0253] It should be understood that various parts of the present disclosure can be implemented by hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or a combination of the following techniques well known in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application-specific integrated circuits having suitable combinational logic gate circuits, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), and the like.

[0254] Those of ordinary skill in the art of this technology can understand that all or part of the steps carried by the method of implementing the above embodiments can be completed by a program instructing relevant hardware. The program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

[0255] In addition, each functional unit in various embodiments of the present disclosure may be integrated into one processing module, may exist separately as individual physical units, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0256] The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disc, etc. Although the embodiments of the present disclosure have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure. Those of ordinary skill in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present disclosure.

Claims

1. A management method for a financial product, characterized in that, Including: By a first node in response to a product configuration operation, configuring product basic information, storing the product basic information in a database, and sending a product identifier of the product basic information to a second node; By the second node receiving the product identifier, querying the product basic information associated with the product identifier from the database, in response to a demand configuration operation, configuring at least one product demand information according to the product basic information, and associating and storing the product demand information with the product identifier in the database, and sending a demand identifier of the product demand information to a third node; By the third node receiving the demand identifier, querying the product demand information associated with the demand identifier from the database, obtaining an execution code adapted to the product demand information, executing the execution code to obtain execution information, and associating and storing the code information with the demand identifier in the database; wherein, the code information includes the execution code and the corresponding execution information; By a fourth node obtaining the product identifier, and querying the product basic information and product demand information associated with the product identifier from the database, and the code information associated with the demand identifier of the product demand information, and generating a financial product associated with the product identifier based on the product basic information, the product demand information, and the code information when the product demand information and the code information meet the closing requirements; Wherein, the code information further includes at least one of a demand category of the product demand information, a code theme information of the execution code, and a code function description information; The method further includes: By the third node associating and storing the code information with at least one of the demand identifier, task information, the submission times of the code information, code defects in the execution information, the code scale of the execution code, the code complexity of the execution code, the code equivalent of the execution code, and the test coverage rate of the execution code in the database.

2. The method according to claim 1, characterized in that The data transmitted between nodes is encrypted data; Sending the product identifier of the product basic information from the first node to the second node includes: By the first node using the public key of the second node to perform an encryption process on the product identifier to obtain encrypted data of the first node; By the first node sending the encrypted data of the first node to the second node; Wherein, the public key of the second node includes a public key exponent E and a modulus N, the modulus N is greater than a first set threshold, and the encryption process includes: By the first node encoding the product identifier based on a first encoding algorithm to obtain a target value; By the first node encrypting the target value using the public key exponent E and the modulus N to obtain an encrypted value; By the first node encoding the encrypted value based on a second encoding algorithm to obtain the encrypted data of the first node.

3. The method according to claim 2, characterized in that The step of by the first node encrypting the target value using the public key exponent E and the modulus N to obtain an encrypted value includes: Obtain the E-th power of the target value through the first node to obtain a first intermediate value; Perform a modulo operation of N on the first intermediate value through the first node to obtain the encrypted value.

4. The method according to claim 2, wherein The receiving of the product identifier through the second node includes: Receiving the encrypted data of the first node through the second node; Performing a decryption process on the encrypted data of the first node by using the private key of the second node through the second node to obtain the product identifier; Wherein, the private key of the second node includes a private key exponent D and the modulus N, and the decryption process includes: Decoding the encrypted data of the first node based on the second coding algorithm through the second node to obtain the encrypted value; Performing a decryption process on the encrypted value by using the private key exponent D and the modulus N through the second node to obtain the target value; Decoding the target value based on the first coding algorithm through the second node to obtain the product identifier.

5. The method according to claim 4, wherein The performing a decryption process on the encrypted value by using the private key exponent D and the modulus N through the second node to obtain the target value includes: Obtaining a second intermediate value by taking the D-th power of the encrypted value through the second node; Performing a modulo operation of N on the second intermediate value through the second node to obtain the target value.

6. The method according to any one of claims 1-5, characterized in that, The number of the product demand information is multiple, and sending the demand identifier of the product demand information from the second node to the third node includes: Determining a first demand identifier from the demand identifiers of the multiple product demand information through the second node; Associatively storing the first demand identifier, the product identifier and the task information in the database through the second node; wherein, the task information includes a reference execution code adapted to the reference demand information and execution information obtained by running the reference execution code; the reference demand information includes product demand information shared among the generated financial products and / or default product demand information; Sending a second demand identifier other than the first demand identifier among the multiple demand identifiers to the third node through the second node; Correspondingly, obtaining an execution code adapted to the product demand information through the third node includes: Obtaining an execution code adapted to the product demand information associated with the second demand information through the third node; Correspondingly, when the product demand information and the code information meet the closing requirements, generating a financial product associated with the product identifier based on the product basic information, the product demand information and the code information through the fourth node includes: Querying the task information associated with the product identifier from the database through the fourth node; Generating a financial product associated with the product identifier based on the product basic information, the product demand information, the code information and the task information when the product demand information, the code information and the task information meet the closing requirements through the fourth node.

7. The method according to claim 6, characterized in that The closing requirements are determined according to the planned date and requirement description information in the product requirement information; Through the fourth node, query the product basic information and product requirement information associated with the product identifier, and the code information associated with the requirement identifier of the product requirement information from the database, and when the product requirement information and the code information meet the closing requirements, generate a financial product associated with the product identifier based on the product basic information, the product requirement information, and the code information, including: Through the fourth node, determine whether the planned date has been reached, and when the planned date has been reached, query the product basic information, product requirement information, and task information associated with the product identifier, and the code information associated with the requirement identifier of the product requirement information from the database; Through the fourth node, determine the target requirement information that must be completed from the multiple product requirement information according to the requirement description information; Through the fourth node, when the requirement status of the target requirement information is the completed status, determine whether the number of defects in the execution information in the code information or task information associated with the requirement identifier of the target requirement information is lower than the second set threshold; Through the fourth node, when the number of defects is lower than the second set threshold, determine that the product requirement information, the code information, and the task information meet the closing requirements; Through the fourth node, generate a financial product associated with the product identifier based on the product basic information, the product requirement information, the code information, and the task information.

8. The method according to claim 7, wherein The method further includes: Through the fourth node, when the requirement status is the uncompleted status, or when the number of defects is higher than or equal to the second set threshold, determine that the product requirement information, the code information, and the task information do not meet the closing requirements, and determine the reasons for not meeting the closing requirements; Through the fourth node, display the reasons, and / or send the reasons to the third node; Wherein, in response to the requirement status being the uncompleted status, the reason is used to indicate that the code writing of the target requirement information is not completed; in response to the number of defects being greater than or equal to the second set threshold, the reason is used to indicate that the code writing quality of the target requirement information does not meet the expected requirements.

9. The method according to claim 7, wherein After the fourth node determines whether the planned date has been reached, the method further includes: When the planned date has not been reached, through the second node, receive a modification instruction for the product requirement information associated with the third requirement identifier among the requirement identifiers of the multiple product requirement information; Through the second node, in response to the modification instruction, update the product requirement information associated with the third requirement identifier in the database; Through the second node, send the third requirement identifier to the third node; Through the third node, query the updated product requirement information associated with the third requirement identifier from the database; The third node updates the code information or task information associated with the third requirement identifier according to the updated product requirement information.

10. The method according to any one of claims 1-5, characterized in that, When the product requirement information and the code information meet the requirements for project closure, the method further includes: The fourth node performs project closure processing on the financial product and updates the product status of the financial product to the closed status; The fourth node generates a requirement document associated with the requirement category in the product requirement information according to the product requirement information; The fourth node generates a code document associated with the requirement category according to the execution code; The fourth node stores the requirement category, the requirement document, and the code document in association with each other in the database.

11. The method according to any one of claims 1-5, characterized in that, The method further includes: The fifth node obtains the product identifier of the financial product; wherein, the fifth node is used to manage the first node, the second node, the third node, the fourth node, and the database; The fifth node queries the target information associated with the product identifier from the database; The fifth node visually displays the target information.

Images