A solution packaging method, device, equipment and readable storage medium

Abstract

The present invention discloses a solution encapsulation method. After receiving a solution encapsulation request, the method uses a structured model language to automatically extract corresponding solution demand information to match the business side capability requirements, and automatically generates a capability solution corresponding to the stakeholder instance according to the capability requirements. The capability solution can accurately describe the business capability requirements, meet the user's demand information, and solve practical problems. The solution can shorten the development cycle of business requirements through low-code programming, and at the same time improve the accuracy of business solutions. The present invention also discloses a solution encapsulation device, equipment and readable storage medium, which have corresponding technical effects.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a solution packaging method, device, equipment and readable storage medium. Background Art

[0002] Currently, the service industry is undergoing profound and rapid changes. Customer behavior and usage habits have undergone tremendous changes. Customers go to outlets less and less to handle business, and mobile APPs have become the mainstream. Therefore, customer flow and customer interaction are gradually transforming to the mobile Internet ecosystem. Customers increasingly expect excellent customer experience, convenient business processing procedures, and fast and efficient responses.

[0003] Currently, when IT departments develop software to meet customer needs for specific businesses, the instability of business solutions directly affects the progress of IT development and also brings system risks.

[0004] In summary, how to solve the defects of the existing IT development progress directly affected by the instability of business solutions is a technical problem that technical personnel in this field urgently need to solve. Summary of the invention

[0005] The purpose of the present invention is to provide a solution encapsulation method, device, equipment and readable storage medium to solve the problem that the instability of existing business solutions directly affects the progress of IT development.

[0006] In order to solve the above technical problems, the present invention provides the following technical solutions:

[0007] A solution packaging method, comprising:

[0008] After receiving the solution packaging request, obtain value claims and stakeholder information; wherein the stakeholder information includes: stakeholders and information on relationships between stakeholders;

[0009] Creating a stakeholder instance according to the stakeholder information;

[0010] Match the capability requirements corresponding to the value demands;

[0011] Generating a capability solution corresponding to the stakeholder instance according to the capability requirement;

[0012] Output the capability solution.

[0013] Optionally, the outputting the capability solution includes:

[0014] Determine the dimensions of the capabilities solution presented;

[0015] If the display dimension is process display, identifying the elements included in the capability solution, determining the association relationship between the elements and the role responsibilities, generating a process model, and outputting the process model;

[0016] If the display dimension is entity display, determine the resource information of the business resources called in the capability solution, match the resource information to the process model, generate an entity model, and output the entity model;

[0017] If the display dimension is product display, extract product value information of the capability solution, match the product value information to the process model, generate a product model, and output the product model;

[0018] If the display dimension is decision display, the logic rules called in the capability solution are extracted, and the logic rules are matched to the process model to generate a decision model, and the decision model is output.

[0019] Optionally, the solution packaging method further includes:

[0020] After receiving the simulation execution request, determining the elements required for the execution of the capability solution as the elements to be simulated;

[0021] Obtaining input data corresponding to the element to be simulated;

[0022] Inputting the input data into the capability solution according to the workflow execution order, and obtaining the generated simulation data;

[0023] The simulation data is output according to the workflow execution order.

[0024] Optionally, after outputting the capability solution, the method further includes:

[0025] Obtain implementation requirements and test cases for the capability solution;

[0026] The value proposition, the implementation requirements and the test cases are presented on the capability solution.

[0027] Optionally, after outputting the capability solution, the method further includes:

[0028] Extracting elements to be evaluated in the capability solution according to maturity indicator evaluation rules;

[0029] Calling maturity index evaluation rules to perform maturity evaluation on the element to be evaluated and generate a maturity index;

[0030] The maturity indicator is output.

[0031] Optionally, before outputting the capability solution, the method further includes:

[0032] Encapsulating the capability solution, the elements in the capability solution, and the data contained in the elements according to the resource type based on business relevance to obtain an encapsulation package;

[0033] Accordingly, the outputting of the capability solution specifically includes: outputting the encapsulation package.

