A service model management method and device and electronic equipment

Abstract

The specification provides a business model management method, device and electronic equipment, wherein the method comprises: starting a workflow according to a business requirement, and automatically transferring the business requirement to an associated leading requirement specialist; splitting the business requirement to obtain a plurality of requirement items; establishing a task for each requirement item, and assigning the task to an associated task performer through the workflow; after each task is completed, summarizing the task completion results to the leading requirement specialist through the workflow; after receiving a submission request of the leading requirement specialist, transferring the summary results to an approval personnel through the workflow; and after obtaining an approval passing identifier, triggering a business server to update a business model using the summary results. The model change work caused by requirement changes is promoted in the manner of task node transfer of the workflow, and the reason for business model change, change content and workload of each participant are recorded in the task node, so that the model change work can be orderly carried out.

Description

Technical Field

[0001] This application relates to the field of automation technology, and in particular to a business model management method, apparatus and electronic equipment. Background Technology

[0002] A company's business model can be categorized by level as follows: value chain (Level 1), business domain (Level 2), activities (Level 3), tasks (Level 4), and steps (Level 5). Business domains can include customer management and information gathering. Level 3 activities refer to end-to-end processes, such as creating or modifying a customer view. Level 4 tasks are those used to implement Level 3 activities, and Level 5 steps are the steps used to implement Level 4 tasks. In other words, a company's business model is a software system that describes the objects and elements involved in the company's management and operations, as well as the attributes, behaviors, and relationships between these objects and elements.

[0003] When business requirements change, the business model usually needs to be updated accordingly. In existing technologies, the process of updating the business model based on business requirements typically involves: requirements specialists and developers collaborating offline to study the aspects of the existing business model that need to be changed, and then the developers modify the business model accordingly.

[0004] However, this model update method makes it difficult to track the reasons for and content of business model changes, and it is also difficult to determine the workload of each participant in the business model change, resulting in relatively chaotic management. Summary of the Invention

[0005] The purpose of this application is to provide a business model management method, apparatus, and electronic device to solve the problem of chaotic business model update management.

[0006] To address the aforementioned technical problems, this specification provides a business model management method, comprising: acquiring business requirements; initiating a workflow based on the business requirements and automatically transferring the business requirements to the associated lead requirement specialist; breaking down the business requirements into multiple requirement items; for each requirement item, performing the following operations: creating a task for the current requirement item and assigning the task to the associated task executor through the workflow; after each task is completed, summarizing the completion results of each task to the lead requirement specialist through the workflow; upon receiving a submission request from the lead requirement specialist, transferring the summarized results to the approver through the workflow; and after obtaining an approval indicator, triggering the business server to update the business model using the summarized results.

[0007] In some embodiments, after each task is completed, the workflow is used to summarize the results of each task to the lead requirement specialist, including: after each task is completed, obtaining the storage link of the aggregated code segment and / or the execution result of the aggregated code segment after the code segment corresponding to each task is aggregated from the code management system; and transferring the storage link of the aggregated code segment and / or the execution result of the aggregated code segment to the lead requirement specialist through the workflow.

[0008] In some embodiments, after obtaining the approval identifier, the business server is triggered to update the business model using the aggregated results, including: after obtaining the approval identifier, sending an update model instruction to the code version management system, wherein the update model instruction contains the identifier of the aggregated results in the code version management system, and the update model instruction causes the code version management system to deploy the code segment corresponding to the identifier to the business server, thereby updating the business model.

[0009] In some embodiments, the business requirement is broken down into multiple requirement items, including: receiving multiple requirement items input by the lead requirement specialist, wherein the requirement items are obtained based on the breakdown of the business requirement.

[0010] In some embodiments, the business requirement is split into multiple requirement items, including: after receiving an automatic splitting instruction input by the lead requirement specialist, the business requirement is input into a pre-trained first network model, and the first network model splits the business requirement and outputs multiple requirement items.

[0011] In some embodiments, creating a task for a current requirement item includes: transferring the current requirement item to an associated person; receiving a task input by the associated person, the task being used to implement the current requirement item.

