Process model generation method and device, equipment and medium

By generating business subfields and value flows, the business architecture process model is automatically constructed, which solves the problems of high cost and low efficiency of process model construction in the existing technology, and achieves fast and high-accuracy process modeling.

CN119313230APending Publication Date: 2025-01-14INDUSTRIAL AND COMMERCIAL BANK OF CHINA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311555742.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-11-21
Publication Date
2025-01-14

AI Technical Summary

Technical Problem

The construction of process models in existing business architectures requires a lot of manpower, material resources and time, and the modeling is costly and inefficient, mainly due to the need to manually analyze and operate various systems to build and associate multiple levels.

Method used

By obtaining the business scope of responsibilities and the business scope applied by the business department, generating business subfields, and building a value stream based on the relationship between activities and subfields, thereby automatically generating process models.

Benefits of technology

It realizes rapid generation and high accuracy of process models, reduces manual investment, and improves modeling efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119313230A_ABST
    Figure CN119313230A_ABST
Patent Text Reader

Abstract

The invention provides a method for generating a process model, relates to the technical field of business architecture, and can be applied to the field of financial science and technology and other fields. The method for generating the process model comprises the following steps: acquiring a business field and a responsibility range of a business department and a business range of an application; for each application, generating a service sub-field according to the correlation between the service range of the application and the responsibility range of each service department; obtaining applications involved in the execution of the target business and processing flows involved in each application; generating an activity for each processing flow, wherein each activity has an association relationship with a service sub-field corresponding to an application involved when the activity is generated; and generating a value flow for each service sub-field according to the association relationship between each activity and the service sub-field. The invention further provides a process model generation device and equipment, a storage medium and a program product.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the technical field of business architecture, and in particular to a method, apparatus, device, medium and program product for generating a process model. Background Art

[0002] Business architecture can be used to guide which business models are needed to achieve a business requirement, the services to be provided in each business model, and the collaborative relationships such as data transmission or call between different business models. Write or adjust the business architecture according to the required use cases.

[0003] Promoting digital transformation through business architecture has become the best choice for many enterprises. For example, business architecture can include: process model, product model and entity model. However, the construction of each model in the business architecture often requires a lot of human, material and time resources.

[0004] Taking the process model as an example, the process model includes five levels: business domain, value stream, activities, tasks, steps and rules. The construction of each level requires modelers to aggregate information from various systems and filter and integrate them. In addition, multiple levels must be associated and connected. The above processes require manual analysis and operation by modelers, which results in high modeling costs and low modeling efficiency. Summary of the invention

[0005] In view of the above problems, the present disclosure provides a method, apparatus, device, medium and program product for generating a process model.

[0006] According to a first aspect of the present disclosure, a method for generating a process model is provided, comprising:

[0007] Obtaining a business domain of at least one business department, a scope of responsibility of each of the business departments, and a business scope of at least one application;

[0008] For each application, a business sub-domain is generated according to the correlation between the business scope of the application and the scope of responsibility of each business department, wherein each business sub-domain has a corresponding relationship with the application, and when the application is related to the scope of responsibility of multiple business departments, a business sub-domain is generated for each business department;

[0009] Obtain the applications involved in the execution of the target business and the processing flow involving each application;

[0010] Generating an activity for each of the processing flows to obtain a first activity set, in which each activity has an association relationship with a business sub-domain corresponding to an application involved in generating the activity;

[0011] According to the association relationship between each activity in the first activity set and the business sub-domain, a value stream is generated for each business sub-domain to obtain the process model.

[0012] According to an embodiment of the present disclosure, according to the association relationship between each activity in the first activity set and the business sub-domain, a value stream is generated for each of the business sub-domains to obtain the process model, including:

[0013] For the xth business sub-domain, according to the logical relationship between the activities in the first activity set that have the association relationship with the xth business sub-domain, a value stream is generated for the xth business sub-domain;

[0014] Wherein, the x is a positive integer.

[0015] According to an embodiment of the present disclosure, according to the association relationship between each activity in the first activity set and the business sub-domain, a value stream is generated for each of the business sub-domains to obtain the process model, including:

[0016] In the same business area, merge the business sub-areas with similar value streams;

[0017] When there is no business sub-field with a similar value stream under the same business field, the business sub-field under the business field is upgraded to the business field.

[0018] According to an embodiment of the present disclosure, for each application, generating a business sub-domain according to the correlation between the business scope of the application and the scope of responsibility of each business department includes: for a business department,

[0019] When the business scope of the application is greater than or equal to the responsibility scope of the business department, a business sub-domain is generated, and the name of the business sub-domain includes the name of the application;

[0020] When the business scope of the application is smaller than the responsibilities of the business department, a business sub-domain is generated based on the application, and the name of the business sub-domain includes the name of the application and a name to be verified mark;

[0021] In the currently generated business sub-fields, if the applications corresponding to two business sub-fields belong to the same business department, the two business sub-fields are merged, and the name of the merged business sub-field includes the name of the application with the largest business scope.

[0022] According to an embodiment of the present disclosure, when the business scope of the application is smaller than the scope of responsibility of the business department, generating a business sub-domain for each application according to the correlation between the business scope of the application and the scope of responsibility of each business department also includes:

[0023] A business sub-field is generated according to the uncovered responsibilities of the business department, and the name of the business sub-field includes a name to be confirmed mark.

[0024] According to an embodiment of the present disclosure, for each application, a business sub-domain is generated according to the correlation between the business scope of the application and the scope of responsibility of each business department, including:

[0025] Obtain the database table that the application is responsible for;

[0026] When the database tables that two applications are responsible for are consistent, determine whether the two applications belong to the same business department;

[0027] When two applications belong to one business department, the two business sub-areas corresponding to the two applications are merged;

[0028] When two applications do not belong to the same business department, the business sub-fields corresponding to the two applications are marked as integration to be confirmed.

[0029] According to an embodiment of the present disclosure, obtaining the applications involved in the execution of the target service and the processing flow when each application is involved includes:

[0030] Acquire an IT service call link of a target business, wherein the IT service call link includes multiple IT services connected in series in an execution order, wherein the multiple IT services include an IT service used by the target business during execution, and each of the IT services belongs to an application;

[0031] The IT services that are adjacent to each other and belong to the same application in the IT service call link are regarded as one processing flow.

[0032] According to an embodiment of the present disclosure, obtaining an IT service call link of a target business includes:

[0033] The first IT service called by the target business when it is initiated is obtained and annotated as a business label, wherein the business label is configured to: color each called IT service along with the processing progress of the target business;

[0034] According to the staining result, the IT service call link of the target business is obtained.

[0035] According to an embodiment of the present disclosure, generating an activity for each of the processing flows includes:

[0036] For a processing flow, the IT service is converted into a task of the activity, wherein the service name of the IT service is converted into a task name of the task, the service steps of the IT service are converted into task steps of the task, and the processing logic of the IT service is converted into business rules of the task steps.

[0037] According to an embodiment of the present disclosure, constructing an activity for each of the processing flows to obtain a first activity set further includes:

[0038] Obtaining the execution subject of the task;

[0039] When the execution subjects of two adjacent tasks are the same, the two adjacent tasks are merged into one task group, and the execution subjects are used as candidate roles;

[0040] When the execution entities of two identical task groups are different, the execution entities of the two task groups are merged.

