Model modeling method and system, electronic equipment and storage medium

Abstract

The invention discloses a modeling method and system of a model, electronic equipment and a storage medium, and relates to the technical field of computers. The method comprises the steps that a plurality of models to be modeled of a product are determined, and different models to be modeled are used for representing different modeling stages of the product; structuring the to-be-modeled model to obtain at least one structured model, the structured model being a resource for at least representing a modeling process of the to-be-modeled model; determining an association result among a plurality of structured models corresponding to the plurality of to-be-modeled models, the association result being used for representing a mutually associated logical relationship among the plurality of structured models; and based on the association result, modeling the plurality of structured models to obtain a target model of the product. The technical problem that the modeling effect of the model is poor is solved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a modeling method, system, electronic device and storage medium for a model. Background Art

[0002] At present, modeling design usually includes scenario modeling, process modeling, domain modeling, data modeling, etc. However, the modeling strategy (i.e., modeling methodology) of the model to be modeled in the above modeling design is out of touch with the implementation, and does not pay attention to the connection and consistency between different modeling design stages, resulting in poor modeling effect.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide a modeling method, system, electronic device and storage medium for a model, so as to at least solve the technical problem of poor modeling effect.

[0005] According to one aspect of an embodiment of the present application, a modeling method is provided. The method may include: determining multiple models to be modeled of a product, wherein different models to be modeled are used to represent different modeling stages of the product; performing structured processing on the models to be modeled to obtain at least one structured model, wherein the structured model is a resource for at least representing the modeling process of the model to be modeled; determining the association results between multiple structured models corresponding to the multiple models to be modeled, wherein the association results are used to represent the logical relationship between the multiple structured models; based on the association results, modeling the multiple structured models to obtain the target model of the product.

[0006] According to another aspect of the embodiment of the present application, a modeling method of a model is provided. The method may include: in response to an input instruction acting on an operation interface, displaying multiple models of a product to be modeled on the operation interface, wherein different models to be modeled are used to represent different modeling stages of the product; in response to a processing instruction acting on the operation interface, displaying a target model of the product on the operation interface, wherein the target model is obtained by modeling multiple structured models based on the association results between multiple structured models corresponding to the multiple models to be modeled, the structured model is a resource used to at least represent the modeling process of the model to be modeled, the association results are used to represent the logical relationship between the multiple structured models, and the structured model is obtained by structurally processing the model to be modeled.

[0007] According to another aspect of the embodiment of the present application, a modeling system is provided. The system may include: a client, used to upload multiple models to be modeled of a product, wherein different models to be modeled are used to represent different modeling stages of the product; a server, connected to the client, used to perform structured processing on the models to be modeled to obtain at least one structured model, wherein the structured model is a resource used to at least represent the modeling process of the model to be modeled; determining the association results between multiple structured models corresponding to the multiple models to be modeled, wherein the association results are used to represent the logical relationship between the multiple structured models; based on the association results, modeling the multiple structured models to obtain a target model of the product; and sending the target model to the client.

[0008] According to another aspect of an embodiment of the present application, a computing device is also provided, which may include a memory and a processor: the memory is used to store an executable program; the processor is used to run the program, wherein the modeling method of any one of the above models is executed when the program is run.

[0009] According to another aspect of an embodiment of the present application, an electronic device is also provided. The electronic device may include a memory and a processor: the memory is used to store computer-executable instructions, and the processor is used to execute computer-executable instructions. When the above-mentioned computer-executable instructions are executed by the processor, a modeling method of any one of the above-mentioned models is implemented.

[0010] According to another aspect of an embodiment of the present application, a processor is further provided, and the processor is used to run a program, wherein the modeling method of any one of the above models is executed when the program is running.

[0011] According to another aspect of an embodiment of the present application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute a modeling method of any of the above models.

[0012] According to another aspect of an embodiment of the present application, a computer program product is also provided, including a non-volatile computer-readable storage medium, the non-volatile computer-readable storage medium storing a computer program, and the computer program, when executed by a processor, implements a modeling method of any of the above models.

[0013] In an embodiment of the present application, multiple models to be modeled of a product are determined, wherein different models to be modeled are used to represent different modeling stages of the product; the models to be modeled are structured to obtain at least one structured model, wherein the structured model is a resource for at least representing the modeling process of the model to be modeled; the association results between multiple structured models corresponding to the multiple models to be modeled are determined, wherein the association results are used to represent the logical relationship between the multiple structured models; based on the association results, multiple structured models are modeled to obtain the target model of the product. In other words, the embodiment of the present application carries and covers the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the model to be modeled through the linkage system of structured models, thereby achieving the purpose of paying attention to the association and consistency between different modeling stages through the association between structured models, thereby achieving the effect of improving model modeling and solving the technical problem of poor model modeling effect.

[0014] It is easy to notice that the above general description and the following detailed description are only for the purpose of exemplifying and explaining the present application, and do not constitute a limitation of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0016] Figure 1 It is a schematic diagram of an application scenario of a modeling method of a model according to an embodiment of the present application;

[0017] Figure 2 is a flow chart of a modeling method of a model according to an embodiment of the present application;

[0018] Figure 3 is a flow chart of a modeling method of another model according to an embodiment of the present application;

[0019] Figure 4 is a schematic diagram of a modeling system of a model according to an embodiment of the present application;

[0020] Figure 5 It is a schematic diagram of the logical relationship between the elements of a structured model linkage system according to an embodiment of the present application;

[0021] Figure 6 is a schematic diagram of a logical relationship between different modeling stages according to an embodiment of the present application;

[0022] Figure 7 is a schematic diagram of upstream and downstream associations of a structured model according to an embodiment of the present application;

[0023] Figure 8 is a schematic diagram of an association between a scenario domain and a bounded context according to an embodiment of the present application;

[0024] Fig. 9 is a schematic diagram of the association of internal models of a bounded context according to an embodiment of the present application;

[0025] Fig.10 It is a structural block diagram of a computing environment of a modeling method of a model according to an embodiment of the present application;

[0026] Fig.11 is a schematic diagram of a modeling device of a model according to an embodiment of the present application;

[0027] Fig.12 is a schematic diagram of a modeling device of another model according to an embodiment of the present application;

[0028] Fig.13 is a structural block diagram of a computer terminal according to an embodiment of the present application;

[0029] Fig.14 is a block diagram of an electronic device according to a modeling method of a model in an embodiment of the present application;

[0030] Fig.15 It is a hardware structure block diagram of a computer terminal (or mobile device) for implementing a modeling method of a model according to an embodiment of the present application. DETAILED DESCRIPTION

[0031] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0033] It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application, such as the data for verification, are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0034] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following explanations:

[0035] A structured model refers to a model that is carried by structured data, in order to achieve the purposes of online, versioned, linked, real-time verification, rationality analysis, sedimentation and distribution of the structured model;

[0036] Model linkage refers to the network of relationships formed between structured models. Changes in one node in a structured model can cascade and affect other nodes.

[0037] Model verification refers to the verification of the correctness and rationality of a structured model.

[0038] The modeling method of the above model provided in the embodiment of the present application can be applied to Figure 1 The application scenarios shown are not limited to these. Figure 1 is a schematic diagram of an application scenario of a modeling method of a model according to an embodiment of the present application, in which Figure 1In the application scenario shown, the server 10 can be a cloud. The server 10 can be connected to one or more client devices 20 via a local area network connection, a wide area network connection, an Internet connection, or other types of data networks. The client devices 20 here may include but are not limited to: smart phones, tablet computers, laptops, PDAs, personal computers, smart home devices, vehicle-mounted devices, etc. The client devices together constitute the client relative to the server. An operating interface for obtaining multiple models to be modeled of a product can be deployed on the graphical user interface on the client device. The client device 20 can interact with the user through a graphical user interface to implement the modeling method of the model provided in the embodiment of the present application.

[0039] In an embodiment of the present application, the system composed of the client device 20 and the server 10 can perform the following steps: perform corresponding operations in the operation interface on the client device 20 to obtain the operation interface of multiple models to be modeled of the product. The client device can obtain multiple models to be modeled and send them to the server through the network. After receiving the multiple models to be modeled, the server can perform the following steps: Step S102, determine multiple models to be modeled of the product, wherein different models to be modeled are used to represent different modeling stages of the product; Step S104, structure the models to be modeled to obtain at least one structured model, wherein the structured model is a resource for at least representing the modeling process of the model to be modeled; Step S106, determine the association results between multiple structured models corresponding to the multiple models to be modeled, wherein the association results are used to represent the logical relationship between the multiple structured models; Step S108, based on the association results, model the multiple structured models to obtain the target model of the product.

[0040] Under the above operating environment, this application provides Figure 2 Modeling approach for the model shown. Figure 2 is a flow chart of a modeling method of a model according to an embodiment of the present application, such as Figure 2 As shown, the method may include the following steps:

[0041] Step S202, determining a plurality of models to be built of the product.

[0042] In the technical solution provided in the above step S202 of the present application, multiple models to be modeled of the product can be determined. Among them, the product can be an auxiliary tool or platform (for example, the BizWorks modeling platform) used when designing and developing software. The product can be used to carry the modeling methodology of the model to be modeled, and the model to be modeled can be used to represent the various design stages in the entire development process. Optionally, taking the BizWorks modeling platform as an example, the platform covers the entire process from demand analysis, scenario modeling, technical design to code implementation. The BizWorks modeling platform can be regarded as a combination of design software and specification manuals. The design software can provide a graphical interface and tools to help developers create, edit and maintain structured models at different modeling stages. The specification manual has a series of modeling methodologies and rules built in. As guiding principles for design, these specifications are not limited to theoretical guidance, but also include actual templates, verification rules and code generation specifications.

[0043] It should be noted that different models to be modeled can be used to represent different modeling stages of the product. The modeling stage can be called the modeling design stage. The modeling stage can at least include: domain modeling stage, scenario modeling stage, technical modeling stage, assembly modeling stage, etc. The models to be modeled can at least include: domain modeling model, scenario modeling model, technical modeling model, assembly modeling model, etc. Among them, the domain modeling model is based on the principle of domain-driven design, which converts the scenario requirements into a model that can be implemented by software. The domain modeling model is represented in the form of a graph, such as an entity relationship diagram, a state diagram, a behavior diagram, etc., and is also represented in the form of structured data. The scenario modeling model is a model that connects the scenario requirements with the technical implementation. The scenario modeling model can also be represented in the form of a graph, such as a flow chart, an activity diagram, etc., and is also represented in the form of structured data. Structured data can be used to describe the nodes of the scenario modeling process, the attributes and relationships of the scenario modeling objects, etc. The technical modeling model is a model that converts the abstraction of scenario modeling into a technical design. The technical modeling model can be represented in a graph, such as a component diagram, a deployment diagram, an interface diagram, etc., but the technical modeling model is more represented in the form of structured data, such as a configuration file, an architecture document, etc. The assembly modeling model is a model that designs scenario capabilities (or functions) as independent, assembleable components. The assembly modeling model is also represented in the form of diagrams and structured data. The above models can all use structured data as a representation form. Through structured data, it can support model online, version control, real-time verification, rationality analysis, and difference comparison.

[0044] Optionally, the above products can serve as specifications in the modeling process (modeling design process) while effectively carrying the modeling methodology. Since the above products can help the design team to perform modeling design work in accordance with standardized methods, such as clarifying the workflow, standardizing the operation steps, and unifying the design standards, so as to perform modeling design work in a more systematic and standardized manner and ensure the consistency and reliability of the modeling results, the above products themselves are the embodiment of the specifications, that is, using the products means following the specifications.

[0045] Step S204: perform structural processing on the model to be built to obtain at least one structured model.

[0046] In the technical solution provided in the above step S204 of the present application, after determining multiple models to be modeled of the product, the determined models to be modeled can be structured to obtain at least one structured model. The structured model can be a resource used to at least represent the modeling process of the model to be modeled, for example, the structured model can be a scene asset data or a model asset.

[0047] It should be noted that structured processing can be a systematic and orderly processing of the model to be modeled to ensure that the model to be modeled has a clear structure and organization, which is convenient for analysis and understanding. Structured processing includes but is not limited to: data cleaning, feature selection, feature conversion, and selection of appropriate modeling algorithms and model structures. Structured processing can be used to convert raw, messy or unstructured data into a structured data form suitable for modeling. Data cleaning includes removing or correcting incomplete, erroneous, inaccurate or irrelevant data. For the model to be modeled, data cleaning is mainly carried out on the data collected or generated during the design phase of the model to be modeled. Feature selection can be used to determine the input variables that are helpful for the prediction of the model to be modeled, and relevant elements that can reflect the needs of the scenario can be selected from a large number of candidate model elements. Feature conversion refers to converting the elements of the model to be modeled into a form that is conducive to modeling. By performing structured processing on the model to be modeled, a clear, orderly and easy-to-understand structured model can be obtained.