[0012] In some embodiments, establishing a task for the current requirement includes: after receiving an instruction to automatically establish a task, inputting the current requirement into a pre-trained second network model, the second network model being used to establish a task to implement the current requirement.

[0013] The second aspect of this specification provides a business model management device, comprising: an acquisition unit for acquiring business requirements, initiating a workflow based on the business requirements, and automatically transferring the business requirements to an associated lead requirement specialist; a splitting unit for splitting the business requirements into multiple requirement items; a processing unit for performing the following operations on each requirement item: creating a task for the current requirement item and assigning the task to an associated task executor through the workflow; a summarizing unit for summarizing the completion results of each task to the lead requirement specialist through the workflow after each task has been completed; a transfer unit for transferring the summarizing results to an approver through the workflow after receiving a submission request from the lead requirement specialist; and an update unit for triggering a business server to update the business model using the summarizing results after obtaining an approval approval identifier.

[0014] In some embodiments, after each task is completed, the aggregation unit obtains the storage link of the aggregated code segment and / or the execution result of the aggregated code segment from the code management system, and then transfers the storage link of the aggregated code segment and / or the execution result of the aggregated code segment to the lead requirement specialist through the workflow.

[0015] In some embodiments, after obtaining the approval identifier, the update unit sends an update model instruction to the code version management system. The update model instruction includes the identifier of the summary result in the code version management system. The update model instruction causes the code version management system to deploy the code segment corresponding to the identifier to the business server, thereby updating the business model.

[0016] In some embodiments, the splitting unit includes: a first receiving subunit, configured to receive multiple requirement items input by the lead requirement specialist, the requirement items being split according to the business requirements.

[0017] In some embodiments, the splitting unit includes: a first automatic splitting subunit, configured to input the business requirement into a pre-trained first network model after receiving an automatic splitting instruction from the lead requirement specialist, wherein the first network model splits the business requirement and outputs multiple requirement items.

[0018] In some embodiments, the processing unit includes: a transfer unit for transferring the current demand item to the associated person; and a second receiving subunit for receiving a task input by the associated person, the task being used to implement the current demand item.

[0019] In some embodiments, the processing unit includes: a second automatic creation subunit, configured to input the current requirement item into a pre-trained second network model after receiving an automatic task creation instruction, wherein the second network model is used to create a task to implement the current requirement item.

[0020] A third aspect of this specification provides an electronic device, comprising: a memory and a processor, wherein the processor and the memory are communicatively connected to each other, the memory stores computer instructions, and the processor executes the computer instructions to implement the steps of the method described in any of the first aspects.

[0021] A fourth aspect of this specification provides a computer storage medium storing computer program instructions that, when executed by a processor, implement the steps of the method described in any of the first aspects.

[0022] A fifth aspect of this specification provides a computer program product comprising a computer program that, when executed by a processor, implements the steps of the method described in any of the first aspects.

[0023] The business model management methods, devices, and electronic equipment provided in this manual promote model changes caused by changes in requirements through the workflow of task nodes. Each task node records the reason for the business model change (i.e., providing the correspondence between requirements and business model changes), the content of the change, and the workload of each participant. This unified tracking and management of business model updates ensures that model changes are carried out in an orderly manner, preventing confusion and duplication of work. Driven by business requirements, the system links business model updates, enabling business requirements to be assigned to specific individuals and facilitating timely processing of business needs. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0025] Figure 1 This document illustrates a schematic diagram of the methods implemented by the business model management system provided in this specification.

[0026] Figure 2 This document shows a flowchart of the method for the business model management system provided in this specification;

[0027] Figure 3 This diagram illustrates the dialog box for filling in business requirements displayed on the modeling information page.

[0028] Figure 4 A schematic diagram of the page showing the breakdown of requirements is provided.

[0029] Figure 5 A schematic diagram of the page for filling in the split requirements items is shown;

[0030] Figure 6 A schematic diagram of the requirements list for the task to be created is shown;