[0034] Optionally, before outputting the package, the method further includes:

[0035] The packaging package is disclosed in a manner and / or authorized in a manner according to the privacy level.

[0036] A solution packaging device, comprising:

[0037] An information acquisition unit, configured to acquire value claims and stakeholder information after receiving a solution packaging request; wherein the stakeholder information includes: stakeholders and information on relationships between stakeholders;

[0038] An instance creation unit, used to create a stakeholder instance according to the stakeholder information;

[0039] A demand matching unit, used to match the capability requirements corresponding to the value demands;

[0040] A solution generating unit, configured to generate a capability solution corresponding to the stakeholder instance according to the capability requirement;

[0041] A solution output unit is used to output the capability solution.

[0042] A computer device comprising:

[0043] Memory for storing computer programs;

[0044] A processor is used to implement the steps of the above solution encapsulation method when executing the computer program.

[0045] A readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the solution encapsulation method are implemented.

[0046] The method provided in the embodiment of the present invention, after receiving a solution encapsulation request, automatically extracts the corresponding solution demand information using a structured model language to match the business side capability requirements, and automatically generates a capability solution corresponding to the stakeholder instance based on the capability requirements. The capability solution can accurately describe the business capability requirements, meet the user's demand information, and solve practical problems. The solution can shorten the development cycle of business requirements through low-code programming, and at the same time improve the accuracy of business solutions.

[0047] Correspondingly, the embodiments of the present invention further provide a solution packaging device, an apparatus and a readable storage medium corresponding to the above-mentioned solution packaging method, which have the above-mentioned technical effects and will not be described in detail here. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0049] Figure 1 It is an implementation flow chart of a solution packaging method in an embodiment of the present invention;

[0050] Figure 2 This is a schematic diagram of a capability capsule in an embodiment of the present invention;

[0051] Figure 3 A schematic diagram of a packaging process in an embodiment of the present invention;

[0052] Figure 4 A schematic diagram of an overall packaging and injection process in an embodiment of the present invention;

[0053] Figure 5 This is a schematic diagram of the structure of a solution packaging device in an embodiment of the present invention;

[0054] Figure 6 The figure is a schematic diagram of the structure of a computer device in an embodiment of the present invention. DETAILED DESCRIPTION

[0055] The core of the present invention is to provide a solution packaging method to solve the problem that the instability of the existing business solution directly affects the progress of IT development.

[0056] In order to enable those skilled in the art to better understand the scheme of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0057] Please refer to Figure 1 , Figure 1 This is a flow chart of a solution packaging method in an embodiment of the present invention, the method comprising the following steps:

[0058] S101. After receiving the solution packaging request, obtain value claims and stakeholder information;

[0059] When a user requests automatic generation of a business plan, the user is first guided to input value demands and stakeholder information to create a stakeholder instance.

[0060] The value demand refers to the specific value demand for which a business plan needs to be generated, which is also equivalent to the "business goal"; the stakeholder information refers to the user-side subject information required to meet the value demand, and the specific information type contained therein is not limited. In this embodiment, the information including: stakeholders and relationship information between stakeholders is taken as an example. Other information configurations can refer to the introduction of this embodiment and will not be repeated here.

[0061] The stakeholder module triggers the feedback system of the background model. The background module predicts and identifies the associated registration module, pushes the front end and informs the user of the actions that can be taken, such as entering value or value drivers. After the user enters, the device can register, store and display based on the model structure, register the stakeholder unit in the model, and register the created instance.

[0062] For example, the business solution generated by the user request is the customer collection capability, and the stakeholders involved may include collectors, customers, etc. Among them, the stakeholders are registered in the ontology model of the execution subject of this method (solution encapsulation device, also known as "capability capsule"), and defined in the entity model of the business model (generated business solution model), and the collectors, customers, etc. are also included in the digital product of the business solution as data; value claims, for example, customers as stakeholders hope to avoid additional charges due to arrears, and collectors hope to reduce the energy and cost of collection.