[0048] Optionally, when the model to be modeled is a scenario modeling model, the scenario modeling model is structured to obtain scenario domain models, domain architecture models, scenario process models, story models, scenario object models and other structured models. When the model to be modeled is a technical modeling model, the technical modeling model is structured to obtain bounded context models, bounded context mapping derivation models, application service models, aggregation models, domain object models, domain service models, domain behavior design models and other structured models.

[0049] For example, take the online shopping scenario as an example to perform data cleaning and feature selection on the scenario modeling model to obtain the above structured model for explanation. In the online shopping scenario, the original user story description may include a large amount of natural language text, describing the entire process from user browsing products to completing payment. By performing data cleaning and feature selection on the user story description, a scenario domain model that defines core domain objects such as products, users, orders, and the relationships and rules between domain objects can be obtained: Based on the scenario domain model, different bounded contexts such as product management, order processing, and payment processing are divided, and the domain architecture model of modules and components within each bounded context is defined; a flowchart of user shopping is drawn, including steps such as browsing products, selecting products, and paying, as well as a scenario process model of the preconditions and postconditions of each step; a story model that structures the user story description; a scenario object model that describes each object and entity involved in a specific scenario, for example, products have attributes such as name and price, and orders are associated with entities such as products, users, and payments.

[0050] Step S206, determining the association results between the multiple structured models corresponding to the multiple models to be built.

[0051] In the technical solution provided in the above step S206 of the present application, after the model to be modeled is structured to obtain multiple structured models, the association results between the multiple structured models corresponding to the multiple models to be modeled can be determined. The association results can be used to represent the logical relationship between the multiple structured models.

[0052] Optionally, after obtaining multiple structured models, an association mapping between structured models can be created based on predefined association rules. For example, a reference can be created from a structured model to a structured model to be associated, or structured information of the structured model to be associated can be embedded in the structured model. Based on the association mapping, the association between the structured models can be clarified, so that the association results between the multiple structured models can be determined.

[0053] For example, in the scenario modeling phase, a user story model is defined, which describes how users add items to the shopping cart and complete the payment. In the technical modeling phase, a bounded context and microservice architecture are created, which includes two bounded contexts: shopping cart management and payment processing. In the code model phase, a specific code structure and class definition are generated. By creating a reference to the story of adding items to the shopping cart in the user story model in the description of the shopping cart management bounded context, it is possible to create a reference to the structured model to be associated with the structured model. In the model that describes the process of adding items to the shopping cart, the specific steps and postconditions in the user story model are directly embedded. For example, in the description of the process node, the actions that the user needs to log in, select items, click the add to shopping cart button, and the postconditions for updating the shopping cart status after successfully adding items can be listed in detail, so that the structured information of the structured model to be associated can be embedded in the structured model.

[0054] Optionally, bidirectional linkage between structured models can be achieved by sharing data or variables between structured models. When the data or variables in one structured model change, the other structured model will be updated or adjusted accordingly. This bidirectional linkage can ensure the consistency and coordination between structured models. Bidirectional linkage can also be achieved by calling or nesting structured models. One structured model can call the function or method of another structured model to obtain data or perform specific operations, so that different structured models can cooperate with each other to achieve more complex functions and tasks.

[0055] For example, the multiple structured models corresponding to the scene modeling model may include: scene domain model, domain architecture model, scene process model, story model, scene object model and other structured models, then the association result may be the association result between the scene domain model and the story model, and the association result may be used to represent the two-way linkage between the scene domain model and the story model. That is, changes in the scene domain model will affect the story model, and changes in the story model will also affect the scene domain model. The association result may also be the association result between the scene domain model and the scene object model, and the association result may be used to represent the two-way linkage between the scene domain model and the scene object model. That is, changes in the scene domain model will affect the scene object model, and changes in the scene object model will also affect the scene domain model.

[0056] For another example, since the above-mentioned scene domain model is bidirectionally linked with the story model and the scene object model respectively, when any of the above-mentioned structured models changes, it will cascade and affect other structured models.

[0057] For another example, the multiple structured models corresponding to the technical modeling model may include: bounded context model, bounded context mapping derivation model, application service model, aggregation model, domain object model, domain service model, domain behavior design model, and the association result may be the association result between the bounded context model and the scenario domain model, or the association result between the bounded context mapping derivation model and the bounded context model and the story model, respectively. Since the scenario domain model and the story model are structured models corresponding to the scenario modeling model, this embodiment can determine the association result between the multiple structured models corresponding to the scenario modeling model and the multiple structured models corresponding to the technical modeling model, that is, it can determine the association result between the multiple structured models corresponding to different models to be modeled.

[0058] Step S208: Based on the association result, multiple structured models are modeled to obtain a target model of the product.

[0059] In the technical solution provided in the above step S208 of the present application, after determining the association results between multiple structured models corresponding to multiple models to be modeled, the multiple structured models can be modeled based on the determined association results to obtain a target model of the product.

[0060] In this embodiment, the target model can be a linkage system of structured models. After obtaining the association results between multiple structured models, based on the association results, multiple structured models can be modeled in the following manner to obtain a linkage system of structured models: identify the relationship between different structured models, and define rules to guide the linkage of structured models according to the dependencies and interactions between structured models to achieve two-way linkage between structured models. For example, based on the dependencies and interactions between structured models, other related models that need to be linked and updated when the model is updated can be defined. For example, when a new scenario requirement is added to the user story model, the corresponding parts in the scenario domain model and the code model need to be updated; if the attributes of an entity are modified in the scenario domain model, the corresponding class definition in the code model also needs to be updated synchronously. By establishing a model version control system, the version information and change log of each structured model update are recorded, and the version backtracking and difference comparison of the structured model are supported. Using automated tools, the code framework or document is automatically generated based on the structured model. The linkage system of structured models supports the continuous integration and continuous deployment process of software development to ensure the consistency of design and implementation.

[0061] This embodiment can ensure a high degree of consistency between the model design and the final code implementation, reducing the error from design to implementation. The model linkage system helps to timely discover the irrationality in the design, avoiding a lot of rework in later development and maintenance, thereby reducing the overall maintenance cost. The model linkage system also supports rapid changes in scenario requirements, and can quickly adapt to changes in scenario requirements through flexible adjustment of the model.

[0062] Through the above steps S202 to S208 of the present application, multiple models to be modeled of the product are determined, wherein different models to be modeled are used to represent different modeling stages of the product; the models to be modeled are structured to obtain at least one structured model, wherein the structured model is a resource for at least representing the modeling process of the model to be modeled; the association results between multiple structured models corresponding to the multiple models to be modeled are determined, wherein the association results are used to represent the logical relationship between the multiple structured models; based on the association results, multiple structured models are modeled to obtain the target model of the product. In other words, the embodiment of the present application carries and covers the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the model to be modeled through the linkage system of structured models, thereby achieving the purpose of paying attention to the association and consistency between different modeling stages through the association between structured models, thereby achieving the effect of improving model modeling and solving the technical problem of poor model modeling effect.

[0063] The above method of this embodiment is further introduced below.

[0064] As an optional implementation, the model to be modeled is structured to obtain at least one structured model, including: determining a modeling strategy for the model to be modeled, wherein the modeling strategy is used to represent the rules for modeling the model to be modeled; and according to the modeling strategy, the model to be modeled is structured to obtain a structured model.

[0065] In this embodiment, the modeling strategy can be used to represent the rules for modeling the models to be modeled, and can also be called a modeling methodology. After determining multiple models to be modeled of a product, the models to be modeled can be structured according to the modeling methodology to obtain a structured model.

[0066] Optionally, according to the modeling methodology, the elements of the model to be modeled can be identified. For example, in the domain modeling stage, the elements of the model to be modeled can include domains, sub-domains, aggregations, entities, value objects, domain events, etc. The elements of the model to be modeled identified above are converted into structured data, and the attributes and relationships of each element can be represented by a custom data structure. Further, according to the structured data, the association relationship between the models is designed to obtain a structured model.

[0067] It should be noted that the domain refers to a specific scope of the scenario, which can be composed of some common scenario rules and concepts. For example, in the field of e-commerce, the domain can be product management, order processing, inventory management, payment processing, etc. Sub-domains are subdivisions of the domain, which can focus on a specific scenario function or concept set within the domain. For example, the field of product management can include sub-domains such as listing, delisting, classification, and search of products. Aggregates can be used to encapsulate some related entities. The root entity of an aggregate is usually a domain object, which provides access and control to the objects inside the aggregate. For example, in the order processing domain, an order can be an aggregate root, which can contain multiple related entities such as order lines, shipping addresses, and order status. The operations and status updates of these entities are performed through order objects. Entities are domain objects with unique identifiers. For example, in e-commerce, users, products, orders, etc. are entities. Value objects are domain objects without unique identifiers. The equality of value objects is determined by their attribute values. For example, in the field of product management, the price of a product is a value object, and the equality of the price of a product is determined by the unit price of the product. Domain events can be used to indicate important changes in a domain, and can be listened to and responded to by multiple subdomains or services to achieve collaboration and asynchronous communication within the domain. For example, in the e-commerce domain, when the inventory of goods in the commodity management domain decreases, a domain event can be triggered, which can be listened to by the order processing domain to ensure that there is enough inventory when processing orders.

[0068] This embodiment structures the modeling model according to the modeling methodology, and the obtained structured model can clearly express the relationship between different modeling stages, such as the relationship between the scenario modeling model and the technical modeling model. The association design can support the linkage update between the upstream and downstream structured models, that is, when a part of the structured model changes, the relevant parts of other structured models that depend on this part can be automatically updated.

[0069] As an optional implementation, the model to be modeled is structured according to the modeling strategy to obtain a structured model, including: determining the structured data of the model to be modeled according to the modeling strategy, wherein the structured data is used to carry the modeling process of the model to be modeled; and using the structured data to perform online structured processing on the model to be modeled to obtain a structured model.

[0070] In this embodiment, structured data can be used to carry a structured model. After determining the modeling methodology of the model to be built, the structured data of the model to be built can be determined according to the modeling methodology, and the determined structured data can be further used to perform online structured processing on the model to be built to obtain a structured model.

[0071] Optionally, by selecting an online modeling tool, the model to be modeled is imported into the online modeling tool. In the online modeling tool, the elements of the model to be modeled are identified according to the modeling methodology, the identified elements of the model to be modeled are converted into structured data, and further based on the structured data, the association relationship between the models is designed to obtain a structured model, that is, the structured models have an association relationship.

[0072] This embodiment transfers the design process of the structured model from traditional offline documents and charts to an online platform, that is, by transferring the design process of the structured model completed offline to online, it solves the problem of low long-term sustainable iteration and management efficiency of the structured model caused by the existence of a large number of manual combing and management of offline documents and tables. After the structured model is online, it can also be displayed and edited through a graphical interface, making the design process of the structured model more intuitive.

[0073] As an optional implementation, the model to be built is subjected to online structured processing using structured data to obtain a structured model, including: verifying the structured data; and using the verified structured data to perform online structured processing on the model to be built to obtain a structured model.

[0074] In this embodiment, after the elements of the model to be built are converted into structured data, the structured data can be verified according to the verification rules. After the structured data is verified, the model to be built can be structured online using the verified structured data to obtain a structured model. The verification rules can be rules that are set in advance according to actual conditions to verify the correctness of the structured data, design rationality, etc., and the verification rules can be continuously supplemented during actual use.

[0075] For example, based on the verification rules, the correctness of structured data can be verified. The correctness verification mainly focuses on whether the structured data is complete and whether the content is missing, so as to ensure that the necessary information is correctly included in the structured data. For example, aggregation can be used to achieve the cohesion of scene logic and reduce the coupling between scene objects. The aggregate root is the entrance to the aggregate, and the entities and value objects inside the aggregate can be accessed through the aggregate root. If the aggregate root is defined, the aggregate root should have corresponding aggregate members (entities and value objects), as well as a logical description of the aggregate. If an aggregate member of an aggregate root is omitted in the modeling design, or the responsibilities of the aggregate root are not defined, the above-mentioned missing content problems can be found when the structured data is verified for correctness.

[0076] For another example, based on the verification rules, the influence of structured data being deleted by mistake can be prevented. For example, when deleting a certain structured data, if the structured data is referenced in other parts of the structured model, the deletion operation will cause errors in other parts of the structured model that reference the structured data, which will affect the correctness and integrity of the structured model. This embodiment can prevent the above-mentioned error problems caused by the deletion operation by verifying whether the structured model is deleted by mistake.