[0041] According to an embodiment of the present disclosure, constructing an activity for each of the processing flows to obtain a first activity set further includes: drawing an activity diagram for at least one activity according to the execution subjects of the tasks and the task groups.

[0042] According to an embodiment of the present disclosure, generating a value stream for each of the business sub-fields according to the association relationship between each activity in the first activity set and the business sub-field to obtain the process model includes:

[0043] Get the database table that each activity is responsible for;

[0044] Group activities responsible for the same database tables into the same value stream;

[0045] Based on semantic analysis, target activities are selected from the same value stream by the names of the activities;

[0046] The name of the value stream is generated according to the name of the target activity and the database table that the target activity is responsible for.

[0047] According to an embodiment of the present disclosure, the generating method further includes:

[0048] Acquire an enterprise value chain and a department type of the business department, wherein the enterprise value chain includes a core production node and an auxiliary production node;

[0049] According to the type of the business department, the business domain of the business department is associated with at least one of the core production node and the auxiliary production node.

[0050] According to an embodiment of the present disclosure, generating a business sub-domain under the business domain according to the correlation between the scope of responsibility and the business scope of each application includes:

[0051] The relevance of the business scope of the application to the responsibilities of each business department is analyzed through natural language processing technology.

[0052] A second aspect of the present disclosure provides a device for generating a process model, which includes:

[0053] A first acquisition module, used to acquire a business domain of at least one business department, a scope of responsibility of each of the business departments, and a business scope of at least one application;

[0054] A sub-domain generation module, for generating a business sub-domain for each application according to the correlation between the business scope of the application and the scope of responsibility of each business department, wherein each business sub-domain has a corresponding relationship with the application, and when the application is related to the scope of responsibility of multiple business departments, a business sub-domain is generated for each business department;

[0055] The second acquisition module is used to acquire the applications involved in the execution of the target business and the processing flow involved in each application;

[0056] An activity generation module, configured to generate an activity for each of the processing flows to obtain a first activity set, wherein each activity in the first activity set is associated with a business sub-domain corresponding to an application involved in generating the activity;

[0057] The value stream generation module is used to generate a value stream for each of the business sub-fields according to the association relationship between each activity in the first activity set and the business sub-field, so as to obtain the process model.

[0058] The third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned method for generating a process model.

[0059] The fourth aspect of the present disclosure further provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the above-mentioned method for generating a process model.

[0060] The fifth aspect of the present disclosure also provides a computer program product, including a computer program, which implements the above-mentioned method for generating a process model when executed by a processor.

[0061] One or more of the above embodiments have the following advantages or beneficial effects:

[0062] In the embodiments of the present disclosure, through the generation method of the process model of the embodiments of the present disclosure, starting from the actual running system, relevant information (the scope of responsibilities of the business department and the business scope of the application) is extracted from the enterprise organizational architecture system and the IT architecture management system, and then business sub-fields are formed based on the correlation between the scope of responsibilities and the business scope, and activities are generated through the applications involved in the actual execution of the target business. Then, the value stream of each business sub-field is inferred. At this time, there is a clear association between the business field, the value stream and the activity. For example, a business field may include a business sub-field, and the business sub-field has a value stream, which is composed of corresponding activities. Thus, a basic process model can be constructed. The embodiments of the present disclosure do not require a lot of manpower to achieve the goal of process modeling, and the model generation speed is fast and the accuracy is high. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0064] Figure 1 The application scenario diagram schematically shows the method, device, electronic device, storage medium and program product for generating a process model according to an embodiment of the present disclosure;

[0065] Figure 2 A flowchart schematically shows a method for generating a process model according to an embodiment of the present disclosure;

[0066] Figure 3 A flowchart of generating a value stream according to an embodiment of the present disclosure is schematically shown;

[0067] Figure 4 One of the flow charts for merging business sub-fields according to an embodiment of the present disclosure is schematically shown;

[0068] Figure 5 A flowchart of generating a business sub-domain according to an embodiment of the present disclosure is schematically shown;

[0069] Figure 6 The second flowchart schematically shows the merging of business sub-fields according to an embodiment of the present disclosure;

[0070] Figure 7 A flowchart schematically shows an acquisition processing flow according to an embodiment of the present disclosure;

[0071] Figure 8 A flowchart of merging tasks according to an embodiment of the present disclosure is schematically shown;

[0072] Fig. 9A flowchart for grouping activities into value streams according to an embodiment of the present disclosure is schematically shown;

[0073] Fig.10 A flowchart for establishing association between a business domain and an enterprise value chain according to an embodiment of the present disclosure is schematically shown;

[0074] Fig.11 The structure block diagram of the device for generating the process model according to the embodiment of the present disclosure is schematically shown;

[0075] Fig.12 A block diagram of an electronic device suitable for implementing a method for generating a process model according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0076] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0077] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0078] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0079] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0080] It should be noted that the method, device, electronic device, storage medium and program product for generating a process model provided in the embodiments of the present disclosure relate to the field of business architecture technology. The method, device, electronic device, storage medium and program product for generating a process model provided in the embodiments of the present disclosure can be applied to the financial field or any field other than the financial field. The embodiments of the present disclosure do not limit the application fields of the method, device, electronic device, storage medium and program product for generating a process model.

[0081] In the disclosed technical solutions, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0082] The embodiments of the present disclosure provide a method for obtaining the business domain of at least one business department, the scope of responsibilities of each business department, and the business scope of at least one application. For each application, a business sub-domain is generated based on the correlation between the business scope of the application and the scope of responsibilities of each business department, wherein each business sub-domain has a corresponding relationship with the application, and when the application is related to the scope of responsibilities of multiple business departments, a business sub-domain is generated for each business department. The IT service call link of the target business is obtained, and the IT service call link includes: the applications involved in the execution of the target business, and the processing flow when each application is involved. An activity is generated for each processing flow to obtain a first activity set, in which each activity in the first activity set has an association relationship with the business sub-domain corresponding to the application involved when generating the activity. Based on the association relationship between each activity in the first activity set and the business sub-domain, a value stream is generated for each business sub-domain to obtain a process model.

[0083] Through the method for generating a process model of the embodiment of the present invention, starting from the actual running system, relevant information (the scope of responsibilities of the business department and the business scope of the application) is extracted from the enterprise organizational architecture system and the IT architecture management system, and then business sub-fields are formed based on the correlation between the scope of responsibilities and the business scope. Activities are generated through the applications involved in the actual execution of the target business, and then the value stream of each business sub-field is inferred. At this time, there is a clear association between the business field, the value stream and the activity. For example, a business field may include a business sub-field, and the business sub-field has a value stream, which is composed of corresponding activities. Thus, a basic process model can be constructed. The embodiment of the present invention does not require a lot of manpower to achieve the goal of process modeling, and the model generation speed is fast and the accuracy is high.

[0084] Figure 1 The application scenario diagram schematically shows the method, device, electronic device, storage medium and program product for generating a process model according to an embodiment of the present disclosure.

[0085] like Figure 1 As shown, the application scenario 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for a communication link between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0086] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

[0087] The terminal devices 101 , 102 , and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0088] The server 105 may be a server that provides various services, such as a background management server (only an example) that provides support for websites browsed by users using the terminal devices 101, 102, and 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0089] It should be noted that the method for generating the process model provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the device for generating the process model provided in the embodiment of the present disclosure can generally be set in the server 105. The method for generating the process model provided in the embodiment of the present disclosure can also be executed by a server or a server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Accordingly, the device for generating the process model provided in the embodiment of the present disclosure can also be set in a server or a server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105.