[0031] Figure 7 This diagram illustrates a task that has been created under a requirement item;

[0032] Figure 8 A schematic diagram of the task entry page is shown;

[0033] Figure 9 This diagram illustrates the relationships between the business model management system and other systems.

[0034] Figure 10 This specification shows a schematic block diagram of a business model management device provided in an embodiment.

[0035] Figure 11 A schematic block diagram of an electronic device provided in this specification is shown. Detailed Implementation

[0036] To enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0037] This specification provides a business model management method, such as Figure 1 and Figure 2 As shown, this method is applied to a business model management system. The method includes the following steps:

[0038] S10: Obtain business requirements, initiate a workflow based on the business requirements, and automatically transfer the business requirements to the associated lead requirement specialist.

[0039] Business requirements can come from the customers served by the business, from business operations personnel, or from front-end designers; in other words, business requirements can come from anyone related to the business.

[0040] In some embodiments, business requirements may be filled in by the aforementioned personnel in the business model management system, for example, Figure 3The diagram illustrates a dialog box for filling in business requirements on the modeling information page. According to the diagram, when filling in business requirements, one should typically specify a business requirement number (which can be filled in by the personnel or automatically assigned by the system), enter the business requirement name, the contact person and the department submitting the requirement, and select the business model type—either a domain model or a process model. A domain model is a coded representation of conceptual classes or real-world objects within a domain, or even a visual representation based on that coded representation. A process model refers to the internal processing flow of a software method. The suggested completion time can be specified by the personnel filling in the business requirements or automatically determined by the system.

[0041] In some embodiments, business requirements may also be obtained from other systems. For example, they may be obtained from a business complaint management system.

[0042] The lead requirements specialist is the person in charge of all requirements.

[0043] In some embodiments, there may be only one lead request specialist, in which case the associated lead request specialist can be uniquely identified.

[0044] In some embodiments, there may be multiple lead requirements specialists, each with different responsibilities. In some cases, the lead requirements specialist may be designated in the business requirements, for example... Figure 3 The business requirement form requires specifying a lead request specialist, i.e., the person responsible for executing the task. In some cases, this can be determined based on keywords in the business requirement description. For example, if the business requirement contains "assistance in investigation," then lead request specialist A will be responsible; if it contains "deposit," then lead request specialist B will be responsible; and if it contains "loan," then lead request specialist C will be responsible. In other cases, the textual description of the business requirement can be input into a pre-trained network model with semantic recognition capabilities. The network model will then output the lead request specialist, and this output specialist will be used as the lead request specialist associated with that business requirement.

[0045] "Transfer" refers to the process in a workflow where, after the current task node completes its task, the next task node becomes the new current task node, and the tasks of the new current task node are executed. Transferring work content W to personnel P means assigning the work content to personnel P, who then processes it under their account. In this specification, "personnel P" can be used to refer to the task node they are responsible for.

[0046] The business model management system operates on a workflow, which drives model changes caused by changes in requirements through task node flow. The reasons for the business model changes, the content of the changes, and the workload of each participant are recorded at the task nodes. This ensures that the model change work is carried out in an orderly manner and prevents chaos and duplication of work.

[0047] Steps S20, S30, S40, S50, and S60 in this manual are all implemented using a workflow.

[0048] S20: Break down business requirements into multiple requirement items.

[0049] A business requirement item refers to a requirement granularity extracted from the content of business requirements. Each business requirement item can completely describe an end-to-end business requirement. The principle for breaking down requirement items is that the resulting requirement items can completely describe the end-to-end requirements or accurately describe the points of change in the business process.

[0050] In some embodiments, the task of splitting requirement items can be performed by professionals, such as a lead requirement specialist, or by other professionals who then send the splitting results to the lead requirement specialist. The lead requirement specialist can do so through methods such as... Figure 4 The page shown initiates the requirement item splitting process; clicking the "Split Requirement Items" button in the operation bar will redirect you to the page shown. Figure 5 The page shown is for filling in the split requirements items. On this page, you can fill in the name, description and other information of each split requirement item.