[0077] For another example, based on the verification rules, the design rationality of structured data can be verified. For example, the aggregate root can be called across the aggregate boundary, and the entity and value object cannot directly cross the boundary. In this way, the rationality of the aggregate design is verified, thereby ensuring the clarity of the scene logic and the maintainability of the code.

[0078] This embodiment verifies structured data in different aspects based on verification rules, which can ensure the quality of modeling design, avoid potential problems in the design and implementation process, and improve the efficiency of software development and the reliability of the final product.

[0079] As an optional implementation, the method further includes: determining a version of the structured model; and publishing the version of the structured model.

[0080] In this embodiment, a version control system can be used to manage the version of the structured model, and the version number of the structured model can be composed of three numbers, representing the major version, the minor version, and the patch version respectively. When an important interface change affects the system using the existing structured model, the major version number can be increased. When adding a function without destroying the compatibility of the existing structured model, the minor version number can be increased. When fixing a bug or making a small adjustment without changing the function or interface of the structured model, the patch version number can be increased. By using a version control system to automatically record every change to the structured model, the version number of the new version can be automatically determined according to the nature of the change to the structured model, and the new version of the structured model can be released.

[0081] This embodiment manages the structured model as design asset data in a versioned manner, which can flexibly support the release and iteration of the structured model version. Through versioned management, the change history of the structured model can be clearly tracked, and the content and reasons for the modification of the structured model can be understood.

[0082] As an optional implementation, the model to be modeled is structured to obtain at least one structured model, including: determining the knowledge data required for the model to be modeled, and the modeling products of the model to be modeled during the modeling process, wherein the knowledge data is used to represent the knowledge in the modeling scenario to which the product belongs; and determining, from the product's resource database, a structured model that carries at least the knowledge data and the modeling products.

[0083] In this embodiment, the knowledge data can be used to represent the knowledge in the modeling scenario to which the product belongs. For example, the knowledge data can at least be used to represent the scenario knowledge, and the knowledge data can at least include scenario processes, scenario activities, scenario domain architectures, scenario objects, etc. The modeling product can be a design product of modeling. For example, the modeling product can at least include design patterns, architecture decisions, technical implementation solutions, user stories, requirement documents, etc. The resource database can include a variety of scenario asset data.

[0084] Optionally, as a kind of scenario asset data, the structured model not only captures the scenario process, rules and structure, but also contains the logic and implementation details of the design decision, thus becoming a carrier of scenario knowledge and design products. The scenario knowledge such as scenario process, scenario activities, scenario domain architecture, scenario objects, etc. required for the model to be modeled can be collected. Based on the collected scenario knowledge, the design products that need to be generated in the modeling design process can be defined. Further, from the product resource database, a structured model that carries the above scenario knowledge and design products can be selected.

[0085] In this embodiment, the structured model is a kind of scene asset data, carrying important scene knowledge, design process and design products, thereby achieving the purpose of continuous accumulation and rapid reuse.

[0086] As an optional implementation, determining a structured model that at least carries knowledge data and modeling products from a resource database of a product includes: determining an initial structured model that at least carries knowledge data and modeling products from the resource database; adjusting the initial structured model based on code development requirement information to obtain a structured model, wherein the code development requirement information is used to represent the code development requirements of the structured model to be determined; the method also includes: storing the structured model as resource data in the resource database.

[0087] In this embodiment, the initial structured model can be an existing structured model that carries knowledge data and modeling products. Code development requirement information can be used to represent the code development requirements of the structured model to be determined. The initial structured model that carries scenario knowledge and design products can be determined from the resource database, that is, the existing structured model is determined. When the scenario requirements change, the initial structured model is adjusted, and the initial structured model can be adjusted by modifying the initial structured model file or in a graphical modeling tool. A code generator or a model-to-code conversion tool can be used to automatically convert the adjusted initial structured model into code, and the generated code can directly enter the automated construction process. After the above development is completed, a code reverse engineering tool can be used to extract new model information, update or create a new structured model.

[0088] Optionally, after generating a new structured model as described above, the structured model can be stored as resource data in a resource database. The newly generated structured model becomes part of the model asset library and can be reused by subsequent projects, thereby saving design time and helping to maintain the consistency of the design architecture.

[0089] This embodiment adjusts the existing structured model and quickly generates code to enter development. After the development is completed, the newly generated structured model is further precipitated as a new model asset, achieving the purpose of continuous iteration of the structured model and automatic production of code, thereby realizing rapid conversion and feedback from conceptual design to technical implementation, improving software development efficiency, reducing duplication of work, and ensuring code quality.

[0090] As an optional implementation, determining the association results between multiple structured models corresponding to multiple models to be modeled includes: determining model elements in the models to be modeled, wherein the model elements are used to represent data associated with upstream models and / or downstream models of the models to be modeled in the multiple models to be modeled; and determining the association results between the multiple structured models based on the model elements.

[0091] In this embodiment, the model elements can be used to represent data associated with the upstream model and / or downstream model of the model to be modeled in the multiple models to be modeled, and can also be called model design elements. The model elements of the scenario modeling model can at least include scenario entities, scenario rules, scenario processes, scenario events, etc. The model elements of the technical modeling model can at least include application architecture, data structure, interface definition, service component, event consumer, event producer, etc.

[0092] Optionally, by setting a mapping rule from the model elements of one model to the model elements of another model, for example, setting a mapping rule from the model elements of the scenario modeling model to the model elements of the technical modeling model, and determining the dependency relationship between the model elements. According to the above mapping rules and dependency relationships, the model elements of the scenario modeling model are structurally associated with the model elements of the technical modeling model, and multiple structured models can be obtained, and the multiple structured models have association results.

[0093] This embodiment determines the association results between multiple structured models based on model elements. Since the flexibility of model elements allows the design to make local adjustments without destroying the overall structure of the system, the association results between the determined structured models can more clearly view the cascading impact of adjusting the structured models, thereby improving the convenience of adding new functions or adjusting existing functions.

[0094] As an optional implementation, determining model elements in the model to be modeled includes: determining multiple sub-processes of the model to be modeled, wherein the sub-processes are used to constitute the modeling process of the model to be modeled; in response to cascading the sub-processes to the upstream model and / or downstream model in the model to be modeled, determining the model elements based on the sub-processes.

[0095] In this embodiment, sub-processes can be used to constitute the modeling process of the model to be modeled. Multiple sub-processes have process levels, and multiple sub-processes can be nested. For example, the sub-process with the highest process level can nest the sub-process with the second highest process level, and so on.

[0096] Optionally, based on the nested relationship between the above-mentioned multiple sub-processes, the models in different sub-processes can be cascaded to determine the upstream model and / or downstream model in the model to be modeled. When the sub-process cascades the upstream model and / or downstream model in the model to be modeled, the model elements can be further determined based on the above-mentioned sub-processes, for example, the above-mentioned sub-processes can be determined as model elements.

[0097] This embodiment determines model elements based on sub-processes and affects upstream and downstream models through a cascading mechanism, which can significantly improve the efficiency, accuracy and consistency of structured model design, while simplifying the development process and improving the maintainability and scalability of the system.

[0098] As an optional implementation, determining the model elements based on the sub-process includes: determining the modeling products of the sub-process and / or the model to be modeled in the sub-process as the model elements.

[0099] In this embodiment, the sub-process and / or the modeling products of the model to be modeled in the sub-process, that is, the design process and design products of each link of the modeling, can be determined as model elements.

[0100] This embodiment subdivides the design process and related products of each link of modeling into model elements, which can significantly improve the efficiency and accuracy of modeling. At the same time, by standardizing and structuring the expression of model elements, the maintainability, scalability and knowledge accumulation ability of modeling design can be enhanced.

[0101] As an optional implementation, based on model elements, determining the association results between multiple structured models includes: establishing an association network between multiple structured models according to the model elements, wherein the model nodes in the association network change as the associated model nodes of the model nodes in the association network change.

[0102] In this embodiment, the association network can be a network of interconnected structured models formed by organizing and associating different structured models in a structured manner, and can also be called a relationship network. In the association network, each structured model can be regarded as a model node, and the edge represents the relationship and dependency between structured models. The association network presents a hierarchical structure, in which some models (such as scenario modeling models) are at a higher level, while other models (such as code models) are at a lower level. The high-level model can guide the design and implementation of the low-level model, and the changes of the low-level model will also feedback and affect the high-level model, forming a closed-loop linkage.

[0103] It should be noted that the scenario rules and logic are defined in the scenario modeling model at a higher level, and the scenario rules and logic are passed as guiding principles to the technical modeling model and code model at a lower level. For example, the steps and rules defined in the scenario flow in the scenario modeling model can guide the bounded context design in the technical modeling model, as well as the definition of functions and classes in the code model.

[0104] Optionally, the model nodes in the association network change as the associated model nodes of the model nodes in the association network change, that is, when a model node in the association network changes, other model nodes associated with the model node will also change.

[0105] The advantage of the structured model in this embodiment is that after the model is structured, an association network is formed, and changes to the model nodes can be cascaded and synchronized and updated, that is, changes to the model nodes can cascade to affect other nodes associated with them, thereby facilitating the analysis and query of the structured model.

[0106] As an optional implementation, based on the association results, multiple structured models are modeled to obtain a target model of the product, including: according to the association network, multiple structured models are modeled to obtain a target model of the product.

[0107] In this embodiment, the relationships and dependencies between structured models can be determined based on the association network. Since the association network can reflect the linkage mechanism between structured models, multiple structured models can be modeled according to the association network. The obtained target model aggregates the information of the structured models, ensuring the consistency and integrity between various levels of modeling design (for example, scenarios, data, technical architecture, security, etc.).

[0108] This embodiment models multiple structured models according to the association network, and can establish associations between structured models, ensuring the uniformity and integrity of information between structured models. Changes in each structured model can cascade to the associated models, so that each step of the modeling design process can be traced, which also facilitates the maintenance and updating of the structured model, ensuring the sustainability of the modeling design.

[0109] As an optional implementation, the method also includes: determining a code model corresponding to the structured model in the target model, wherein the code model is developed using the code of the structured model; determining difference information between the code model and the structured model; structuring the difference information; updating the code model using the structured difference information; and updating the target model using the updated code model.

[0110] In this embodiment, the code model can be a model obtained by code development using a structured model. Code can be generated based on the structured model, and the code can be developed to obtain the above code model. By performing a two-way comparison between the code model and the structured model, the difference information between the code model and the structured model can be determined, and the difference information can be used to indicate whether the implementation and design of the structured model deviate. Among them, the code of the structured model can be a specific code representation of converting the structured model into a programming language through the code model.

[0111] Optionally, the above difference information can be structured to obtain structured difference information, that is, the difference information is stored in the form of structured data to facilitate subsequent processing. The code model is updated using the structured difference information, and the difference information can be parsed into specific operation instructions, such as which codes need to be added, which codes need to be modified or deleted. According to the parsed operation instructions, the code model is updated using an automated script or an update tool integrated in the development platform.

[0112] Furthermore, the updated code model is used to update the target model. The updated code model can be compared with the structured model to identify model differences caused by code model changes. Based on the comparison results of the updated code model and the structured model, the structured model is adjusted to reflect the actual implementation status of the updated code, thereby obtaining an updated target model. For example, if a new class or interface appears in the updated code model, a corresponding description can be added to the structured model, such as the properties and relationships of the class or interface.

[0113] This embodiment compares the differences between the code model and the structured model, that is, supports structured comparison of model differences, thereby achieving the purpose of design and implementation consistency of the structured model. That is, the structured model system and upstream and downstream associations can support consistency requirements on scenario modeling and technical modeling, and technical modeling and code implementation.

[0114] As an optional implementation, determining multiple models to be built for a product includes: determining a modeling scenario to which the product belongs; and determining the models to be built in the modeling scenario.

[0115] In this embodiment, the modeling scenario may include at least scenario modeling, technical modeling, domain modeling, assembly modeling, code model, etc. For example, the model to be modeled in the scenario modeling scenario may be a scenario modeling model, and the model to be modeled in the technical modeling scenario may be a technical modeling model, so that different models to be modeled in different modeling scenarios can be determined.

[0116] Through diversified modeling scenarios, this embodiment can comprehensively analyze scenario processes, data structures, user interactions, architectural designs, etc. from multiple angles and levels, ensuring the depth and comprehensiveness of the modeling design, thereby providing a comprehensive perspective on modeling design and implementation.

[0117] As an optional implementation, the model to be modeled is structured to obtain at least one structured model, including: in response to the model to be modeled being a scenario modeling model, the scenario modeling model is structured to obtain at least one of the following structured models: a scenario domain model, a domain architecture model, a scenario process model, a story model, and a scenario object model, wherein the scenario domain model is used to divide the domain of the modeling scenario to which the product belongs, the domain architecture model is used to represent the architecture of the domain of the modeling scenario, the scenario process model is used to represent processes of different levels under the modeling scenario, the story model is used to represent use cases under the modeling scenario, and the scenario object model is used to represent scene objects under the modeling scenario.