[0063] S102, creating a stakeholder instance according to the stakeholder information;

[0064] Based on the acquired stakeholder information, a corresponding stakeholder instance is created. A stakeholder instance refers to a copy of the stored stakeholder information so that the stakeholder information can be subsequently called to generate a business plan. The specific process of creating a stakeholder instance can refer to the relevant implementation method, which will not be repeated here.

[0065] S103, matching the capability requirements corresponding to the value demands;

[0066] According to the determined value demands, the capability requirements corresponding to the value demands are obtained and stored. The value demands are the goals on the user side, while the capability requirements are the implementation goals on the technical side. By matching the capability requirements corresponding to the value demands, the goal conversion from application to technology is achieved, and the technical goals to be achieved are determined, so that the corresponding business implementation can be carried out based on this. The capability requirements can be: target capabilities, current pain points, etc. Specifically, when the value demand is to reduce the collection cost, the required capabilities (i.e., capability requirements) may include: timely identification of the collection object, analysis of its repayment ability, recommendation of repayment plan, timely reminder to customers, etc.; for example, if the value demand is to reduce the collection cost, the current pain points (i.e., capability requirements) may include: the collector cannot avoid causing unnecessary interference to the customer, etc.

[0067] It should be noted that in this embodiment, the execution order of step S102 and step S103 is not limited. Figure 1 In the example, step S102 is executed first and then step S103 is executed, but both steps can also be executed at the same time.

[0068] S104. Generate a capability solution corresponding to the stakeholder instance according to the capability requirement;

[0069] According to the determined capability requirements (such as current pain points and required capabilities), based on the ontological relationship (i.e. the relationship information between stakeholders), the corresponding capability solutions are obtained from the business model.

[0070] Specifically, based on the context contained in the capability requirements, extract the elements contained in the context and locate the elements in the ontology model; based on the entry and scenario information contained in the context, determine the association scope of the elements corresponding to the business model and model data; based on the association scope, determine the business model and corresponding model content associated with the context as the capability solution.

[0071] S105, output capacity solution.

[0072] Based on the business model scope involved, build and demonstrate the business processes, input and output entities, or business decision logic in the business solution.

[0073] Push the capability solution and display the view framework. Based on the acquired capability solution and display requirements, the view framework can be displayed. The view framework can be but not limited to paging, list, matrix, tree structure, and various predefined special view formats, etc.; data can also be obtained, based on the model, data identifier, and usage scenario characteristics, the corresponding data type is located, and the relevant data is obtained from the database or file storage, and the associated domain values ​​and other associated restrictions are obtained, and the data is pushed and the content is displayed in the view framework. Based on the required display method and characteristics, according to the model type, data type, data content and display restricted view framework, the content is displayed. The content can be but not limited to lists, texts, multimedia content, etc.

[0074] The above content introduces a solution extraction process. Accordingly, in order to ensure the comprehensiveness of the solution, the solution needs to be registered. The implementation method of registration is not limited in this embodiment. It can be set for the above extraction process. For example, it can be specifically divided into the following steps: (1) Registration: Submit the context and identify the allowed navigation operations based on the context. According to the capsule element type, the created entry and the scene when creating or updating, first locate the element in the ontology model, and then identify the relationship scope involved in the element in the model in this context based on the scene, starting point, view and other factors, and return the allowed creation or update navigation operation scope; (2) Parsing: When creation and updating occur, the content may be a model or data. The updated content will be passed to the background module; (3) Parsing: After the background module accepts and judges, if it is a model type, it is stored and integrated into the business model; (4) Parsing: After the background module accepts and judges, if it is a specific instance of the model, that is, the data type, it needs to be stored as data first; (5) Storage: Attach the saved data to the business model; (6) Storage: Data and model are registered in the ontology model. Of course, in this embodiment, only the above-mentioned extraction and registration process is introduced as an example, and other implementation methods can refer to the introduction of this embodiment, which will not be repeated here.