[0090] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0091] In the embodiments of the present disclosure, the process model may include multiple levels, among which the business domain is the first level of the process model, which reflects the overall value creation process of the enterprise and is a manifestation of the bank's service capabilities, and is divided into two categories: product domain and management domain. The value stream is the second level of the process model, which is a relatively high-level description of how the business domain creates value, which facilitates a quick understanding of the operation process of the business domain. The activity is the third level of the process model, which is triggered by an event and is an interaction process with stakeholders to meet stakeholder needs or specific business purposes, describing an end-to-end complete business process. The task is the fourth level of the process model, which is the main component unit of the third-level activity. It is a set of steps performed by a role within a certain period of time with a clear business purpose.

[0092] In the embodiments of the present disclosure, taking banking business as an example, the business areas include but are not limited to: personal deposits, personal accounts, credit cards, personal loans, etc. The value stream includes but is not limited to: business planning, business preparation, customer service, etc. Activities include but are not limited to: formulating management systems, issuing credit cards, withdrawing credit card funds, repaying credit card debts, etc. Tasks include but are not limited to: identifying individual customers, monitoring real-time fraud risks, accepting credit card fund withdrawal applications, settling foreign exchange, etc.

[0093] The embodiments of the present disclosure provide a method for automatically generating a process model. The embodiments of the present disclosure extract relevant information from an enterprise organizational architecture system and an IT architecture management system, and then form business domains, value streams, activities, etc. through screening and combination, and then associate the business domains, value streams, activities, etc. together to form a process model.

[0094] The following will be based on Figure 1 The scene described by Figure 2The method for generating the process model of the disclosed embodiment is described in detail.

[0095] Figure 2 The flowchart of the method for generating a process model according to an embodiment of the present disclosure is schematically shown.

[0096] like Figure 2 As shown, the method for generating the process model of this embodiment includes steps S210 to S250. It should be noted that although Figure 2 The steps in the figure are shown in sequence as indicated by the arrows, but the steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of the steps, and they can be executed in other orders. Moreover, at least some of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0097] In step S210, the business domain of at least one business department, the scope of responsibility of each business department, and the business scope of at least one application are obtained.

[0098] In an embodiment of the present disclosure, the business domain and the scope of responsibilities of a business department may be obtained from an enterprise organizational structure system, and the business scope of an application and the business departments involved in each application may be obtained from an IT management structure.

[0099] In step S220, for each application, a business sub-domain is generated according to the correlation between the business scope of the application and the scope of responsibility of each business department, wherein each business sub-domain has a corresponding relationship with the application, and when the application is related to the scope of responsibility of multiple business departments, a business sub-domain is generated for each business department. When the application is only related to the scope of responsibility of one business department, a business sub-domain is generated. At this time, the business sub-domain and the business domain are associated together through the business department, and the subordinate relationship between the business sub-domain and the business domain can be recorded.

[0100] In the embodiments of the present disclosure, one or more business sub-fields are generated for each application, and the number of generated business sub-fields depends on the business department involved in the application. For example, for application B1, it is used by business department A1 and business department A2 at the same time, so two business sub-fields can be generated for each. Among them, business sub-field C1 can be generated according to the correlation between the business scope of application B1 and the scope of responsibilities of business department A1 (for example, overlapping parts), and business sub-field C2 can be generated according to the correlation between the business scope of application B1 and the scope of responsibilities of business department A2 (for example, overlapping parts). After the business sub-fields are generated, the business sub-fields can be named with the name of the application, and similar business sub-fields can be merged in combination with the business department to which the application belongs.

[0101] In step S230, an IT service call link of the target business is obtained, where the IT service call link includes: applications involved in the execution of the target business, and a processing flow involving each application.

[0102] In an embodiment of the present disclosure, the application involved in the target business when executing a business may refer to the application to which the IT service used by the target business when executing belongs. For example, when the target business (such as a transfer business) is executed, it first executes a function E1 (such as withdrawing money) through application B1, and then executes a function E2 (such as transferring money) through application B2. Then, when the target business is executed, the applications involved include application B1 and application B2.

[0103] In an embodiment of the present disclosure, the IT service used by the target business during execution can be obtained through an IT service call link. The IT service call link includes multiple IT services connected in series in an execution order. The multiple IT services include the IT service used by the target business during execution. Each IT service belongs to an application. The IT service call link is segmented based on the application as a dimension (for example, the segmentation condition is that two adjacent IT services belong to different applications). The IT service call link can be cut into N segments, each of which includes an application and the processing flow of the application.

[0104] In step S240, an activity is generated for each processing flow to obtain a first activity set. In the first activity set, each activity has an association relationship with a business sub-domain corresponding to an application involved in generating the activity.

[0105] In step S230, the processing flow is intercepted with cross-application events as the dividing point. Each processing flow involves and only involves one application. In step S220, a business sub-field is generated for each application. Based on this correspondence, a corresponding business sub-field can be found for each activity, and then the activity is associated with the corresponding business sub-field.

[0106] In step S250, a value stream is generated for each business sub-domain according to the association relationship between each activity in the first activity set and the business sub-domain, so as to obtain a process model.

[0107] In the embodiments of the present disclosure, for each business sub-domain, activities associated with it can be found from the first activity set, and then, according to the business logic relationship between the activities, these activities are spliced ​​to form a value stream of the business sub-domain.

[0108] Through the method for generating a process model of the embodiment of the present invention, starting from the actual running system, relevant information (the scope of responsibilities of the business department and the business scope of the application) is extracted from the enterprise organizational architecture system and the IT architecture management system, and then business sub-fields are formed based on the correlation between the scope of responsibilities and the business scope. Activities are generated through the applications involved in the actual execution of the target business, and then the value stream of each business sub-field is inferred. At this time, there is a clear association between the business field, the value stream and the activity. For example, a business field may include a business sub-field, and the business sub-field has a value stream, which is composed of corresponding activities. Thus, a basic process model can be constructed. The embodiment of the present invention does not require a lot of manpower to achieve the goal of process modeling, and the model generation speed is fast and the accuracy is high.

[0109] Combine the following Figures 2 to 10 The method for generating the process model of the embodiment of the present disclosure is further described.

[0110] Figure 3 The flowchart of generating a value stream according to an embodiment of the present disclosure is schematically shown.

[0111] Reference Figure 3 , in some specific embodiments, step S250 includes step S251.

[0112] In step S251, for the xth business sub-domain, a value stream is generated for the xth business sub-domain according to the logical relationship between the activities in the first activity set that are associated with the xth business sub-domain, where x is a positive integer.

[0113] In the embodiment of the present disclosure, each activity has an association relationship with at least one business sub-field, and therefore, one or more activities having an association relationship with the xth business sub-field may be acquired from the first activity set.

[0114] Furthermore, a logical relationship analysis is performed on the activities associated with the same business sub-domain. The logical relationship may include the business logic between these activities, such as the order of execution and the prerequisites for execution. Two activities that have these business logical associations can be said to have a logical relationship.

[0115] For example, each activity further includes tasks. The logical relationship between two activities can be confirmed based on the logical relationship between the tasks in the two activities. For example, task F1 needs to be completed after task F2. Task F1 and task F2 belong to two activities. Then, it can be considered that there is a logical relationship between the two activities. The confirmation of the task can be determined based on the IT service used by the target business when executing. The details will be explained in detail below, so it will not be repeated here.