[0118] In this embodiment, the scenario domain model can be an abstract representation of the scenario functions and scenario logic, describing the core concepts, rules, processes and data of the scenario. The scenario domain model can at least include scenario entities (e.g., customers, orders), value objects (e.g., addresses, currency units), aggregations (usually composed of one entity and multiple associated entities), domain services (services that perform specific tasks in the scenario domain), etc. By constructing a scenario domain model, the scenario boundaries can be clearly defined, the scenario requirements can be identified, and the core logic related to the scenario can be assisted in modeling and design.

[0119] Optionally, the domain architecture model describes the component structure and the relationship between component structures within the scenario domain, and is an extension of the scenario domain model. The domain architecture model may at least include bounded contexts, the relationship between bounded contexts, and the division of microservices or modules. The domain architecture model can be used to understand the scenario domain at the technical level, ensure the consistency of technical implementation and scenario requirements, and guide the boundary division of microservices or modules.

[0120] It should be noted that the association between the scenario domain model and the domain architecture model can be achieved by identifying and mapping the elements in the scenario domain model to the corresponding elements in the domain architecture model. For example, the entity in the scenario domain model will first be identified and analyzed to determine the scenario domain to which the entity belongs. Then, based on the scope and boundaries of the scenario domain, the entity is mapped to the corresponding bounded context in the domain architecture model. For example, the customer and order entities can be mapped to the order processing bounded context.

[0121] Optionally, the scenario process model can be a model that describes how scenario operations flow through one or more scenario entities, defining the sequence, roles, and triggering conditions of scenario activities. The scenario process model can include at least activity nodes, swimlanes (indicating organizations or roles that perform activities), message flows, events, etc. The scenario process model can be used to identify and optimize scenario processes, ensuring that the modeling design can support and enhance scenario operations, improve efficiency, and reduce errors. The scenario process model can also support multi-layer sub-process nesting associations, i.e., L1-L5 processes, where L1 can be used to represent the highest-level main process, L2 can be used to represent sub-processes under L1, and so on.

[0122] Optionally, the story model can also be called a user story model, which describes the functions that the system should provide from the user's perspective. The user story model may at least include users, actions, results, and possible preconditions and postconditions. The user story model can structuredly decompose the use case's preconditions, trigger conditions, postconditions, execution steps, constraint rules, acceptance conditions and other information, and can be used as input for subsequent product requirements document (PRD) use cases and bounded context mapping inference models of technical modeling models. That is, the above-mentioned structured decomposition information is used as input for subsequent PRD use cases and bounded context mapping inference models of technical modeling models.

[0123] Optionally, the scene object model describes the entities, attributes and behaviors of the entities in the scene domain. Scene objects are usually mapped to objects in the database structure or scene logic. The scene object model may at least include entities (e.g., products, customers), attributes (e.g., customer addresses), behaviors (e.g., creating orders, shipping), etc. The scene object model can be used to provide data structure definitions, guide data storage and scene logic implementation, and ensure data consistency and integrity.

[0124] This embodiment structures the scenario modeling model into the above-mentioned structured model, which can fully understand the scenario requirements and modeling design goals, ensure that the technical implementation is highly consistent with the scenario requirements, improve development efficiency, reduce errors and maintenance costs, and at the same time improve product quality and user experience.

[0125] As an optional implementation, determining the association results between multiple structured models corresponding to multiple models to be modeled includes at least one of the following: determining the association results between the scene domain model and the story model and the scene object model respectively; determining the association results between the domain architecture model and the scene domain model; determining the association results between the scene process model and the story model and the scene object model respectively.

[0126] In this embodiment, the scenario domain model is associated with the user story model. Since the user story model provides scenarios and requirements inputs for the scenario domain model, the interaction requirements and scenario processes of entities in the scenario domain model can be identified by analyzing the user story model, ensuring that the model covers key user requirements and scenarios.

[0127] Optionally, the scene object model is part of the scene domain model. The scene object model describes the scene entities and the relationships between entities in more detail. The scene domain model provides high-level scene concepts, while the scene object model defines the implementation details of these scene concepts in detail. By associating the scene domain model with the scene object model, the scene domain model can transition from abstract concepts to specific data structures and scene logic.

[0128] Optionally, the scenario domain model is associated with the user story model and the scenario object model respectively, and can be used to assist in deriving the classification division of the domain, that is, to derive the classification division of the scenario domain (bounded context).

[0129] Optionally, the scenario domain model describes the scenario concepts, and the domain architecture model shows how these scenario concepts are implemented from a technical level. By associating the domain architecture model with the scenario domain model, the scenario entities and rules in the scenario domain model are converted into technical components and boundaries in the domain architecture model, such as bounded contexts and microservices.

[0130] Optionally, scenario activities in the user story model can be mapped to one or more steps in the scenario process model. By associating the user story model with the scenario process model, it can be ensured that user needs are accurately understood and implemented when modeling, designing, and implementing functions. For example, the user story model describes how to place an order, while the scenario process model shows in detail the steps from order creation to order completion, including checking inventory, confirming payment, etc., which helps developers build a process that matches the user story model.

[0131] Optionally, when designing a scenario process model, a specific scenario object is required to support the execution of the process. For example, if the process includes "updating customer information", a scenario object "customer" is required to carry the logic of information update. The above requirements can be achieved by associating the scenario process model with the scenario object model.

[0132] It should be noted that after associating or mapping the elements of different models, the corresponding and dependent relationships between different models are the association results between the models. For example, the scenario entities and rules in the scenario domain model are transformed (mapped) into technical components and boundaries in the domain architecture model, that is, the bounded context elements in the scenario domain model are mapped into microservice elements in the domain architecture model, which is the process of determining the association results between the scenario domain model and the domain architecture model.

[0133] By determining the association results between the scenario domain model and the story model, this embodiment can ensure that the operations and goals in the user story model can be accurately mapped to the entities and behaviors in the scenario domain model, thereby reducing misunderstandings of requirements. By determining the association results between the scenario domain model and the scenario object model, the scenario rules and logic can be clarified, reducing the ambiguity in the modeling and design phase. By determining the association results between the domain architecture model and the scenario domain model, it is ensured that the technical architecture design is consistent with the scenario domain model, reducing the disconnection between technical implementation and scenario requirements. By determining the association results between the scenario process model and the story model and the scenario object model, respectively, it is ensured that each step in the scenario process complies with the scenario rules, and the rationality of the process is verified through the scenario object model. That is, by determining the association results between the above-mentioned structured models, this embodiment can ensure the consistency between scenario requirements and technical implementation.

[0134] As an optional implementation, the model to be modeled is structured to obtain at least one structured model, including: in response to the model to be modeled being a technical modeling model, the technical modeling model is structured to obtain at least one of the following structured models: a bounded context model, a bounded context mapping inference model, an application service model, an aggregation model, a domain object model, a domain service model, and a domain behavior design model, wherein the bounded context model is used to represent the carrier of the associated scenario modeling model and the technical modeling model, the bounded context mapping inference model is used to derive the service model provided by the bounded context of the product, the application service model is used to determine the application service of the product, the aggregation model is used to cluster scenario objects, the domain object model is used to carry the logic of the modeling scenario, the domain service model is used to carry different combination services of the product in the domain, and the domain behavior design model is used to derive the service strategy and object behavior of the product in the domain.

[0135] In this embodiment, the bounded context model can be an important carrier for connecting the scenario modeling model and the technical modeling model. The bounded context model can be formed based on the scenario domain division of the scenario modeling model. The bounded context mapping derivation model is based on the bounded context model and the execution steps of the user story model (describing the interaction logic between different bounded contexts) to derive the application service model provided by each bounded context.

[0136] Optionally, the application service model is derived through the bounded context mapping deduction model, or is created from 0-1. The application service model can be used to subsequently generate an application programming interface (API). There are two ways to generate an application service model. The first way is to derive it through the bounded context mapping deduction model and then publish it. The second way is to create from 0-1, that is, to directly create an application service model on the platform without derivation. This is usually for situations where it is clear which application service models are needed.

[0137] Optionally, the aggregate model can be used to better classify domain object models according to scenario cohesion, and the aggregates should be loosely coupled, with cross-aggregate calls only made through aggregate roots. The aggregate root model encapsulates and exposes aggregate-related service capabilities.

[0138] Optionally, domain object models can be generated in batches based on scenario object models. Domain object models are key models that carry scenario logic. Domain object models are divided into multiple model types, including aggregate roots, entities, and value objects, according to their responsibilities. Domain service models can be used to carry cross-aggregate service combinations. The input parameters and output parameters (i.e., input and output parameters) of domain service models must use domain object models. The domain behavior design model uses the application service model or domain event model as the entry point, and further analyzes and derives the capabilities that need to be deposited in the domain layer, i.e., domain service methods and domain object behaviors, within a bounded context model.

[0139] This embodiment achieves a two-way linkage from scenario requirements to technical implementation by structuring the technical modeling model into the above-mentioned multiple structural models. While supporting a smooth transition from scenario design to technical implementation, it ensures that the technical implementation can accurately reflect the scenario requirements and improves the consistency between design and implementation. Through the structured processing of the technical modeling model, the design and implementation can be flexibly adjusted to support agile development and rapid iteration. For example, through the domain behavior design model, the scenario process and rules can be easily adjusted to quickly respond to changes in scenario requirements.

[0140] As an optional implementation, determining the association results between multiple structured models corresponding to multiple models to be modeled includes at least one of the following: determining the association results between the bounded context model and the scenario domain model; determining the association results between the bounded context mapping inference model and the bounded context model and the story model respectively; determining the association results between the application service model and the bounded context mapping inference model; determining the association results between the aggregation model and the domain object model; determining the association results between the domain service model and the domain object model; determining the association results between the domain behavior design model and the bounded context model.

[0141] In this embodiment, the bounded context model is associated with the scenario domain model, that is, the bounded context model is formed based on the scenario domain model. The bounded context mapping derivation model is associated with the bounded context model and the story model, that is, the bounded context mapping derivation model can derive the application service model based on the bounded context model and the story model, and the application service model is associated with the bounded context mapping derivation model, that is, the application service model is derived from the bounded context mapping derivation model.

[0142] Optionally, the aggregation model is associated with the domain object model, that is, the domain object model is classified according to the scenario cohesion through the aggregation model. The domain service model is associated with the domain object model, that is, the input parameters and output parameters of the domain service model need to use the domain object model. The domain behavior design model is associated with the bounded context model, that is, the domain behavior design model analyzes and derives the capabilities that need to be deposited in the domain layer within the bounded context model, that is, the domain service methods and domain object behaviors.

[0143] This embodiment ensures the coherence of the entire design system from macro to micro by determining the association results between structured models, and ensures consistency at different levels such as scenario domain, technical implementation and code model. The association between structured models helps the development team to quickly locate the context of function implementation, reduce understanding costs, and improve coding efficiency. At the same time, model-based development can reduce human errors and improve code quality. The linkage system between structured models provides a flexible change management mechanism. When the scenario requirements change, the relevant technical modeling models and code models can be automatically updated by adjusting the scenario domain model or story model.

[0144] As an optional implementation, the model to be built includes one of the following models of the product: a domain modeling model, an assembly modeling model, a code model, a process modeling model, and a data modeling model.

[0145] In this embodiment, the above-mentioned scenario modeling model and technical modeling model can constitute a domain modeling model. The scenario modeling model, technical modeling model, domain modeling model and code model can constitute an assembled modeling model. The code model can be used to extract key information on the code side, for example, it can be extracted with the assistance of tools or automatically. The code model can be used to express the implementation of the model design elements by the code. The code model can at least include an application service code model, a structural object code model, a domain object code model, a domain service code model, a domain event code model, a data model code model, etc. Based on the code model, a two-way comparison and linkage of design and implementation can be achieved.

[0146] Optionally, the process modeling model can be a model that describes and designs the various steps in the scenario process and the relationships and interactions between these steps. The process modeling model can be used to clearly show how the scenario process works, identify bottlenecks in the process, optimize efficiency, and provide a design basis for the automated process. The data modeling model can be a model that focuses on organizing and structuring data to ensure data accuracy and consistency. The data modeling model can be used to design database structures, formulate data processing rules, and define the data transmission format of the API.