[0075] The output display object and display method of the specific capability solution are not limited in this embodiment and can be set accordingly according to the display requirements of the actual solution, which will not be described in detail here.

[0076] Based on the above introduction, the technical solution provided by the embodiment of the present invention, after receiving the solution packaging request, uses the structured model language to automatically extract the corresponding solution demand information to match the business side capability requirements, and automatically generates a capability solution corresponding to the stakeholder instance according to the capability requirements. The capability solution can accurately describe the business capability requirements, meet the user's demand information, and solve practical problems. This solution can shorten the development cycle of business requirements through low-code programming, and at the same time improve the accuracy of business solutions.

[0077] It should be noted that, based on the above embodiments, the embodiments of the present invention also provide corresponding improved solutions. In the preferred / improved embodiments, the same steps or corresponding steps as those in the above embodiments can be referenced to each other, and the corresponding beneficial effects can also be referenced to each other, which will not be described one by one in the preferred / improved embodiments of this article.

[0078] The display entry dimensions of the structure in the solution can be diverse, such as capability-process-entity, or capability-product-product component-acceptance criteria, or capability enabling factor-entity-process, etc. In the above embodiment, there is no limitation on the output display object and display method of the specific capability solution. In order to improve the flexibility of the display method, several display dimensions can be configured for user customization. In this embodiment, the output method of the solution is mainly introduced from the four display dimensions of process, entity, product and decision.

[0079] Specifically, before presenting a solution, first identify the display dimension path. The user selects the entry dimension of a certain capability solution, such as starting from the process. After receiving it in the background, calculate the relationship coefficient based on the registered relationship in the ontology model. The combination relationship coefficient is the highest, the inheritance relationship coefficient is the second, and the association relationship coefficient is the lowest; the direct relationship is the highest, and the indirect relationship is the second. Get all possible paths from this dimension to the leaf node of the model. Identify the possible solution clue paths under this dimension. Select the optimal path and push it to the front-end display, and guide the user to define the content.

[0080] (1) If the display dimension is process display, identify the elements included in the capability solution, determine the relationship between the elements and the role responsibilities, generate a process model, and output the process model.

[0081] From solution association to process, business solutions are mainly reflected in the process, which can be activities that reflect the customer value network or tasks that reflect role responsibilities. If it is an activity, the workflow, roles, tasks, etc. can be clarified.

[0082] If the user chooses to trigger from the process (such as saving money), the target feature corresponding to the workflow node (such as an activity) will be extracted in the background. All direct relationships will be predicted or analyzed based on the relationship samples in the model. The next element of the possible solution for the corresponding target will be predicted or analyzed, and the possible model feature element feedback will be pushed to the front end. The relevant feedback data and feature information will be stored and displayed in a modular architecture.

[0083] Digital products will display the structure, sequence, and role responsibilities between the elements in the business model based on the elements included in the capability solution. If the product includes data, it can also be displayed in detail.

[0084] (2) If the display dimension is entity display, determine the resource information of the business resources called in the capability solution, match the resource information to the process model, generate an entity model, and output the entity model.

[0085] Based on the capability solution, the required business resource structure, identification, attributes and association relationships are displayed, and connected with the corresponding links in the process model to display the entity scope and input and output dependencies involved in the process;

[0086] From the process association to the entity, the process needs input and output, supports the definition of business resources in the form of business objects or entities, and is structured into attributes, domains, and instances. In order to support multi-dimensional structuring, it is also possible to go directly from capability enablement factors or solutions to entities.

[0087] (3) If the display dimension is product display, extract the product value information of the capability solution, match the product value information to the process model, generate a product model, and output the product model.

[0088] Based on the capability solution, the products and value propositions involved in the solution are demonstrated, and connected with the corresponding links in the process model to explain the value composition of process delivery. The process is the link of the delivered product as a product production line.

[0089] From the process to the product, the product is the main factor affecting the process change. In the process plan, the definition of the steps is mainly related to the product conditions. In order to support multi-dimensional structuring, the basic products that embody the value proposition can also be directly associated with the market from the value point of view.