[0116] In the embodiment of the present disclosure, activities with business logic relationships are spliced ​​and stored in the corresponding value stream according to the business logic, and the value stream may include the business logic sequence number. Activities without logical relationships are not put into the value stream for the time being, and can wait for confirmation by staff in the subsequent process.

[0117] After generating the value stream, record the relationship between the activities and the value stream, as well as the relationship between the value stream and the business sub-domain. In this way, the value stream of each business sub-domain can be inferred based on the activities in the first activity set. When constructing the value stream, the logical relationship between the activities is determined based on the actual processing flow of the target business, and the value stream is generated quickly and accurately.

[0118] Figure 4 One of the flow charts for merging business sub-fields according to an embodiment of the present disclosure is schematically shown.

[0119] Reference Figure 4 In some specific embodiments, step S250 also includes step S252 and step S253.

[0120] In step S252, in the same business domain, business sub-domains with similar value streams are merged.

[0121] In step S253, when there is no business sub-domain with similar value flow under the same business domain, the business sub-domain under the business domain is upgraded to a business domain. Otherwise, the above merging operation is continued.

[0122] In the embodiments of the present disclosure, each value stream is configured with a corresponding purpose information, and the purpose information includes: a goal that is expected to be achieved through multiple activities on the value stream. Optionally, the purpose information can be processed into features that can be semantically analyzed, and then the consistency of the goals between multiple value streams can be compared and analyzed using semantic analysis technology, and then the similarity of the value streams of each business sub-field under the same business field can be determined. For example, the purpose information can be processed into vector features that can express the actual goal, and then these vector features between multiple value streams can be compared through semantic analysis technologies such as work2vec to determine the similarity of each value stream.

[0123] Through semantic analysis technology, the logical connection between different value streams can be visualized as the similarity of vector features, and the consistency of goals between different value streams can be quickly analyzed. Then, the business sub-domains corresponding to value streams with consistent (or similar) goals are merged to complete the integration of business sub-domains. The integrated business sub-domains will be upgraded to business domains. At this time, each business domain has only one value stream, and the value streams between different business sub-domains are different, thus completing the construction of the relationship between business domains and value streams in the process model.

[0124] In an embodiment of the present disclosure, if the value streams of N business sub-fields are similar, the N business sub-fields are merged into one. Optionally, semantic analysis technology can be used to filter out the most representative name from these business sub-fields as the name of the merged business sub-field. The most representative name can refer to the name that most accurately reflects the business content of the business sub-field. The screening rules can be determined according to actual needs, and the embodiment of the present disclosure does not limit this.

[0125] Optionally, after the business sub-domains are merged, the ownership relationship between the business sub-domains and the business domain is updated, and the relationship between the merged business sub-domains and the business domain should be cancelled.

[0126] Optionally, the activities of the merged business sub-areas are migrated to similar value streams, thereby updating the belonging relationships between each activity and the business sub-area.

[0127] Optionally, when there are no two business sub-domains with similar value streams under the same business domain, in addition to upgrading the business sub-domain to a business domain, the original business domain is also cancelled, and the relationship between the business domain and the enterprise value chain is updated. The enterprise value chain will be introduced in detail below, so it will not be described here.

[0128] Figure 5 The flowchart of generating a business sub-domain according to an embodiment of the present disclosure is schematically shown.

[0129] Reference Figure 5In some specific embodiments, step S220 includes: step S221 to step S223.

[0130] In step S221, when the business scope of the application is greater than or equal to the responsibility scope of the business department, a business sub-domain is generated, and the name of the business sub-domain includes the name of the application.

[0131] Optionally, semantic recognition technology may be applied to analyze the consistency between the business scope of the application for which the business department is responsible and the business scope of the business department.

[0132] In step S222, when the business scope of the application is smaller than the responsibility scope of the business department, a business sub-domain is generated based on the application, and the name of the business sub-domain includes the name of the application and a name to be verified mark.

[0133] In step S223, in the currently generated business sub-domains, if the applications corresponding to the two business sub-domains belong to the same business department, the two business sub-domains are merged, and the name of the merged business sub-domain includes the name of the application with the largest business scope. If the two business sub-domains belong to different business departments but have similar names, the business sub-domains are marked, and the modeling personnel are asked to confirm whether to integrate the two business sub-domains.

[0134] Through the above method, business sub-fields can be quickly generated. At the same time, the name of each business sub-field can represent the maximum business scope involved, thereby more accurately defining the business boundaries of the business sub-field. Optionally, after integrating two business sub-fields, if the business scopes of the applications corresponding to the two business sub-fields are similar, the names of the two business sub-fields are retained and marked for confirmation by the modeler.

[0135] In the embodiments of the present disclosure, the name, scope of responsibilities, and type of the business department can be obtained from the enterprise organizational structure, and the name of the application, the leading business department, and the business scope can be obtained from the IT architecture management system. Optionally, the application name and business scope can be filled in under the leading business department to form a secondary view, and then the business department involved in each application can be obtained.

[0136] In some specific embodiments, when the business scope of the application is smaller than the responsibility scope of the business department, step S220 also includes step S224.

[0137] In step S224, a business sub-domain is generated based on the uncovered responsibilities of the business department, and the name of the business sub-domain includes a name to be confirmed mark. In the embodiment of the present disclosure, the uncovered responsibilities of the business department may refer to the responsibilities that are not involved in the business scope of the application that the business department is responsible for. For this part, each uncovered responsibility can be listed as a business sub-domain and marked with a to be confirmed mark, waiting for confirmation by the modeler in the subsequent process.

[0138] Figure 6 The second flowchart of merging business sub-fields according to an embodiment of the present disclosure is schematically shown.

[0139] Reference Figure 6 In some specific embodiments, step S220 also includes steps S224 to S227.

[0140] In step S224, the database table that the application is responsible for is obtained.

[0141] In step S225, when the database tables that the two applications are responsible for are consistent, it is determined whether the two applications belong to the same business department.

[0142] In step S226, when the two applications belong to one business department, the two business sub-domains corresponding to the two applications are merged.

[0143] In step S227, when the two applications do not belong to the same business department, the business sub-domains corresponding to the two applications are marked as integration to be confirmed.

[0144] In an embodiment of the present disclosure, the table name of the database table that the application is responsible for can be obtained from the IT architecture management system, wherein the database table that the application is responsible for can refer to the database table that the application can edit, for example, the application can add, gate, modify, etc. operations on the database table. If the table names of the database tables that different applications are responsible for are the same and belong to the same business department, the business sub-domains corresponding to the application are integrated into one. In this way, when generating business sub-domains, the business sub-domains can be integrated, reducing the processing volume of subsequent steps (for example, step S250 will generate a value stream for each business sub-domain).

[0145] Optionally, the name of the integrated business sub-domain may include: the name of the business sub-domain before integration is connected by "+". After the business sub-domains are integrated, the relationship between the business sub-domains and the business domains is updated. At this time, under the same business domain, the business sub-domains of applications responsible for the same database table and belonging to the same business department will be integrated together. Under the same business domain, the business sub-domains of applications responsible for the same database table and not belonging to the same business department will be marked. For example, these two business sub-domains will be marked as integration to be confirmed, so that the modeler will confirm whether to integrate.

