A business risk management method, device and equipment

Abstract

The embodiments of the present application disclose a business risk management method, device, and equipment. For a newly launched and to-be-released business, a business risk template matching the type can be selected according to its business type. The business risk template contains multiple risk items corresponding to this type of business. In this way, multiple risk items can be presented to the corresponding developers. Obviously, for a business to be released, the risk items that need to be configured will be intuitively presented to the developers.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a business risk management method, apparatus, and device. Background Art

[0002] With the development of Internet technology, users can access services (such as insurance products) provided by corresponding service providers (such as financial platforms, websites, banks, etc.) through the Internet. For the service provider's backend, during the service development phase, it is usually necessary to set up corresponding risk monitoring measures for risks that may arise during the application process of the service.

[0003] In the prior art, developers usually rely on experience to configure corresponding risk monitoring and verification scripts for a certain business to be launched during the development phase, so as to monitor the risks that may arise in the business.

[0004] Based on existing technology, we need a more effective way to manage business risks. Summary of the Invention

[0005] The embodiments of the present application provide a business risk management method, apparatus, and device to provide a more effective business risk management approach.

[0006] An embodiment of the present application provides a business risk management method, the method comprising:

[0007] For the business to be released, determine a business risk template that matches the type of the business to be released; wherein the business risk template includes multiple risk items corresponding to the type of business;

[0008] The risk items included in the business risk template are displayed.

[0009] An embodiment of the present application provides a business risk management device, the device comprising:

[0010] A template determination module determines, for a business to be released, a business risk template that matches the type of the business to be released; wherein the business risk template includes multiple risk items corresponding to the type of business;

[0011] The display module displays the risk items included in the business risk template.

[0012] An embodiment of the present application provides a business risk management device, including:

[0013] Storage, which stores business risk management procedures;

[0014] The processor calls the business risk management program stored in the memory and executes:

[0015] For the business to be released, determine a business risk template that matches the type of the business to be released; wherein the business risk template includes multiple risk items corresponding to the type of business;

[0016] The risk items included in the business risk template are displayed.

[0017] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0018] For newly launched businesses awaiting release, developers can select a matching business risk template based on their business type. This template includes multiple risk items specific to that business type, allowing developers to easily configure these risk items. This intuitively presents the required risk items for each business to be released. Furthermore, templated business risk templates are more convenient to use, no longer relying solely on individual developer experience, and are less susceptible to developer turnover or business changes.

[0019] The above-mentioned business risk management method in the embodiment of this specification associates each risk item with a business use case. Developers usually base their development on business use cases, so this method is more intuitive. In addition, the business use case is linked to the business risk template to form a universal, templated tool, which makes it easier for business personnel responsible for risk to pay more attention to business use cases and business risk templates, while developers pay more attention to the improvement of risk items, thereby optimizing personnel allocation and reducing manpower consumption. The same risk item may correspond to multiple businesses. The above-mentioned method can effectively improve the reusability of risk items and their related scripts and policies, thereby improving the convenience of business maintenance and development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0021] Figure 1 A schematic diagram of the architecture based on which the business risk management provided in the embodiments of this specification is based;

[0022] Figure 2 The business risk management process provided in the embodiments of this specification;

[0023] Figure 3 A schematic diagram of a business risk template in an actual business scenario provided by the embodiments of this specification;

[0024] Figure 4A business logic diagram for an actual business scenario provided by the embodiments of this specification;

[0025] Figure 5 This is a schematic diagram of the business risk management device structure provided in the embodiments of this specification. DETAILED DESCRIPTION

[0026] To make the purpose, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the specific embodiments of this application and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0027] In one or more embodiments of this specification, the business may include various software products or Internet services and other software-related businesses, such as insurance products, stock products, fund products and other financial products, or APP clients, software programs, cloud computing services, cloud storage services, etc.

[0028] Generally speaking, in the embodiments of this specification, users can obtain corresponding services through the Internet, so the services described are mainly the above-mentioned software products or Internet service services. However, in some business scenarios in some actual applications, hardware equipment related to the business may also fall within the scope of the "business" described in the embodiments of this specification. The hardware equipment related to the business may include business servers (or server clusters), databases (or database clusters), blockchain networks, etc. It may also include some hardware components inside the device, such as a central processing unit (CPU), memory, hard disk, physical interfaces on the device, and so on.

[0029] Then, the pending services can be considered as services that are in the development stage but have not yet been released for user use.

