Modeling Method, System, Electronic Device, and Storage Medium

Abstract

The present application discloses a modeling method, system, electronic device, and storage medium for a model, relating to the field of computer technology. Among them, the method includes: determining a plurality of models to be modeled for a product, where different models to be modeled are used to represent different modeling stages of the product; performing a structuring process on the models to be modeled to obtain at least one structured model, where the structured model is a resource for at least representing the modeling process of the models to be modeled; determining an association result between a plurality of structured models corresponding to the plurality of models to be modeled, where the association result is used to represent the logical relationship of mutual association between the plurality of structured models; and based on the association result, performing modeling on the plurality of structured models to obtain a target model of the product. The present application solves the technical problem of poor modeling effect of the model.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more particularly, to a method, system, electronic device, and storage medium for modeling a model. Background Art

[0002] Currently, modeling design usually includes scene 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 disjoint from implementation, and does not pay attention to the association and consistency between different modeling design stages, thus resulting in a poor effect of model modeling.

[0003] In response to the above problems, no effective solution has been proposed yet. Summary of the Invention

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

[0005] According to one aspect of the embodiments of this application, a method for modeling a model is provided. The method may include: determining a plurality of models to be modeled for a product, where different models to be modeled are used to represent different modeling stages of the product; performing a structuring process on the models to be modeled to obtain at least one structured model, where the structured model is a resource for at least representing the modeling process of the models to be modeled; determining an association result between a plurality of structured models corresponding to the plurality of models to be modeled, where the association result is used to represent the logical relationship of mutual association between 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.

[0006] According to another aspect of the embodiments of this application, a method for modeling a model is provided. The method may include: in response to an input instruction acting on an operation interface, displaying a plurality of models to be modeled for a product on the operation interface, where different models to be modeled are used to represent different modeling stages of the product; and in response to a processing instruction acting on the operation interface, displaying a target model of the product on the operation interface, where the target model is obtained by modeling a plurality of structured models based on an association result between the plurality of structured models corresponding to the plurality of models to be modeled, the structured model is a resource for at least representing the modeling process of the models to be modeled, the association result is used to represent the logical relationship of mutual association between the plurality of structured models, and the structured model is obtained by performing a structuring process on the models to be modeled.

[0007] According to another aspect of the embodiments of the present application, a modeling system for a model is provided. The system may include: a client for uploading multiple models to be modeled of a product, where different models to be modeled are used to represent different modeling stages of the product; a server connected to the client for performing structured processing on the models to be modeled to obtain at least one structured model, where the structured model is a resource for at least representing the modeling process of the models to be modeled; determining an association result between multiple structured models corresponding to the multiple models to be modeled, where the association result is used to represent the logical relationship of mutual association between the multiple structured models; based on the association result, performing modeling on 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 the embodiments of the present application, a computing device is further provided. The computing device may include a memory and a processor: the memory is used for storing an executable program; the processor is used for running the program, where when the program runs, it executes the modeling method of the model in any one of the above.

[0009] According to another aspect of the embodiments of the present application, an electronic device is further provided. The electronic device may include a memory and a processor: the memory is used for storing computer-executable instructions, and the processor is used for executing the computer-executable instructions. When the computer-executable instructions are executed by the processor, the modeling method of the model in any one of the above is implemented.

[0010] According to another aspect of the embodiments of the present application, a processor is further provided. The processor is used for running a program, where when the program runs, it executes the modeling method of the model in any one of the above.

[0011] According to another aspect of the embodiments of the present application, a computer-readable storage medium is further provided. The computer-readable storage medium includes a stored program, where when the program runs, it controls the device where the storage medium is located to execute the modeling method of the model in any one of the above.

[0012] According to another aspect of the embodiments of the present application, a computer program product is further provided, including a non-volatile computer-readable storage medium. The non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the modeling method of the model in any one of the above is implemented.

[0013] In the embodiments of the present application, multiple models to be modeled for a product are determined, where different models to be modeled are used to represent different modeling stages of the product; the models to be modeled are structurally processed to obtain at least one structured model, where the structured model is a resource used to represent at least the modeling process of the models to be modeled; the association result between multiple structured models corresponding to the multiple models to be modeled is determined, where the association result is used to represent the logical relationship of mutual association between the multiple structured models; based on the association result, the multiple structured models are modeled to obtain the target model of the product. That is to say, the embodiments of the present application carry and cover the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the models to be modeled through the linkage system of the structured model, so as to achieve the purpose of paying attention to the association and consistency between different modeling stages through the association between the structured models, and further realizing the improvement of the model modeling effect 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 exemplifying and explaining the present application and do not constitute a limitation to 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 to the present application. In the drawings:

[0016] 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;

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

[0018] Figure 3 is a flowchart of another modeling method of a 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 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 the logical relationship between different modeling stages according to an embodiment of the present application;

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

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

[0024] Figure 9 It is a schematic diagram showing the internal model association of a bounded context according to an embodiment of the present application;

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

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

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

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

[0029] Figure 14 It is a block diagram of an electronic device for a modeling method of a model according to an embodiment of the present application;

[0030] Figure 15 It is a hardware structural 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 implementation manners

[0031] In order to enable those skilled in the art of the present technology to better understand the solution of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0032] It should be noted that the terms "first", "second", etc. in the description, claims and the above-mentioned drawings of this application are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of this application described here can be implemented in an order other than those illustrated or described here. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily limit to those steps or units clearly listed, but may include other steps or units 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 for analysis, stored data, displayed data, etc.) involved in this application, for example, 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 need to comply with the relevant laws, regulations and standards of relevant countries and regions, and corresponding operation entrances are provided for users to choose to authorize or refuse.

[0034] First, some nouns or terms that appear in the process of describing the embodiments of this application are applicable to the following explanations:

[0035] A structured model refers to a model carried by structured data to achieve purposes such as online, versioning, linkage, real-time verification, rationality analysis, precipitation and distribution of the structured model;

[0036] Model linkage refers to the relationship network formed among structured models. When a node in a structured model changes, it 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 by the embodiments of this application can be applied to the Figure 1 application scenarios shown, but not limited thereto. Figure 1 It is a schematic diagram of the application scenario of a modeling method of a model according to the embodiments of this application. As shown in Figure 1In the application scenario shown, the server 10 can be a cloud. The server 10 can connect to one or more client devices 20 through a local area network connection, a wide area network connection, an Internet connection, or other types of data networks. Here, the client devices 20 can include, but are not limited to: smart phones, tablet computers, laptop computers, personal digital assistants, personal computers, smart home devices, in-vehicle devices, etc. The client devices together constitute the client opposite to the server. An operation interface for obtaining multiple models to be modeled of the product can be deployed on the graphical user interface of the client device. The client device 20 can interact with the user through the graphical user interface to implement the model modeling method provided by the embodiments of the present application.

[0039] In the embodiments of the present application, the system composed of the client device 20 and the server 10 can perform the following steps: Execute 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, where different models to be modeled are used to represent different modeling stages of the product; Step S104, perform a structuring process on the models to be modeled to obtain at least one structured model, where the structured model is a resource used to at least represent the modeling process of the models to be modeled; Step S106, determine the association result between multiple structured models corresponding to the multiple models to be modeled, where the association result is used to represent the logical relationship of mutual association between the multiple structured models; Step S108, based on the association result, perform modeling on the multiple structured models to obtain the target model of the product.

[0040] In the above operating environment, the present application provides a Figure 2 model modeling method as shown. Figure 2 It is a flowchart of a model modeling method according to an embodiment of the present application. As Figure 2 shown, the method can include the following steps:

[0041] Step S202, determine multiple models to be modeled of the product.

[0042] In the technical solution provided in step S202 of the present application, multiple models to be modeled for the product can be determined. Among them, the product can be an auxiliary tool or platform used in the design and development of software (for example, the BizWorks modeling platform). The product can be used to carry the modeling methodology for the models to be modeled, and the models to be modeled can be used to represent each design stage in the entire development process. Optionally, taking the BizWorks modeling platform as an example, this platform covers the entire process from requirement analysis, scenario modeling, technical design to code implementation. The BizWorks modeling platform can be regarded as a combination of a design software and a specification manual. The design software can provide a graphical interface and tools to help developers create, edit, and maintain structured models in different modeling stages. The specification manual incorporates a series of modeling methodologies and rules 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 referred to as the modeling design stage, and the modeling stage can at least include: the domain modeling stage, the scenario modeling stage, the technical modeling stage, the assembly modeling stage, etc. The models to be modeled can at least include: the domain modeling model, the scenario modeling model, the technical modeling model, the assembly modeling model, etc. Among them, the domain modeling model is based on the principles of domain-driven design, converting scenario requirements into models that can be implemented by software. The domain modeling model is represented in the form of diagrams, such as entity relationship diagrams, state diagrams, behavior diagrams, etc., and is also represented in the form of structured data. The scenario modeling model is a model that connects scenario requirements and technical implementation. The scenario modeling model can also be represented in the form of diagrams, such as flowcharts, activity diagrams, etc., and is also represented in the form of structured data. The structured data can be used to describe the nodes of the scenario modeling process, the attributes and relationships of scenario modeling objects, etc. The technical modeling model is a model that transforms the abstractions of scenario modeling into technical designs. The technical modeling model can be represented by diagrams, such as component diagrams, deployment diagrams, interface diagrams, etc., but the technical modeling model is more represented in the form of structured data, such as configuration files, architecture documents, etc. The assembly modeling model is a model that designs scenario capabilities (or functions) as independent and assemblable 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 the form of expression. Through structured data, online support for the models, version control, real-time verification, rationality analysis, and difference comparison, etc., can be achieved.