[0147] In an embodiment of the present application, multiple models to be modeled of a product are determined, wherein different models to be modeled are used to represent different modeling stages of the product; the models to be modeled are structured to obtain at least one structured model, wherein the structured model is a resource for at least representing the modeling process of the model to be modeled; the association results between multiple structured models corresponding to the multiple models to be modeled are determined, wherein the association results are used to represent the logical relationship between the multiple structured models; based on the association results, multiple structured models are modeled to obtain the target model of the product. In other words, the embodiment of the present application carries and covers the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the model to be modeled through the linkage system of structured models, thereby achieving the purpose of paying attention to the association and consistency between different modeling stages through the association between structured models, thereby achieving the effect of improving model modeling and solving the technical problem of poor model modeling effect.

[0148] The present application also provides a modeling method for a model. Figure 3 is a flow chart of a modeling method of another model according to an embodiment of the present application, such as Figure 3 As shown, the method may include the following steps:

[0149] Step S302, in response to an input instruction on the operation interface, a plurality of models of the product to be built are displayed on the operation interface, wherein different models to be built are used to represent different modeling stages of the product.

[0150] In the technical solution provided in the above step S302 of the present application, the input instruction can be an instruction triggered by the user through the input control on the operation interface, for example, the input control can be a button, menu, form writing control, etc., and the user can trigger the input instruction by clicking a button, selecting a drop-down menu, filling in a form, etc. The product can be used to carry the modeling methodology of the model to be modeled. For example, the product can be a modeling design software, a design flowchart template, a project management tool, a design specification manual, etc. that presents the model to be modeled. This is only for example, and does not specifically limit the type of product.

[0151] It should be noted that different models to be modeled can be used to represent different modeling stages of the product. The modeling stage can be called the modeling design stage. The modeling stage can at least include: domain modeling stage, scenario modeling stage, technical modeling stage, assembly modeling stage, etc. The models to be modeled can at least include: domain modeling model, scenario modeling model, technical modeling model, assembly modeling model, etc.

[0152] Optionally, the above products can serve as specifications in the modeling process (modeling design process) while effectively carrying the modeling methodology. Since the above products can help the design team to perform modeling design work in accordance with standardized methods, such as clarifying the workflow, standardizing the operation steps, and unifying the design standards, so as to perform modeling design work in a more systematic and standardized manner and ensure the consistency and reliability of the modeling results, the above products themselves are the embodiment of the specifications, that is, using the products means following the specifications.

[0153] Step S304, in response to the processing instruction acting on the operation interface, the target model of the product is displayed on the operation interface, wherein the target model is obtained by modeling multiple structured models based on the association results between multiple structured models corresponding to the multiple models to be modeled, the structured model is a resource used to at least represent the modeling process of the model to be modeled, the association result is used to represent the logical relationship between the multiple structured models, and the structured model is obtained by structuring the model to be modeled.

[0154] In the technical solution provided in the above step S304 of the present application, the processing instruction may be an instruction for processing a plurality of models to be built. In response to the processing instruction acting on the operation interface, the plurality of models to be built may be transmitted to the server, and the server processes the plurality of models to be built to obtain a target model, and transmits the target model to the client to display the target model of the product on the operation interface of the client.

[0155] It should be noted that the structured model can be a resource used to at least represent the modeling process of the model to be modeled. For example, the structured model can be a scene asset data or a model asset. Structural processing can be a systematic and orderly processing of the model to be modeled to ensure that the model to be modeled has a clear structure and organization, which is convenient for analysis and understanding. Structural processing includes but is not limited to: data cleaning, feature selection, feature conversion, and selection of appropriate modeling algorithms and model structures. By performing structural processing on the model to be modeled, a clear, orderly, and easy-to-understand structured model can be obtained.

[0156] For example, when the model to be modeled is a scenario modeling model, the scenario modeling model is structured to obtain scenario domain models, domain architecture models, scenario process models, story models, scenario object models and other structured models. When the model to be modeled is a technical modeling model, the technical modeling model is structured to obtain bounded context models, bounded context mapping derivation models, application service models, aggregation models, domain object models, domain service models, domain behavior design models and other structured models.

[0157] For example, the multiple structured models corresponding to the scene modeling model may include structured models such as scene domain model, domain architecture model, scene process model, story model, scene object model, etc., then the association result may be the association result between the scene domain model and the story model, and the association result between the scene domain model and the story model may be used to represent the two-way linkage between the scene domain model and the story model. That is, changes in the scene domain model will affect the story model, and changes in the story model will also affect the scene domain model. The association result may also be the association result between the scene domain model and the scene object model, and the association result between the scene domain model and the scene object model may be used to represent the two-way linkage between the scene domain model and the scene object model. That is, changes in the scene domain model will affect the scene object model, and changes in the scene object model will also affect the scene domain model.

[0158] For another example, since the above-mentioned scene domain model is bidirectionally linked with the story model and the scene object model respectively, when any of the above-mentioned structured models changes, it will cascade and affect other structured models.

[0159] Optionally, bidirectional linkage between structured models can be achieved by sharing data or variables between structured models. When the data or variables in one structured model change, the other structured model will be updated or adjusted accordingly. This bidirectional linkage can ensure the consistency and coordination between structured models. Bidirectional linkage can also be achieved by calling or nesting structured models. One structured model can call the function or method of another structured model to obtain data or perform specific operations, so that different structured models can cooperate with each other to achieve more complex functions and tasks.

[0160] For another example, the multiple structured models corresponding to the technical modeling model may include: bounded context model, bounded context mapping derivation model, application service model, aggregation model, domain object model, domain service model, domain behavior design model, and the association result may be the association result between the bounded context model and the scenario domain model, or the association result between the bounded context mapping derivation model and the bounded context model and the story model, respectively. Since the scenario domain model and the story model are structured models corresponding to the scenario modeling model, this embodiment can determine the association result between the multiple structured models corresponding to the scenario modeling model and the multiple structured models corresponding to the technical modeling model, that is, it can determine the association result between the multiple structured models corresponding to different models to be modeled.

[0161] Optionally, the target model can be a linkage system of structured models. After obtaining the association results between multiple structured models, based on the association results, multiple structured models can be modeled in the following ways to obtain a linkage system of structured models: identify the relationship between different structured models, and define rules to guide the linkage of structured models according to the dependencies and interactions between structured models to achieve two-way linkage between structured models. By establishing a model version control system, the version information and change log of each structured model update are recorded to support version backtracking and difference comparison of structured models. Using automated tools, code frameworks or documents are automatically generated based on structured models. The linkage system of structured models supports the continuous integration and continuous deployment process of software development to ensure the consistency of design and implementation.

[0162] This embodiment can ensure a high degree of consistency between the model design and the final code implementation, reducing the error from design to implementation. The model linkage system helps to timely discover the irrationality in the design, avoiding a lot of rework in later development and maintenance, thereby reducing the overall maintenance cost. The model linkage system also supports rapid changes in scenario requirements, and can quickly adapt to changes in scenario requirements through flexible adjustment of the model.

[0163] Through the above steps S302 to S304 of the present application, in response to the input instruction acting on the operation interface, multiple models of the product to be modeled are displayed on the operation interface, wherein different models to be modeled are used to represent different modeling stages of the product; in response to the processing instruction acting on the operation interface, the target model of the product is displayed on the operation interface, wherein the target model is obtained by modeling multiple structured models based on the association results between multiple structured models corresponding to the multiple models to be modeled, the structured model is a resource used to at least represent the modeling process of the model to be modeled, the association result is used to represent the logical relationship between the multiple structured models, and the structured model is obtained by structured processing of the model to be modeled. In other words, the embodiment of the present application carries and covers the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the model to be modeled through the linkage system of the structured model, thereby achieving the purpose of paying attention to the association and consistency between different modeling stages through the association between the structured models, thereby achieving the effect of improving the model modeling and solving the technical problem of poor model modeling effect.

[0164] The present application also provides a modeling system for a model. Figure 4 is a schematic diagram of a modeling system according to an embodiment of the present application, such as Figure 4 As shown, the modeling system of the model may include: a client 402 and a server 404 .

[0165] The client 402 is used to upload multiple models of a product to be built, wherein different models to be built are used to represent different modeling stages of the product.

[0166] Optionally, the product can be used to carry the modeling methodology of the model to be modeled. For example, the product can be modeling design software, design flow chart template, project management tool, design specification manual, etc. that presents the model to be modeled. This is only an example and does not limit the type of product. The modeling stage can be called the modeling design stage. The modeling stage can at least include: domain modeling stage, scenario modeling stage, technical modeling stage, assembly modeling stage, etc. The model to be modeled can at least include: domain modeling model, scenario modeling model, technical modeling model, assembly modeling model, etc.

[0167] Optionally, the above products can serve as specifications in the modeling process (modeling design process) while effectively carrying the modeling methodology. Since the above products can help the design team to perform modeling design work in accordance with standardized methods, such as clarifying the workflow, standardizing the operation steps, and unifying the design standards, so as to perform modeling design work in a more systematic and standardized manner and ensure the consistency and reliability of the modeling results, the above products themselves are the embodiment of the specifications, that is, using the products means following the specifications.

[0168] Server 404 is connected to the client and is used to perform structured processing on the model to be modeled to obtain at least one structured model, wherein the structured model is a resource used to at least represent the modeling process of the model to be modeled; determine the association results between multiple structured models corresponding to the multiple models to be modeled, wherein the association results are used to represent the logical relationship between the multiple structured models; based on the association results, model the multiple structured models to obtain a target model of the product; and send the target model to the client.

[0169] It should be noted that the structured model can be a resource used to at least represent the modeling process of the model to be modeled. For example, the structured model can be a scene asset data or a model asset. Structural processing can be a systematic and orderly processing of the model to be modeled to ensure that the model to be modeled has a clear structure and organization, which is convenient for analysis and understanding. Structural processing includes but is not limited to: data cleaning, feature selection, feature conversion, and selection of appropriate modeling algorithms and model structures. By performing structural processing on the model to be modeled, a clear, orderly, and easy-to-understand structured model can be obtained.

[0170] For example, when the model to be modeled is a scenario modeling model, the scenario modeling model is structured to obtain scenario domain models, domain architecture models, scenario process models, story models, scenario object models and other structured models. When the model to be modeled is a technical modeling model, the technical modeling model is structured to obtain bounded context models, bounded context mapping derivation models, application service models, aggregation models, domain object models, domain service models, domain behavior design models and other structured models.

[0171] For example, the multiple structured models corresponding to the scene modeling model may include structured models such as scene domain model, domain architecture model, scene process model, story model, scene object model, etc., then the association result may be the association result between the scene domain model and the story model, and the association result between the scene domain model and the story model may be used to represent the two-way linkage between the scene domain model and the story model. That is, changes in the scene domain model will affect the story model, and changes in the story model will also affect the scene domain model. The association result may also be the association result between the scene domain model and the scene object model, and the association result between the scene domain model and the scene object model may be used to represent the two-way linkage between the scene domain model and the scene object model. That is, changes in the scene domain model will affect the scene object model, and changes in the scene object model will also affect the scene domain model.

[0172] For another example, since the above-mentioned scene domain model is bidirectionally linked with the story model and the scene object model respectively, when any of the above-mentioned structured models changes, it will cascade and affect other structured models.

[0173] Optionally, bidirectional linkage between structured models can be achieved by sharing data or variables between structured models. When the data or variables in one structured model change, the other structured model will be updated or adjusted accordingly. This bidirectional linkage can ensure the consistency and coordination between structured models. Bidirectional linkage can also be achieved by calling or nesting structured models. One structured model can call the function or method of another structured model to obtain data or perform specific operations, so that different structured models can cooperate with each other to achieve more complex functions and tasks.

[0174] For another example, the multiple structured models corresponding to the technical modeling model may include: bounded context model, bounded context mapping derivation model, application service model, aggregation model, domain object model, domain service model, domain behavior design model, and the association result may be the association result between the bounded context model and the scenario domain model, or the association result between the bounded context mapping derivation model and the bounded context model and the story model, respectively. Since the scenario domain model and the story model are structured models corresponding to the scenario modeling model, this embodiment can determine the association result between the multiple structured models corresponding to the scenario modeling model and the multiple structured models corresponding to the technical modeling model, that is, it can determine the association result between the multiple structured models corresponding to different models to be modeled.

[0175] Optionally, the target model can be a linkage system of structured models. After obtaining the association results between multiple structured models, based on the association results, multiple structured models can be modeled in the following ways to obtain a linkage system of structured models: identify the relationship between different structured models, and define rules to guide the linkage of structured models according to the dependencies and interactions between structured models to achieve two-way linkage between structured models. By establishing a model version control system, the version information and change log of each structured model update are recorded to support version backtracking and difference comparison of structured models. Using automated tools, code frameworks or documents are automatically generated based on structured models. The linkage system of structured models supports the continuous integration and continuous deployment process of software development to ensure the consistency of design and implementation.