[0146] In some specific embodiments, in step S220, natural language processing technology (NPL) can be used to analyze the correlation between the business scope of the application and the scope of responsibilities of each business department, that is, the size relationship between the above-mentioned scope of responsibilities and the business scope, as well as the relationship between the business departments to which each application belongs, so as to obtain faster and more accurate recognition results.

[0147] Figure 7 The flowchart schematically shows the acquisition process flow according to an embodiment of the present disclosure.

[0148] Reference Figure 7 In some specific embodiments, step S230 includes step S231 and step S232.

[0149] In step S231, an IT service call link of the target business is obtained. The IT service call link includes multiple IT services connected in series in an execution order. The multiple IT services include IT services used by the target business during execution. Each IT service belongs to an application.

[0150] In step S232, IT services that are adjacent to each other and belong to the same application in the IT service call link are regarded as a processing flow.

[0151] In an embodiment of the present disclosure, an IT service call link includes multiple IT services connected in series in an execution order, and the multiple IT services include an IT service used by a target business during execution. Each IT service belongs to an application. In this way, the IT service call link is segmented based on the application as a dimension (for example, the segmentation condition is that two adjacent IT services belong to different applications). The IT service call link can be cut into N segments, each of which includes an application and the processing flow of the application.

[0152] In some specific embodiments, step S231 includes S2311 and S2312.

[0153] In step S2311, the first IT service called by the target business when it is initiated is obtained and annotated as a business label. The business label is configured to color each called IT service according to the processing progress of the target business.

[0154] In step S2312, the IT service call link of the target business is obtained according to the staining result.

[0155] In the embodiment of the present disclosure, through the above method, the service tag can be marked at the source of the target service, so that when the service is initiated, the service tag will be colored and recorded with the service processing process for each called IT service until the target service processing is completed. In this way, all IT services used by the target service can be captured, and these IT services are connected in series according to the execution order to form an IT service call link.

[0156] In some specific embodiments, step S240 includes step S241.

[0157] In step S241, for a processing flow, the IT service is converted into an active task, wherein the service name of the IT service is converted into the task name of the task, the service steps of the IT service are converted into the task steps of the task, and the processing logic of the IT service is converted into the business rules of the task steps.

[0158] In the embodiment of the present disclosure, all IT services in the application system are converted into tasks. The specific rules are as follows:

[0159] Convert the service name of the IT service into the task name of the task. For example, according to the IT service specification, you can extract the verb in the IT service name as the "verb" of the task name; obtain the table name of the database table processed by the IT service as the "noun" of the task name. Use "verb" + "noun" to assemble a complete task name. Record the mapping relationship between the task name and the IT service name.

[0160] Convert the processing steps of IT services into the task steps of tasks. For example, obtain verbs from each line of code in IT services, translate them into Chinese, and use them as the "verbs" of the task steps; use the field names of the fields processed by each line of code as the "nouns" of the task steps. Use "verbs" + "nouns" to assemble a complete task step name, and record the relationship between the task steps and the tasks.

[0161] Convert the logic of IT service processing into the business rules of the step, and use the specific processing logic in the code as the business rules of the step. If there is no processing logic in the code and only the reading of the parameter table, use the corresponding content in the corresponding parameter table as the business rules of the step. Record the relationship between business rules and steps.

[0162] Through the above method, the machine language is translated into natural language. The task name and task step name contain verbs and nouns, which can express both the execution logic of the corresponding code and the execution object of the corresponding code, and can clearly express the content of the task and task step.

[0163] Figure 8 The flowchart of merging tasks according to an embodiment of the present disclosure is schematically shown.

[0164] Reference Figure 8 In some specific embodiments, step S240 also includes steps S242 to S244.

[0165] In step S242, the execution subject of the task is obtained.

[0166] In step S243, when the execution subjects of two adjacent tasks are the same, the two adjacent tasks are merged into one task group, and the execution subject is used as a candidate role.

[0167] In step S244, when the execution subjects of two identical task groups are different, the execution subjects of the two task groups are merged.

[0168] In the embodiment of the present disclosure, the IT services used by the target business during execution can be obtained from the IT service call link. Since an activity is created each time an application is involved, the IT services used during this period can be used as tasks under the activity. Optionally, according to the mapping relationship between IT services and tasks in the aforementioned embodiment, the corresponding IT services in the IT service call link can be converted into tasks and grouped under the corresponding activities, and the relationship between tasks and activities, as well as the logical relationship between tasks, can be recorded.

[0169] In the embodiment of the present disclosure, the execution subjects (e.g., operators) of two adjacent tasks can be analyzed according to the logical relationship between the tasks. If the execution subjects of the two adjacent tasks are the same, the two adjacent tasks are grouped into one task group. This process is repeated until the two adjacent tasks are executed by different execution subjects.

[0170] Optionally, the task name of the combined task group includes: the task names of the tasks before the combination, connected by "+", for example, "task name 1 + task name 2 + ...", and marked as pending confirmation, waiting for the final confirmation of the modeling personnel. Optionally, after combining the tasks, the association relationship between the tasks is recorded (as if they belong to a task group).

[0171] Optionally. The execution subject includes the operator. After the task combination is completed, the position of the operator corresponding to the task combination is used as an alternative role. In the IT service call link, if the positions of operators with the same task combination are different, these same task combinations are marked, and all positions are combined into "position 1+position 2+...", waiting for confirmation by the modeler.

[0172] After completing the above steps, record the association between roles and tasks (or task combinations).

[0173] In this way, the real IT service processing flow can be obtained based on the IT service call link, and the tasks under each activity and the steps of each task can be generated, so as to quickly and accurately complete the construction of activities, tasks, task steps and the relationship between each task and role in the process model.

[0174] In some specific embodiments, step S240 also includes step S245.

[0175] In step S245, an activity diagram is drawn for at least one activity according to the execution subjects of the tasks and task groups.

[0176] For example, after completing the relationship between each task and the role, lanes are generated according to the roles, for example, one lane is generated for each role. A starting lane is added before the first lane. After that, the task (task combination) is placed in the corresponding lane (corresponding to the same role). For the first task of each activity diagram, the corresponding IT service call link is retrieved. If there are no other tasks (or IT services) before the first task (or IT service), the customer in the IT service call link is used as the role of the starting lane; if there are other tasks (the task belongs to other activities) before the first task, the application to which the previous task belongs is obtained, and then the name of the business sub-domain corresponding to the application is obtained, and then the name is used as the role of the starting lane. After that, the start icon and the end icon are added to the starting lane, and then the execution order of each task is determined according to the IT service call link, and in the activity diagram, the connection line is drawn according to the execution order, wherein, after the last task, the end icon in the starting lane can be connected to complete the drawing of the activity diagram.

[0177] In this way, the actual processing flow of each IT service in the IT service call link can be combined to draw an activity diagram for each activity, thereby clearly showing the processing of each task and the interaction process between each execution subject.

[0178] Fig. 9 The flowchart for grouping activities into value streams according to an embodiment of the present disclosure is schematically shown.

[0179] Reference Fig. 9 In some specific embodiments, step S250 includes steps S254 to S257.

[0180] In step S254, the database table that each activity is responsible for is obtained.

[0181] In step S255, activities responsible for the same database table are grouped into the same value stream.

[0182] In step S256, based on semantic analysis, target activities are screened out from the same value stream by the names of the activities.