[0090] (4) If the display dimension is decision display, extract the logical rules called in the capability solution, match the logical rules to the process model, generate a decision model, and output the decision model.

[0091] Based on the capability solution, the business rules, calculation rules, judgment rules, assignment rules and other logical rules involved in the solution are displayed, and the relationship with entities and products is guided;

[0092] From process association to decision-making, business decision logic is an important embodiment of the solution in process execution. The present invention can support the structured display of each decision logic and establish associations with products and entities. In order to support multi-dimensional structuring, it can also support associations from value drive to decision-making.

[0093] It should be noted that in this embodiment, only the display output method of the above solution is introduced as an example, and other methods can refer to the introduction of this embodiment and will not be repeated here.

[0094] Optionally, after executing the output capability solution in step S105, in order to further improve the user experience, the following steps may be further performed:

[0095] S106. Obtain implementation requirements and test cases for capability solutions;

[0096] S107. Demonstrate value proposition, implementation requirements and test cases for capability solutions.

[0097] List the business needs, implementation requirements and test cases involved in the solution. The backend device analyzes all data in the solution, traverses all elements in the solution, extracts the target feature identifier, matches the model identifier and data identifier with the corresponding information in the database, and obtains the data. The data, feature information and related elements corresponding to the solution elements are fed back to the system or target terminal, and the relevant feedback data and feature information are structured and displayed according to the module architecture, so that users can fully understand the detailed information of the solution and improve the user experience.

[0098] Optionally, after executing the output capability solution in step S105, in order to further ensure the reliability of the output solution, the following steps may be further performed:

[0099] S107. Extract the elements to be evaluated in the capability solution according to the maturity indicator evaluation rules;

[0100] S108, calling the maturity index evaluation rule to perform maturity evaluation on the element to be evaluated, and generating a maturity index;

[0101] S109. Output maturity index.

[0102] Obtain all capability items in the capability solution, push them to the front end, display them in a visual way, and prompt the user to define the assessment criteria and set the starting and ending points. The back end obtains the elements in the capability solution, displays the workflow list and lists the solutions according to the identification of the elements in the capability solution, obtains the elements required for solution evaluation, displays and guides users to identify strong and weak relationships and weights. The back end calculates the priority of the solution based on the association relationship, and pushes feedback to the front end system. Perform visual display.

[0103] In this embodiment, by defining the maturity indicators of the capabilities in the solution, the business solution is defined from the perspective of external stakeholders, all elements required for the business solution are collected, and extended customization and maturity assessment are supported, which can assist users in analyzing the maturity of the obtained capability solutions.

[0104] Optionally, based on the above embodiment, the following steps may be further performed:

[0105] S110, after receiving the simulation execution request, determining the elements required for the capability solution execution as the elements to be simulated;

[0106] S111, obtaining input data corresponding to the element to be simulated;

[0107] S112, inputting the input data into the capability solution according to the workflow execution order, and obtaining the generated simulation data;

[0108] S113. Output simulation data according to the workflow execution order.

[0109] The front end selects solution elements and applies for simulation execution. The back end obtains models and data, and obtains elements required for simulation based on the model structure, identification, attributes, and structural relationships of the model, such as workflows. Combined with the input and output of the workflow, and the branch organization interface, a visualization interface is built based on the entity definition of input and output, and pushed to the front end. In the order of the workflow, it is displayed in sequence and supports the creation of sample data, which is stored according to the identification.

[0110] The method proposed in this embodiment performs simulation execution on the generated capability solutions (such as process models, entity models, product models, and decision models), supports the structuring of business knowledge, does not require additional development, and users can simulate the execution of business solutions to verify whether the expected capabilities and the effectiveness of the capability solutions can be provided, thereby improving the reliability of the output capability solutions.

[0111] To further facilitate users to call capability solutions, after generating solutions and before outputting them, you can further perform the following steps:

[0112] S114, encapsulating the capability solution, the elements in the capability solution, and the data contained in the elements according to the business relevance according to the resource type to obtain an encapsulation package;