[0051] In some embodiments, the task of splitting requirement items can also be automatically performed by the business model management system. For example, a first network model for splitting business requirements can be pre-trained and embedded into the business model management system. When the lead requirement specialist inputs an automatic splitting command, the business model management system automatically inputs the business requirements to be split into the first network model, which then splits the business requirements and outputs multiple split requirement items. The lead requirement specialist can confirm each requirement item output by the first network model and perform add, delete, or modify operations to obtain the final splitting result. That is, in this embodiment, the business requirements are initially split using the first network model to share some of the work of the lead requirement specialist, but the final result is based on the confirmation of the lead requirement specialist, thereby ensuring the accuracy of the splitting result.

[0052] In some embodiments, in addition to splitting requirement items, requirement items can also be merged and adjusted. For example... Figure 2As shown, requirement A can be broken down into requirement A1 and requirement A2, requirement B and requirement C can be merged into requirement B', and requirement D is an adjustment of requirement D'. This specification mainly uses the breakdown of requirement items to illustrate the business model management system provided in this specification.

[0053] S30: For each requirement item, perform the following operations: create a task for the current requirement item, and assign the task to the associated task executor through the workflow.

[0054] The tasks established in business model management refer to the work of writing or adjusting code segments that can be used to implement requirements.

[0055] In some embodiments, a task can be created for the current requirement by transferring the current requirement to a relevant person and receiving the task input from that person. In some cases, the relevant person may be someone other than the lead requirement specialist, in which case the current requirement needs to be transferred to the relevant person; in other cases, the relevant person may be the lead requirement specialist, in which case the current requirement can be transferred to the lead requirement specialist himself.

[0056] In some embodiments, the associates for establishing tasks based on requirements typically include multiple associates, each with different responsibilities. In some cases, associates can be specified in the requirements. In others, they can be determined based on keywords in the requirements description. In still others, the textual description of the requirements can be input into a pre-trained network model with semantic recognition capabilities, and the network model can output associates, which are then used as the associates for the requirements.

[0057] The page that the associated person sees can be like Figure 6 As shown, Figure 6 The page displays a list of all requirements for tasks to be created under the associated person's name, where "Assign Task" is the function to create a task for each requirement. Clicking... Figure 6 Following the "Assign Task" button (highlighted in bold), you can navigate to... Figure 7 The task assignment interface shown. Figure 7 The image shows examples of some tasks that have already been assigned. When you click... Figure 7 When you click the "Assign Task" button, you can also jump to... Figure 8 The task entry page shown allows associated users to... Figure 8 On the page shown, fill in the information for the newly assigned task. This information may include the task name, task number, task type (iterative optimization, deletion, or addition), the model level involved in the task (level 3 activity, level 4 activity, or level 5 step; see the background technology section for details), suggested completion time, and the responsible person for the task.

[0058] In some embodiments, the task creation for the current requirement item can also be automatically performed by the business model management system. For example, a second network model for creating tasks for requirement items can be pre-trained and embedded into the business model management system. When a user inputs an automatic task creation command, the business model management system automatically inputs the requirement item to be created into the second network model, which then automatically creates tasks for the requirement item and outputs one or more created tasks. The user can confirm the tasks output by the second network model and perform add, delete, or modify operations to obtain the final task creation result. That is, in this embodiment, the second network model is used to initially create tasks for the business requirements, sharing some of the user's workload, but the final result is based on the user's confirmation, thus ensuring the accuracy of the task creation result.

[0059] The “assigned task executor” in the above-mentioned “assigning the task to the associated task executor” can be determined in any of the following ways: 1. specified in the task; 2. determined according to the keywords in the task description; 3. inputting the textual description of the task into a pre-trained network model with semantic recognition function, outputting the task execution by the network model, and using the output task executor as the associated task executor.