[0183] In step S257, the name of the value stream is generated according to the name of the target activity and the database table that the target activity is responsible for.

[0184] In an embodiment of the present disclosure, the table name of the database table that each task in the activity is responsible for can be obtained, wherein the database table that each task is responsible for can refer to the editing operation performed by the task on the database table, such as adding, blocking and modifying operations. Then, according to the database table that each task is responsible for, determine the database table that each activity is responsible for. Then, group the activities responsible for the same database table into the same value stream. Record the relationship between the activity and the value stream. Optionally, the value stream at this time can be represented by a number, and the number can be determined based on the business logic between the activities in the value stream. Optionally, semantic analysis technology (such as work2vec) can be used to filter out the most representative activity names under the same value stream. The most representative activity name can refer to an action that can achieve the value stream goal, such as "transfer". Then, extract the key verb from the activity name, and then use the verb + the table name of the database table to assemble the value stream name. In this way, the name and number can be quickly generated for the value stream, and the name can reflect the core operation of the value stream.

[0185] Fig.10 The flowchart for establishing association between a business domain and an enterprise value chain according to an embodiment of the present disclosure is schematically shown.

[0186] Reference Fig.10 In some specific embodiments, the generating method further includes: step S310 and step S320.

[0187] In step S310, the enterprise value chain and the department type of the business department are obtained, and the enterprise value chain includes core production nodes and auxiliary production nodes.

[0188] In step S320, according to the type of the business department, the business domain of the business department is associated with at least one of the core production node and the auxiliary production node.

[0189] In an embodiment of the present disclosure, an enterprise value chain canvas can be drawn according to Porter's value chain theory. Optionally, information such as the name of the business department, the main scope of responsibilities, and the type of department can be obtained from the enterprise organizational structure system. The business department whose department type is a profit department (such as a production department, a sales department, etc.) or a profit-generating business department is screened out as a core production node in the enterprise value chain. At the same time, the relevant information of the business department is placed in the core production chain, and the business field of the business department and the enterprise value chain are recorded. The business department type is a cost department (such as a service department, human resources, etc.) or a business department that provides service support for the profit-generating business department is screened out as an auxiliary production node in the enterprise value chain, and the relevant information of the business department is placed in the auxiliary production chain, and the business field of the business department and the value chain are recorded. In the above manner, the construction of the relationship between the enterprise value chain and the business field can be completed.

[0190] At this point, the entire process model includes a complete relationship chain of enterprise value chain-business domain-value stream-activity-task-task steps. At the same time, each activity will also have an activity diagram that records the interaction process of the task execution subjects, thereby completing the automatic generation of the entire process model.

[0191] In some specific embodiments, after the process model is generated, the process model can be queried and displayed as needed.

[0192] For example, you can draw a business domain view of the enterprise according to the relationship between the business domain and the enterprise value chain. For example, you can draw the value stream of each business domain according to the relationship between the value stream and the business domain. For example, you can list the activities under the value stream according to the relationship between the activities and the value stream. For example, you can draw a task operation step diagram from top to bottom according to the relationship between the steps and tasks and their business logic sequence, and display the business rules followed by each step next to the step.

[0193] In the embodiments of the present disclosure, the parts marked as to be confirmed by the modeler in the aforementioned embodiments need to be manually verified by the modeler.

[0194] In some specific embodiments, the modeling personnel process the content to be confirmed in the modeling results completed by the system and update it according to the following situations:

[0195] When updating the name of each asset (business area, value stream, activity, task, business rule), replace the original name with the new one.

[0196] Asset integration (including business areas, value streams, activities, tasks):

[0197] Add new assets of corresponding levels (such as business areas, value streams, activities, tasks), and have the modelers manually enter the new asset names; mark the integrated assets of the same level as "cancelled".

[0198] The next-level assets of the asset are displayed to prompt the modeler to adjust. When integrating business areas, the modeler selects the value stream of the integrated business area and drags it to the new business area to form the value stream of the new business area and record the relationship between the value stream and the business area. When integrating value streams, select the value stream to be integrated, manually enter the name of the new value stream or use one of the value streams, directly move the activities under the integrated value stream into the new value stream, and record the relationship between the activities and the value stream; when integrating activities, directly connect the tasks of the integrated activities in series according to the business processing logic, and record the relationship between the tasks and the activities; when integrating tasks, directly splice the steps of the integrated tasks according to the processing logic, and record the relationship between the steps and the tasks. The modeler adjusts or confirms the assembly results.

[0199] When the assets at a certain level change, the assets at the next level should be adjusted according to the above principles. When integrating activities, adjacent activities can only be integrated according to the logical order of business processing.

[0200] Asset separation (including business areas, value streams, activities)

[0201] Add new assets of corresponding levels (such as business areas, value streams, activities), and have the modelers manually enter the new asset names; mark the split assets of the same level as "cancelled".

[0202] The next-level assets of the split assets are displayed, prompting the modeler to adjust. When splitting a business area, the modeler adds a new business area and enters the name; selects the value stream of the split business area and drags it to the new business area, or adds or modifies the value stream that forms the new business area, and records the relationship between the value stream and the business area. When splitting a value stream, you can choose to add a new value stream after the current value stream, and the modeler enters the name, and then moves the activities under the split value stream into the new value stream, and records the relationship between the activities and the value stream; when splitting an activity, the modeler selects the first and last tasks of the new activity and the names of the activities to which they belong, and the system generates a new activity diagram according to the original processing logic, and records the relationship between the tasks and the activities; when integrating tasks, the steps of the tasks to be integrated are directly spliced ​​together according to the processing logic, and the relationship between the steps and the tasks is recorded. The modeler adjusts or confirms the assembly results. Task splitting is not allowed.

[0203] The value stream of the business area after system verification and splitting must be different from the value streams of all existing business areas; if there are identical value streams, the modeler is prompted to integrate the two business areas.

[0204] Through the above method, the resource investment in process model building can be greatly reduced, and the basic sorting work of digital transformation can be completed more quickly.

[0205] Based on the above-mentioned process model generation method, the present disclosure also provides a process model generation device. Fig.11 The device is described in detail.

[0206] Fig.11 The structural block diagram of the device for generating a process model according to an embodiment of the present disclosure is schematically shown.

[0207] like Fig.11 As shown, the process model generation device 1100 of this embodiment includes a first acquisition module 1110 , a sub-domain generation module 1120 , a second acquisition module 1130 , an activity generation module 1140 and a value stream generation module 1150 .

[0208] The first acquisition module 1110 is used to acquire the business domain of at least one business department, the scope of responsibility of each business department and the business scope of at least one application. In one embodiment, the first acquisition module 1110 can be used to execute the above-described step S210, which will not be described in detail here.

[0209] The sub-domain generation module 1120 is used to generate a business sub-domain for each application according to the correlation between the business scope of the application and the scope of responsibility of each business department, wherein each business sub-domain has a corresponding relationship with the application. When the application is related to the scope of responsibility of multiple business departments, a business sub-domain is generated for each business department. In one embodiment, the sub-domain generation module 1120 can be used to execute step S220 described above, which will not be repeated here.

[0210] The second acquisition module 1130 is used to acquire the applications involved in the execution of the target service and the processing flow involved in each application. In one embodiment, the second acquisition module 1130 can be used to execute the step S230 described above, which will not be repeated here.