[0030] In actual applications, there may be certain risks for the above businesses, especially for financial products (such as insurance products). Take insurance products as an example:

[0031] For example, when a user purchases an insurance product, the premium they pay may be incorrect. Another example is when a service provider provides an incorrect insurance coverage during the automated claims process. Clearly, for internet-based insurance products, service providers need to monitor these risks that arise in real-world applications. Therefore, during the product development phase, appropriate risk monitoring scripts must be configured to provide timely information on various risks or potential risks that arise during actual use. This requires insurance product developers to configure the appropriate risk monitoring scripts for their respective products during development. This process relies heavily on the developer's experience, which varies greatly. Furthermore, in real-world scenarios, developer turnover or business changes can impact development efficiency and costs.

[0032] Based on this, a business risk management method is provided in an embodiment of this specification to implement template management of risks that may be involved in a business, thereby improving development efficiency and reducing development costs.

[0033] The business risk management method in the embodiment of this specification can be adopted as follows Figure 1 The architecture shown.

[0034] exist Figure 1 In this context, a business system can be considered a system provided by the business provider's backend for the development, testing, debugging, and release of business products or services. In practical applications, this business system may include clustered or distributed business servers, computers, and other business equipment. Furthermore, it may also include business equipment in the form of a blockchain network. Of course, the specific implementation of the business system will be determined by the needs of the actual application and is not specifically limited here. In the embodiments of this specification, the business system is primarily intended for business personnel in the backend of the business provider.

[0035] The business system templates the risks corresponding to different types of business and generates corresponding business risk templates. These business risk templates can be provided to different developers for use.

[0036] certainly, Figure 1 This is just a simple architecture example. In different business scenarios, the architecture may also include a corresponding database (which can be used to store templated business risk templates or related corresponding policy information). The specific architecture adopted will be determined by the needs of the actual application and should not be used as a limitation of this application.

[0037] Based on Figure 1 The architecture shown in the figure, the business risk management process provided by the embodiment of the present application is as follows Figure 2 As shown, the process specifically includes the following steps:

[0038] Step S201: for a business to be released, determine a business risk template that matches the type of the business to be released.

[0039] In the embodiments of this specification, different types of business usually correspond to different risks. For example, for insurance products, life insurance and property insurance belong to different insurance categories (i.e., different types). For these two insurance products, if a user uses life insurance, the medical history information, physical condition information, etc. provided by the user may be wrong, thereby causing risks in the life insurance product; if a user uses property insurance, the property certificate, property value and other information provided by the user may be wrong, thereby causing risks in the property insurance product. It can be seen that the risks are different for different types of insurance products. Of course, the above content is only an example and should not constitute a limitation of this application.

[0040] From this, we can see that during the development phase, the business system can generate matching business risk templates for different types of businesses.

[0041] It should be noted that, as a feasible embodiment of this specification, the business risk template described herein can be implemented using a configuration file in a format such as .ini, .cfg, .conf, or .txt. Furthermore, the business risk template can have a corresponding template identifier, which can be used to identify the type of business to which the template belongs. Of course, in some application scenarios, the template identifier can also be used to identify a specific product or product series.

[0042] For example: the business risk template name (i.e., template identifier) of an insurance product is "Health Insurance". The template identifier reflects that the insurance type corresponding to the business risk template is health insurance. Accordingly, if the insurance product to be released is also an insurance product of the health insurance type, then the business risk template named "Health Insurance" can be determined.

[0043] In the embodiments of this specification, the business risk template includes multiple risk items corresponding to the business type. Each risk item represents a risk that may arise in the actual application of the business, such as the premium paid by the user during the insurance application stage, the user information provided by the user, or the insurance amount paid during the claim settlement stage.

[0044] During the business development phase, developers can configure corresponding risk monitoring scripts or corresponding response strategies based on the risk items listed in each business risk template. To this end, the following step S203 can be executed.

[0045] Step S203: displaying the risk items included in the business risk template.

[0046] In the embodiments of this specification, once a corresponding business risk template is determined, the risk items contained in the business risk template can be displayed to the corresponding developer, so that the developer can configure the corresponding risk monitoring script, response strategy or corresponding plan based on the displayed risk items.

[0047] Of course, in actual applications, there are many ways to display risk items, such as displaying risk items in a specific risk item display area, or directly displaying risk items in the above business risk template in a floating layer, pop-up window, etc. Figure 3 As shown, on the business risk template, developers can obtain the risk items corresponding to the insurance product of type "life insurance".