[0113] Accordingly, step S105 outputs the capability solution, specifically: outputs the encapsulation package.

[0114] The packaging output unit is used to classify and package the generated capability solutions (such as process models, entity models, product models, decision models), the elements contained in the capability solutions, and the data contained in each element into digital products. The generated package can be called a capability capsule. Figure 2 As shown, the packaging process is as follows Figure 3 shown.

[0115] The elements of the capsule can determine the scope in the ontology model according to the selected value and capability scope, and encapsulate the required ontology, business model, data and other solution resources together in a packaged manner. Encryption can be used during encapsulation, and it is ensured that the decrypted capsule solution still carries the hierarchical structure of the ontology model, business model, and data model, and that the business solution itself is still a complete structured solution to deliver the promised capabilities.

[0116] The encapsulation result of the capability solution is a capsule package. In order to interpret the business solution, the capsule can allow the encapsulation of components in various formats, including business models, views, XML, PPT, etc., which are encrypted and packaged in formats such as ZIP and JASON. The encapsulated package can be large or small, depending on the encapsulation capability.

[0117] Furthermore, before outputting the package, the public and / or authorized modes of the package can be further set according to the privacy level. The provider can choose to disclose some content in a limited manner, such as introduction, maturity level, etc. When packaging, the provider can choose public authorization, specified authorization or private authorization mode. After purchasing, the consumer can inject it into his own business model and customize the business plan based on his own situation.

[0118] To deepen the understanding of the capability solution encapsulation process, this embodiment introduces a process of encapsulation and injection, such as Figure 4 shown.

[0119] On the left, the supplier can select a capability to be packaged according to the requirements and start packaging. Since the capability capsule itself is structured, the packaging process of the capability capsule can be fully automated:

[0120] 1. Determine the scope of the ontology model: The input is the ontology model of the capability solution. Based on the subject to be encapsulated, the capability capsule design will traverse the ontology and define the scope. The output is the ontology model of the selected scope.

[0121] 2. Understand the business solution: The input is the business model of the capability solution. Focusing on the scope of the ontology model, understand the business model elements involved in this capability, including products, processes, entities, rules, decisions, etc. The output is the associated business model;

[0122] 3. Define the capsule declaration model: The input is the ontology model and business model. Based on the defined capability scope, ontology model, and business model, gather various resources required for the capability and build an external declaration of the capability solution. This declaration helps understand the purpose, plan, maturity, and quality of the capability. The output is the capsule declaration and capability resources.

[0123] 4. Package solution resources: The input is capability resources. Various capability resources, including ontology models (vocabulary, classification, definition, relationship, etc.), business models (value proposition, customer, market, service, process, entity, rule, etc.) and data (pictures, views, instances, etc.) are packaged according to structural associations. The output is a package (also called a capability capsule package).

[0124] 5. Encrypted capsule: The input is a capsule package, and the contents of the capsule package are encrypted according to the encryption key and password. You can choose the public or specified range authorization mode to achieve exchange, and the output is the encrypted capsule package.

[0125] On the right, consumers can purchase and inject the capability declaration into their own business model and execute it. The process is as follows:

[0126] 1. Decryption capsule: The user needs to enter a password to decrypt the capsule according to the authorization level, and the output is the declaration model of the capsule.

[0127] 2. Understand the declaration model: Based on the declaration of the package, interpret the overview of the package, the values, capabilities and solutions involved, and the output is the declaration model.

[0128] 3. Understand solution resources: According to the declaration model, the resources involved in the solution of the structural capability, understand the hierarchy and structural association, and the output is the resources of the encapsulated package.

[0129] 4. Inject business model: Inject the business model in the resources into the consumer's business model. Based on the consumer's ontology model, resolve conflicts and achieve integration. The output is a business model with new capabilities.

[0130] 5. Inject solution resources: Inject other solution resources in the resources, such as data, forms, pictures, etc., into the consumer's business model. The output is a business model with capability enabling factors and data and other resources.