[0176] This embodiment can ensure a high degree of consistency between the model design and the final code implementation, reducing the error from design to implementation. The model linkage system helps to timely discover the irrationality in the design, avoiding a lot of rework in later development and maintenance, thereby reducing the overall maintenance cost. The model linkage system also supports rapid changes in scenario requirements, and can quickly adapt to changes in scenario requirements through flexible adjustment of the model.

[0177] In the system, multiple models to be modeled of a product are uploaded through the client, wherein different models to be modeled are used to represent different modeling stages of the product; the server is connected to the client, and the model to be modeled is structured by the server to obtain at least one structured model, wherein the structured model is a resource for at least representing the modeling process of the model to be modeled; the association results between multiple structured models corresponding to the multiple models to be modeled are determined, wherein the association results are used to represent the logical relationship between the multiple structured models; based on the association results, multiple structured models are modeled to obtain the target model of the product; and the target model is sent to the client. In other words, the embodiment of the present application carries and covers the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the model to be modeled through the linkage system of structured models, thereby achieving the purpose of paying attention to the association and consistency between different modeling stages through the association between structured models, thereby achieving the effect of improving model modeling and solving the technical problem of poor model modeling effect.

[0178] The technical solution of the embodiment of the present disclosure is further introduced below with examples in combination with preferred implementation modes.

[0179] At present, in the modeling design methodology, for example, scenario modeling, process modeling, Unified Modeling Language (UML), domain modeling, data modeling, and assembly modeling, process modeling, data modeling and other methodologies have corresponding products, but they are only for specific fields and can provide template tools, but they do not pay attention to and cannot solve the upstream and downstream associations and consistency issues of the methodology; scenario modeling, domain modeling and other methodologies only remain at the theoretical level and lack the support of effective products, resulting in the problem of disconnection between methodology and implementation. Due to the complexity of the actual implementation of the above-mentioned methodologies, it is impossible to achieve implementation by relying solely on methodology or single-point tools. Products that effectively carry the methodology are needed as specifications in the construction process (using the product means following the specification).

[0180] In related technologies, UML modeling tools only provide static diagram drawing of models. After the product is completed, it serves as a static diagram. It does not pay attention to the relationship and consistency between different modeling and design stages, nor does it pay attention to the implementation of the design content on the implementation side. It cannot further play a role in how to better guide the implementation of scenario design, resulting in poor model modeling effect.

[0181] In order to solve the above problems, the present application proposes a mechanism for implementing a modeling methodology using a structured model linkage system. The structured model in this embodiment supports upstream and downstream linkage mechanisms, and can simultaneously support domain modeling, scenario modeling, technical modeling, assembly modeling, and code models (and design linkage).

[0182] The above method of this embodiment is further introduced below.

[0183] In this embodiment, the assembly modeling methodology may be composed of a domain modeling methodology, a scenario modeling methodology, a technical modeling methodology, and a code model. Figure 5 is a schematic diagram of the logical relationship between the elements of a structured model linkage system according to an embodiment of the present application, such as Figure 5 As shown in the figure, the Packaged Business Capabilities (PBC) metamodel corresponds to the above-mentioned assembly modeling methodology. It can be seen that there is an association between the design, development and operation elements in the assembly modeling methodology. The operation part can include elements such as asset operation information and scenario identity. In the design part, the system process, scenario capability, and business capability PRD are respectively associated with business capabilities. Publishing business capabilities can obtain business capability assets, publishing solutions can obtain solution assets, and publishing various application components can obtain component assets. Among them, the business capability API is associated with scenario activities, scenario activities are associated with business capability processes, and business capability processes are associated with business capabilities. Each application component can include front-end application components, back-end for frontend (BEF) application components, microservice application components, and integrated application components. Among them, the front-end application components involve menus, pages, blocks, front-end scenario components, front-end interaction flows, front-end components, and front-end technical metadata. BEF application components involve APIs, service orchestration, and BEF technical metadata. Microservice application components involve APIs, domain models, data models, service models, structural objects, and application technical metadata. Integration application components involve integration flows, integration connectors, and integration application technical metadata.

[0184] In the development part, the business capability part is used to develop business capability engineering, the front-end technical metadata is used to develop front-end engineering, the BEF technical metadata is used to develop BEF application engineering, the application technical metadata is used to develop microservice application engineering, and the integrated application technical metadata is used to develop integrated application engineering. Business capability engineering involves application engineering dependencies, front-end engineering involves page code and front-end component code, BEF application engineering involves BEF API and BEF API implementation, microservice application engineering involves API interface and domain model implementation, and integrated application engineering involves integrated API. Through the above pipeline construction, asset mirroring can be obtained.

[0185] The domain modeling methodology can be composed of the scenario modeling methodology and the technical modeling methodology. The structured models involved in the scenario modeling methodology can at least include the scenario domain model, the domain architecture model, the scenario process model, the user story model and the scenario object model, that is, the scenario modeling methodology is supported by the association between the above structured models.

[0186] The scenario domain model is associated with the user story model and the scenario object model, which can be used to assist in the derivation of the classification of the domain and is associated with the bounded context model of the technical modeling methodology (the bounded context model corresponds to the microservice application). Among them, the bounded context model can be the corresponding product of the microservice application in the design phase. Associating the scenario domain model with the bounded context model can play a connecting role, that is, associating the scenario with the scenario domain, and associating the technology with the microservice, thereby achieving the coordination between the scenario modeling methodology and the technical modeling methodology. The domain architecture model is associated with the scenario domain model, and the domain architecture model is associated with the bounded context model / microservice application to form an application architecture model.

[0187] The scenario process model is associated with the unified language through roles and with the user story model through the scenario activity model. The scenario process model can derive scenario objects and associate them with scenario objects. Among them, the scenario process can support multi-layer sub-process nesting association, that is, L1-L5 process. L1 can be used to represent the highest level main process, L2 can be used to represent the sub-process under L1, L3 can be used to represent the sub-process under L2, L4 can be used to represent the sub-process under L3, and L5 can be used to represent the sub-process under L4. It should be noted that the roles defined in the unified language can be used as the swimlane roles of the scenario process model. The user story model can be used as the activity node of the scenario process model to form a process, that is, the elements of the scenario design are structurally associated front and back. When the roles in the unified language or the content of the user story model changes, the scenario process model will also be refreshed in real time.

[0188] The user story model decomposes the use case's preconditions, trigger conditions, postconditions, execution steps, constraint rules, acceptance conditions and other information in a structured manner, which can be used as input for the bounded context timing derivation of subsequent PRD use cases and technical modeling methodology. In other words, the above structured decomposition information is used as input for the bounded context timing derivation of subsequent PRD use cases and technical modeling. In addition to the association between scene objects, the scene object model can also be used to batch import and generate domain objects to associate the scene modeling methodology with the technical modeling methodology.

[0189] The structured models involved in the technical modeling methodology may at least include the bounded context model, bounded context mapping derivation model, application service model, aggregation model, domain object model, domain service model, and domain behavior design model, that is, the association between the above structured models is used to support the technical modeling methodology. The bounded context model is an important carrier for connecting the scenario modeling methodology and the technical modeling methodology. The bounded context model is formed based on the scenario domain division of the scenario modeling methodology. The bounded context model can be associated with the scenario domain model / sub-domain model. The bounded context model can be used as an important input for microservice application development and associated implementation.

[0190] The bounded context mapping derivation model can derive the service model provided by each bounded context model based on the execution steps of the bounded context model and the user story model (describing the interaction logic between different bounded contexts), where the execution steps of the bounded context model can be used to describe the interaction logic between different bounded context models. The bounded context mapping derivation model only focuses on the capabilities provided by each bounded context model to the outside world, and does not involve its internal logic.

[0191] The application service model is derived through the bounded context mapping deduction model, or is created from 0-1. The application service model can be used to generate API interfaces later. There are two ways to generate the application service model. The first way is to derive it through the context mapping deduction model and then publish it. The second way is to create it from 0-1, that is, to create the application service model directly on the platform without deduction. It is usually used for situations where it is clear which application service models are needed.

[0192] Aggregate models can be used to better classify domain object models according to scenario cohesion. Aggregates should be loosely coupled and cross-aggregate calls should only be made through aggregate roots. Aggregate-related service capabilities are encapsulated and exposed to the outside through aggregate root models. Domain object models can be generated in batches based on scenario object models and are key models for carrying scenario logic. Domain object models are divided into multiple model types, including aggregate roots, entities, and value objects, based on their responsibilities. Domain service models are used to carry cross-aggregate service combinations. The input parameters and output parameters (i.e., input and output parameters) of domain service models must use domain object models. The domain behavior design model uses the application service model or domain event model as the entry point, and further analyzes and derives the capabilities that need to be deposited in the domain layer, i.e., domain service methods and domain object behaviors, within a bounded context model.

[0193] The code model can be used to extract key information on the code side, through tool-assisted or automated extraction, to express the implementation of model design elements by the code. The code model may include at least application service code model, structural object code model, domain object code model, domain service code model, domain event code model, data model code model, etc. Based on the code model, two-way comparison and linkage between design and implementation can be achieved.

[0194] Figure 6 is a schematic diagram of a logical relationship between different modeling stages according to an embodiment of the present application, such as Figure 6 As shown, scenario modeling includes scenario processes, and scenario processes include L1 scenario processes, L2 scenario processes, L3 scenario processes, and L4 scenario processes, wherein L2 scenario processes are sub-processes of L1 scenario processes, and L3 scenario processes are sub-processes of L2 scenario processes. Scenario services (use cases) are generally generated from L3 scenario processes, and scenario services (use cases) belong to the scenario domain, or scenario services (use cases) belong to the scenario domain through scenario objects. L4 scenario processes are generally generated from scenario services (use cases). Scenario services (use cases) are associated with PRD use cases of requirement modeling and context mapping timing derivation of technical modeling.

[0195] Technical modeling can include models such as bounded context, aggregation, context mapping timing derivation, application services, domain events, domain services, domain objects, and domain behavior design. Context mapping timing derivation can derive application services and domain events, which can be used as inputs for domain behavior design, and domain behavior design can derive domain services and domain objects. In addition, the business capability process of business capability modeling is also associated with the L4 scenario process.

[0196] Figure 7 is a schematic diagram of upstream and downstream associations of a structured model according to an embodiment of the present application, such as Figure 7 As shown in the figure, scenario flow design and user story design can be used as inputs for scenario object design, scenario object design can be imported into domain object design, and domain object design can be imported into data modeling. In addition, scenario domain design can also be used as input for bounded contexts, so that the upstream and downstream of each structured model can be interconnected.

[0197] Figure 8 is a schematic diagram of the association between a scenario domain and a bounded context according to an embodiment of the present application, such as Figure 8As shown, the scenario domain may include at least: transaction domain, commodity domain, user domain, payment domain, inventory domain, and order domain. The transaction domain is associated with the transaction context, the commodity domain is associated with the commodity context, the user domain includes the account domain and the member domain, the account domain is associated with the user context, the member domain is associated with the member context, the payment domain is associated with the payment context, the inventory domain is associated with the inventory context, and the order domain is associated with the order context.

[0198] This embodiment also supports multi-version management of bounded context models. From Table 1, we can see the scenario domains associated with each bounded context, as well as the latest versions of each bounded context model. Through multi-version management, the change history of the bounded context model can be traced. Changes to the bounded context model may have an impact on upstream and downstream services. Multi-version management can help identify the scope of impact of the change, assess the risk of the change, and ensure a smooth transition of the change in other related services. For example, before a new version of the bounded context model is released, its impact on existing service interfaces and data structures can be analyzed through version comparison, so as to formulate a corresponding migration plan.

[0199] Table 1 Bounded context model multi-version management table

[0200]

[0201] Fig. 9 is a schematic diagram of the association of the internal model of a bounded context according to an embodiment of the present application, such as Fig. 9 As shown, the bounded context model is used as the input of the mapping inference model, and the mapping inference model is associated with the application service model and the domain event consumer model respectively. The bounded context model is associated with the domain event producer model, the domain object design model, and the domain entity object model respectively. The domain entity object model can be imported into the data modeling model, and the domain entity object model can also be used as the input of the domain behavior design model. The domain behavior design model is associated with the domain service, and the domain entity object model is associated with the modeling mapping model. The context mapping model is associated with the application service model, the mapping inference model, the domain event consumer model, and the domain event producer model respectively.

[0202] There are corresponding products for modeling methodology, but they are only for specific fields, such as providing rich templates and tools for process modeling and data modeling, and they do not pay attention to and cannot solve the problems of upstream and downstream association and consistency within the modeling methodology system. This embodiment can better carry and cover the design process and design products of each link of the modeling methodology through the structured model linkage system, and at the same time can pay attention to the upstream and downstream linkage and consistency problems through the association between structured models.