[0044] Optionally, while effectively carrying the modeling methodology, the above product can also serve as a specification in the modeling process (modeling design process). Since the above product can help the design team to carry out modeling design work in a standardized way, for example, clarify the work process, standardize the operation steps, and unify the design standards, so as to carry out modeling design work more systematically and standardly, ensuring the consistency and reliability of the modeling results. Therefore, the above product itself is an embodiment of the specification, that is to say, using the product means following the specification.

[0045] Step S204: Perform a structuring process on the model to be modeled to obtain at least one structured model.

[0046] In the technical solution provided in 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. Among them, the structured model can be a resource for at least representing the modeling process of the model to be modeled. For example, the structured model can be a type of scenario asset data or model asset.

[0047] It should be noted that the structuring process can be a systematic and orderly process for the model to be modeled to ensure that the model to be modeled has a clear structure and organization, facilitating analysis and understanding. The structuring process includes, but is not limited to: data cleaning, feature selection, feature transformation, selecting appropriate modeling algorithms and model structures. The structuring process 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, incorrect, 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 stage of the model to be modeled. Feature selection can be used to determine the input variables that are helpful for predicting the model to be modeled, and relevant elements that can reflect the scenario requirements can be selected from a large number of candidate model elements. Feature transformation refers to converting the elements of the model to be modeled into a form that is conducive to modeling. By performing a structuring process 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, performing a structuring process on the scenario modeling model can obtain structured models such as a scenario domain model, a domain architecture model, a scenario process model, a story model, and a scenario object model. When the model to be modeled is a technical modeling model, performing a structuring process on the technical modeling model can obtain structured models such as a bounded context model, a bounded context mapping derivation model, an application service model, an aggregation model, a domain object model, a domain service model, and a domain behavior design model.

[0049] For example, taking the online shopping scenario as an example, the scenario modeling model is described through data cleaning and feature selection and other structured processing to obtain the above-mentioned structured model. In the online shopping scenario, the original user story description may include a large amount of natural language text, describing the entire process of a user from browsing products to completing payment. Through data cleaning and feature selection and other structured processing of the user story description, a scenario domain model can be obtained that defines core domain objects such as products, users, and orders, as well as the relationships and rules between domain objects: Based on the scenario domain model, different bounded contexts such as product management, order processing, and payment processing are divided, and a 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 making payments, as well as a scenario process model of the preconditions and postconditions of each step; a structured story model of the user story description; a scenario object model that describes each object and entity involved in a specific scenario. For example, a product has attributes such as name and price, and an order is related to entities such as products, users, and payments.

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

[0051] In the technical solution provided in step S206 of the present application above, after performing structured processing on the models to be modeled to obtain multiple structured models, the association result between multiple structured models corresponding to multiple models to be modeled can be determined. Among them, the association result can be used to represent the logical relationship of mutual association between multiple structured models.

[0052] Optionally, after obtaining multiple structured models, based on predefined association rules, an association mapping between structured models can be created. For example, a reference pointing from a structured model to a structured model to be associated can be created, or the structured information of the structured model to be associated can be embedded in the structured model. Based on this association mapping, the association between structured models can be clarified, and thus the association result between 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 products to the shopping cart and complete the payment. In the technical modeling phase, a bounded context and a microservice architecture are created, which include two bounded contexts: shopping cart management and payment processing. In the code model phase, a specific code structure and class definitions are generated. By creating a reference in the description of the shopping cart management bounded context that points to the story of adding products to the shopping cart in the user story model, a reference to a structured model can be created to point to another structured model to be associated. In the model describing the process of adding products 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, actions such as the user needs to log in, select products, and click the add-to-cart button can be detailed, and the postcondition of the update of the shopping cart status after successfully adding products can be implemented to embed the structured information of the structured model to be associated in the structured model.

[0054] Optionally, the two-way linkage between structured models can be achieved by sharing data or variables between the structured models. When the data or variables in one structured model change, the other structured model will also be updated or adjusted accordingly. This two-way linkage can ensure the consistency and coordination between structured models. The two-way linkage can also be achieved by mutual invocation or nesting between structured models. One structured model can call the functions or methods 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, multiple structured models corresponding to the scenario modeling model can include: scenario domain model, domain architecture model, scenario process model, story model, scenario object model, etc. Then the association result can be the association result between the scenario domain model and the story model, and this association result can be used to represent the two-way linkage between the scenario domain model and the story model. That is, changes in the scenario domain model will affect the story model, and changes in the story model will also affect the scenario domain model. The association result can also be the association result between the scenario domain model and the scenario object model, and this association result can be used to represent the two-way linkage between the scenario domain model and the scenario object model. That is, changes in the scenario domain model will affect the scenario object model, and changes in the scenario object model will also affect the scenario domain model.

[0056] For another example, because of the two-way linkage between the above-mentioned scenario domain model and the story model and the scenario object model respectively, when any one 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, and domain behavior design model. The association result may be the association result between the bounded context model and the scenario domain model, and may also be 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, therefore, 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, 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, model the multiple structured models to obtain the target model of the product.

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

[0060] In this embodiment, the target model may be a linkage system of structured models. After obtaining the association result between the multiple structured models, based on this association result, the multiple structured models can be modeled in the following way to obtain the linkage system of structured models: identify the relationships between different structured models, and according to the dependencies and interactions between the structured models, define rules to guide the linkage of the structured models to achieve two-way linkage between the structured models. For example, based on the dependency relationship and interaction relationship between the 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 an attribute of an entity is 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, record the version information and change log of each structured model update, support version backtracking and difference comparison of structured models. Use automated tools to automatically generate code frameworks or documents based on structured models. The linkage system of structured models supports the continuous integration and continuous deployment processes of software development, ensuring 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 promptly detect unreasonable aspects in the design, avoiding a large amount 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 this application, multiple models to be modeled of the product are determined, where different models to be modeled are used to represent different modeling stages of the product; the models to be modeled are structurally processed to obtain at least one structured model, where the structured model is a resource used to at least represent the modeling process of the models to be modeled; the association result between the multiple structured models corresponding to the multiple models to be modeled is determined, where the association result is used to represent the logical relationship of mutual association between the multiple structured models; based on the association result, the multiple structured models are modeled to obtain the target model of the product. That is to say, the embodiment of this application uses the linkage system of the structured model to carry and cover the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the models to be modeled, thereby achieving the purpose of paying attention to the association and consistency between different modeling stages through the association between the structured models, and further realizing the improvement of the model modeling effect and solving the technical problem of poor model modeling effect.

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

[0064] As an optional implementation manner, structurally processing the models to be modeled to obtain at least one structured model includes: determining the modeling strategy of the models to be modeled, where the modeling strategy is used to represent the rules for modeling the models to be modeled; according to the modeling strategy, structurally processing the models to be modeled to obtain the 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 the modeling methodology. After determining the multiple models to be modeled of the product, the models to be modeled can be structurally processed according to the above modeling methodology to obtain the structured model.

[0066] Optionally, according to the modeling methodology, the elements of the models to be modeled can be identified. For example, in the domain modeling stage, the elements of the models to be modeled can include domain, sub-domain, aggregation, entity, value object, domain event, etc. Converting the above-identified elements of the models to be modeled into structured data, and custom data structures can be used to represent the attributes and relationships of each element. Further, based on the structured data, the association relationships between the models are designed to obtain the structured model.

[0067] It should be noted that a domain refers to a specific scope of a scenario and can be composed of some common scenario rules and concepts. For example, in the e-commerce domain, the domain can include product management, order processing, inventory management, payment processing, etc. A sub-domain is a subdivision of a domain and can focus on a specific scenario function or concept set within the domain. For example, the product management domain can include sub-domains such as product listing, delisting, classification, and search. Aggregation can be used to encapsulate some related entities. The root entity of an aggregation is usually a domain object that provides access to and control over the internal objects of the aggregation. For example, in the order processing domain, an order can be an aggregation root and can contain multiple related entities such as order lines, shipping addresses, and order statuses. The operations and status updates of these entities are carried out through the order object. An entity is a domain object with a unique identifier. For example, in e-commerce, users, products, orders, etc. are entities. A value object is a domain object without a unique identifier, and the equality of a value object is determined by its attribute values. For example, in the product management domain, the product price is a value object, and the equality of the product price is determined by the unit price of the product. Domain events can be used to represent important changes that occur in a domain and can be listened to and responded to by multiple sub-domains or services for realizing collaboration and asynchronous communication within the domain. For example, in the e-commerce domain, when the inventory of a product in the product management domain decreases, a domain event can be triggered, and this event can be listened to by the order processing domain to ensure that sufficient inventory is checked when processing an order.