[0060] like Figure 2 As shown, for requirement A1, task A1 is created, task A1 is associated with model A1, and the task is assigned to task executor A1; for requirement A2, task A2 is created, task A2 is associated with models A21 and A22, and task A2 is assigned to task executor A2; for requirement B', task B' is created, task B' is associated with model B', and task B' is assigned to task executor B'; for requirement D', task D' is created, task D' is associated with model D', and task D' is assigned to task executor D'; for requirement N, task N is created, task N is associated with model N, and task N is assigned to task executor N.

[0061] S40: After each task is completed, the results of each task are summarized and sent to the lead request specialist through the workflow.

[0062] like Figure 2 As shown, each task executor (A1, A2, B, D...N) submits the task completion result to the lead requirements specialist (Z) after completing their respective tasks. The completion result can refer to the specific content of the task, such as the written code segment and its execution result, or sending the storage link of the code segment to the lead requirements specialist; or it can be a description of the task completion status, such as "100% complete."

[0063] Once all tasks related to a business requirement have been completed by all responsible parties, the business model management system automatically summarizes the results from each task executor and sends them to the lead requirement specialist. For example, if... Figure 9 As shown, the system can automatically retrieve the storage link of the aggregated code segment obtained by each task executor (stored in the code version control system), and download the execution result of the aggregated code segment. It then sends the storage link and / or the execution result of the aggregated code segment to the lead specialist. Here, aggregation refers to the ability of multiple code segments to achieve the desired effect when executed together. However, there may be situations where multiple code segments cannot be aggregated.

[0064] S50: After receiving the request from the lead request specialist, the summary results are transferred to the approver through the workflow.

[0065] The lead requirement specialist can operate the business model management system and transfer the summarized results to the approvers within the system.

[0066] In some embodiments, the approver may refer to the approver within the enterprise, and the approver conducts the approval under the business model management system, that is, the approval process is implemented by the business model management system.

[0067] In other embodiments, the approvers are not internal company personnel, or although they are internal personnel, the approval process is not conducted using the business model management system, but rather a dedicated approval system. That is, the business model management system is not used to implement the approval workflow. In this case, such as... Figure 9 As shown, a communication component can be set up between the business model management system and the approval system to enable data transmission between the two systems, so that the summary results of the business model management system can be sent to the approval system, and the approval system can send the approval results to the business model management system.

[0068] S60: After obtaining the approval indicator, the business server is triggered to update the business model using the aggregated results.

[0069] like Figure 9As shown, the target content of the task executed by the task executor is stored in the code version control system. The code version control system is connected to the business server and can deploy updated code segments to the business server to update the business model running on the business server. Therefore, S60 can be: after obtaining the approval result, the business model management system sends an update model instruction to the code version control system. This update model instruction may contain the identifier of the aggregated code segment (i.e., the summary result) in the code version control system (the identifier can be the code version or the storage link). This update model instruction causes the code version control system to deploy the code segment corresponding to the identifier to the business server to update the business model.

[0070] The business model management method provided in this manual promotes model changes caused by requirement changes through the workflow of task nodes. Each task node records the reason for the business model change (i.e., providing the correspondence between requirements and business model changes), the content of the change, and the workload of each participant. This unified tracking and management of business model updates ensures that model changes are carried out in an orderly manner, preventing confusion and duplication of work. Driven by business requirements, the method links business model updates, enabling business requirements to be assigned to specific individuals and facilitating timely processing of business needs.

[0071] This specification provides a business model management device that can be used to implement... Figure 1 The business model management method shown. For example... Figure 10 The device includes an acquisition unit 10, a splitting unit 20, a processing unit 30, a summarizing unit 40, a transfer unit 50, and an updating unit 60.

[0072] The acquisition unit 10 is used to acquire business requirements, initiate a workflow based on the business requirements, and automatically transfer the business requirements to the associated lead requirement specialist.

[0073] The splitting unit 20 is used to split the business requirement into multiple requirement items.

[0074] The processing unit 30 is used to perform the following operations for each requirement item: create a task for the current requirement item, and assign the task to the associated task executor through the workflow.