[0211] The activity generation module 1140 is used to generate an activity for each processing flow to obtain a first activity set, in which each activity has an association relationship with a business sub-domain corresponding to the application involved in generating the activity. In one embodiment, the activity generation module 1140 can be used to execute step S240 described above, which will not be repeated here.

[0212] The value stream generation module 1150 is used to generate a value stream for each business sub-domain according to the association relationship between each activity in the first activity set and the business sub-domain to obtain a process model. In one embodiment, the value stream generation module 1150 can be used to execute the step S250 described above, which will not be repeated here.

[0213] In the embodiments of the present disclosure, for each business sub-domain, activities with an associated relationship therewith can be found from the first activity set, and then, according to the business logic relationship between the activities, these activities are spliced ​​to form a value stream of the business sub-domain. At this time, there is a clear association between the business domain, the value stream and the activities. For example, a business domain can include a business sub-domain (for example, multiple business sub-domains under a business domain can be integrated), and the business sub-domain has a value stream, which is spliced ​​by corresponding activities, thereby forming a basic process model.

[0214] Through the process model generation device of the embodiment of the present invention, starting from the actual running system, relevant information is extracted from the enterprise organizational structure system and the IT architecture management system, and then business areas, value streams and activities are formed through screening and combination. Then, the business areas, value streams and activities are linked together to form a process model, thereby achieving the goal of completing process modeling without investing a lot of manpower.

[0215] According to an embodiment of the present disclosure, any multiple modules of the first acquisition module 1110, the sub-domain generation module 1120, the second acquisition module 1130, the activity generation module 1140, and the value stream generation module 1150 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first acquisition module 1110, the sub-domain generation module 1120, the second acquisition module 1130, the activity generation module 1140, and the value stream generation module 1150 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, at least one of the first acquisition module 1110 , the sub-domain generation module 1120 , the second acquisition module 1130 , the activity generation module 1140 , and the value stream generation module 1150 may be at least partially implemented as a computer program module, which may perform corresponding functions when executed.

[0216] In some specific embodiments, the generating device is further configured to perform the following steps:

[0217] For the xth business sub-domain, according to the logical relationship between the activities in the first activity set that have the association relationship with the xth business sub-domain, a value stream is generated for the xth business sub-domain;

[0218] Wherein, the x is a positive integer.

[0219] In some specific embodiments, the generating device is further configured to perform the following steps:

[0220] In the same business area, merge the business sub-areas with similar value streams;

[0221] When there is no business sub-field with a similar value stream under the same business field, the business sub-field under the business field is upgraded to the business field.

[0222] In some specific embodiments, the generating device is further configured to perform the following steps:

[0223] For a business unit,

[0224] When the business scope of the application is greater than or equal to the responsibility scope of the business department, a business sub-domain is generated, and the name of the business sub-domain includes the name of the application;

[0225] When the business scope of the application is smaller than the responsibilities of the business department, a business sub-domain is generated based on the application, and the name of the business sub-domain includes the name of the application and a name to be verified mark;

[0226] In the currently generated business sub-fields, if the applications corresponding to two business sub-fields belong to the same business department, the two business sub-fields are merged, and the name of the merged business sub-field includes the name of the application with the largest business scope.

[0227] In some specific embodiments, the generating device is further configured to perform the following steps:

[0228] A business sub-field is generated according to the uncovered responsibilities of the business department, and the name of the business sub-field includes a name to be confirmed mark.

[0229] In some specific embodiments, the generating device is further configured to perform the following steps:

[0230] Obtain the database table that the application is responsible for;

[0231] When the database tables that two applications are responsible for are consistent, determine whether the two applications belong to the same business department;

[0232] When two applications belong to one business department, the two business sub-areas corresponding to the two applications are merged;

[0233] When two applications do not belong to the same business department, the business sub-fields corresponding to the two applications are marked as integration to be confirmed.

[0234] In some specific embodiments, the generating device is further configured to perform the following steps:

[0235] Acquire an IT service call link of a target business, wherein the IT service call link includes multiple IT services connected in series in an execution order, wherein the multiple IT services include an IT service used by the target business during execution, and each of the IT services belongs to an application;

[0236] The IT services that are adjacent to each other and belong to the same application in the IT service call link are regarded as one processing flow.

[0237] In some specific embodiments, the generating device is further configured to perform the following steps:

[0238] The first IT service called by the target business when it is initiated is obtained and annotated as a business label, wherein the business label is configured to: color each called IT service along with the processing progress of the target business;

[0239] According to the staining result, the IT service call link of the target business is obtained.

[0240] In some specific embodiments, the generating device is further configured to perform the following steps:

[0241] For a processing flow, the IT service is converted into a task of the activity, wherein the service name of the IT service is converted into a task name of the task, the service steps of the IT service are converted into task steps of the task, and the processing logic of the IT service is converted into business rules of the task steps.

[0242] In some specific embodiments, the generating device is further configured to perform the following steps:

[0243] Obtaining the execution subject of the task;

[0244] When the execution subjects of two adjacent tasks are the same, the two adjacent tasks are merged into one task group, and the execution subjects are used as candidate roles;

[0245] When the execution entities of two identical task groups are different, the execution entities of the two task groups are merged.

[0246] In some specific embodiments, the generating device is further configured to perform the following steps:

[0247] An activity diagram is drawn for at least one activity according to the tasks and the execution entities of the task group.

[0248] In some specific embodiments, the generating device is further configured to perform the following steps:

[0249] Get the database table that each activity is responsible for;

[0250] Group activities responsible for the same database tables into the same value stream;

[0251] Based on semantic analysis, target activities are selected from the same value stream by the names of the activities;

[0252] The name of the value stream is generated according to the name of the target activity and the database table that the target activity is responsible for.

[0253] In some specific embodiments, the generating device is further configured to perform the following steps:

[0254] Acquire an enterprise value chain and a department type of the business department, wherein the enterprise value chain includes a core production node and an auxiliary production node;

[0255] According to the type of the business department, the business domain of the business department is associated with at least one of the core production node and the auxiliary production node.

[0256] In some specific embodiments, the generating device is further configured to perform the following steps:

[0257] The relevance of the business scope of the application to the responsibilities of each business department is analyzed through natural language processing technology.

[0258] Fig.12 A block diagram of an electronic device suitable for implementing a method for generating a process model according to an embodiment of the present disclosure is schematically shown.

[0259] like Fig.12 As shown, the electronic device 1200 according to an embodiment of the present disclosure includes a processor 1201, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1202 or a program loaded from a storage part 1208 into a random access memory (RAM) 1203. The processor 1201 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1201 may also include an onboard memory for caching purposes. The processor 1201 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0260] In RAM 1203, various programs and data required for the operation of electronic device 1200 are stored. Processor 1201, ROM 1202 and RAM 1203 are connected to each other via bus 1204. Processor 1201 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 1202 and / or RAM 1203. It should be noted that the program can also be stored in one or more memories other than ROM 1202 and RAM 1203. Processor 1201 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0261] According to an embodiment of the present disclosure, the electronic device 1200 may further include an input / output (I / O) interface 1205, which is also connected to the bus 1204. The electronic device 1200 may further include one or more of the following components connected to the I / O interface 1205: an input portion 1206 including a keyboard, a mouse, etc.; an output portion 1207 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 1208 including a hard disk, etc.; and a communication portion 1209 including a network interface card such as a LAN card, a modem, etc. The communication portion 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the I / O interface 1205 as needed. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1210 as needed, so that a computer program read therefrom is installed into the storage portion 1208 as needed.