[0068] In this embodiment, the to-be-modeled model is structured according to the modeling methodology, and the obtained structured model can clearly express the associations between different modeling stages. For example, the association between the scenario modeling model and the technical modeling model. This association design can support the linked 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 alternative implementation, according to the modeling strategy, the to-be-modeled model is structured to obtain a structured model, including: determining the structured data of the to-be-modeled model according to the modeling strategy, where the structured data is used to carry the modeling process of the to-be-modeled model; and using the structured data to perform online structuring on the to-be-modeled model to obtain a structured model.

[0070] In this embodiment, the structured data can be used to carry the structured model. After determining the modeling methodology of the to-be-modeled model, according to the modeling methodology, the structured data of the to-be-modeled model can be determined, and further using the determined structured data to perform online structuring on the to-be-modeled model, a structured model can be obtained.

[0071] Optionally, by selecting an online modeling tool, import the model to be modeled into the online modeling tool. In this online modeling tool, identify the elements of the model to be modeled according to the modeling methodology, convert the identified elements of the model to be modeled into structured data, and further design the association relationships between the models based on the structured data, so as to obtain a structured model, that is, there are association relationships between the structured models.

[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 be completed online, thus solving the problems of long-term sustainable iteration and low management efficiency of the structured model caused by the situation where a large amount of manual sorting and management are carried out through 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 alternative implementation, use the structured data to perform online structured processing on the model to be modeled to obtain a structured model, including: verifying the structured data; using the verified structured data to perform online structured processing on the model to be modeled to obtain a structured model.

[0074] In this embodiment, after converting the elements of the model to be modeled into structured data, the structured data can be verified according to the verification rules. After the verification of the structured data passes, the verified structured data can be used to perform online structured processing on the model to be modeled to obtain a structured model. Among them, the verification rules can be rules for verifying the correctness, design rationality, etc. of the structured data set according to the actual situation in advance, and these verification rules can be continuously supplemented during actual use.

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

[0076] As another example, based on the verification rules, the impact of incorrect deletion of structured data can be prevented. For instance, when deleting a certain piece of structured data, if this 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 this structured data, which will affect the correctness and integrity of the structured model. Through verifying whether the structured model has been incorrectly deleted, this embodiment can prevent the above-mentioned error problems caused by the deletion operation.

[0077] As 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, while entities and value objects cannot directly cross the boundary. Then, the rationality verification of the aggregate design passes, thus ensuring the clarity of the scenario logic and the maintainability of the code.

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

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

[0080] In this embodiment, a version control system can be used to manage the versions of the structured model. The version number of the structured model can consist of three numbers, representing the major version, minor version, and patch version respectively. When important interfaces change and affect the systems using the existing structured model, the major version number can be increased. When adding functions without breaking the compatibility of the existing structured model, the minor version number can be increased. When fixing bugs or making minor adjustments without changing the functions or interfaces of the structured model, the patch version number can be increased. By using the version control system to automatically record each change of the structured model, the version number of the new version can be automatically determined according to the nature of the changes of the structured model, and the structured model of the new version can be published.

[0081] This embodiment version-manages the structured model as design asset data, which can flexibly support the release and iteration of the structured model versions. Through version management, the change history of the structured model can be clearly traced, and the modified content and reasons of the structured model can be understood.

[0082] As an optional implementation manner, performing structured processing on the model to be modeled to obtain at least one structured model includes: determining the knowledge data required by the model to be modeled, as well as the modeling products during the modeling process of the model to be modeled, where the knowledge data is used to represent the knowledge in the modeling scenario to which the product belongs; and determining at least one structured model in the resource database of the product 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 scenario knowledge, and the knowledge data can at least include scenario processes, scenario activities, scenario domain architectures, scenario objects, etc. The modeling products can be the design products of the modeling. For example, the modeling products can at least include design patterns, architecture decisions, technical implementation solutions, user stories, requirement documents, etc. The resource database can include various scenario asset data.

[0084] Optionally, as a kind of scenario asset data, the structured model not only captures the scenario processes, rules, and structures, but also contains the logic and implementation details of the design decisions, thus becoming the carrier of scenario knowledge and design products. The scenario knowledge such as scenario processes, scenario activities, scenario domain architectures, 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 during the modeling design process can be defined. Further, from the product's resource database, a structured model that can carry the above-mentioned scenario knowledge and design products can be selected.

[0085] In this embodiment, as a kind of scenario asset data, the structured model carries important scenario knowledge, design processes, and design products, thus achieving the purpose of continuous precipitation and rapid reuse.

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

[0087] In this embodiment, the initial structured model can be an existing structured model that carries knowledge data and modeling products. The code development requirement information can be used to represent the code development requirements of the structured model to be determined. An initial structured model that carries scenario knowledge and design products, that is, an existing structured model, can be determined from the resource database. When the scenario requirements change, the initial structured model can be adjusted by modifying the initial structured model file or adjusting the initial structured model 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 build process. After the above development is completed, a code reverse engineering tool can be used to extract new model information to update or create a new structured model.

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

[0089] In this embodiment, the existing structured model is adjusted and code is quickly generated for development. After development, the newly generated structured model is further refined into a new model asset, achieving the purpose of continuous iteration of the structured model and automatic code generation. Thus, it realizes the rapid conversion and feedback from conceptual design to technical implementation, improves software development efficiency, reduces repetitive labor, and ensures code quality.

[0090] As an alternative implementation, determining the association result between multiple structured models corresponding to multiple models to be modeled includes: determining the model elements in the models to be modeled, where the model elements are used to represent data associated with the upstream model and / or downstream model of the model to be modeled among multiple models to be modeled; and determining the association result 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 among multiple models to be modeled, and can also be referred to as 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 components, event consumers, event producers, etc.

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

[0093] This embodiment determines the association result between multiple structured models based on the model elements. Since the flexibility of the model elements allows for local adjustments in the design without disrupting the overall structure of the system, the association result between the determined structured models can more clearly show the cascading impact of adjusting the structured model, thus improving the convenience of adding new functions or adjusting existing functions.

[0094] As an alternative implementation, determining the model elements in the model to be modeled includes: determining multiple sub-processes of the model to be modeled, where the sub-processes are used to constitute the modeling process of the model to be modeled; in response to the sub-processes cascading 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, the sub-processes can be used to constitute the modeling process of the model to be modeled. The multiple sub-processes have process levels, and the 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 nesting relationship between the above 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-processes cascade the upstream model and / or downstream model in the model to be modeled, the model elements can be further determined based on the above sub-processes. For example, the above sub-processes can be determined as the model elements.

[0097] This embodiment determines the model elements based on the sub-processes and affects the upstream and downstream models through the cascading mechanism, which can significantly improve the efficiency, accuracy, and consistency of the structured model design. At the same time, it simplifies the development process and improves the maintainability and scalability of the system.

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

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

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

[0101] As an alternative implementation, determining the association result between multiple structured models based on the model elements includes: establishing a connection network between multiple structured models according to the model elements, where the model nodes in the connection network change as the associated model nodes of the model nodes in the connection network change.

[0102] In this embodiment, the associated network can be a network in which different structured models are organized and associated in a structured manner, and the structured models are interconnected with each other, and it can also be called a relationship network. In the associated network, each structured model can be regarded as a model node, and the edges represent the relationships and dependencies between the structured models. The associated network presents a hierarchical structure, where some models (such as the scenario modeling model) are at a higher level, while other models (such as the code model) are at a lower level. The high-level models can guide the design and implementation of the low-level models, and the changes in the low-level models will also feedback and affect the high-level models, forming a closed-loop linkage.

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

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

[0105] The advantage of the structured model in this embodiment is that after the model is structured, an associated network is formed, and the change energy levels of the model nodes can be cascaded and updated. That is, the change of a model node can cascade and affect other nodes associated with it, thus facilitating the analysis and query of the structured model.

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

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

[0108] In this embodiment, multiple structured models are modeled according to the association network, which can establish the association between structured models, ensuring the unity and integrity of information between structured models. The changes in each structured model can cascade and affect the associated models, enabling each step in the modeling design process to be traced. At the same time, it is also convenient for the maintenance and update of structured models, ensuring the sustainability of the modeling design.

[0109] As an alternative implementation, the method further includes: in the target model, determining the code model corresponding to the structured model, where the code model is developed using the code of the structured model; determining the difference information between the code model and the structured model; performing structured processing on 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 developed using the code of the structured model. Based on the structured model, code can be generated, and by developing the code, the above-mentioned code model can be obtained. 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 this difference information can be used to indicate whether there are deviations in the implementation and design of the structured model. Among them, the code of the structured model can be the specific code representation obtained by converting the structured model into a programming language through the code model.

[0111] Optionally, structuring the above difference information can obtain the structured difference information, that is, the difference information is stored in the form of structured data for subsequent processing. Using the structured difference information to update the code model, the difference information can be parsed into specific operation instructions. For example, which codes need to be added, which codes need to be modified or deleted. According to the parsed operation instructions, an automated script or an update tool integrated in the development platform is used to update the code model.

[0112] Furthermore, using the updated code model to update the target model, the updated code model can be compared with the structured model to identify the model differences caused by the change of the code model. Based on the comparison result between the updated code model and the structured model, the structured model is adjusted to reflect the actual implemented state of the updated code, thereby obtaining the updated target model. For example, if new classes or interfaces appear in the updated code model, corresponding descriptions, such as the attributes and relationships of the class or interface, can be added to the structured model.

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

[0114] As an alternative implementation, determine multiple models to be modeled for the product, including: determining the modeling scenario to which the product belongs; determining the models to be modeled under the modeling scenario.

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

[0116] This embodiment can comprehensively analyze the scenario process, data structure, user interaction, architecture design, etc. from multiple angles and levels through diverse modeling scenarios, ensuring the depth and comprehensiveness of the modeling design, thereby providing a comprehensive perspective on the modeling design and implementation.

[0117] As an alternative implementation, perform structured processing on the model to be modeled to obtain at least one structured model, including: in response to the model to be modeled being a scenario modeling model, perform structured processing on the scenario modeling model to obtain at least one of the following structured models: scenario domain model, domain architecture model, scenario process model, story model, scenario object model, where 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 different levels of processes under the modeling scenario, the story model is used to represent the use cases under the modeling scenario, and the scenario object model is used to represent the scenario objects under the modeling scenario.

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

[0119] Optionally, the domain architecture model describes the component structure within the scenario domain and the relationships between component structures, and is an extension of the scenario domain model. The domain architecture model can at least include bounded contexts, the relationships 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 between technical implementation and scenario requirements, and guide the boundary division of microservices or modules.

[0120] It should be noted that the association result 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 entities in the scenario domain model are first identified and analyzed to determine the scenario domain to which the entity belongs. Then, according to the scope and boundary of the scenario domain, the entity is mapped to the corresponding bounded context in the domain architecture model. For instance, 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 among one or more scenario entities, defining the order, roles, and trigger conditions of scenario activities. The scenario process model can at least include activity nodes, swimlanes (representing the organizations or roles that execute activities), message flows, events, etc. The scenario process model can be used to identify and optimize scenario processes, ensure that the modeling design can support and enhance scenario operations, improve efficiency, and reduce errors. The scenario process model can also support nested associations of multi-level sub-processes, namely L1-L5 processes. L1 can be used to represent the highest-level main process, L2 can be used to represent the sub-process under L1, and so on.

[0122] Optionally, the story model can also be called the user story model. The user story model describes the functions that the system should provide from the perspective of users. The user story model can at least include users, actions, results, and possible preconditions and postconditions. The user story model can structurally decompose information such as the preconditions, trigger conditions, postconditions, execution steps, constraint rules, and acceptance conditions of use cases, and can be used as the input for the bounded context mapping derivation models of subsequent product requirements documents (Product Requirements Document, abbreviated as PRD) use cases and technical modeling models. That is, the above-structurally decomposed information is used as the input for the bounded context mapping derivation models of subsequent PRD use cases and technical modeling models.

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

[0124] This embodiment structures the scenario modeling model into the above-mentioned structured model, which can comprehensively understand the scenario requirements and modeling design goals, ensure a high degree of consistency between the technical implementation and the scenario requirements, improve the development efficiency, reduce errors and maintenance costs, and at the same time improve the quality of the product and the user experience.

[0125] As an alternative 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 scenario domain model and the story model and the scenario object model respectively; determining the association result between the domain architecture model and the scenario domain model; determining the association results between the scenario process model and the story model and the scenario object model respectively.

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

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

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

[0129] Optionally, the scenario domain model describes 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 transformed into technical components and boundaries in the domain architecture model, such as bounded contexts and microservices.

[0130] Optionally, the 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 ensure that when modeling and implementing functions, the user requirements are accurately understood and executed. For example, the user story model describes how to place an order, while the scenario process model details the steps from order creation to order completion, including inventory checking, payment confirmation, etc., which helps developers build a process that matches the user story model.

[0131] Optionally, when designing the scenario process model, specific scenario objects are needed to support the execution of the process. For example, if the process includes "updating customer information", then there needs to be a "customer" scenario object to carry the logic of information update. By associating the scenario process model with the scenario object model, the above requirements can be achieved.

[0132] It should be noted that after associating or mapping the elements of different models as described above, the mutual correspondence and dependency relationships between the different models are the association results of the models. For example, the scenario entities and rules in the above 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 to the microservice elements in the domain architecture model, which is the process of determining the association results of the scenario domain model and the domain architecture model.

[0133] 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 by determining the association results between the scenario domain model and the story model, reducing the misunderstanding 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 design stage. By determining the association results between the domain architecture model and the scenario domain model, it ensures 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 can ensure that each step in the scenario process conforms to the scenario rules and verify the rationality of the process through the scenario object model. That is, this embodiment can ensure the consistency between scenario requirements and technical implementation by determining the association results between the above-mentioned structured models.

[0134] As an alternative 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, structuring the technical modeling model to obtain at least one of the following structured models: a bounded context model, a bounded context mapping derivation model, an application service model, an aggregation model, a domain object model, a domain service model, a domain behavior design model, where the bounded context model is used to represent the carrier that associates the scenario modeling model and the technical modeling model, the bounded context mapping derivation 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 services 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 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.

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

[0136] Optionally, the application service model is derived through the bounded context mapping derivation model or created from scratch (0-1). The application service model can be used to subsequently generate an Application Programming Interface (API) interface. Among them, there are two ways to generate the application service model. The first way is to derive it through the bounded context mapping derivation model and then publish and generate it. The second way is 0-1 creation, that is, directly create the application service model on the platform without derivation, usually for the case where it is already relatively clear which application service models are needed.

[0137] Optionally, the aggregation model can be used to better classify the domain object model according to scenario cohesion, and the aggregations should maintain loose coupling, and only cross-aggregation calls are made through the aggregation root. The service capabilities related to the aggregation are encapsulated and exposed externally through the aggregation root model.

[0138] Optionally, the domain object model can be batch-generated based on the scenario object model. The domain object model is the key model that carries scenario logic. The domain object model is divided into multiple model types such as aggregate root, entity, and value object according to responsibilities. The domain service model can be used to carry service combinations across aggregates. The input parameters and output parameters (i.e., input and output parameters) of the domain service model need to use the domain object model. The domain behavior design model takes the application service model or the domain event model as the entry point, and further analyzes and derives the capabilities that need to be precipitated in the domain layer within a bounded context model, namely domain service methods and domain object behaviors.

[0139] In this embodiment, by structuring the technical modeling model into the above-mentioned multiple structural models, the two-way linkage from scenario requirements to technical implementation is realized. While supporting the 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 structuring process 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 alternative 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 result between the bounded context model and the scenario domain model; determining the association results between the bounded context mapping derivation model and the bounded context model and the story model respectively; determining the association result between the application service model and the bounded context mapping derivation model; determining the association result between the aggregation model and the domain object model; determining the association result between the domain service model and the domain object model; determining the association result 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 division of the scenario domain model. The bounded context mapping derivation model is associated with the bounded context model and the story model respectively, that is, the bounded context mapping derivation model can derive the application service model based on the bounded context model and the story model. 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 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 precipitated in the domain layer within the bounded context model, namely domain service methods and domain object behaviors.

[0143] In this embodiment, by determining the association results between structured models, the coherence of the entire design system from macro to micro is ensured, and the consistency at different levels such as the scenario domain, technical implementation, and code model is guaranteed. The association between structured models helps the development team quickly locate the context of function implementation, reduces the understanding cost, and improves the coding efficiency. At the same time, model-based development can reduce human errors and improve the 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 alternative implementation, the model to be modeled includes one of the following models of the product: domain modeling model, assembly modeling model, code model, process modeling model, and data modeling model.

[0145] In this embodiment, the above-mentioned scenario modeling model and technical modeling model can form a domain modeling model. The scenario modeling model, technical modeling model, domain modeling model, and code model can form an assembly modeling model. The code model can be used to extract key information on the code side. For example, through tool assistance or automation extraction, the code model can be used to express the implementation of the code for the landing of model design elements. The code model can at least include application service code model, structure 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.

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

[0147] In the embodiments of the present application, multiple models to be modeled of a product are determined, where different models to be modeled are used to represent different modeling stages of the product; the models to be modeled are structurally processed to obtain at least one structural model, where the structural model is a resource used to represent at least the modeling process of the models to be modeled; the association result between multiple structural models corresponding to the multiple models to be modeled is determined, where the association result is used to represent the logical relationship of mutual association between the multiple structural models; based on the association result, the multiple structural models are modeled to obtain the target model of the product. That is to say, through the linkage system of the structural model, the embodiments of the present application carry and cover the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the models to be modeled, so as to achieve the purpose of paying attention to the association and consistency between different modeling stages through the association between the structural models, and further realizing the improvement of the model modeling effect and solving the technical problem of poor model modeling effect.

[0148] The embodiments of the present application also provide a method for modeling a model, Figure 3 which is a flowchart of another method for modeling a model according to the embodiments of the present application, as Figure 3 shown. The method may include the following steps:

[0149] Step S302, in response to an input instruction acting on the operation interface, display multiple models to be modeled of the product on the operation interface, where different models to be modeled are used to represent different modeling stages of the product.

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

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

[0152] Optionally, while carrying the effective bearing modeling methodology, the above product can also be used as a specification in the modeling process (modeling design process). Since the above product can help the design team carry out modeling design work in a standardized manner, for example, clarify the work process, standardize the operation steps, and unify the design standards, so as to carry out modeling design work more systematically and standardly, ensuring the consistency and reliability of the modeling results. Therefore, the above product itself is an embodiment of the specification, that is to say, using the product means following the specification.

[0153] Step S304: In response to a processing instruction acting on the operation interface, display the target model of the product on the operation interface, where the target model is obtained by modeling multiple structured models based on the association result between multiple structured models corresponding to 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, and the association result is used to represent the logical relationship of mutual association between multiple structured models. The structured model is obtained by performing structured processing on the model to be modeled.

[0154] In the technical solution provided in step S304 of the present application, the processing instruction can be an instruction for processing multiple models to be modeled. In response to the processing instruction acting on the operation interface, multiple models to be modeled can be transmitted to the server, and the server processes the multiple models to be modeled to obtain the 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 type of scenario asset data or model asset. Structured processing can be to perform systematic and orderly processing on the model to be modeled to ensure that the model to be modeled has a clear structure and organization, facilitating analysis and understanding. Structured processing includes, but is not limited to: data cleaning, feature selection, feature transformation, and selecting appropriate modeling algorithms and model structures. By performing structured 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, performing structured processing on the scenario modeling model can obtain structured models such as a scenario domain model, a domain architecture model, a scenario process model, a story model, and a scenario object model. When the model to be modeled is a technical modeling model, performing structured processing on the technical modeling model can obtain structured models such as a bounded context model, a bounded context mapping derivation model, an application service model, an aggregation model, a domain object model, a domain service model, and a domain behavior design model.

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

[0158] For another example, since the above-mentioned scenario domain model is in two-way linkage with the story model and the scenario object model respectively, when any one of the above-mentioned structured models changes, it will cascade and affect other structured models.

[0159] Optionally, the two-way 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, another structured model will also be updated or adjusted accordingly. This two-way linkage can ensure the consistency and coordination between structured models. The two-way linkage can also be achieved by mutual invocation or nesting between structured models. One structured model can call the functions or methods 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 technology modeling model may include: a bounded context model, a bounded context mapping derivation model, an application service model, an aggregation model, a domain object model, a domain service model, and a domain behavior design model. The association result may be the association result between the bounded context model and the scenario domain model, and may also be the association results 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 results between the multiple structured models corresponding to the scenario modeling model and the multiple structured models corresponding to the technology modeling model, that is, can determine the association results between the multiple structured models corresponding to different models to be modeled.

[0161] Optionally, the target model may be the linkage system of the structured models. After obtaining the association results among multiple structured models, based on the association results, the multiple structured models can be modeled in the following ways to obtain the linkage system of the structured models: identify the relationships among different structured models, define rules to guide the linkage of the structured models according to the dependencies and interactions among the structured models, so as to achieve two-way linkage among the structured models. By establishing a model version control system, record the version information and change logs of each update of the structured models, and support version backtracking and difference comparison of the structured models. Use automated tools to automatically generate code frameworks or documents based on the structured models. The linkage system of the structured models supports the continuous integration and continuous deployment processes of software development, ensuring the consistency of design and implementation.

[0162] This embodiment can ensure a high degree of consistency between model design and final code implementation, reducing errors from design to implementation. The model linkage system helps to promptly discover unreasonable parts in the design, avoiding a large amount 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 steps S302 to S304 of the present application above, in response to an input instruction acting on the operation interface, multiple to-be-modeled models of the product are displayed on the operation interface, where different to-be-modeled models are used to represent different modeling stages of the product; in response to a processing instruction acting on the operation interface, the target model of the product is displayed on the operation interface, where the target model is obtained by modeling multiple structured models based on the association results among the multiple structured models corresponding to the multiple to-be-modeled models. The structured model is a resource used to at least represent the modeling process of the to-be-modeled model, the association result is used to represent the logical relationship of mutual association among the multiple structured models, and the structured model is obtained by performing structured processing on the to-be-modeled model. That is to say, the embodiment of the present application, through the linkage system of the structured models, carries and covers the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the to-be-modeled model, thereby achieving the purpose of paying attention to the association and consistency among different modeling stages through the association among the structured models, further realizing the improvement of the model modeling effect, and solving the technical problem of poor model modeling effect.

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

[0165] The client 402 is used to upload multiple models to be modeled for the product, where different models to be modeled are used to represent different modeling stages of the product.

[0166] Optionally, the product can be used to carry the modeling methodology for the models to be modeled. For example, the product can be modeling design software for presenting the models to be modeled, a design flow chart template, a project management tool, a design specification manual, etc. This is only for illustration and does not specifically limit the type of the product. The modeling stage can be called the modeling design stage, and 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 models, scenario modeling models, technical modeling models, assembly modeling models, etc.

[0167] Optionally, while effectively carrying the modeling methodology, the above-mentioned product can also be used as a specification in the modeling process (modeling design process). Since the above-mentioned product can help the design team carry out modeling design work in a standardized manner, for example, clarify the work process, standardize the operation steps, and unify the design standards, so as to carry out modeling design work more systematically and standardly, and ensure the consistency and reliability of the modeling results. Therefore, the above-mentioned product itself is an embodiment of the specification, that is, using the product means following the specification.

[0168] The server 404 is connected to the client and is used to perform structured processing on the models to be modeled to obtain at least one structured model, where the structured model is a resource for at least representing the modeling process of the models to be modeled; determine the association result between multiple structured models corresponding to multiple models to be modeled, where the association result is used to represent the logical relationship of mutual association between multiple structured models; based on the association result, perform modeling on multiple structured models to obtain the 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 for at least representing the modeling process of the models to be modeled. For example, the structured model can be a type of scenario asset data, model asset. The structured processing can be to perform systematic and orderly processing on the models to be modeled to ensure that the models to be modeled have a clear structure and organization, which is convenient for analysis and understanding. The structured processing includes but is not limited to: data cleaning, feature selection, feature transformation, and selecting appropriate modeling algorithms and model structures. By performing structured processing on the models 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 scene modeling model, structuring the scene modeling model can result in structured models such as a scene domain model, a domain architecture model, a scene process model, a story model, and a scene object model. When the model to be modeled is a technology modeling model, structuring the technology modeling model can result in structured models such as a bounded context model, a bounded context mapping derivation model, an application service model, an aggregation model, a domain object model, a domain service model, and a domain behavior design model.

[0171] For example, the multiple structured models corresponding to the scene modeling model may include: structured models such as a scene domain model, a domain architecture model, a scene process model, a story model, and a scene object model. Then, the association result can 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 can 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 can 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 can 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 in two-way linkage with the story model and the scene object model respectively, when any one of the above-mentioned structured models changes, it will cascade and affect other structured models.

[0173] Optionally, the two-way 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, another structured model will also be updated or adjusted accordingly. This two-way linkage can ensure the consistency and coordination between structured models. The two-way linkage can also be achieved by mutual invocation or nesting between structured models. One structured model can call the functions or methods 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, and domain behavior design model. 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, therefore, 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, can determine the association result between the multiple structured models corresponding to different models to be modeled.

[0175] Optionally, the target model may be a linkage system of structured models. After obtaining the association result between the multiple structured models, based on this association result, the multiple structured models can be modeled in the following ways to obtain a linkage system of structured models: identify the relationships between different structured models, define rules to guide the linkage of structured models according to the dependencies and interactions between structured models, so as to achieve two-way linkage between structured models. By establishing a model version control system, record the version information and change log of each structured model update, and support version backtracking and difference comparison of structured models. Use automated tools to automatically generate code frameworks or documents based on structured models. The linkage system of structured models supports the continuous integration and continuous deployment processes of software development, ensuring the consistency between design and implementation.

[0176] This embodiment can ensure a high degree of consistency between model design and final code implementation, reducing the error from design to implementation. The model linkage system helps to promptly discover unreasonable parts in the design, avoiding a large amount of rework in later development and maintenance, thus 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 this system, multiple models to be modeled of a product are uploaded through a client. Among them, different models to be modeled are used to represent different modeling stages of the product. The server is connected to the client, and the models to be modeled are structurally processed by the server to obtain at least one structured model. The structured model is a resource used to represent at least the modeling process of the model to be modeled. Determine the association result between multiple structured models corresponding to multiple models to be modeled. The association result is used to represent the logical relationship of mutual association between multiple structured models. Based on the association result, model multiple structured models to obtain the target model of the product. Send the target model to the client. That is to say, through the linkage system of structured models in the embodiments of the present application, the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the model to be modeled is carried and covered, so as to achieve the purpose of paying attention to the association and consistency between different modeling stages through the association between structured models, and further realize the improvement of the model modeling effect, and solve the technical problem of poor model modeling effect.

[0178] The technical solutions of the embodiments of the present disclosure will be further introduced by way of examples in combination with preferred embodiments below.

[0179] Currently, in modeling design methodologies, such as scenario modeling, process modeling, Unified Modeling Language (UML), domain modeling, data modeling, and assembly modeling, there are corresponding products for process modeling, data modeling, etc., but they are only for specific fields and can provide template tools, but do not pay attention to or solve the problems of upstream and downstream association and consistency of the methodology. Methodologies such as scenario modeling and domain modeling only stay at the theoretical level and lack the support of effective products, resulting in the disconnection between the methodology and implementation. Due to the complex actual implementation of the above methodologies, it is impossible to achieve implementation only by the methodology or single-point tools. An effective product to carry the methodology is needed and used as a specification in the construction process (using the product means following the specification).

[0180] In related technologies, UML modeling tools only provide the drawing of static diagrams of models, which are used as static diagrams after the product is completed. They do not pay attention to the association and consistency between different modeling design stages, nor do they pay attention to the implementation of the design content on the implementation side, etc., and cannot further play the role of better guiding the implementation of scenario design, resulting in the problem of poor model modeling effect.

[0181] To solve the above problems, the present application proposes a mechanism for realizing a modeling methodology through a structured model linkage system. The structured model in this embodiment supports an upstream and downstream linkage mechanism and can simultaneously support domain modeling, scenario modeling, technical modeling, assembly modeling, and code model (linkage with design).

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

[0183] In this embodiment, the assembly modeling methodology can consist of a domain modeling methodology, a scenario modeling methodology, a technology modeling methodology, and a code model. 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. As Figure 5 shown, the Packaged Business Capabilities (PBC) meta-model corresponds to the above assembly modeling methodology. It can be seen that there are correlation relationships among the elements of design, development, and operation 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 capabilities, and business capabilities PRD are respectively associated with business capabilities. Releasing business capabilities can obtain business capability assets, releasing solutions can obtain solution assets, and releasing each application component can obtain component assets. Among them, business capability APIs are 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 a front-end application component, a Backend For Frontend (BEF) application component, a microservice application component, and an integration application component. Among them, the front-end application component involves menus, pages, blocks, front-end scenario components, front-end interaction flows, front-end components, and front-end technical metadata. The BEF application component involves APIs, service orchestration, and BEF technical metadata. The microservice application component involves APIs, domain models, data models, service models, structural objects, and application technical metadata. The integration application component involves integration flows, integration connectors, and integration application technical metadata.

[0184] In the development part, the business capabilities part is used to develop business capability projects, the front-end technical metadata is used to develop front-end projects, the BEF technical metadata is used to develop BEF application projects, the application technical metadata is used to develop microservice application projects, and the integration application technical metadata is used to develop integration application projects. Business capability projects involve application project dependencies, front-end projects involve page code and front-end component code, BEF application projects involve BEF APIs and BEF API implementations, microservice application projects involve API interfaces and domain model implementations, and integration application projects involve integration APIs. Through the above pipeline construction, asset images can be obtained.

[0185] The domain modeling methodology can consist of a scenario modeling methodology and a technology modeling methodology. The structured models involved in the scenario modeling methodology can at least include a scenario domain model, a domain architecture model, a scenario process model, a user story model, and a scenario object model, that is, the association between the above structured models is used to support the scenario modeling methodology.

[0186] The scenario domain model is associated with the user story model and the scenario object model, and can be used to assist in deriving 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 product corresponding to the microservice application in the design phase. Associating the scenario domain model with the bounded context model can play a connecting role, connecting the upper level, i.e., associating scenarios with the scenario domain, and connecting the lower level, i.e., associating technology with microservices, so as to realize the coordination of 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 is associated with scenario objects. Among them, the scenario process can support nested associations of multiple levels of sub-processes, namely L1-L5 processes. 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 by 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 nodes of the scenario process model to form a process, that is, to structurally associate the elements of the scenario design before and after. When the roles or the content of the user story model in the unified language change, the scenario process model will also be refreshed in real time.

[0188] The user story model structurally disassembles information such as the preconditions, trigger conditions, postconditions, execution steps, constraint rules, and acceptance conditions of use cases, and can be used as the input for subsequent PRD use cases and the bounded context timing derivation of the technical modeling methodology. That is, the above-structurally disassembled information is used as the input for subsequent PRD use cases and the bounded context timing derivation of technical modeling. In addition to the associations between scenario objects, the scenario object model can also be used for batch import to generate domain objects to associate the scenario modeling methodology and the technical modeling methodology.

[0189] The structured models involved in the technical modeling methodology can at least include the bounded context model, the bounded context mapping derivation model, the application service model, the aggregation model, the domain object model, the domain service model, and the 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 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, and the bounded context model can be associated with the scenario domain model / sub-domain model. The bounded context model can subsequently be used as an important input for microservice application development and associated implementation.

[0190] Based on the execution steps of the bounded context model and the user story model (which describe the interaction logic between different bounded contexts), the bounded context mapping derivation model can derive the service models provided by each bounded context model. Among them, the execution steps of the bounded context model can be 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 externally and does not involve its internal logic.

[0191] The application service model is derived through the bounded context mapping derivation model or created from scratch (0-1). The application service model can be used to generate API interfaces subsequently. Among them, there are two ways to generate the application service model. The first way is to derive it through the context mapping derivation model and then publish and generate it. The second way is 0-1 creation, that is, directly create the application service model on the platform without derivation, usually for the situation where it is already clear which application service models are needed.

[0192] The aggregation model can be used to better classify the domain object model according to scenario cohesion. The aggregations should maintain loose coupling, and only cross-aggregation calls are made through the aggregate root. The aggregate root model encapsulates and exposes the service capabilities related to the aggregation externally. The domain object model can be generated in batches based on the scenario object model and is a key model for carrying scenario logic. The domain object model is divided into multiple model types such as aggregate root, entity, and value object according to responsibilities. The domain service model is used to carry the service composition across aggregations, and the input parameters and output parameters (i.e., input and output parameters) of the domain service model need to use the domain object model. The domain behavior design model takes the application service model or the domain event model as the entry point and further analyzes and derives the capabilities that need to be precipitated in the domain layer within a bounded context model, that is, the domain service methods and the behaviors of domain objects.

[0193] The code model can be used to extract key information on the code side, through tool assistance or automated extraction, to express the implementation of the code for the landing of the model design elements. 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, two-way comparison and linkage between design and implementation can be achieved.

[0194] Figure 6 It is a schematic diagram of the logical relationship between different modeling stages according to an embodiment of the present application. As Figure 6 shown, scenario modeling includes scenario processes, and the scenario processes include L1 scenario process, L2 scenario process, L3 scenario process, and L4 scenario process. Among them, the L2 scenario process is a subprocess of the L1 scenario process, and the L3 scenario process is a subprocess of the L2 scenario process. Scenario services (use cases) generally originate from the L3 scenario process. Scenario services (use cases) belong to the scenario domain, or scenario services (use cases) belong to the scenario domain through scenario objects. The L4 scenario process generally originates from scenario services (use cases). Scenario services (use cases) are respectively associated with the PRD use cases of requirements modeling and the context mapping time sequence derivation of technical modeling.

[0195] Technical modeling can include models such as bounded context, aggregation, context mapping time sequence derivation, application service, domain event, domain service, domain object, and domain behavior design. The context mapping time sequence derivation can derive application services and domain events. Application services and domain events 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 It is a schematic diagram of the upstream and downstream association of a structured model according to an embodiment of the present application. As Figure 7 shown, scenario process design and user story design can be used as inputs for scenario object design. The scenario object design can be imported into domain object design, and the domain object design can be imported into data modeling. In addition, scenario domain design can also be used as an input for bounded context, so that the upstream and downstream of each structured model can be associated with each other.

[0197] Figure 8 It is a schematic diagram of the association between a scenario domain and a bounded context according to an embodiment of the present application. As Figure 8As shown in the figure, the scenario fields can at least include: transaction field, product field, user field, payment field, inventory field, and order field. The transaction field is associated with the transaction context, the product field is associated with the product context, the user field includes an account field and a membership field. The account field is associated with the user context, the membership field is associated with the membership context, the payment field is associated with the payment context, the inventory field is associated with the inventory context, and the order field is associated with the order context.

[0198] This embodiment also supports the multi-version management of the bounded context model. As can be seen from Table 1, the scenario fields respectively 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. Since the changes in the bounded context model may affect the upstream and downstream services. Through multi-version management, it can help identify the scope of influence of the changes, evaluate the change risks, and ensure the smooth transition of the changes in other related services. For example, before the release of the new version of the bounded context model, the impact on the existing service interfaces and data structures can be analyzed through version comparison, so as to formulate corresponding migration plans.

[0199] Table 1 Multi-version management table of the bounded context model

[0200]

[0201] Figure 9 is a schematic diagram of the internal model association of a bounded context according to an embodiment of the present application, as Figure 9 shown, the bounded context model serves as the input of the mapping derivation model, and the mapping derivation model is respectively associated with the application service model and the domain event consumer model. The bounded context model is respectively associated with the domain event producer model, the domain object design model, and the domain entity object model. The domain entity object model can be imported into the data modeling model. The domain entity object model can also serve 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 respectively associated with the application service model, the mapping derivation model, the domain event consumer model, and the domain event producer model.

[0202] There are corresponding products for the modeling methodology, but only for specific fields. For example, for process modeling and data modeling, rich templates and tools are provided, and the issues of upstream and downstream association and consistency within the modeling methodology system are not concerned and cannot be solved. Through the structured model linkage system, this embodiment can better carry and cover the design processes and design products of each link of the modeling methodology, and at the same time, the upstream and downstream linkage and consistency issues can be concerned through the relevance between the structured models.

[0203] Regarding the problem that the modeling methodology only stays at the theoretical level, for example, scenario modeling, domain modeling, assembly modeling, etc., lacking the support of mature products. The structured model system proposed in this embodiment has good productization feasibility and can support diverse modeling scenarios.

[0204] Regarding the complex situation in the actual implementation process of the modeling methodology, it is impossible to achieve only relying on the methodology or single-point tools. There is a need for a product that can effectively carry the methodology and become a specification in the system construction process (using the product means following the design specification). The product based on the structured model system in this embodiment itself carries the specifications for model design (scenario modeling, technical modeling) and development implementation. Through versioning, real-time verification, difference comparison, rationality analysis, design and implementation consistency verification, etc. of the structured model, the implementation specification is guaranteed in a productized way.

[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, design and implementation consistency, and productization of the modeling methodology.

[0206] Regarding the onlineization of the structured model, this embodiment completes the structured model design process that was originally completed offline online. For scenario modeling, there are many situations where a large amount of manual sorting and management are carried out through offline documents and tables, resulting in great challenges for the long-term sustainable iteration and management of the structured model. The onlineization of the structured model can solve the above problems.

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

[0208] Regarding the real-time linkage within the structured model system, the structured model can form an association network after structuring the model. The change energy level of the structured model nodes can be cascaded and synchronized for update. That is, when a node in the structured model changes, it will cascade and affect other nodes, and at the same time, it also realizes more flexible analysis and query of the impact on the structured model.

[0209] Regarding the difference comparison of the structured model, this embodiment supports the structured comparison of the differences in the structured model. That is, after designing the structured model and generating code based on the structured model and developing the generated code, a two-way comparison can be made between the structured model design and the code implementation to find out whether there is a deviation between the implementation and the design. When making a difference comparison of the structured model, a structured difference comparison can be carried out.

[0210] For the real-time verification and analysis of the design rationality of a structured model, based on structured data and verification rules (which can be continuously supplemented), it can support the real-time verification of the structured model, including but not limited to: the correctness verification of the structured model, and the consistency verification of the design and implementation of the structured model. The correctness verification of the structured model can at least include: verifying whether the content of the structured model is missing, whether deleting the structured model will cause errors to the referenced party, and the determination of the design rationality based on scenario rules, etc. For example, when determining the design rationality of scenario rules, if loose coupling is ensured between aggregations, that is, cross-aggregation calls are only made through the aggregation root, then the design of the scenario rules is determined to be reasonable. Secondly, for the consistency verification of the design and implementation of the structured model, the structured model system and its upstream and downstream associations in this embodiment can support the consistency requirements for scenario modeling and technical modeling, and technical modeling and code implementation.

[0211] Regarding the precipitation, distribution, and reuse of scenario assets, as a type of scenario asset data, the structured model carries important scenario knowledge, design processes, and design products, and can be continuously precipitated and quickly reused. By adjusting the existing structured model, code can be quickly generated, and the generated code can be developed. After development, the code can be further precipitated into new model assets. The structured model can also flexibly support distribution scenarios such as the export and import of scenario assets.

[0212] In the embodiment of the present application, multiple models to be modeled of a product are determined, where different models to be modeled are used to represent different modeling stages of the product; the models to be modeled are structurally processed to obtain at least one structured model, where the structured model is a resource used to at least represent the modeling process of the models to be modeled; the association result between the multiple structured models corresponding to the multiple models to be modeled is determined, where the association result is used to represent the logical relationship of mutual association between the multiple structured models; based on the association result, the multiple structured models are modeled to obtain the target model of the product. That is to say, through the linkage system of the structured model in the embodiment of the present application, the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the models to be modeled is carried and covered, so as to achieve the purpose of paying attention to the association and consistency between different modeling stages through the association between the structured models, and further realizing the improvement of the model modeling effect and solving the technical problem of poor model modeling effect.

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

[0214] End user 1002 can provide and access services through a web browser or other software applications on the client. In some embodiments, the provision and / or request of end user 1002 can be provided to the ingress gateway 1030. The ingress gateway 1030 can include a corresponding proxy to handle the provision and / or request for services (one or more services provided in the computing environment 1001).

[0215] Services are provided or deployed according to 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 means. VM-based virtualization can be achieved by initializing a virtual machine to simulate a real computer and execute programs and applications without directly accessing any actual hardware resources. While virtualizing the machine with a virtual machine, according to container-based virtualization, containers can be launched to virtualize the entire operating system (OS) so that multiple workloads can run on a single operating system instance.

[0216] In one embodiment of container-based virtualization, several containers of a service can be assembled into a Pod (e.g., Kubernetes Pod). For example, as Figure 10 shown, service 1020-2 can be equipped with one or more Pods 1040-1, 1040-2, …, 1040-N (collectively referred to as Pods). A Pod 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 the Pod handle 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 this.

[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. As Figure 10 shown, service "A" 1020-1 receives a user request from end user 1002 from ingress gateway 1030. Service "A" 1020-1 may invoke service "D" 1020-2, and service "D" 1020-2 may request service "E" 1020-3 to execute one or more functions.

[0218] The computing environment described above may be a cloud computing environment, where the allocation of resources is managed by a cloud service provider, allowing the development of functions without considering the implementation, adjustment, or expansion of servers. This computing environment allows developers to execute code in response to events without building or maintaining complex infrastructure. Services can be split into groups of functions that can scale automatically and independently, 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 modeling apparatus for a model for implementing the modeling method of the model shown above Figure 2 shown.

[0220] Figure 11 is a schematic diagram of a modeling apparatus for a model according to an embodiment of the present application. As Figure 11 shown, the modeling apparatus 1100 for 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 determination unit 1102 is configured to determine a plurality of models to be modeled for a product, where different models to be modeled are used to represent different modeling stages of the product.

[0222] The processing unit 1104 is configured to perform a structuring process on the models to be modeled to obtain at least one structured model, where the structured model is a resource for at least representing the modeling process of the models to be modeled.

[0223] The second determination unit 1106 is configured to determine an association result between a plurality of structured models corresponding to the plurality of models to be modeled, where the association result is used to represent the logical relationship of mutual association between the plurality of structured models.

[0224] The modeling unit 1108 is configured to perform modeling on the plurality of structured models based on the association result to obtain a target model of the product.

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

[0226] In the modeling device of this model, a plurality of models to be modeled of a product are determined by the first determination unit 1102, where different models to be modeled are used to represent different modeling stages of the product. The models to be modeled are structurally processed by the processing unit 1104 to obtain at least one structured model, where the structured model is a resource for at least representing the modeling process of the models to be modeled. The association result between a plurality of structured models corresponding to the plurality of models to be modeled is determined by the second determination unit 1106, where the association result is used to represent the logical relationship of mutual association between the plurality of structured models. Based on the association result, the modeling unit 1108 models the plurality of structured models to obtain the target model of the product. That is to say, in the embodiment of the present application, through the linkage system of structured models, the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the models to be modeled is carried and covered, so as to achieve the purpose of paying attention to the association and consistency between different modeling stages through the association between structured models, and further realizing the improvement of the model modeling effect and solving the technical problem of poor model modeling effect.

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

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

[0229] The first display unit 1202 is configured to display a plurality of models to be modeled of a product on the operation interface in response to an input instruction acting on the operation interface, where different models to be modeled are used to represent different modeling stages of the product.

[0230] A second display unit 1204, configured to respond to a processing instruction acting on an operation interface and display a target model of a product on the operation interface, where the target model is obtained by modeling multiple structured models based on an association result between the multiple structured models corresponding to 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 result is used to represent the logical relationship of mutual association between the multiple structured models, and the structured model is obtained by performing structured processing on the model to be modeled.

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

[0232] In the modeling device of this model, the first display unit 1202 responds to an input instruction acting on the operation interface and displays multiple models to be modeled of a product on the operation interface, where different models to be modeled are used to represent different modeling stages of the product. The second display unit 1204 responds to a processing instruction acting on the operation interface and displays a target model of the product on the operation interface, where the target model is obtained by modeling multiple structured models based on an association result between the multiple structured models corresponding to 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 result is used to represent the logical relationship of mutual association between the multiple structured models, and the structured model is obtained by performing structured processing on the model to be modeled. That is to say, in the embodiment of the present application, through the linkage system of structured models, the design of each modeling stage of the modeling strategy (i.e., modeling methodology) of the model to be modeled is carried and covered, so as to achieve the purpose of paying attention to the association and consistency between different modeling stages through the association between structured models, and further realizing the improvement of the model modeling effect and solving the technical problem of poor model modeling effect.

[0233] The embodiment of the present application can provide a computer terminal, and the computer terminal can be any computer terminal device in a computer terminal group. Optionally, in this embodiment, the above computer terminal can also be replaced with a terminal device such as a mobile terminal.

[0234] Optionally, in this embodiment, the above computer terminal can be located in at least one of multiple network devices in a computer network.

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

[0236] Optionally, Figure 13 is a structural block diagram of a computer terminal according to an embodiment of the present application, as Figure 13 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] Among them, the memory may be used to store software programs and modules, such as the program instructions / modules corresponding to the modeling method and device of the model in the embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, implements the above-mentioned modeling method of the model. 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 memories, or other non-volatile solid-state memories. In some instances, the memory may further include a memory remotely disposed relative to the processor, and these remote memories may be connected to the terminal A through a network. Examples of the above network include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0238] The processor may call the information and application programs stored in the memory through the transmission device to execute the following steps: in response to an input instruction acting on the operation interface, displaying a plurality of models to be modeled for the product on the operation interface, where 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 the target model of the product on the operation interface, where the target model is obtained by performing modeling on a plurality of structured models based on the association result between the plurality of structured models corresponding to the plurality of models to be modeled, the structured model is a resource for at least representing the modeling process of the models to be modeled, the association result is used to represent the logical relationship of mutual association between the plurality of structured models, and the structured model is obtained by performing a structuring process on the models to be modeled.

[0239] Those of ordinary skill in the art can understand, Figure 13The structure shown is only schematic. The computer terminal A can also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a personal digital assistant, and mobile Internet devices (abbreviated as MID), personal access displays (abbreviated as PAD), and other terminal devices. Figure 13 It does not limit the structure of the above computer terminal A. For example, the computer terminal A may further include more or fewer components (such as a network interface, a display device, etc.) than those shown Figure 13 in the figure, or have a different configuration from that Figure 13 shown.

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

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

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

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

[0244] Optionally, the above computer program product may include a non-volatile computer-readable storage medium, and the above non-volatile computer-readable storage medium can be used to store a computer program, and the above computer program, when executed by a processor, implements the method provided in the above embodiments.

[0245] The embodiments of the present application can provide an electronic device, and the electronic device may include a memory and a processor.

[0246] Figure 14A block diagram of an electronic device for a modeling method of a model according to an embodiment of the present application. The electronic device is intended to represent various forms of digital computers, such as, for example, laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as, for example, personal digital processors, cellular telephones, 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 claimed herein.

[0247] As Figure 14 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 plurality 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 magnetic 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 via a computer network such as the Internet and / or various telecommunication networks.

[0249] The computing unit 1401 can be various general-purpose and / or special-purpose 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 graphic processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 1401 executes 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 can be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as the storage unit 1408. In some embodiments, part or all of the computer program can be loaded and / or installed onto 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 can be executed. Alternatively, in other embodiments, the computing unit 1401 can be configured to execute the modeling method of the model in any other suitable manner (e.g., by means of firmware).

[0250] The various embodiments of the systems and techniques described above in this article can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGA), application specific integrated circuits (ASIC), application specific standard parts (ASSP), system-on-a-chip (SOC), complex programmable logic devices (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a dedicated or general-purpose programmable processor, receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting the 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. This program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing devices, such that when the program code is executed by the processor or controller, the functions / operations specified in the flowchart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, executed partially on the machine and partially on a remote machine as an independent software package, or executed entirely on a remote machine or server.

[0252] The method embodiments provided by the embodiments of the present application can be executed in a mobile terminal, a computer terminal, or a similar computing device. Figure 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, as Figure 15 shown, the computer terminal 150 (or mobile device) can include one or more (shown as 1502a, 1502b,..., 1502n in the figure) processors 1502 (the processor 1502 can include, but is not limited to, processing devices such as a microcontroller unit (MCU) or a field programmable gate array (FPGA)), a memory 1504 for storing data, and a transmission device 1506 for communication functions. In addition, it can also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which can be included as one of the ports of the BUS bus), a network interface, a power supply, and / or a camera. Those of ordinary skill in the art can understand that Figure 15 the structure shown is only schematic and does not limit the structure of the above electronic device. For example, the computer terminal 150 can also include more or fewer components than Figure 15 shown, or have a different configuration from Figure 15 shown.

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

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