[0048] Through the above steps, for newly launched businesses awaiting release, a matching business risk template can be selected based on their business type. This business risk template contains multiple risk items corresponding to that business type, allowing developers to easily configure these risk items. Clearly, developers will be able to intuitively configure the risk items required for the business to be released. Furthermore, this template-based business risk template is more convenient to use, no longer relying entirely on the developer's personal experience, and is less susceptible to developer turnover or business changes.

[0049] It should be noted that the business risk template described above can be generated in the following ways:

[0050] Obtain each business use case of each type of insurance product, determine the risk items corresponding to each type of business use case based on the business use cases, and generate a business risk template corresponding to the type of insurance product based on the risk items corresponding to each type of business use case.

[0051] The business use cases described here can be considered as a collection of interactive action sequences between users and service providers during the application process of an insurance product. For example, during the application phase, the entire process of a user purchasing an insurance product can be considered a business use case; another example is during the claim phase, when the service provider pays the user the insured amount.

[0052] It should be understood that in the embodiments of this specification, a business use case is an abstract description based on actual business actions. That is, the business system can simulate the actual business execution process through the business use case. On this basis, the risks (i.e., risk items) that may exist in the actual application of the business can be determined based on the business use case.

[0053] For each business use case, corresponding risk items can be identified, and developers can use this information to configure corresponding monitoring scripts, verification scripts, response plans, or test cases. That is, in the embodiments of this specification, the above method also includes: for the risk items in the business use case, setting a risk control processing script for monitoring the risk items, and establishing a corresponding relationship between the risk control processing script and each risk item in the business use case.

[0054] The risk control processing script includes at least one of a monitoring script, a verification script, a test case, and a contingency plan script.

[0055] In this way, in the embodiment of this specification, a business risk template can be generated based on multiple business use cases, and accordingly, the risk items corresponding to the business use cases can also be "inherited" into the business risk template.

[0056] Of course, if there are new risk items, they can be updated in the corresponding business use case. Then, for the business risk template generated based on the business use case, the risk items therein will be updated accordingly.

[0057] In summary, if Figure 4 The figure shows the correspondence between risk items, business use cases, business risk templates and products in the embodiments of this specification.

[0058] In summary, the above-mentioned business risk management method in the embodiments of this specification associates various risk items with business use cases. Developers usually base their development on business use cases, so this method is more intuitive. In addition, the business use cases are linked to the business risk templates to form a universal, templated tool, which makes it easier for business personnel responsible for risks to pay more attention to business use cases and business risk templates, while developers pay more attention to the improvement of risk items, thereby optimizing personnel allocation and reducing manpower consumption. The same risk item may correspond to multiple businesses. The above-mentioned method can effectively improve the reusability of risk items and their related scripts and policies, thereby improving the convenience of business maintenance and development efficiency.

[0059] It should be understood that the business risk management method mentioned above in this specification can be applied in the development stage of other businesses besides insurance products.

[0060] The above is a business risk management method provided by the embodiment of the present application. Based on the same idea, the embodiment of the present application also provides a business risk management device, which is applied to the development stage of the business, such as Figure 5 The device comprises:

[0061] The template determination module 501 determines, for a business to be released, a business risk template that matches the type of the business to be released; wherein the business risk template includes multiple risk items corresponding to the type of business;

[0062] The display module 502 displays the risk items included in the business risk template.

[0063] Specifically, the business to be released includes: insurance products to be released.

[0064] On this basis, the device also includes: a template module 503, which obtains various business use cases of various types of insurance products, determines the risk items corresponding to each type of business use case based on the various business use cases, and generates a business risk template corresponding to this type of insurance product based on the risk items corresponding to each type of business use case.

[0065] The apparatus further includes: a script configuration module 504 for setting, for each risk item in the business use case, a risk control processing script for monitoring the risk item, and establishing a corresponding relationship between the risk control processing script and each risk item in the business use case;

[0066] The risk control processing script includes at least one of a monitoring script, a verification script, a test case, and a contingency plan script.

[0067] The apparatus further comprises: a risk updating module 505, which adds a risk item to a corresponding business use case when a new risk item is added.

[0068] In such Figure 5 Based on the business risk management device shown, this embodiment of the specification also provides a business risk management device, including:

[0069] Storage, which stores business risk management procedures;

[0070] The processor calls the business risk management program stored in the memory and executes:

[0071] For the business to be released, determine a business risk template that matches the type of the business to be released; wherein the business risk template includes multiple risk items corresponding to the type of business;