[0262] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiment; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method for generating a process model according to the embodiment of the present disclosure is implemented.

[0263] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus, or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 1202 and / or RAM 1203 described above and / or one or more memories other than ROM 1202 and RAM 1203.

[0264] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the method for generating a process model provided by the embodiment of the present disclosure.

[0265] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 1201. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0266] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 1209, and / or installed from the removable medium 1211. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0267] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1209, and / or installed from the removable medium 1211. When the computer program is executed by the processor 1201, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0268] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0269] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0270] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0271] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A method for generating a process model, characterized in that: include: Obtaining a business domain of at least one business department, a scope of responsibility of each of the business departments, and a business scope of at least one application; For each application, a business sub-domain is generated according to the correlation between the business scope of the application and the scope of responsibility of each business department, wherein each business sub-domain has a corresponding relationship with the application, and when the application is related to the scope of responsibility of multiple business departments, a business sub-domain is generated for each business department; Obtain the applications involved in the execution of the target business and the processing flow involving each application; Generating an activity for each of the processing flows to obtain a first activity set, in which each activity has an association relationship with a business sub-domain corresponding to an application involved in generating the activity; According to the association relationship between each activity in the first activity set and the business sub-domain, a value stream is generated for each business sub-domain to obtain the process model.

2. The generation method according to claim 1, characterized in that: According to the association relationship between each activity in the first activity set and the business sub-domain, a value stream is generated for each business sub-domain to obtain the process model, including: For the xth business sub-domain, according to the logical relationship between the activities in the first activity set that have the association relationship with the xth business sub-domain, a value stream is generated for the xth business sub-domain; Wherein, the x is a positive integer.

3. The generation method according to claim 1, characterized in that: According to the association relationship between each activity in the first activity set and the business sub-domain, a value stream is generated for each business sub-domain to obtain the process model, including: In the same business area, merge the business sub-areas with similar value streams; When there is no business sub-field with a similar value stream under the same business field, the business sub-field under the business field is upgraded to the business field.

4. The generation method according to claim 1, characterized in that: For each application, a business sub-area is generated according to the correlation between the business scope of the application and the scope of responsibility of each business department, including: for a business department, When the business scope of the application is greater than or equal to the responsibility scope of the business department, a business sub-domain is generated, and the name of the business sub-domain includes the name of the application; When the business scope of the application is smaller than the responsibilities of the business department, a business sub-domain is generated based on the application, and the name of the business sub-domain includes the name of the application and a name to be verified mark; In the currently generated business sub-fields, if the applications corresponding to two business sub-fields belong to the same business department, the two business sub-fields are merged, and the name of the merged business sub-field includes the name of the application with the largest business scope.

5. The generation method according to claim 4, characterized in that: When the business scope of the application is smaller than the scope of responsibility of the business department, generating a business sub-domain for each application according to the correlation between the business scope of the application and the scope of responsibility of each business department also includes: A business sub-field is generated according to the uncovered responsibilities of the business department, and the name of the business sub-field includes a name to be confirmed mark.

6. The generation method according to claim 1, characterized in that: For each application, a business sub-area is generated according to the relevance between the business scope of the application and the scope of responsibility of each business department, including: Obtain the database table that the application is responsible for; When the database tables that two applications are responsible for are consistent, determine whether the two applications belong to the same business department; When two applications belong to one business department, the two business sub-areas corresponding to the two applications are merged; When two applications do not belong to the same business department, the business sub-fields corresponding to the two applications are marked as integration to be confirmed.

7. The generation method according to claim 1, characterized in that: Obtain the applications involved in the execution of the target business and the processing flow of each application, including: Acquire an IT service call link of a target business, wherein the IT service call link includes multiple IT services connected in series in an execution order, wherein the multiple IT services include an IT service used by the target business during execution, and each of the IT services belongs to an application; The IT services that are adjacent to each other and belong to the same application in the IT service call link are regarded as one processing flow.

8. The generation method according to claim 7, characterized in that: The step of obtaining the IT service call link of the target business includes: The first IT service called by the target business when it is initiated is obtained and annotated as a business label, wherein the business label is configured to: color each called IT service along with the processing progress of the target business; According to the staining result, the IT service call link of the target business is obtained.

9. The generation method according to claim 7, characterized in that: The step of generating an activity for each processing flow includes: For a processing flow, the IT service is converted into a task of the activity, wherein the service name of the IT service is converted into a task name of the task, the service steps of the IT service are converted into task steps of the task, and the processing logic of the IT service is converted into business rules of the task steps.

10. The generation method according to claim 9, characterized in that: The step of constructing an activity for each of the processing flows to obtain a first activity set further includes: Obtaining the execution subject of the task; When the execution subjects of two adjacent tasks are the same, the two adjacent tasks are merged into one task group, and the execution subjects are used as candidate roles; When the execution entities of two identical task groups are different, the execution entities of the two task groups are merged.

11. The generation method according to claim 10, characterized in that: The step of constructing an activity for each of the processing flows to obtain a first activity set further includes: drawing an activity diagram for at least one activity according to the tasks and the execution subjects of the task groups.

12. The generation method according to claim 1, characterized in that: Generating a value stream for each of the business sub-fields according to the association relationship between each activity in the first activity set and the business sub-field to obtain the process model includes: Get the database table that each activity is responsible for; Group activities responsible for the same database tables into the same value stream; Based on semantic analysis, target activities are selected from the same value stream by the names of the activities; The name of the value stream is generated according to the name of the target activity and the database table that the target activity is responsible for.

13. The generation method according to claim 1, characterized in that: The generating method further comprises: Acquire an enterprise value chain and a department type of the business department, wherein the enterprise value chain includes a core production node and an auxiliary production node; According to the type of the business department, the business domain of the business department is associated with at least one of the core production node and the auxiliary production node.

14. The generation method according to claim 1, characterized in that: According to the correlation between the scope of responsibility and the business scope of each application, a business sub-domain is generated under the business domain, including: The relevance of the business scope of the application to the responsibilities of each business department is analyzed through natural language processing technology.

15. A device for generating a process model, characterized in that: include: A first acquisition module, used to acquire a business domain of at least one business department, a scope of responsibility of each of the business departments, and a business scope of at least one application; A sub-domain generation module, for generating a business sub-domain for each application according to the correlation between the business scope of the application and the scope of responsibility of each business department, wherein each business sub-domain has a corresponding relationship with the application, and when the application is related to the scope of responsibility of multiple business departments, a business sub-domain is generated for each business department; The second acquisition module is used to acquire the applications involved in the execution of the target business and the processing flow involved in each application; An activity generation module, configured to generate an activity for each of the processing flows to obtain a first activity set, wherein each activity in the first activity set is associated with a business sub-domain corresponding to an application involved in generating the activity; The value stream generation module is used to generate a value stream for each of the business sub-fields according to the association relationship between each activity in the first activity set and the business sub-field, so as to obtain the process model.

16. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are enabled to execute the method for generating a process model according to any one of claims 1 to 14.

17. A computer-readable storage medium, characterized in that: Executable instructions are stored thereon, and when the instructions are executed by a processor, the processor executes the method for generating a process model according to any one of claims 1 to 14.