[0075] The aggregation unit 40 is used to aggregate the results of each task to the lead request specialist through the workflow after each task has been completed.

[0076] The workflow unit 50 is used to transfer the summary results to the approver through the workflow after receiving the submission request from the lead request specialist.

[0077] The update unit 60 is used to trigger the business server to update the business model with the summary results after obtaining the approval mark.

[0078] In some embodiments, after each task is completed, the aggregation unit obtains the storage link of the aggregated code segment and / or the execution result of the aggregated code segment from the code management system, and then transfers the storage link of the aggregated code segment and / or the execution result of the aggregated code segment to the lead requirement specialist through the workflow.

[0079] In some embodiments, after obtaining the approval identifier, the update unit sends an update model instruction to the code version management system. The update model instruction includes the identifier of the summary result in the code version management system. The update model instruction causes the code version management system to deploy the code segment corresponding to the identifier to the business server, thereby updating the business model.

[0080] In some embodiments, the splitting unit includes: a first receiving subunit, configured to receive multiple requirement items input by the lead requirement specialist, the requirement items being split according to the business requirements.

[0081] In some embodiments, the splitting unit includes: a first automatic splitting subunit, configured to input the business requirement into a pre-trained first network model after receiving an automatic splitting instruction from the lead requirement specialist, wherein the first network model splits the business requirement and outputs multiple requirement items.

[0082] In some embodiments, the processing unit includes: a transfer unit for transferring the current demand item to the associated person; and a second receiving subunit for receiving a task input by the associated person, the task being used to implement the current demand item.

[0083] In some embodiments, the processing unit includes: a second automatic creation subunit, configured to input the current requirement item into a pre-trained second network model after receiving an automatic task creation instruction, wherein the second network model is used to create a task to implement the current requirement item.

[0084] The description and beneficial effects of the above-mentioned business model management device can be found in the description and beneficial effects section of the method section, and will not be repeated here.

[0085] This invention also provides an electronic device, such as... Figure 11 As shown, the electronic device may include a processor 1101 and a memory 1102, wherein the processor 1101 and the memory 1102 may be connected via a bus or other means. Figure 11 Taking the example of a connection between China and Israel via a bus.

[0086] Processor 1101 may be a central processing unit (CPU). Processor 1101 may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or combinations thereof.

[0087] Memory 1102, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as program instructions / modules corresponding to the business model management method in this embodiment of the invention (e.g., Figure 10 The acquisition unit 10, splitting unit 20, processing unit 30, summarizing unit 40, transfer unit 50, and update unit 60 are shown. The processor 1101 executes various functional applications and data classification by running non-transitory software programs, instructions, and modules stored in the memory 1102, thereby realizing the business model management method in the above method embodiment.

[0088] The memory 1102 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created by the processor 1101, etc. Furthermore, the memory 1102 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory 1102 may optionally include memory remotely located relative to the processor 1101, and these remote memories may be connected to the processor 1101 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0089] The one or more modules are stored in the memory 1102, and when executed by the processor 1101, the above-mentioned business model management method is performed.

[0090] For details regarding the electronic device described above, please refer to the relevant descriptions and effects in the above embodiments for further understanding; they will not be repeated here.

[0091] This specification provides a computer storage medium that stores computer program instructions, which, when executed by a processor, implement the steps of the above-described business model management method.

[0092] This specification provides a computer program product that includes a computer program that, when executed by a processor, implements the steps of the above-described business model management method.

[0093] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk drive (HDD), or solid-state drive (SSD), etc.; the storage medium can also include combinations of the above types of memory.

[0094] The various embodiments in this specification are described in a progressive manner. For the same or similar parts between the various embodiments, please refer to each other. The focus of each embodiment is to describe the differences from other embodiments.

[0095] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions.

[0096] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0097] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute certain parts of the methods of various embodiments of this application.

[0098] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc.

[0099] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0100] Although this application has been described through embodiments, those skilled in the art will know that this application has many modifications and variations without departing from the spirit of this application, and it is intended that the appended claims cover such modifications and variations without departing from the spirit of this application.