[0131] At this point, the capability capsule is integrated with the consumer's business model, and users can begin to simulate and verify new business capabilities. The above explains the process of encapsulating business solutions into capability capsules, as well as the use process after acquisition. This can realize online capability exchange in the Internet model.

[0132] It should be noted that, in this embodiment, only the above-mentioned encapsulation and decapsulation process is introduced as an example, and other implementation methods can refer to the introduction of this embodiment, which will not be repeated here.

[0133] The digitally packaged business capability solution provided in this embodiment can realize the commercialization, digital acquisition and exchange of business solutions. By using packaging technology, the solution content can be completely packaged and exchanged online. Users can verify the simulation and inject it into their own models, thereby improving the user experience.

[0134] Corresponding to the above method embodiment, the embodiment of the present invention further provides a solution packaging device. The solution packaging device described below and the solution packaging method described above can be referred to in correspondence with each other.

[0135] See also Figure 5 As shown, the device includes the following modules:

[0136] The information acquisition unit 110 is mainly used to obtain value demands and stakeholder information after receiving a solution packaging request; wherein the stakeholder information includes: stakeholders and information on relationships between stakeholders;

[0137] The instance creation unit 120 is mainly used to create a stakeholder instance according to the stakeholder information;

[0138] The demand matching unit 130 is mainly used to match the capability requirements corresponding to the value demands;

[0139] The solution generation unit 140 is mainly used to generate a capability solution corresponding to the stakeholder instance according to the capability requirement;

[0140] The solution output unit 150 is mainly used to output capability solutions.

[0141] Corresponding to the above method embodiment, the embodiment of the present invention further provides a computer device. The computer device described below and the solution packaging method described above can refer to each other.

[0142] The computer equipment includes:

[0143] Memory for storing computer programs;

[0144] The processor is used to implement the steps of the solution encapsulation method of the above method embodiment when executing a computer program.

[0145] For details, please refer to Figure 6, is a specific structural diagram of a computer device provided in this embodiment. The computer device may have relatively large differences due to different configurations or performances, and may include one or more processors (central processing units, CPU) 322 (for example, one or more processors) and a memory 332, and the memory 332 stores one or more computer applications 342 or data 344. Among them, the memory 332 can be a temporary storage or a permanent storage. The program stored in the memory 332 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations in the data processing device. Furthermore, the central processing unit 322 can be configured to communicate with the memory 332 to execute a series of instruction operations in the memory 332 on the computer device 301.

[0146] The computer device 301 may also include one or more power supplies 326 , one or more wired or wireless network interfaces 350 , one or more input and output interfaces 358 , and / or one or more operating systems 341 .

[0147] The steps in the solution packaging method described above may be implemented by the structure of a computer device.

[0148] Corresponding to the above method embodiment, an embodiment of the present invention further provides a readable storage medium. The readable storage medium described below and the solution packaging method described above can refer to each other.

[0149] A readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the solution encapsulation method of the above method embodiment.

[0150] The readable storage medium may specifically be a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, or other readable storage medium that can store program codes.

[0151] Those skilled in the art may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

Claims