[0072] The risk items included in the business risk template are displayed.

[0073] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the device, equipment, and media embodiments are generally similar to the method embodiments, so their descriptions are relatively simple. For relevant parts, refer to the descriptions of the method embodiments and will not be repeated here.

[0074] The foregoing description of specific embodiments of this specification is intended to be a description of other embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions, steps, or modules recited in the claims may be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0075] In the 1990s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements today can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD through their own programming, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly done using "logic compiler" software. This is similar to the software compiler used when developing programs. Before compilation, the original code must also be written in a specific programming language, called a hardware description language (HDL). There is not just one HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that by simply programming the method flow in one of these hardware description languages and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

[0076] The controller can be implemented in any suitable manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that in addition to implementing the controller in a purely computer-readable program code format, the controller can be implemented in the form of logic gates, switches, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the means for implementing various functions included therein can also be considered as structures within the hardware component. Or even, the means for implementing various functions can be considered as both a software module implementing the method and a structure within the hardware component.

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

[0078] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing this application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0079] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

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

[0081] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

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

[0083] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0084] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0085] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0086] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0087] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0088] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0089] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

[0090] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. A business risk management method, applied to the development stage of a business, the method comprises: For a business to be released, determining a business risk template that matches the type of the business to be released; wherein, the business risk template contains multiple risk items corresponding to the business of the type of the business to be released; the business risk template is a risk template generated according to the risk items corresponding to business use cases; the business to be released includes a financial product to be released; the business risk template is used to display the risk items to developers; the risk items are used to represent matters where risks may occur in the actual application of the business to be released; Displaying the risk items included in the business risk template.

2. The method according to claim 1, wherein the business to be released comprises: An insurance product to be released.

3. The method according to claim 2, generating a business risk template by the following method: Obtaining each business use case of various insurance products; Determining, according to each business use case, the risk items corresponding to each type of business use case; Generating a business risk template corresponding to this type of insurance product according to the risk items corresponding to each type of business use case.

4. The method according to claim 3, the method further comprises: When a new risk item is added, adding the risk item to the corresponding business use case.

5. The method according to claim 3, the method further comprises: For the risk items in the business use case, setting a risk control processing script for monitoring the risk items, and establishing a corresponding relationship between the risk control processing script and each risk item in the business use case; Wherein, the risk control processing script includes at least one of a monitoring script, a verification script, a test case, and a pre - plan script.

6. The method according to claim 2, the risk items include at least one of the insurance premium paid by a user during the insurance application stage, the user information provided by the user, and the insurance amount paid during the claim settlement stage.

7. A business risk management device, applied to the development stage of a business, the device comprises: A template determination module, configured to determine, for a business to be released, a business risk template that matches the type of the business to be released; wherein, the business risk template contains multiple risk items corresponding to the business of the type of the business to be released; the business risk template is a risk template generated according to the risk items corresponding to business use cases; the business to be released includes a financial product to be released; the business risk template is used to display the risk items to developers; the risk items are used to represent matters where risks may occur in the actual application of the business to be released; A display module, configured to display the risk items included in the business risk template.

8. The device according to claim 7, wherein the business to be released comprises: An insurance product to be released.

9. The device according to claim 8, the device further comprises: A templatization module, configured to obtain each business use case of various insurance products, determine the risk items corresponding to each type of business use case according to each business use case, and generate a business risk template corresponding to this type of insurance product according to the risk items corresponding to each type of business use case.

10. The device according to claim 9, the device further comprises: A risk update module, configured to add the risk item to the corresponding business use case when a new risk item is added.

11. The device according to claim 9, the device further comprises: A script configuration module, configured to set a risk control processing script for monitoring the risk item for the risk item in the business use case, and establish a correspondence between the risk control processing script and each risk item in the business use case; wherein, the risk control processing script includes at least one of a monitoring script, a verification script, a test case, and a pre - plan script.

12. A business risk management device, applied to the development stage of a business, the device comprises: A memory, configured to store a business risk management program; A processor, configured to call the business risk management program stored in the memory and execute: For a to - be - released business, determine a business risk template matching the type of the to - be - released business; wherein, the business risk template contains multiple risk items corresponding to the business of the type of the to - be - released business; the business risk template is a risk template generated according to the risk items corresponding to the business use case; the to - be - released business includes a to - be - released financial product; the business risk template is used to display the risk items to developers; the risk items are used to represent matters that may pose risks in the actual application of the to - be - released business; Display the risk items included in the business risk template.

Images