[0255] To provide for interaction with a user, the systems and techniques described herein can 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 trackball) by which the user can provide input to the computer. Other kinds of devices can also be used to provide for interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic, speech, or tactile input).

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

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

[0258] It should be noted that the serial numbers of the embodiments of the present application are only for description and do not represent the superiority or inferiority of the embodiments.

[0259] In the above embodiments of the present application, the descriptions of the various embodiments have their own emphases. For parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0260] In the several embodiments provided by the present 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 illustrative. For example, the division of units is only a logical function division, and there can 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 displayed or discussed coupling or direct coupling or communication connection to each other can be through some interfaces, and the indirect coupling or communication connection of units or modules can be in an electrical or other form.

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

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

[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 such an understanding, the technical solution of the present application, in essence, 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. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the various embodiments of the present application. The foregoing storage medium includes: various media that can store program codes, such as USB flash drives, read-only memories, random access memories, mobile hard disks, magnetic disks, or optical discs.

[0264] The above are only the preferred embodiments of the present application. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present application, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present application.

Claims

1. A modeling method, characterized in that: include: Determine a plurality of to-be-modeled models of a product, wherein different to-be-modeled models are used to represent different modeling stages of the product, and the product is used to carry the modeling strategies of the to-be-modeled models; 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, modeling is performed on the plurality of structured models to obtain a target model of the product; Determining the association results between the multiple structured models corresponding to the multiple models to be modeled, comprising: determining the model elements in the models to be modeled, wherein the model elements are used to represent data associated with the upstream models and / or downstream models of the models to be modeled in the multiple models to be modeled; establishing an association network between the multiple structured models according to the model elements, wherein the model nodes in the association network change with the changes of the associated model nodes of the model nodes in the association network.

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 the modeling strategy of 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 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.

9. The method according to claim 8, 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.

10. The method according to claim 1, 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.

11. 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.

12. The method according to any one of claims 1 to 11, 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.

13. The method according to claim 12, 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.

14. The method according to claim 12, 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.

15. A modeling method, characterized in that: include: In response to an input instruction acting on an operation interface, a plurality of models of a 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, and the product is used to carry the modeling strategy of the models to be built; 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 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 association result is an association network between the multiple structured models established according to the model elements in the model to be modeled, the model elements are 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, the model nodes in the association network change with the change of the associated model nodes of the model nodes in the association network, and the structured model is obtained by structuring the model to be modeled.

16. A modeling system of a model, characterized in that: include: The client is used to upload multiple models to be built of a product, wherein different models to be built are used to represent different modeling stages of the product, and the product is used to carry the modeling strategy of the models to be built; 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 the 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 the target model of the product; and send the target model to the client; Determining the association results between the multiple structured models corresponding to the multiple models to be modeled, comprising: determining the model elements in the models to be modeled, wherein the model elements are used to represent data associated with the upstream models and / or downstream models of the models to be modeled in the multiple models to be modeled; establishing an association network between the multiple structured models according to the model elements, wherein the model nodes in the association network change with the changes of the associated model nodes of the model nodes in the association network.

17. 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 15 when running.

18. 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 15 when running.

Images