[0203] In view of the problem that modeling methodology remains at the theoretical level, such as scenario modeling, domain modeling, assembly modeling, etc., and lacks the support of mature products, the structured model system proposed in this embodiment has good product feasibility and can support diverse modeling scenarios.

[0204] In view of the complexity of the actual implementation of modeling methodology, it is necessary to rely solely on methodology or single-point tools to implement it. Products that effectively carry the methodology and become the norm in the system construction process (using the product means following the design specifications). This embodiment is based on the product of the structured model system, which carries the specifications for model design (scenario modeling, technical modeling) and development implementation, and ensures the implementation of the specifications in a productized manner through versioning, real-time verification, difference comparison, rationality analysis, design and implementation consistency verification of the structured model.

[0205] The structured model linkage system proposed in this embodiment plays an effective supporting role in realizing the upstream and downstream linkage of the modeling methodology, designing and implementing consistency, and productizing the modeling methodology.

[0206] Regarding the onlineization of structured models, this embodiment completes the structured model design process that was originally completed offline online. For scenario modeling, there is a large amount of manual sorting and management through offline documents and tables, which leads to great challenges in the long-term sustainable iteration and management of structured models. The onlineization of structured models can solve the above problems.

[0207] Regarding the versioning of structured models, structured model design, as an important part of system design and construction, needs to be promoted as part of R&D iteration. Versioning the structured model as design asset data can flexibly support the release and iteration of structured model versions.

[0208] For real-time linkage within the structured model system, the structured model can structure the model to form an association network. Changes to the structured model nodes can be synchronized and updated in a cascade. That is, when a node in the structured model changes, it will cascade affect other nodes. At the same time, it also enables more flexible analysis and query of the impact on the structured model.

[0209] With respect to the difference comparison of structured models, this embodiment supports structured comparison of structured model differences. That is, after designing the structured model, generating code based on the structured model, and developing the generated code, a two-way comparison can be performed on the structured model design and the code implementation to find out whether there is a deviation between the implementation and the design. A structured difference comparison can be performed when performing a difference comparison on the structured model.

[0210] For the analysis of real-time verification and design rationality of structured models, based on structured data and verification rules (continuous supplementation), real-time verification of structured models can be supported, including but not limited to: correctness verification of structured models, consistency verification of the design and implementation of structured models. The correctness verification of structured models can at least include: verifying whether the content of the structured model is missing, whether deleting the structured model will cause errors in the referenced party, and judging the rationality of the design based on scenario rules. For example, when judging the rationality of the design of scenario rules, if loose coupling is guaranteed between aggregations, that is, cross-aggregation calls are made only through aggregation roots, the design of the scenario rules is judged to be reasonable. Secondly, the consistency verification of the design and implementation of the structured model is performed. The structured model system and upstream and downstream associations of this embodiment can support the consistency requirements of scenario modeling and technical modeling, technical modeling and code implementation.

[0211] For the accumulation and distribution and reuse of scene assets, the structured model, as a kind of scene asset data, carries important scene knowledge, design process and design products, which can be continuously accumulated and quickly reused. By adjusting the existing structured model, code can be quickly generated and developed. The developed code can be further accumulated into new model assets. The structured model can also flexibly support distribution scenarios such as exporting and importing scene assets.

[0212] In an embodiment of the present application, multiple models to be modeled of a product are determined, wherein different models to be modeled are used to represent different modeling stages of the product; the models to be modeled are structured to obtain at least one structured model, wherein the structured model is a resource for at least representing the modeling process of the model to be modeled; the association results between multiple structured models corresponding to the multiple models to be modeled are determined, wherein the association results are used to represent the logical relationship between the multiple structured models; based on the association results, multiple structured models are modeled to obtain the target model of the product. In other words, the embodiment of the present application carries and covers the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the model to be modeled through the linkage system of structured models, thereby achieving the purpose of paying attention to the association and consistency between different modeling stages through the association between structured models, thereby achieving the effect of improving model modeling and solving the technical problem of poor model modeling effect.

[0213] Fig.10 is a structural block diagram of a computing environment of a modeling method of a model according to an embodiment of the present application, such as Fig.10As shown, computing environment 1001 includes multiple computing nodes (such as servers) running on a distributed network (shown as 1010-1, 1010-2, ..., in the figure). The computing nodes all contain local processing and memory resources, and end users 1002 can remotely run applications or store data in computing environment 1001. Applications can be provided as multiple services 1020-1, 1020-2, 1020-3 and 1020-4 in computing environment 1001, representing services "A", "D", "E" and "H" respectively.

[0214] The end user 1002 can provide and access services through a web browser or other software application on the client, and in some embodiments, the end user 1002's provision and / or request can be provided to the entry gateway 1030. The entry gateway 1030 can include a corresponding agent to handle the provision and / or request for the service (one or more services provided in the computing environment 1001).

[0215] Services are provided or deployed based on various virtualization technologies supported by the computing environment 1001. In some embodiments, services can be provided based on virtual machine (VM)-based virtualization, container-based virtualization, and / or similar methods. Virtual machine-based virtualization can be to simulate a real computer by initializing a virtual machine, and execute programs and applications without directly contacting any actual hardware resources. While the virtual machine virtualizes the machine, according to container-based virtualization, a container can be started to virtualize the entire operating system (Operating System, referred to as OS) so that multiple workloads can run on a single operating system instance.

[0216] In an embodiment based on container virtualization, several containers of a service can be assembled into a Pod (e.g., a Kubernetes Pod). Fig.10 As shown, service 1020-2 can be equipped with one or more Pods 1040-1, 1040-2, ..., 1040-N (collectively referred to as Pods). Pods can include a proxy 1045 and one or more containers 1042-1, 1042-2, ..., 1042-M (collectively referred to as containers). One or more containers in a Pod process requests related to one or more corresponding functions of the service, and the proxy 1045 generally controls network functions related to the service, such as routing, load balancing, etc. Other services can also be equipped with Pods similar to Pods.

[0217] During operation, executing a user request from end user 1002 may require invoking one or more services in computing environment 1001, and executing one or more functions of a service may require invoking one or more functions of another service. Fig.10 As shown, service "A" 1020-1 receives a user request from end user 1002 from ingress gateway 1030, service "A" 1020-1 may call service "D" 1020-2, and service "D" 1020-2 may request service "E" 1020-3 to perform one or more functions.

[0218] The computing environment described above can be a cloud computing environment, where the allocation of resources is managed by the cloud service provider, allowing the development of functions without considering the implementation, adjustment or expansion of servers. The computing environment allows developers to execute code in response to events without building or maintaining complex infrastructure. Services can be divided into a set of functions that can be automatically and independently scaled, rather than expanding a single hardware device to handle potential loads.

[0219] According to an embodiment of the present application, there is also provided a method for implementing the above Figure 2 The modeling method of the model shown is a modeling device of the model.

[0220] Fig.11 is a schematic diagram of a modeling device according to an embodiment of the present application, such as Fig.11 As shown, the modeling device 1100 of the model may include: a first determination unit 1102 , a processing unit 1104 , a second determination unit 1106 , and a modeling unit 1108 .

[0221] The first determining unit 1102 is used to determine multiple models to be built of the product, wherein different models to be built are used to represent different modeling stages of the product.

[0222] The processing unit 1104 is used to perform structural processing on the model to be built to obtain at least one structured model, wherein the structured model is a resource used to at least represent the modeling process of the model to be built.

[0223] The second determining unit 1106 is used to determine the association results between the multiple structured models corresponding to the multiple models to be built, wherein the association results are used to represent the logical relationship between the multiple structured models.

[0224] The modeling unit 1108 is used to model the multiple structured models based on the association results to obtain a target model of the product.

[0225] It should be noted that the first determination unit 1102, the processing unit 1104, the second determination unit 1106, and the modeling unit 1108 correspond to steps S202 to S208, and the four units and the corresponding steps implement the same examples and application scenarios, but are not limited to the above disclosed content. It should be noted that the above units can be hardware components or software components stored in a memory (e.g., memory 1304) and processed by one or more processors (e.g., processors 1302a, 1302b..., 1302n), and the above units can also be run in a computer terminal A as part of the device.

[0226] In the modeling device of the model, a plurality of models to be modeled of the product are determined by the first determination unit 1102, wherein different models to be modeled are used to represent different modeling stages of the product. The model to be modeled is structured by the processing unit 1104 to obtain at least one structured model, wherein the structured model is a resource for at least representing the modeling process of the model to be modeled. The association results between the plurality of structured models corresponding to the plurality of models to be modeled are determined by the second determination unit 1106, wherein the association results are used to represent the logical relationship of the association between the plurality of structured models. The modeling unit 1108 models the plurality of structured models based on the association results to obtain the target model of the product. That is to say, the embodiment of the present application carries and covers the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the model to be modeled through the linkage system of the structured model, thereby achieving the purpose of paying attention to the association and consistency between different modeling stages through the association between the structured models, thereby achieving the effect of improving the modeling, and solving the technical problem of poor effect of the modeling.

[0227] According to an embodiment of the present application, there is also provided a method for implementing the above Figure 3 The modeling method of the model shown is a modeling device of the model.

[0228] Fig.12 is a schematic diagram of a modeling device of another model according to an embodiment of the present application, such as Fig.12 As shown, the modeling device 1200 of the model may include: a first display unit 1202 and a second display unit 1204.

[0229] The first display unit 1202 is used to respond to an input instruction on the operation interface and display multiple models of the product to be built on the operation interface, wherein different models to be built are used to represent different modeling stages of the product.

[0230] The second display unit 1204 is used to respond to the processing instructions acting on the operation interface and display the target model of the product on the operation interface, wherein the target model is obtained by modeling multiple structured models based on the association results between multiple structured models corresponding to the multiple models to be modeled, the structured model is a resource used to at least represent the modeling process of the model to be modeled, the association result is used to represent the logical relationship between the multiple structured models, and the structured model is obtained by structuring the model to be modeled.

[0231] Here, the first display unit 1202 and the second display unit 1204 correspond to steps S302 to S304, and the two units and the corresponding steps implement the same examples and application scenarios, but are not limited to the above disclosed contents. It should be noted that the above units can be hardware components or software components stored in a memory (e.g., memory 1304) and processed by one or more processors (e.g., processors 1302a, 1302b..., 1302n), and the above units can also be run in a computer terminal A as part of a device.

[0232] In the modeling device of the model, the first display unit 1202 responds to the input instruction acting on the operation interface, and displays multiple models of the product to be modeled on the operation interface, wherein different models to be modeled are used to represent different modeling stages of the product. The second display unit 1204 responds to the processing instruction acting on the operation interface, and displays the target model of the product on the operation interface, wherein the target model is obtained by modeling multiple structured models based on the association results between multiple structured models corresponding to the multiple models to be modeled, and the structured model is a resource for at least representing the modeling process of the model to be modeled, and the association result is used to represent the logical relationship between the multiple structured models, and the structured model is obtained by structured processing of the model to be modeled. That is to say, the embodiment of the present application carries and covers the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the model to be modeled through the linkage system of the structured model, thereby achieving the purpose of paying attention to the association and consistency between different modeling stages through the association between the structured models, thereby achieving the effect of improving the model modeling and solving the technical problem of poor effect of the model modeling.

[0233] The embodiment of the present application may provide a computer terminal, which may be any computer terminal device in a computer terminal group. Optionally, in this embodiment, the computer terminal may also be replaced by a terminal device such as a mobile terminal.

[0234] Optionally, in this embodiment, the computer terminal may be located in at least one network device among a plurality of network devices of the computer network.

[0235] In this embodiment, the above-mentioned computer terminal can execute the program code of the following steps in the modeling method of the model: determining multiple models to be modeled of the product, wherein different models to be modeled are used to represent different modeling stages of the product; structuring the models to be modeled to obtain at least one structured model, wherein the structured model is a resource for at least representing the modeling process of the model to be modeled; determining the association results between multiple structured models corresponding to the multiple models to be modeled, wherein the association results are used to represent the logical relationship between the multiple structured models; based on the association results, modeling the multiple structured models to obtain the target model of the product.

[0236] Optionally, Fig.13 is a structural block diagram of a computer terminal according to an embodiment of the present application, such as Fig.13 As shown, the computer terminal A may include: one or more (only one is shown in the figure) processors 1302 , a memory 1304 and a transmission device 1306 .

