CN114548744A - Business risk management method, device and equipment - Google Patents
Business risk management method, device and equipment Download PDFInfo
- Publication number
- CN114548744A CN114548744A CN202210152644.7A CN202210152644A CN114548744A CN 114548744 A CN114548744 A CN 114548744A CN 202210152644 A CN202210152644 A CN 202210152644A CN 114548744 A CN114548744 A CN 114548744A
- Authority
- CN
- China
- Prior art keywords
- business
- risk
- service
- template
- issued
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 31
- 238000000034 method Methods 0.000 claims description 46
- 238000013515 script Methods 0.000 claims description 35
- 238000011161 development Methods 0.000 claims description 20
- 238000012545 processing Methods 0.000 claims description 19
- 238000012544 monitoring process Methods 0.000 claims description 15
- 238000012360 testing method Methods 0.000 claims description 6
- 230000008569 process Effects 0.000 description 18
- 238000010586 diagram Methods 0.000 description 11
- 238000004590 computer program Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 9
- 230000006872 improvement Effects 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 6
- 230000008859 change Effects 0.000 description 4
- 230000036541 health Effects 0.000 description 4
- 230000010485 coping Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000000750 progressive effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000007667 floating Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 229920001296 polysiloxane Polymers 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0635—Risk analysis of enterprise or organisation activities
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/186—Templates
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Development Economics (AREA)
- Game Theory and Decision Science (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Computational Linguistics (AREA)
- Educational Administration (AREA)
- Audiology, Speech & Language Pathology (AREA)
- General Engineering & Computer Science (AREA)
- Artificial Intelligence (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The embodiment of the application discloses a business risk management method, a business risk management device and business risk management equipment, wherein for a newly online business to be issued, a business risk template with matched types can be selected according to the business type of the business to be issued, and the business risk template comprises a plurality of risk items corresponding to the business, so that the risk items can be displayed to corresponding developers. Obviously, for the business needing to be released, the required configuration risk items of the business are intuitively displayed to developers.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for business risk management.
Background
With the development of internet technology, users can obtain services (e.g., insurance products) provided by corresponding service providers (such as financial platforms, websites, banks, etc.) through the internet. For the background of the service provider, in the development phase of the service, it is usually necessary to set corresponding risk monitoring measures for risks that may occur in the application process of the service.
In the prior art, a developer usually relies on experience to configure a corresponding risk monitoring and checking script for a certain service to be online in a development stage, so as to monitor risks that may occur in the service.
Based on the prior art, a more effective business risk management method is needed.
Disclosure of Invention
The embodiment of the application provides a business risk management method, a business risk management device and business risk management equipment, and is used for providing a more effective business risk management mode.
The embodiment of the application provides a business risk management method, which comprises the following steps:
determining a business risk template matched with the type of the business to be issued aiming at the business to be issued; the business risk template comprises a plurality of risk items corresponding to the business;
and displaying the risk items contained in the business risk template.
An embodiment of the present application provides a business risk management device, where the device includes:
the template determining module is used for determining a business risk template matched with the type of the business to be issued aiming at the business to be issued; the business risk template comprises a plurality of risk items corresponding to the business;
and the display module is used for displaying the risk items contained in the business risk template.
The business risk management device provided by the embodiment of the application comprises:
a memory storing a business risk management program;
the processor calls the business risk management program stored in the memory and executes:
determining a business risk template matched with the type of the business to be issued aiming at the business to be issued; the business risk template comprises a plurality of risk items corresponding to the business;
and displaying the risk items contained in the business risk template.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects:
for the newly online service to be released, a service risk template with matched types can be selected according to the service type of the service to be released, and the service risk template comprises a plurality of risk items corresponding to the service, so that the plurality of risk items can be displayed to corresponding developers. Obviously, for the business needing to be released, the required configuration risk items of the business are intuitively displayed to developers. And after the template is formed, the service risk template is more convenient to use and does not depend on the personal experience of developers completely, and meanwhile, the influence of the flow of the developers or the service change is small.
In the business risk management method in the embodiment of the present specification, each risk item is associated with a business case, and a developer is usually based on the business case in a development process, so that the method is more intuitive. In addition, the business case and the business risk template are obtained, a universal and templated tool is formed, business personnel in charge of risk can pay more attention to the business case and the business risk template, and developers can pay more attention to the perfection of risk items, so that personnel allocation is optimized, and labor consumption is reduced. The same risk item may correspond to a plurality of services, and the method can effectively improve the reusability of the risk item and related scripts and strategies thereof, and further can improve the convenience of service maintenance and the development efficiency
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a schematic diagram of an architecture on which business risk management provided by embodiments of the present description is based;
FIG. 2 is a business risk management process provided by embodiments of the present description;
fig. 3 is a schematic diagram of a business risk template in an actual business scenario provided in an embodiment of the present specification;
fig. 4 is a schematic view of service logic in an actual service scenario provided by an embodiment of the present specification;
fig. 5 is a schematic structural diagram of a business risk management device according to an embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In one or more embodiments of the present disclosure, the service may include services of various software products or internet services, such as: financial products such as insurance products, stock products, fund products, and the like, or APP clients, software programs, cloud computing services, cloud storage services, and the like.
Generally speaking, in the embodiment of the present specification, a user may obtain a corresponding service through the internet, and therefore, the service is mainly a service of the above software product or internet service. However, in some service scenarios in some practical applications, hardware devices related to the service may also fall within the coverage of the "service" in the embodiments of the present description. The hardware devices related to the service may include, for example, a service server (or server cluster), a database (or database cluster), a block chain network, and the like. Some hardware components inside the device may also be included, such as a Central Processing Unit (CPU), a memory, a hard disk, a physical interface on the device, and so on.
Then, the service to be released may be considered as a service that has not been released for use by the user in the development stage.
In practical applications, there may be certain risks to the above-mentioned businesses, especially to financial products (e.g., insurance products). Take insurance products as an example:
such as: when a user purchases a certain insurance product, the paid premium is wrong; for another example: in the automatic claim settlement stage, the service provider provides the insurance limit provided by the user with errors. Obviously, the service provider needs to monitor these risks that the insurance product presents in practical applications based on the internet insurance product. Therefore, in the development stage of insurance products, corresponding risk monitoring scripts need to be configured, and various risks or potential risks appearing in the actual application of the insurance products can be timely known. This requires the developer of the insurance product to configure the corresponding risk monitoring script for the corresponding insurance product during the development phase. The process mainly depends on the experience of developers, different developers have different experiences, and in an actual scene, development efficiency and cost may be influenced by the flowing or business change of the developers.
Based on this, in the embodiments of the present specification, a business risk management method is provided to implement templated management on risks that may be involved in a business, thereby improving development efficiency and reducing development cost.
The business risk management method in the embodiment of the present specification may adopt an architecture as shown in fig. 1.
In fig. 1, a business system can be considered as a system provided by a background of a business provider and used for developing, testing, debugging and publishing a business product or a business service. In a practical application scenario, the service system may include service devices such as a cluster-type or distributed service server and a computer, and may further include a service device in the form of a blockchain network. Of course, the specific manner of the service system will be determined according to the actual application requirements, and is not limited in detail here. In the embodiment of the present specification, the service system is mainly oriented to service personnel at the background of the service provider.
And the business system performs templating treatment on the risks corresponding to different types of businesses to generate corresponding business risk templates. The business risk template can be provided for different developers to use.
Of course, fig. 1 is only a simple architecture example, and in different business scenarios, a corresponding database (which can be used to store the business risk template after templating, or the related corresponding policy information) may be further included in the architecture. The specific architecture to be adopted will be determined according to the requirements of practical application, and should not be taken as a limitation of the present application.
Based on the architecture shown in fig. 1, a business risk management process provided in the embodiment of the present application is shown in fig. 2, and the process specifically includes the following steps:
step S201: and determining a business risk template matched with the type of the business to be issued aiming at the business to be issued.
In the embodiments of the present description, different types of services generally correspond to different risks, such as: for the two insurance products, if a user uses the personal risk, the medical history information, the body state information and the like provided by the user may be wrong, so that the risk of the personal risk product is caused; if the user uses property insurance, information such as property certification and property value provided by the user may be wrong, so that the risk of property insurance products is caused. It can be seen that the risk is different for different kinds of insurance products. Of course, the above is merely an example and should not be construed as limiting the present application.
Therefore, in the development stage, the business system can generate matched business risk templates aiming at different types of businesses.
It should be noted that, as a possible embodiment in the present specification, the business risk template may be implemented by a configuration file in a format such as. ini,. cfg,. conf, or. txt. Further, the business risk template may have a corresponding template identification that may be used to identify the type to which the business belongs. Of course, in some application scenarios, the template identification can also be used to characterize a certain product or a certain series of products.
For example: the business risk template name (i.e. template identifier) of an insurance product is "health insurance", and the template identifier reflects that the insurance product corresponding to the business risk template is a health insurance, and accordingly, if the insurance product to be released is also an insurance product of a health insurance, the business risk template named "health insurance" can be determined.
In the embodiment of the present specification, the business risk template includes a plurality of risk items corresponding to the type of business. Each risk item represents the possible risk items of the business in practical application, such as: the insurance premium paid by the user in the application stage, the user information provided by the user or the insurance amount paid in the claim stage, etc.
For the development stage of the business, a developer can configure a corresponding risk monitoring script or a corresponding coping strategy according to the risk items listed in each business risk template. For this, the following step S203 may be performed.
Step S203: and displaying the risk items contained in the business risk template.
In this embodiment of the present specification, once the corresponding business risk template is determined, each risk item included in the business risk template may be presented to the corresponding developer. And enabling the developer to configure corresponding risk monitoring scripts, coping strategies or corresponding plans and the like according to the displayed risk items.
Of course, in practical applications, the risk items can be displayed in various ways, such as: the risk items can be displayed in a specific risk item display area, and the risk items can also be directly displayed on the business risk template in a floating layer mode, a pop-up window mode and the like. As shown in fig. 3, on the business risk template, the developer can know each risk item corresponding to the insurance product with the type of "personal risk".
Through the steps, for the newly online service to be released, the service risk template with the matched type can be selected according to the service type of the newly online service to be released, the service risk template comprises a plurality of risk items corresponding to the service, and thus the risk items can be displayed to corresponding developers. Obviously, for the business needing to be released, the required configuration risk items of the business are intuitively displayed to developers. And after the template is formed, the service risk template is more convenient to use and does not depend on the personal experience of developers completely, and meanwhile, the influence of the flow of the developers or the service change is small.
It should be noted here that, for the business risk template described in the above, it can be generated in the following manner, that is:
the method comprises the steps of obtaining all service cases of various insurance products, determining risk items corresponding to all the service cases according to all the service cases, and generating a service risk template corresponding to the insurance products according to the risk items corresponding to all the service cases.
The service use case described herein can be considered as a set of interaction sequences between a user and a service provider in the application process of the insurance product. For example: in the insurance application stage, the complete process that a user can buy a certain insurance product can be regarded as a service use case; another example is: in the reimbursement phase, the service provider can perform the process of premium reimbursement for the user as a service use case.
It should be understood that, in the embodiment of the present specification, a business use case is an abstract description based on an actual business action, that is, a business system may simulate an actual business execution flow through the business use case. On the basis, the risk (namely, risk item) which may exist when the business is actually applied can be determined according to the business use case.
Based on each service case, corresponding risk items can be determined, and developers can configure corresponding monitoring scripts, check scripts, coping plans or test cases and the like based on the risk items. That is, in an embodiment of the present specification, the method further includes: and setting a wind control processing script for monitoring the risk items aiming at the risk items in the service use cases, and establishing a corresponding relation between the wind control processing script and each risk item in the service use cases.
Wherein the wind control processing script comprises: at least one of a monitoring script, a checking script, a test case and a plan script.
Therefore, in the embodiment of the present specification, the business risk template may be generated by depending on a plurality of business cases, and accordingly, the risk items corresponding to the business cases may be "inherited" to the business risk template.
Of course, if there is a new risk item, it can be updated in the corresponding business use case, and then, for the business risk template generated based on the business use case, the risk item therein will be updated accordingly.
To sum up, as shown in fig. 4, the corresponding relationship between the risk item, the business case, the business risk template, and the product in the embodiment of the present specification is shown.
In summary, the business risk management method in the embodiment of the present specification associates each risk item with a business case, and a developer is usually based on the business case in a development process, so the method is more intuitive. In addition, the business case and the business risk template are obtained, a universal and templated tool is formed, business personnel in charge of risk can pay more attention to the business case and the business risk template, and developers can pay more attention to the perfection of risk items, so that personnel allocation is optimized, and labor consumption is reduced. The same risk item may correspond to a plurality of services, and the method can effectively improve the reusability of the risk item and relevant scripts and strategies thereof, and further can improve the convenience and the development efficiency of service maintenance.
It should be understood that the business risk management methods mentioned above in this specification can be applied in the development phase of other businesses than insurance products.
Based on the same idea, the business risk management method provided in the embodiment of the present application further provides a business risk management device applied to the development phase of a business, as shown in fig. 5. The device comprises:
the template determining module 501 is configured to determine, for a service to be published, a service risk template matching a type to which the service to be published belongs; the business risk template comprises a plurality of risk items corresponding to the business;
a display module 502 for displaying the risk items contained in the business risk template.
Specifically, the service to be issued includes: insurance products to be issued.
On this basis, the device further comprises: the templating module 503 obtains the service cases of the insurance products, determines the risk items corresponding to the service cases according to the service cases, and generates the service risk templates corresponding to the insurance products according to the risk items corresponding to the service cases.
The device further comprises: a script configuration module 504, configured to set a wind control processing script for monitoring a risk item in the service case, and establish a corresponding relationship between the wind control processing script and each risk item in the service case;
wherein the wind control processing script comprises: at least one of a monitoring script, a checking script, a test case and a plan script.
The device further comprises: and the risk updating module 505 is configured to add the risk item to the corresponding service case when a new risk item is added.
On the basis of the business risk management device shown in fig. 5, an embodiment of this specification further provides a business risk management apparatus, including:
a memory storing a business risk management program;
the processor calls the business risk management program stored in the memory and executes:
aiming at the service to be released, determining a service risk template matched with the type of the service to be released; the business risk template comprises a plurality of risk items corresponding to the business;
and displaying the risk items contained in the business risk template.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. Especially, as for the device, apparatus and medium type embodiments, since they are basically similar to the method embodiments, the description is simple, and the related points may refer to part of the description of the method embodiments, which is not repeated here.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps or modules recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, 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 which include, but are not limited to, the following microcontrollers: the ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, 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.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (12)
1. A business risk management method is applied to a business development stage, and comprises the following steps:
determining a business risk template matched with the type of the business to be issued aiming at the business to be issued; the business risk template comprises a plurality of risk items corresponding to the business of the type to which the business to be issued belongs;
and displaying the risk items contained in the business risk template.
2. The method of claim 1, wherein the service to be published comprises: insurance products to be issued.
3. The method of claim 2, generating a business risk template by:
acquiring various service cases of various insurance products;
determining a risk item corresponding to each type of service case according to each service case;
and generating a business risk template corresponding to the insurance products according to the risk item corresponding to each type of business case.
4. The method of claim 3, further comprising:
and when a risk item is newly added, adding the risk item into the corresponding service case.
5. The method of claim 3, further comprising:
setting a wind control processing script for monitoring the risk items aiming at the risk items in the service use case, and establishing a corresponding relation between the wind control processing script and each risk item in the service use case;
wherein the wind control processing script comprises: at least one of a monitoring script, a checking script, a test case and a plan script.
6. The method of claim 2, the risk terms comprising at least one of a premium paid by the user during the application phase, user information provided by the user, an amount of the insurance paid during the claim phase.
7. A business risk management device applied to a development phase of a business, the device comprising:
the template determining module is used for determining a business risk template matched with the type of the business to be issued aiming at the business to be issued; the business risk template comprises a plurality of risk items corresponding to the business of the type to which the business to be issued belongs;
and the display module is used for displaying the risk items contained in the business risk template.
8. The apparatus of claim 7, wherein the traffic to be published comprises: insurance products to be issued.
9. The apparatus of claim 8, further comprising: the templating module is used for acquiring each service case of each type of insurance product, determining the risk item corresponding to each type of service case according to each service case, and generating a service risk template corresponding to each type of insurance product according to the risk item corresponding to each type of service case.
10. The apparatus of claim 9, the apparatus further comprising: and the risk updating module is used for adding the risk items to the corresponding service cases when the risk items are newly added.
11. The apparatus of claim 9, further comprising: the script configuration module is used for setting a wind control processing script for monitoring the risk items aiming at the risk items in the service use cases and establishing a corresponding relation between the wind control processing script and each risk item in the service use cases;
wherein the wind control processing script comprises: at least one of a monitoring script, a checking script, a test case and a plan script.
12. A business risk management device applied to a development phase of a business, the device comprising:
a memory for storing a business risk management program;
a processor, configured to invoke the business risk management program stored in the memory, and execute:
determining a business risk template matched with the type of the business to be issued aiming at the business to be issued; the business risk template comprises a plurality of risk items corresponding to the business of the type to which the business to be issued belongs;
and displaying the risk items contained in the business risk template.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210152644.7A CN114548744A (en) | 2017-12-22 | 2017-12-22 | Business risk management method, device and equipment |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711408048.6A CN108320071B (en) | 2017-12-22 | 2017-12-22 | Business risk management method, device and equipment |
| CN202210152644.7A CN114548744A (en) | 2017-12-22 | 2017-12-22 | Business risk management method, device and equipment |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711408048.6A Division CN108320071B (en) | 2017-12-22 | 2017-12-22 | Business risk management method, device and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114548744A true CN114548744A (en) | 2022-05-27 |
Family
ID=62891512
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210152644.7A Pending CN114548744A (en) | 2017-12-22 | 2017-12-22 | Business risk management method, device and equipment |
| CN201711408048.6A Active CN108320071B (en) | 2017-12-22 | 2017-12-22 | Business risk management method, device and equipment |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711408048.6A Active CN108320071B (en) | 2017-12-22 | 2017-12-22 | Business risk management method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN114548744A (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109191312A (en) * | 2018-08-07 | 2019-01-11 | 阳光财产保险股份有限公司 | A kind of anti-fraud air control method and device of Claims Resolution |
| CN109308573A (en) * | 2018-08-31 | 2019-02-05 | 阿里巴巴集团控股有限公司 | A kind of business risk control method, device and electronic equipment based on risk point |
| CN112732272B (en) * | 2019-10-28 | 2024-05-28 | 阿里巴巴集团控股有限公司 | Application program publishing method and device |
| CN111142749B (en) * | 2019-12-19 | 2023-09-22 | 阳光人寿保险股份有限公司 | Insurance product release method, system and terminal equipment |
| CN113888339B (en) * | 2021-10-09 | 2024-01-19 | 阳光人寿保险股份有限公司 | Method, device, equipment and storage medium for checking risk event |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050278198A1 (en) * | 2004-06-09 | 2005-12-15 | Darren Huxol | Methods and systems for managing a portfolio of insurance products |
| KR20090011146A (en) * | 2007-07-25 | 2009-02-02 | 삼성에스디에스 주식회사 | System and method for risk management and estimation in information technology project |
| CN102360464A (en) * | 2011-09-30 | 2012-02-22 | 镇江睿泰信息科技有限公司 | Software risk test and control method and system thereof |
| CN102819489A (en) * | 2012-07-05 | 2012-12-12 | 北京航空航天大学 | Software reliability designing method driven by defects |
| US20150039384A1 (en) * | 2013-07-31 | 2015-02-05 | Bank Of America Corporation | Program and project risk tool |
| CN104851045A (en) * | 2014-02-13 | 2015-08-19 | 同济大学 | Industrialized project risk control system |
| CN105991574A (en) * | 2015-02-10 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Risk behavior monitoring method and apparatus thereof |
| US20170124464A1 (en) * | 2015-10-28 | 2017-05-04 | Fractal Industries, Inc. | Rapid predictive analysis of very large data sets using the distributed computational graph |
| CN107424069A (en) * | 2017-08-17 | 2017-12-01 | 阿里巴巴集团控股有限公司 | A kind of generation method of air control feature, risk monitoring and control method and apparatus |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9348734B2 (en) * | 2011-12-23 | 2016-05-24 | Sap Se | Generation of automated tests for business software solution packages |
| US8949776B2 (en) * | 2012-08-23 | 2015-02-03 | Sap Se | Gateway consumption framework |
| CN105678455A (en) * | 2016-01-05 | 2016-06-15 | 上海瀚银信息技术有限公司 | Method and system for monitoring transaction risk |
| CN106022651A (en) * | 2016-06-14 | 2016-10-12 | 深圳市迪博企业风险管理技术有限公司 | Risk early warning method based on business attribute and index system |
-
2017
- 2017-12-22 CN CN202210152644.7A patent/CN114548744A/en active Pending
- 2017-12-22 CN CN201711408048.6A patent/CN108320071B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050278198A1 (en) * | 2004-06-09 | 2005-12-15 | Darren Huxol | Methods and systems for managing a portfolio of insurance products |
| KR20090011146A (en) * | 2007-07-25 | 2009-02-02 | 삼성에스디에스 주식회사 | System and method for risk management and estimation in information technology project |
| CN102360464A (en) * | 2011-09-30 | 2012-02-22 | 镇江睿泰信息科技有限公司 | Software risk test and control method and system thereof |
| CN102819489A (en) * | 2012-07-05 | 2012-12-12 | 北京航空航天大学 | Software reliability designing method driven by defects |
| US20150039384A1 (en) * | 2013-07-31 | 2015-02-05 | Bank Of America Corporation | Program and project risk tool |
| CN104851045A (en) * | 2014-02-13 | 2015-08-19 | 同济大学 | Industrialized project risk control system |
| CN105991574A (en) * | 2015-02-10 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Risk behavior monitoring method and apparatus thereof |
| US20170124464A1 (en) * | 2015-10-28 | 2017-05-04 | Fractal Industries, Inc. | Rapid predictive analysis of very large data sets using the distributed computational graph |
| CN107424069A (en) * | 2017-08-17 | 2017-12-01 | 阿里巴巴集团控股有限公司 | A kind of generation method of air control feature, risk monitoring and control method and apparatus |
Non-Patent Citations (2)
| Title |
|---|
| MOHAMMADI, E等: "Factors influencing the policyholders\' satisfaction with the performance of insurance fund in the field of agricultural products: the case study of wheat growers in Ilam.", INTERNATIONAL JOURNAL OF AGRICULTURAL MANAGEMENT AND DEVELOPMENT, vol. 5, no. 4, 31 December 2015 (2015-12-31), pages 357 - 365 * |
| 薛晓慧;: "汽车分期业务的风险管理研究", 中国商论, no. 20, 26 October 2020 (2020-10-26), pages 59 - 60 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108320071B (en) | 2022-02-25 |
| CN108320071A (en) | 2018-07-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108320071B (en) | Business risk management method, device and equipment | |
| CN109597661B (en) | Service function configuration method and device | |
| US10901696B2 (en) | Validating computer documentation via error detection in a natural language of the computer documentation | |
| US11074154B2 (en) | Identifying a source file for use in debugging compiled code | |
| CN108173706B (en) | Service marking method, device and equipment under multi-service system | |
| CN109947643B (en) | A/B test-based experimental scheme configuration method, device and equipment | |
| CN107506181A (en) | Business processing, data processing method, device and electronic equipment | |
| CN103718155A (en) | Runtime system | |
| CN109241026B (en) | Data management method, device and system | |
| US11321084B1 (en) | Application function consolidation recommendation | |
| CN115238826B (en) | Model training method and device, storage medium and electronic equipment | |
| CN113536174A (en) | Interface loading method, device and equipment | |
| US10782940B2 (en) | Code library version management | |
| CN112559346A (en) | Service testing method and device | |
| CN109409037B (en) | Method, device and equipment for generating data confusion rule | |
| CN110347471B (en) | Hierarchical display component system, display component calling method and device | |
| CN108037914B (en) | Method and device for developing android native system by combining js | |
| CN111242731B (en) | Service execution method and device | |
| CN109815116A (en) | A kind of method for testing software and equipment platform and computer readable storage medium | |
| CN110704742B (en) | Feature extraction method and device | |
| CN112596781A (en) | Service execution and service configuration method and device | |
| US20120144398A1 (en) | Delayed expansion of values in context | |
| CN117242457A (en) | Locating neural network performance hot spots | |
| CN113590660A (en) | Data self-service query method and device and electronic equipment | |
| CN113656290A (en) | Mock point automatic identification method, device and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |