A domain modeling method and system for intelligent manufacturing

Through a domain modeling method for intelligent manufacturing, combined with domain-driven design and UBML standards, the problems of incomplete demand and business uncertainty in intelligent manufacturing are solved, and the automatic software construction and efficiency improvement are achieved.

CN113722936BActive Publication Date: 2024-11-26SHANDONG UNIV
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111222560.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-10-20
Publication Date
2024-11-26
Estimated Expiration
2041-10-20

AI Technical Summary

Technical Problem

The existing domain modeling methods cannot effectively deal with incomplete requirements, business uncertainty and randomness in intelligent manufacturing scenarios, and lack solutions for multivariate coupling and multi-scale complex characteristics, which cannot meet the needs of software-defined manufacturing.

Method used

Using a domain modeling method for intelligent manufacturing, we build a domain model suitable for intelligent manufacturing scenarios by defining domain metamodels, constructing modeling primitives, recombining modeling primitives and domain boundary context concepts, and based on knowledge graph completion requirements, Introduce the idea of ​​field-driven design and software engineering, and use industry standards such as UBML to achieve automatic software construction and formal verification.

Benefits of technology

It improves the production efficiency of industrial manufacturing software systems, optimizes knowledge conversion, meets the modeling needs of complex scenarios in intelligent manufacturing, reduces manual intervention, and realizes the automatic construction and verification of software code.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113722936B_ABST
    Figure CN113722936B_ABST
Patent Text Reader

Abstract

The present invention provides a domain modeling method and system for intelligent manufacturing, including defining a domain metamodel, stipulating domain elements and domain specifications that can be inherited by domain modeling; constructing modeling primitives, using the modeling primitives to uniformly model the domain elements of the domain to be modeled, and constructing an initial application domain model; unifying the modeling primitives with the concept of domain context, and clarifying the context boundary of the initial application domain model; constructing a knowledge graph based on the domain specifications of the domain metamodel, and completing the knowledge of the initial application domain model with clear context boundaries to obtain a complete application domain model; in modeling, based on the pre-defined domain metamodel, combined with domain knowledge reasoning, facing specific scenarios, completing the description of requirements, and improving incomplete requirements; by dividing the domain into contexts, by establishing clear boundaries to limit the scope of uncertainty, and by gradually reducing uncertainty through data transmission.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of domain modeling in software development, and in particular relates to a domain modeling method and system for intelligent manufacturing. Background Art

[0002] The statements in this section merely provide background information related to the present invention and do not necessarily constitute prior art.

[0003] After three industrial revolutions, we have now entered the fourth industrial revolution. Entering the information age, the leapfrog development of computing technology, ubiquitous communication means, and the clear goal of intelligence have made the softwareization of industrial technology an urgent need in the industry.

[0004] Software-defined manufacturing is an effective way to softwareize industrial technology. Software-defined manufacturing uses software as a tool and carrier to assist the industry in expressing the manufacturing principles, processes, methods, know-how and other field knowledge accumulated over many years in a standard and standardized manner, thereby completing the first stage of the digital transformation process of industrial manufacturing. Then, the field knowledge composed of these principles, processes, methods and know-how can not only be efficiently promoted and reused in a wider range through digital means, but also can realize the automatic construction of process or control code through low-code platforms and technologies. This is the second stage.

[0005] However, the entire manufacturing chain in intelligent manufacturing covers a variety of production equipment and process, with complex characteristics of multi-variable coupling and multi-scale, and needs to face more and more complex uncertainty problems, with typical uncertain generalized system characteristics. If in some manufacturing fields, the knowledge has not been summarized and become recognized standards and specifications in the field, the software cannot be defined, and there is no basis for the definition. Obviously, industrial domain knowledge and its standardization are the basis and basis for software definition. On the one hand, software-defined manufacturing technology needs to be reasonably abstracted and generalized in combination with its application scenarios, and a domain model suitable for multiple or even all application modes and scenarios should be designed. On the other hand, in the process of combining the domain model with the scenario design, the core elements such as incomplete requirements, uncertainty and random events in the intelligent manufacturing model should be considered, and corresponding countermeasures can be introduced in the modeling method for these elements.

[0006] At present, some relatively mature model specifications have been proposed in certain areas of industrial manufacturing. For example, the PLCopen motion control specification, which is the basis and foundation of software-defined motion control, was developed long before the concept of software-defined manufacturing was formed, but it does not affect the development of the specification in the correct direction of software technology and software engineering. Another example is the PackML specification, which has been highly praised by the packaging industry and many industrial automation companies serving packaging. It has explored a feasible path for software-defined manufacturing in order to efficiently and cost-effectively integrate mechanical equipment produced by different manufacturers into production lines with excellent consistency in control, monitoring, production management, etc.

[0007] However, these are only specifications proposed for individual industrial manufacturing scenarios, and do not cover all aspects of the scenarios. For example, PackML mainly defines a specification model for the process flow of packaging scenarios, which is not only limited in the horizontal breadth of scenarios (multiple scenarios), but also not comprehensive in the vertical depth of scenarios. In addition, the business requirements such as reuse and automatic code construction mentioned in the second phase cannot be met. At the same time, these specifications do not summarize a universal response method for the uncertainty and randomness elements in the intelligent manufacturing model. Summary of the invention

[0008] In order to solve the technical problems existing in the above-mentioned background technology, the present invention provides a domain modeling method and system for intelligent manufacturing, which is fully oriented to intelligent manufacturing scenarios and takes into account some core requirements in intelligent manufacturing scenarios, such as incomplete requirements, business uncertainty, strong randomness, etc., and specifically introduces the ideas and technical methods of software engineering and domain modeling.

[0009] In order to achieve the above object, the present invention adopts the following technical solution:

[0010] A first aspect of the present invention provides a domain modeling method for intelligent manufacturing, comprising:

[0011] Define a domain metamodel to specify the inheritable domain elements and modeling specifications in domain modeling;

[0012] Construct modeling primitives, use modeling primitives to uniformly model the elements of the domain to be modeled, and construct composable domain model basic units;

[0013] Reorganize the modeling primitives to unify them with the concept of domain bounded context and clarify the boundaries of bounded context in specific domain models;

[0014] Based on the domain metamodel, combined with specific application domains, scenario knowledge and expert knowledge, domain elements are uniformly modeled, and a knowledge graph with modeling primitives as nodes is constructed. During the construction process, the initial incomplete requirements are gradually completed, and finally a relatively complete application domain model is obtained.

[0015] A second aspect of the present invention provides a domain modeling system for intelligent manufacturing, comprising:

[0016] The metamodel building module is configured to define a domain metamodel, specifying domain elements and modeling specifications that can be inherited by domain modeling;

[0017] A domain model basic unit construction module is configured to construct modeling primitives, use the modeling primitives to uniformly model the domain elements of the domain to be modeled, and construct a composable domain model basic unit;

[0018] The context boundary determination module is configured to reorganize the modeling primitives to unify them with the domain bounded context concept and clarify the boundaries of the bounded context of the specific domain model;

[0019] The application domain model completion module is configured to uniformly model domain elements based on the domain metamodel, combined with specific application domains, scenario knowledge and expert knowledge, and construct a knowledge graph with modeling primitives as nodes. During the construction process, the initial incomplete requirements can be gradually completed, and finally a relatively complete application domain model is obtained.

[0020] A third aspect of the present invention provides a computer-readable storage medium.

[0021] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps in a domain modeling method for intelligent manufacturing as described in the first aspect above.

[0022] A fourth aspect of the present invention provides a computer device.

[0023] A computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps in a domain modeling method for intelligent manufacturing as described in the first aspect above are implemented.

[0024] Compared with the prior art, the present invention has the following beneficial effects:

[0025] 1. This invention fully considers the essential characteristics of domain modeling in intelligent manufacturing: that is, using domain models to optimize the production mode of industrial manufacturing software systems, thereby improving conversion efficiency. Specifically, it includes three key points: industrial domain knowledge and its standardization; considering solving non-patterns, uncertainties and other problems in manufacturing; conversion of knowledge to software code, and replacement of manual work by software code.

[0026] 2. Based on conventional modeling methods, the modeling method and system of the present invention are fully oriented to intelligent manufacturing scenarios, and take into account some core elements in intelligent manufacturing scenarios, such as incomplete requirements, business uncertainty, randomness, etc., and specifically introduce the ideas and technical methods of software engineering and domain modeling; at the same time, the constructed model complies with industry standards such as UBML, which also facilitates the subsequent dynamic and instant automatic construction and formal verification of the software.

[0027] 3. The present invention provides a domain modeling method and system for the automatic construction process of intelligent manufacturing software, targeting incomplete requirements and business uncertainty. It follows the modeling method ideas of domain-driven design and software engineering, and is based on a pre-defined domain metamodel in the modeling process, combined with domain knowledge reasoning, and oriented to specific scenarios to complete the description of requirements and improve incomplete requirements. For the uncertainty and randomness of the business, the domain is divided into contexts, the scope of uncertainty is limited by establishing clear boundaries, and the uncertainty is gradually reduced through data transmission. Based on the proposed modeling primitives, the domain elements are uniformly modeled, and the element behaviors are expressed in a functional manner to facilitate software reconstruction and combination. Finally, in order to meet the support of the modeling method for the automatic construction of intelligent manufacturing software, a model output and modeling system that supports low-code modeling languages ​​such as UBML is proposed.

[0028] Advantages of additional aspects of the present invention will be given in part in the following description, and in part will become obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The accompanying drawings in the specification, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.

[0030] Figure 1 is a schematic diagram of the structure of a domain metamodel in an embodiment of the present invention;

[0031] Figure 2 is a diagram of a modeling primitive structure in an embodiment of the present invention;

[0032] Figure 3 It is the basic roadmap for domain modeling in the embodiments of the present invention. DETAILED DESCRIPTION

[0033] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

[0034] It should be noted that the following detailed descriptions are all illustrative and intended to provide further explanation of the present invention. Unless otherwise specified, all technical and scientific terms used herein have the same meanings as those commonly understood by those skilled in the art to which the present invention belongs.

[0035] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit exemplary embodiments according to the present invention. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should be understood that when the terms "comprising" and / or "including" are used in this specification, it indicates the presence of features, steps, operations, devices, components and / or combinations thereof.

[0036] It should be noted that the flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the methods and systems according to various embodiments of the present disclosure. It should be noted that each box in the flowchart or block diagram can represent a module, a program segment, or a part of a code, and the module, program segment, or a part of a code may include one or more executable instructions for implementing the logical functions specified in each embodiment. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, or they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the flowchart and / or block diagram, and the combination of boxes in the flowchart and / or block diagram can be implemented using a dedicated hardware-based system that performs a specified function or operation, or can be implemented using a combination of dedicated hardware and computer instructions.

[0037] Before understanding the specific implementation, you need to understand the technical background of domain-driven design (DDD) and UBML:

[0038] (1) UBML is a low-code modeling language based on domain-specific languages ​​for rapid construction of application software. It includes the model standard (UBML-Standard) and its reference implementation, SDK, runtime framework and other components. The main goal is to establish a standardized representation bridge between business and code implementation. It can be understood as inheriting the UML modeling language lineage and targeting specific businesses and scenarios.

[0039] (2) DDD is a model-driven design approach that consists of two phases:

[0040] a) Use a "common language" that domain experts, designers, and developers can understand as a tool for mutual communication, discover and dig out some major domain concepts in the process of continuous communication, and then design these concepts into a domain model;

[0041] b) The domain model drives the software design, and the domain model is expressed in code. The initial details of the domain requirements are obtained through discussions among domain experts at the functional level.

[0042] The modeling method proposed in this invention follows the idea of ​​DDD, focuses on the abstract model description suitable for the field of intelligent manufacturing, and reflects the requirements of the business demand description of users in the field; at the same time, the modeling system can be compatible with UBML, covering the demand description of multiple levels such as user interaction, application interface, domain service, business logic, persistence, etc., and ultimately serves the implementation of the code; the combination of the two solves the problem of automatic construction of software in the field of intelligent manufacturing.

[0043] Embodiment 1

[0044] like Figure 1-3 As shown, this embodiment provides a domain modeling method for intelligent manufacturing. This embodiment uses the method applied to a server as an example. It can be understood that the method can also be applied to a terminal, and can also be applied to a terminal, a server, and a system, and is implemented through the interaction between the terminal and the server. The server can be an independent physical server, or a server cluster or a distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network servers, cloud communications, middleware services, domain name services, security services CDN, and big data and artificial intelligence platforms. The terminal can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, etc., but is not limited to this. The terminal and the server can be directly or indirectly connected via wired or wireless communication, and this application is not limited here.

[0045] In this embodiment, the method includes the following steps:

[0046] Step S1: define a domain metamodel to specify the domain elements and modeling specifications that can be inherited by domain modeling; the metamodel is a model used to represent the model, defines the meta information of the domain modeling elements in the specific application scenario, and helps to standardize the integrity of the model element content and the unification of the expression form;

[0047] Step S2: construct modeling primitives, use the modeling primitives to uniformly model the domain elements to be modeled, and construct a composable domain model basic unit;

[0048] Step S3: Reorganize the modeling primitives to unify them with the concept of domain bounded context and clarify the boundaries of the bounded context of the specific application domain model;

[0049] Step S4: Based on the domain metamodel, combined with specific application domains, scenario knowledge and expert knowledge, the domain elements are uniformly modeled, and a knowledge graph with modeling primitives as nodes is constructed. During the construction process, the initial incomplete requirements are gradually completed, and finally a complete application domain model is obtained.

[0050] In step S1, a domain modeling metamodel for intelligent manufacturing is defined. The metamodel specifies the inheritable elements and modeling specifications of domain modeling, mainly including: bounded context and boundary interface elements, vocabulary elements, entity and attribute elements, event and state elements, instruction and action elements, relationship and dependency elements, etc. The specific steps of defining the domain modeling metamodel are as follows:

[0051] Step S11: Abstract common elements from multiple fields: Before designing the domain metamodel, full consideration should be given to universality. Starting from several representative application fields in intelligent manufacturing, the common elements that can be applied to modeling these application fields should be summarized and abstracted. In addition, when defining the structure of these elements, some factors in intelligent manufacturing should be fully considered, such as incomplete requirements and business uncertainty.

[0052] Step S12: Define the domain metamodel and formulate the element specification details in the domain: After designing each element, consider combining these elements organically to form a complete domain metamodel. In the subsequent domain modeling process, the domain metamodel and its elements should be used as the standard for modeling.

[0053] Based on the domain elements that can be inherited by domain modeling specified in step S1, in step S2, a modeling expression structure for decentralized functional units in the manufacturing field, namely, modeling primitives, is proposed, which can uniformly describe various heterogeneous manufacturing resources to achieve unified modeling of domain elements, specifically:

[0054] Step S21: This step mainly considers the uncertainty existing in a specific field - intelligent manufacturing, and proposes a modeling expression structure - modeling primitive, which combines some elements in the metamodel - entities, actions, states, etc.

[0055] Step S22: A modeling primitive is composed of an entity part and a management shell. The entity is the carrier of static resources, and the management shell carries the dynamic elements on the entity, mainly action elements, and each action element corresponds to a function. The action or behavior elements in the modeling primitive are expressed by functions.

[0056] Step S23: Each function can be called in cascade. Specifically, the connection between each modeling primitive is realized by calling the specific export or import functions, and the data is passed by passing the function parameters. The connection between the dynamic elements in the modeling primitive can also be realized by the combination or calling of the functions inside the modeling primitive.

[0057] In step S3, in response to the uncertainty reduction requirements of business in intelligent manufacturing, a method is proposed to limit the scope of uncertainty by unifying the modeling primitives and bounded context concepts, clarifying the boundaries of bounded contexts composed of modeling primitives or sets of modeling primitives, and gradually reducing uncertainty through the transmission of verified deterministic data, specifically:

[0058] Step S31: This step mainly considers the uncertainty existing in intelligent manufacturing. The functional units in intelligent manufacturing are uniformly encapsulated using modeling primitives to solve the problem of interaction consistency; and the modeling primitives are associated with the bounded context in the domain-driven method. A bounded context includes 1 to n modeling primitives, and the interaction elements of the modeling primitives only appear on the context boundary;

[0059] Step S32: within the limit, the input can be fuzzy or take a value within a range, and the output outside the limit is a definite value, thereby controlling the uncertainty within the context;

[0060] Step S33: The communication between bounded contexts is implemented as the communication between dynamic elements in the modeling primitives. Since the dynamic elements in the modeling primitives are expressed by functions, the communication between bounded contexts is achieved by passing parameters between functions.

[0061] In step S4, in view of the incompleteness of requirements in intelligent manufacturing, a method is proposed to express the knowledge in the field through a knowledge graph standardized by a domain metamodel, and further complete the incomplete requirements through the systematization of knowledge extraction, knowledge expression and knowledge reasoning. Specifically,

[0062] Step S41: This step mainly considers the problem of incomplete requirements in intelligent manufacturing. Based on the domain metamodel, combined with specific application domain / scenario knowledge / expert knowledge, the domain elements are uniformly modeled to construct a knowledge graph with modeling primitives as nodes. The smallest unit of the knowledge graph is a modeling primitive that can describe static resources and dynamic elements, which can describe the domain as completely as possible.

[0063] Step S42: In the process of constructing the domain knowledge graph, the initial incomplete requirements are gradually completed to obtain a relatively complete application domain model;

[0064] Step S43: Due to the reasonability of the knowledge graph, static entities and relationships in the domain can be reasoned through knowledge reasoning to discover some undiscovered domain knowledge and further complete the application domain model;

[0065] Step S44: Repeat steps S42 and S43 to obtain a complete application domain model.

[0066] Specifically, in step S1 of this embodiment, the domain metamodel is an abstraction and condensation of the meta information of each element in the domain, and is composed of the domain metamodel code, the domain metamodel name, the domain metamodel multi-language, and the domain metamodel custom structure. The domain metamodel code is a unique identifier used to identify a metamodel; the domain metamodel name is a unique noun for the metamodel and should be simple, easy to understand, and unambiguous; the domain metamodel multi-language is the representation of the metamodel in different language environments; the domain metamodel custom structure is a more detailed and complete metamodel description information designed by each element in the metamodel according to its own attributes and in combination with actual scenarios and needs, which is equivalent to a scenario-based extension.

[0067] like Figure 1 and Figure 2 As shown, the specific structure or expression of the domain metamodel proposed in this embodiment is as follows:

[0068] (1) Based on the domain division, it is proposed to divide the domain into multiple bounded contexts. Multiple similar or related entities constitute a bounded context.

[0069] The custom composition of bounded context includes three aspects: context name, context type and context communication details. Bounded contexts are connected and integrated through context mapping (various forms of relationships), and messages and parameters are transmitted through context communication. The specific transmission method is the message and parameter transmission between an action in a modeling primitive in one bounded context and an action in a modeling primitive in another bounded context. Therefore, when designing the communication details of bounded context, the triggering action and the triggering action are considered. In addition, the communication details also specify the type elements, including subscribers and publishers, to control the direction of message transmission. At the same time, the bounded context types are specified to include three types: core context (required), common context (such as identity and access), and custom context (such as custom development). The boundary restrictions of bounded contexts and the design of data transmission can reduce uncertainty factors and prevent the model from becoming huge and confusing.

[0070] In addition, a common language for domain models, the vocabulary, is developed in a clear bounded context through a scenario. Its custom components include: vocabulary name, vocabulary type, and vocabulary description. Each element in the domain is controlled by the vocabulary, that is, a limited set of vocabulary is used to describe things, to prevent the abuse of vocabulary in the modeling process, resulting in the dilemma of semantic misalignment.

[0071] (2) After the bounded context is established, the focus is on defining the details of the bounded context, mainly the description of the entity and its static resources and dynamic events, that is, the description of a modeling primitive. The entity is the smallest abstract unit of the domain model and has elements such as attributes, constraints, instructions, actions, and states.

[0072] ·Attributes are properties of an entity. Their custom components include: attribute name, attribute type, attribute version, attribute alias, attribute namespace, and attribute extensibility.

[0073] A command is an action that an entity may be instructed to perform in a specific scenario. Its custom components include: command name, command duration, and command description.

[0074] Actions are actions that entities may perform in specific scenarios. Their custom components include: action name, action type, action parameters, and action return value. Action parameters are composed of action parameter name, action parameter type, action parameter value, and action parameter description. Actions are designed based on functional and responsive software engineering ideas. Behaviors are expressed in a functional way, which is not only easy to combine, but also can achieve the purpose of asynchronous and loose coupling. At the same time, the specific execution direction and method of the action are determined by specifying different parameters;

[0075] ·State refers to the state that an entity may have in a specific scenario. Its custom components include: state name, state type, and state description. Based on the above elements, the instructions, actions, and states of each entity can be arranged into an orderly process, and the processes of each entity can be used to describe specific domain events. In addition, the entity itself has constraints, and multiple entities have relationships and dependencies, so as to achieve more comprehensive control over the entity.

[0076] (3) The entity and its related static and dynamic elements can be regarded as a modeling primitive. A modeling primitive consists of an entity and a management shell. The entity is the carrier of static resources. The management shell is mainly responsible for carrying the dynamic input and output elements on the entity. The instructions and action elements of the entity in the domain enter the management shell as control data and business data, and the event and state elements are output by the management shell as state data and business data. As the smallest model element in the domain, the modeling primitive summarizes and describes the entity and its attributes, constraints, instructions, actions, and states. Therefore, the modeling primitive has a high cohesive characteristic. It is not only reusable, but also easy to combine. Combined with the context boundary composed of the modeling primitive set, it forms a content cohesive and data coupled model to achieve the purpose of reducing uncertainty.

[0077] (4) In addition, in order to ensure the correctness and standardization of data in flow, before control data and business data enter the modeling primitive, they need to be verified through certain data verification rules or methods. For example, the verification of XML format data can be verified by writing XSD files to verify the correctness and standardization of data. Through the data verification process, we can ensure that the correct data is delivered to the correct object at the right time and in the right way, thereby further limiting the uncertainty factors.

[0078] (5) The purpose of reducing uncertainty is achieved through the pre-description and precise control of the process. Therefore, in addition to using the process arrangement of each entity to describe the events in a specific application field, the domain metamodel proposed in the present invention also considers and defines a relatively abstract process flow of the entire scenario, and its custom composition includes: application scenario name and application scenario type. For different application scenarios, process flow specifications for different scenarios can be designed. The pattern of the specification should be similar to the process flow specification designed by PackML. They are all based on the ISA-88 state model, summarizing all the modes of a certain scenario and the operating states corresponding to different modes. Among them, the process flow is divided into two categories: general and variable processes according to different scenario modes. The general process refers to the general process that must be carried out in the scenario, and the variable process refers to one or more additional processes according to the different modes triggered in the scenario. Through the general and variable standardized process control, the uncertainty factor is further controlled by seeking the constant in the ever-changing. And the process flow model finally generated is used to further more accurately guide and standardize the operations such as the automatic construction of software in a certain scenario.

[0079] In addition, in the design of entities, the form of domain knowledge graph is used to express them. First, it can more conveniently display the relationship between entities and more visually display the knowledge base of a certain scenario. Secondly, it provides support for the completion of incomplete requirements: Since the application domain model constructed based on application domain, scenario knowledge and expert knowledge provides a relatively complete and standardized description of the knowledge in this field, for incomplete requirements, when establishing the application domain model, incomplete fields or behaviors can be manually modeled and completed based on the complete and standardized application domain, scenario knowledge and expert knowledge. The modeled requirements will reach a certain degree of completeness and will eventually be presented in the form of an application domain model. Finally, reasoning can be performed based on the knowledge graph to explore knowledge that has not been discovered in the scenario, further improve the application domain model, and provide more powerful and comprehensive support for the completion of incomplete requirements.

[0080] After the specific structure of the domain metamodel is defined, we start to consider the specific construction steps of the application domain model and how to apply it to the needs of automatic software construction. Figure 3 The basic route of domain modeling and the process of assisting in the process from requirements to code construction are as follows:

[0081] (1) As described in step S1, the domain metamodel is defined and constructed to address the incomplete requirements, business uncertainty, strong randomness, and other issues in the field of intelligent manufacturing, and draws on the ideas of DDD and software engineering. The element design format complies with the UBML specification.

[0082] (2) Based on the domain metamodel, the knowledge and scenario details of a certain domain are concretized to construct a specific application domain model. It should be noted that since the elements in the application domain model inherit from the domain metamodel, the application domain model should also comply with the UBML specification.

[0083] (3) Focus on introducing two structures: bounded context and modeling primitives. The purpose of gradually reducing uncertainty is achieved by combining the boundary definition and data transfer of bounded context with the domain knowledge graph, expressing dynamic elements in modeling primitives with functions, correctness verification during data transfer, and pre-description and precise control of processes. The complete knowledge system described by the domain knowledge graph with modeling primitives as nodes can also help to complete incomplete requirements. In addition, the domain knowledge graph representation of the application domain model helps to reason about the knowledge of the scene through algorithms to make the knowledge more complete.

[0084] (4) Through the previous step of reducing business uncertainty and completing incomplete requirements, the main forms of application domain model output include domain knowledge graphs, modeling primitives, UBML models, etc., in which a context containing multiple modeling primitives is visualized in the form of a graph and output in JSON or XML format. The output contains the specific information of the entities in each modeling primitive and all the relationships between the entities; in addition, in order to facilitate reconstruction and combination, the entities represented by each modeling primitive in the context can also be output separately, mainly including all the element information of the modeling primitive and all the relationship information it has. Based on these models, a business requirement model is generated, which is further automatically converted into module-level industrial control code, and the iterative updated requirement model is verified through formal verification.

[0085] In addition, in order to meet the modeling method's demand for automatic software construction, a domain modeling and model output system that supports low-code modeling languages ​​(such as UBML) is proposed. This system is oriented to the incomplete requirements and uncertainty characteristics of intelligent manufacturing scenarios. Based on the domain modeling method proposed above, it follows the description and specification of the domain metamodel proposed in the method to construct the structure of the domain model and its elements. This modeling tool can be used to visually construct a specific application domain model and generate a model that conforms to the UBML standard format, including:

[0086] (1) Input and output modules are configured as follows: Input and output modules are the data sources of each module of the model. Data is input into the model by automatically importing structured data in a certain field and manually constructing unstructured data. The final output is a model that conforms to the UBML standard, and the model storage format is XML file format.

[0087] (2) Context Boundary and Interface Module, which is configured to: describe multiple bounded contexts divided by a certain domain. A certain domain is further divided into different contexts, each context handles a specific unified transaction, and each context can communicate with each other.

[0088] (3) Entity and relationship module, which is configured to: describe the entities and relationships contained in a certain field. Each context contains several entities and relationships, which are stored and represented in the form of knowledge graphs, and entities have attributes, actions, states, instructions and other elements.

[0089] (4) Instruction, action and status module, which is configured to: describe the process standards in a certain field. The instructions, actions and states of each entity can be arranged in order, and at the same time, the overall manufacturing process in the field can also be arranged, thereby generating a set of process standards in the field.

[0090] Embodiment 2

[0091] This embodiment provides a domain modeling system for intelligent manufacturing, including:

[0092] The metamodel building module is configured to define a domain metamodel, specifying domain elements and modeling specifications that can be inherited by domain modeling;

[0093] The domain model initial unit construction module is configured to construct modeling primitives, use the modeling primitives to uniformly model the domain elements of the domain to be modeled, and construct a composable domain model basic unit;

[0094] The context boundary determination module is configured to reorganize the modeling primitives to unify them with the domain bounded context concept and clarify the boundaries of the bounded context in the specific domain model;

[0095] The application domain model completion module is configured to uniformly model domain elements based on the domain metamodel, combined with specific application domains, scenario knowledge and expert knowledge, and construct a knowledge graph with modeling primitives as nodes. During the construction process, the initial incomplete requirements can be gradually completed, and finally a relatively complete application domain model is obtained.

[0096] It should be noted here that the above-mentioned metamodel construction module, initial application domain model construction module, context boundary determination module and application domain model completion module correspond to steps S1 to S4 in Embodiment 1, and the above-mentioned modules and the corresponding steps implement the same examples and application scenarios, but are not limited to the contents disclosed in Embodiment 1. It should be noted that the above-mentioned modules as part of the system can be executed in a computer system such as a set of computer executable instructions.

[0097] Embodiment 3

[0098] This embodiment provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps in the domain modeling method for intelligent manufacturing as described in the above-mentioned embodiment 1 are implemented.

[0099] Embodiment 4

[0100] This embodiment provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the steps in a domain modeling method for intelligent manufacturing as described in the first embodiment above are implemented.

[0101] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.

[0102] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0103] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0104] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0105] A person skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0106] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A domain modeling method for intelligent manufacturing, characterized in that: include: Define a domain metamodel to specify the domain elements and modeling specifications that can be inherited by domain modeling; The inheritable domain elements include bounded context and boundary interface elements, vocabulary elements, entity and attribute elements, event and state elements, instruction and action elements, relationship and dependency elements; Construct modeling primitives, use modeling primitives to uniformly model the domain elements of the domain to be modeled, and construct composable domain model basic units, specifically: Considering the uncertainty in a specific domain, namely intelligent manufacturing, a modeling primitive is proposed. The modeling primitive structure combines the entity, action, and state elements in the metamodel. The modeling primitive is composed of an entity and a management shell; the entity is the carrier of static resources; the management shell is the dynamic input and output elements on the carrier entity; the instructions and action elements of the entity in the domain enter the management shell as control data and business data, and the events and state elements are output by the management shell as state data and business data; The connection between each modeling primitive is realized through the function call between the specific export or import functions, and the data is transferred through the parameter transfer of the function; the connection between the dynamic elements in the modeling primitive can also be realized through the combination or call of the functions inside the modeling primitive; Reorganize the modeling primitives to unify them with the concept of domain bounded context and clarify the boundaries of bounded context in specific domain models; Based on the domain meta-model, combined with specific application domains, scenario knowledge and expert knowledge, the domain elements are uniformly modeled and a knowledge graph with modeling primitives as nodes is constructed. During the construction process, the initial incomplete requirements are gradually completed. By dividing the domain into contexts and establishing clear boundaries to limit the scope of uncertainty and the way data is transmitted, uncertainty can be gradually reduced; ultimately, a relatively complete application domain model can be obtained; In response to the uncertainty reduction needs of business in intelligent manufacturing, the scope of uncertainty is limited by unifying the modeling primitives and bounded context concepts, clarifying the boundaries of bounded contexts composed of modeling primitives or sets of modeling primitives, and gradually reducing uncertainty through the transmission of verified deterministic data; In view of the incompleteness of requirements in intelligent manufacturing, the knowledge in the field is expressed through a knowledge graph standardized by the domain metamodel, and the incomplete requirements are further supplemented through the systematization of knowledge extraction, knowledge expression and knowledge reasoning; The modeling primitives have the characteristics of high cohesion, which are not only reusable but also easy to combine. Combined with the context boundary composed of the modeling primitive set, a content cohesive and data coupled mode is formed to reduce uncertainty. The domain metamodel also considers and defines a relatively abstract process flow of the entire scenario, reducing uncertainty through advance description and precise control of the process.