1. A solution packaging method, characterized in that: include: After receiving the solution packaging request, obtain the value claim and stakeholder information; wherein the stakeholder information includes: stakeholders and information on relationships between stakeholders; the stakeholders are registered in the ontology model and defined in the entity model of the business model; Creating a stakeholder instance according to the stakeholder information; Match the capability requirements corresponding to the value demands; Generating a capability solution corresponding to the stakeholder instance according to the capability requirement; Output the capability solution; wherein, according to the context contained in the capability requirement, extract the elements contained in the context, and locate the elements in the ontology model; according to the entry and scenario information contained in the context, determine the association scope of the elements corresponding to the business model and model data; based on the association scope, determine the business model and corresponding model content associated with the context as the capability solution; The output of the capability solution includes: Determine the dimensions of the capabilities solution presented; If the display dimension is process display, identifying the elements included in the capability solution, determining the association relationship between the elements and the role responsibilities, generating a process model, and outputting the process model; If the display dimension is entity display, determine the resource information of the business resources called in the capability solution, match the resource information to the process model, generate an entity model, and output the entity model; If the display dimension is product display, extract product value information of the capability solution, match the product value information to the process model, generate a product model, and output the product model; If the display dimension is decision display, extract the logic rules called in the capability solution, match the logic rules to the process model, generate a decision model, and output the decision model; Before outputting the capability solution, the method further includes: Encapsulating the capability solution, the elements in the capability solution, and the data contained in the elements according to the resource type based on business relevance to obtain an encapsulation package; Accordingly, the outputting of the capability solution specifically includes: outputting the encapsulation package; Also includes: After receiving the simulation execution request, determining the elements required for the execution of the capability solution as the elements to be simulated; Obtaining input data corresponding to the element to be simulated; Inputting the input data into the capability solution according to the workflow execution order, and obtaining the generated simulation data; The simulation data is output according to the workflow execution order.

2. The solution packaging method according to claim 1, characterized in that: After outputting the capability solution, the method further includes: Obtain implementation requirements and test cases for the capability solution; The value proposition, the implementation requirements and the test cases are presented on the capability solution.

3. The solution packaging method according to claim 1, characterized in that: After outputting the capability solution, the method further includes: Extracting elements to be evaluated in the capability solution according to maturity indicator evaluation rules; Calling maturity index evaluation rules to perform maturity evaluation on the element to be evaluated and generate a maturity index; The maturity indicator is output.

4. The solution packaging method according to claim 1, characterized in that: Before outputting the package, the method further includes: The packaging package is disclosed in a manner and / or authorized in a manner according to the privacy level.

5. A solution packaging device, characterized in that: include: An information acquisition unit, configured to acquire value claims and stakeholder information after receiving a solution encapsulation request; wherein the stakeholder information includes: stakeholders and information on associations between stakeholders; the stakeholders are registered in the ontology model and defined in the entity model of the business model; An instance creation unit, used to create a stakeholder instance according to the stakeholder information; A demand matching unit, used to match the capability requirements corresponding to the value demands; A solution generating unit, configured to generate a capability solution corresponding to the stakeholder instance according to the capability requirement; A solution output unit is used to output the capability solution; wherein, according to the context contained in the capability requirement, elements contained in the context are extracted and the elements are located in the ontology model; according to the entry and scenario information contained in the context, the association scope of the elements corresponding to the business model and model data is determined; based on the association scope, the business model and the corresponding model content associated with the context are determined as the capability solution; The output of the capability solution includes: Determine the dimensions of the capabilities solution presented; If the display dimension is process display, identifying the elements included in the capability solution, determining the association relationship between the elements and the role responsibilities, generating a process model, and outputting the process model; If the display dimension is entity display, determine the resource information of the business resources called in the capability solution, match the resource information to the process model, generate an entity model, and output the entity model; If the display dimension is product display, extract product value information of the capability solution, match the product value information to the process model, generate a product model, and output the product model; If the display dimension is decision display, extract the logic rules called in the capability solution, match the logic rules to the process model, generate a decision model, and output the decision model; Before outputting the capability solution, the method further includes: Encapsulating the capability solution, the elements in the capability solution, and the data contained in the elements according to the resource type based on business relevance to obtain an encapsulation package; Accordingly, the outputting of the capability solution specifically includes: outputting the encapsulation package; Also includes: After receiving the simulation execution request, determining the elements required for the execution of the capability solution as the elements to be simulated; Obtaining input data corresponding to the element to be simulated; Inputting the input data into the capability solution according to the workflow execution order, and obtaining the generated simulation data; The simulation data is output according to the workflow execution order.

6. A computer device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the solution encapsulation method according to any one of claims 1 to 4 when executing the computer program.

7. A readable storage medium, characterized in that: The readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the solution encapsulation method according to any one of claims 1 to 4 are implemented.

Images