[0237] Wherein, the memory can be used to store software programs and modules, such as the modeling method of the model in the embodiment of the present application and the program instructions / modules corresponding to the device, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, the modeling method of the above-mentioned model is realized. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal A via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0238] The processor can call the information and application programs stored in the memory through the transmission device to execute the following steps: responding to input instructions on the operation interface, displaying multiple models of the product to be modeled on the operation interface, wherein different models to be modeled are used to represent different modeling stages of the product; responding to processing instructions on the operation interface, displaying the target model of the product on the operation interface, wherein the target model is obtained by modeling multiple structured models based on the association results between multiple structured models corresponding to the multiple models to be modeled, the structured model is a resource used to at least represent the modeling process of the model to be modeled, the association results are used to represent the logical relationship between the multiple structured models, and the structured model is obtained by structured processing of the model to be modeled.

[0239] It can be understood by those skilled in the art that Fig.13The structure shown is for illustration only, and the computer terminal A may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, abbreviated as MID), a personal access display (Personal Access Display, abbreviated as PAD), and other terminal devices. Fig.13 It does not limit the structure of the above-mentioned computer terminal A. For example, the computer terminal A may also include Fig.13 More or fewer components (such as network interfaces, display devices, etc.) shown in, or with Fig.13 Different configurations are shown.

[0240] A person of ordinary skill in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by instructing the hardware related to the terminal device through a program, and the program may be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

[0241] The embodiment of the present application further provides a computer-readable storage medium. Optionally, in this embodiment, the computer-readable storage medium can be used to store the program code executed by the modeling method provided in the first embodiment.

[0242] Optionally, in this embodiment, the computer-readable storage medium may be located in any one of the computer terminals in a computer terminal group in a computer network, or in any one of the mobile terminals in a mobile terminal group.

[0243] The embodiment of the present application further provides a computer program product. Optionally, in this embodiment, the computer program product may include a computer program, and the computer program implements the method provided in the embodiment when executed by a processor.

[0244] Optionally, the computer program product may include a non-volatile computer-readable storage medium, and the non-volatile computer-readable storage medium may be used to store a computer program. When the computer program is executed by a processor, the method provided in the above embodiment is implemented.

[0245] An embodiment of the present application may provide an electronic device, which may include a memory and a processor.

[0246] Fig.14It is a block diagram of an electronic device according to a modeling method of a model of an embodiment of the present application. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.

[0247] like Fig.14 As shown, the device 1400 includes a computing unit 1401, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 1402 or a computer program loaded from a storage unit 1408 into a random access memory (RAM) 1403. In the RAM 1403, various programs and data required for the operation of the device 1400 can also be stored. The computing unit 1401, the ROM 1402, and the RAM 1403 are connected to each other via a bus 1404. An input / output (I / O) interface 1405 is also connected to the bus 1404.

[0248] A number of components in the device 1400 are connected to the I / O interface 1405, including: an input unit 1406, such as a keyboard, a mouse, etc.; an output unit 1407, such as various types of displays, speakers, etc.; a storage unit 1408, such as a disk, an optical disk, etc.; and a communication unit 1409, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 1409 allows the device 1400 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0249] The computing unit 1401 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 1401 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSP), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 1401 performs the various methods and processes described above, such as the modeling method of the model. For example, in some embodiments, the modeling method of the model may be implemented as a computer software program, which is tangibly included in a machine-readable medium, such as a storage unit 1408. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 1400 via the ROM 1402 and / or the communication unit 1409. When the computer program is loaded into the RAM 1403 and executed by the computing unit 1401, one or more steps of the modeling method of the model described above may be executed. Alternatively, in other embodiments, the computing unit 1401 may be configured to execute the modeling method of the model by any other appropriate manner (for example, by means of firmware).

[0250] Various embodiments of the systems and techniques described above herein may be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard parts (ASSPs), system-on-a-chip systems (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: being implemented in one or more computer programs that may be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor that may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0251] The program code for implementing the method of the present application can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0252] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Fig.15 is a hardware structure block diagram of a computer terminal (or mobile device) for implementing a modeling method of a model according to an embodiment of the present application, such as Fig.15 As shown, the computer terminal 150 (or mobile device) may include one or more (shown in the figure as 1502a, 1502b, ..., 1502n) processors 1502 (the processor 1502 may include but is not limited to a processing device such as a microprocessor (Microcontroller Unit, abbreviated as MCU) or a programmable logic device (Field Programmable Gate Array, abbreviated as FPGA)), a memory 1504 for storing data, and a transmission device 1506 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. Those skilled in the art will understand that Fig.15 The structure shown is only for illustration and does not limit the structure of the above electronic device. Fig.15 More or fewer components as shown, or with Fig.15 Different configurations are shown.

[0253] Fig.15 The hardware structure block diagram shown can be used not only as an exemplary block diagram of the above-mentioned computer terminal 150 (or mobile device), but also as an exemplary block diagram of the above-mentioned server. In an optional embodiment, Fig.15 The block diagram shows the use of the above Fig.15 The computer terminal 150 (or mobile device) is shown as an embodiment of a computing node in the computing environment 701 .

[0254] In the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by an instruction execution system, device or equipment or for use in combination with an instruction execution system, device or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, 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 for short), an optical fiber, a portable compact disc read-only memory (CD-ROM for short), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0255] To provide interaction with a user, the systems and techniques described herein may be implemented on a computer having: a display device (e.g., a cathode ray tube (CRT) or a liquid crystal display (LCD), a monitor for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a path ball), through which the user may provide input to the computer. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0256] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a Local Area Network (LAN), a Wide Area Network (WAN), and the Internet.

[0257] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. The server may be a cloud server, a server of a distributed system, or a server combined with a blockchain.

[0258] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0259] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0260] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0261] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0262] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0263] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, read-only memory, random access memory, mobile hard disk, disk or optical disk, etc., which can store program code.

[0264] The above are only preferred implementations of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A modeling method, characterized in that: include: Determine a plurality of to-be-modeled models of the product, wherein different to-be-modeled models are used to represent different modeling stages of the product; Performing structural processing on the model to be built to obtain at least one structured model, wherein the structured model is a resource for at least representing a modeling process of the model to be built; Determine association results between the plurality of structured models corresponding to the plurality of models to be modeled, wherein the association results are used to represent the logical relationship between the plurality of structured models; Based on the association result, multiple structured models are modeled to obtain a target model of the product.

2. The method according to claim 1, characterized in that Structuring the model to be built to obtain at least one structured model includes: Determining a modeling strategy for the model to be built, wherein the modeling strategy is used to represent a rule for building a model for the model to be built; According to the modeling strategy, the model to be built is structured to obtain the structured model.

3. The method according to claim 2, characterized in that According to the modeling strategy, the model to be modeled is structured to obtain the structured model, including: According to the modeling strategy, determining the structured data of the model to be built, wherein the structured data is used to carry the modeling process of the model to be built; The structured data is used to perform online structured processing on the model to be built to obtain the structured model.

4. The method according to claim 3, characterized in that Using the structured data, performing online structured processing on the model to be built to obtain the structured model, including: Verifying the structured data; The structured data that has passed verification is used to perform online structured processing on the model to be built to obtain the structured model.

5. The method according to claim 1, characterized in that The method further comprises: determining a version of the structured model; The structured model of the version is published.

6. The method according to claim 1, characterized in that Structuring the model to be built to obtain at least one structured model includes: Determine the knowledge data required by the model to be built, and the modeling product of the model to be built during the modeling process, wherein the knowledge data is used to represent the knowledge in the modeling scenario to which the product belongs; The structured model carrying at least the knowledge data and the modeling product is determined from a resource database of the product.

7. The method according to claim 6, characterized in that Determining the structured model carrying at least the knowledge data and the modeling product from a resource database of the product, comprising: Determining, from the resource database, an initial structured model that carries at least the knowledge data and the modeling product; Based on the code development requirement information, the initial structured model is adjusted to obtain the structured model, wherein the code development requirement information is used to represent the code development requirement of the structured model to be determined; The method further includes: storing the structured model as resource data in the resource database.

8. The method according to claim 1, characterized in that: Determining the association results between the plurality of structured models corresponding to the plurality of models to be modeled includes: Determine a model element in the model to be modeled, wherein the model element is used to represent data associated with an upstream model and / or a downstream model of the model to be modeled in the plurality of models to be modeled; Based on the model elements, the association results between the plurality of the structured models are determined.

9. The method according to claim 8, characterized in that Determining the model elements in the model to be built includes: Determine a plurality of sub-processes of the model to be built, wherein the sub-processes are used to constitute a modeling process of the model to be built; In response to the sub-process cascading the upstream model and / or the downstream model in the to-be-modeled model, the model elements are determined based on the sub-process.

10. The method according to claim 9, characterized in that Determining the model elements based on the sub-process includes: The sub-process and / or the modeling product of the model to be modeled in the sub-process are determined as the model elements.

11. The method according to claim 8, characterized in that Determining the association results between the plurality of structured models based on the model elements includes: According to the model elements, an association network among the plurality of structured models is established, wherein the model nodes in the association network are changed as the associated model nodes of the model nodes in the association network are changed.

12. The method according to claim 11, characterized in that Based on the association result, multiple structured models are modeled to obtain a target model of the product, including: According to the association network, multiple structured models are modeled to obtain the target model of the product.

13. The method according to claim 1, characterized in that The method further comprises: In the target model, determining a code model corresponding to the structured model, wherein the code model is developed using the code of the structured model; Determining difference information between the code model and the structured model; Performing structured processing on the difference information; Using the structured difference information, updating the code model; The target model is updated using the updated code model.

14. The method according to any one of claims 1 to 13, characterized in that Identify multiple models of the product to be built, including: Determining the modeling scenario to which the product belongs; Determining the model to be modeled under the modeling scenario; The model to be modeled is structured to obtain at least one structured model, including: in response to the model to be modeled being a scenario modeling model, the scenario modeling model is structured to obtain at least one of the following structured models: a scenario domain model, a domain architecture model, a scenario process model, a story model, and a scenario object model, wherein the scenario domain model is used to divide the domain of the modeling scenario to which the product belongs, the domain architecture model is used to represent the architecture of the domain of the modeling scenario, the scenario process model is used to represent processes of different levels under the modeling scenario, the story model is used to represent use cases under the modeling scenario, and the scenario object model is used to represent scenario objects under the modeling scenario.

15. The method according to claim 14, characterized in that Determining the association results between the plurality of structured models corresponding to the plurality of models to be modeled comprises at least one of the following: Determine the association results between the scene domain model and the story model and the scene object model respectively; Determine the association result between the domain architecture model and the scenario domain model; Determine the association results between the scene process model and the story model and the scene object model respectively.

16. The method according to claim 14, characterized in that Structuring the model to be built to obtain at least one structured model includes: In response to the model to be modeled being a technical modeling model, the technical modeling model is structured to obtain at least one of the following structured models: a bounded context model, a bounded context mapping inference model, an application service model, an aggregation model, a domain object model, a domain service model, and a domain behavior design model, wherein the bounded context model is used to represent a carrier that associates the scenario modeling model and the technical modeling model, the bounded context mapping inference model is used to derive a service model provided by the bounded context of the product, the application service model is used to determine the application service of the product, the aggregation model is used to cluster the scenario objects, the domain object model is used to carry the logic of the modeling scenario, the domain service model is used to carry different combined services of the product in the domain, and the domain behavior design model is used to derive the service strategy and object behavior of the product in the domain.

17. A modeling method, characterized in that: include: In response to an input instruction on the operation interface, a plurality of models of the product to be built are displayed on the operation interface, wherein different models to be built are used to represent different modeling stages of the product; In response to a processing instruction acting on the operation interface, a target model of the product is displayed on the operation interface, wherein the target model is obtained by modeling multiple structured models based on the association results between multiple structured models corresponding to the multiple models to be modeled, the structured model is a resource for at least representing the modeling process of the model to be modeled, the association results are used to represent the logical relationship between the multiple structured models, and the structured model is obtained by structuring the model to be modeled.

18. A modeling system of a model, characterized in that: include: A client, used to upload multiple models of a product to be built, wherein different models of the product to be built are used to represent different modeling stages of the product; The server is connected to the client and is used to perform structured processing on the model to be modeled to obtain at least one structured model, wherein the structured model is a resource used to at least represent the modeling process of the model to be modeled; determine the association results between multiple structured models corresponding to multiple models to be modeled, wherein the association results are used to represent the logical relationship between the multiple structured models; based on the association results, model the multiple structured models to obtain the target model of the product; and send the target model to the client.

19. A computing device, characterized in that include: A memory storing an executable program; A processor, configured to run the program, wherein the program executes the method according to any one of claims 1 to 17 when running.

20. An electronic device, characterized in that: include: A memory storing an executable program; A processor, connected to the memory via a bus, and configured to run the program, wherein the program executes the method described in any one of claims 1 to 17 when running.

Images