Claims

1. A service model management method characterized by comprising: The method comprises the following steps: acquiring a business requirement, starting a workflow according to the business requirement, and automatically transferring the business requirement to an associated lead requirement specialist; splitting the business requirement into multiple requirement items; for each requirement item, performing the following operations: establishing a task for the current requirement item, and assigning the task to an associated task performer through the workflow; after each task is completed, aggregating the task completion results to the lead requirement specialist through the workflow; after receiving a submission request from the lead requirement specialist, transferring the aggregated results to an approval personnel through the workflow; after obtaining an approval identifier, triggering the business server to update the business model using the aggregated results; after each task is completed, aggregating the task completion results to the lead requirement specialist through the workflow, which comprises: after each task is completed, obtaining a storage link of an aggregated code segment and / or an execution result of the aggregated code segment corresponding to each task from a code management system; and transferring the storage link of the aggregated code segment and / or the execution result of the aggregated code segment to the lead requirement specialist through the workflow; after obtaining the approval identifier, triggering the business server to update the business model using the aggregated results, which comprises: after obtaining the approval identifier, sending an update model instruction to a code version management system, wherein the update model instruction contains an identifier of the aggregated results in the code version management system, and the update model instruction causes the code version management system to deploy a code segment corresponding to the identifier to the business server to update the business model.

2. The method of claim 1, wherein, The method of splitting the business requirement into multiple requirement items comprises: receiving multiple requirement items input by the lead requirement specialist, wherein the requirement items are obtained by splitting the business requirement.

3. The method of claim 1, wherein, The method of splitting the business requirement into multiple requirement items comprises: after receiving an automatic splitting instruction input by the lead requirement specialist, inputting the business requirement into a pre-trained first network model, wherein the first network model splits the business requirement and outputs multiple requirement items.

4. The method of claim 1, wherein, The method of establishing a task for the current requirement item comprises: transferring the current requirement item to an associated person; receiving a task input by the associated person, wherein the task is used to implement the current requirement item.

5. The method of claim 1, wherein, The method of establishing a task for the current requirement item comprises: after receiving an automatic task establishment instruction, inputting the current requirement item into a pre-trained second network model, wherein the second network model is used to establish a task for implementing the current requirement item.

6. A service model management apparatus characterized by comprising: The method comprises the following steps: an acquisition unit is configured to acquire a business requirement, start a workflow according to the business requirement, and automatically transfer the business requirement to an associated lead requirement specialist; a splitting unit is configured to split the business requirement into multiple requirement items; a processing unit is configured to perform the following operations for each requirement item: establish a task for the current requirement item, and assign the task to an associated task performer through the workflow; an aggregation unit is configured to aggregate the task completion results to the lead requirement specialist through the workflow after each task is completed; a transfer unit is configured to transfer the aggregated results to an approval personnel through the workflow after receiving a submission request from the lead requirement specialist; and An updating unit is configured to trigger the business server to update the business model with the summary result after obtaining the approved identifier. The summary unit obtains the storage link of the aggregated code segment and / or the execution result of the aggregated code segment corresponding to each task from the code management system after each task is executed, and transfers the storage link of the aggregated code segment and / or the execution result of the aggregated code segment to the leading demand officer through the workflow. The updating unit sends an updating model instruction to the code version management system after obtaining the approved identifier, the updating model instruction including the identifier of the summary result in the code version management system, and the updating model instruction causing the code version management system to deploy the code segment corresponding to the identifier to the business server to update the business model.

7. An electronic device, comprising: The computer storage medium stores computer program instructions, and the computer program instructions are executed by the processor to implement the steps of the method in any one of claims 1 to 5. The computer storage medium stores computer program instructions, and the computer program instructions are executed by the processor to implement the steps of the method in any one of claims 1 to 5.

8. A computer storage medium, characterized in that, The computer program is executed by the processor to implement the steps of the method in any one of claims 1 to 5.

9. A computer program product, characterised in that, ​

Images