2. A domain modeling method for intelligent manufacturing as claimed in claim 1, characterized in that: Before using modeling primitives to uniformly model the domain elements of the domain to be modeled, common elements of multiple application domains to be modeled are summarized and abstracted.

3. The domain modeling method for intelligent manufacturing according to claim 1, characterized in that: The boundary of the bounded context includes context name, context type and context communication details; The context types include core context, common context and custom context.

4. A domain modeling method for intelligent manufacturing as claimed in claim 3, characterized in that: The context communication details define context type elements, which include two types: subscriber and distributor, and are used to control the direction of message delivery.

5. The domain modeling method for intelligent manufacturing according to claim 1, characterized in that: The modeling primitive is the smallest model element in the field, which centrally summarizes and describes entities and the attributes, constraints, instruction actions, and states contained in the entities.

6. A domain modeling system for intelligent manufacturing, characterized in that: include: A metamodel building module is configured to define a domain metamodel, specifying domain elements and modeling specifications that can be inherited by domain modeling; the inheritable domain elements include bounded context and boundary interface elements, vocabulary elements, entity and attribute elements, event and state elements, instruction and action elements, and relationship and dependency elements; The domain model initial unit construction module is configured to construct modeling primitives, use modeling primitives to uniformly model the domain elements of the domain to be modeled, and construct a composable domain model basic unit, specifically: Considering the uncertainty in a specific domain, namely intelligent manufacturing, a modeling primitive is proposed. The modeling primitive structure combines the entity, action, and state elements in the metamodel. The modeling primitive is composed of an entity and a management shell; the entity is the carrier of static resources; the management shell is the dynamic input and output elements on the carrier entity; the instructions and action elements of the entity in the domain enter the management shell as control data and business data, and the events and state elements are output by the management shell as state data and business data; The connection between each modeling primitive is realized through the function call between the specific export or import functions, and the data is transferred through the parameter transfer of the function; the connection between the dynamic elements in the modeling primitive can also be realized through the combination or call of the functions inside the modeling primitive; The context boundary determination module is configured to reorganize the modeling primitives to unify them with the domain bounded context concept and clarify the boundaries of the bounded context in the specific domain model; The application domain model completion module is configured to uniformly model domain elements based on the domain metamodel, combined with specific application domains, scenario knowledge and expert knowledge, and construct a knowledge graph with modeling primitives as nodes. During the construction process, the initial incomplete requirements can be gradually completed; By dividing the domain into contexts and establishing clear boundaries to limit the scope of uncertainty and the way data is transmitted, uncertainty can be gradually reduced; ultimately, a relatively complete application domain model can be obtained; In response to the uncertainty reduction needs of business in intelligent manufacturing, the scope of uncertainty is limited by unifying the modeling primitives and bounded context concepts, clarifying the boundaries of bounded contexts composed of modeling primitives or sets of modeling primitives, and gradually reducing uncertainty through the transmission of verified deterministic data; In view of the incompleteness of requirements in intelligent manufacturing, the knowledge in the field is expressed through a knowledge graph standardized by the domain metamodel, and the incomplete requirements are further supplemented through the systematization of knowledge extraction, knowledge expression and knowledge reasoning; The modeling primitives have the characteristics of high cohesion, which are not only reusable but also easy to combine. Combined with the context boundary composed of the modeling primitive set, a content cohesive and data coupled mode is formed to reduce uncertainty. The domain metamodel also considers and defines a relatively abstract process flow of the entire scenario, reducing uncertainty through advance description and precise control of the process.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps in the domain modeling method for intelligent manufacturing as described in any one of claims 1 to 5 are implemented.

8. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps in the domain modeling method for intelligent manufacturing as described in any one of claims 1-5 are implemented.