CN120179249B - Object-process relationship modeling method, device, terminal and medium - Google Patents
Object-process relationship modeling method, device, terminal and mediumInfo
- Publication number
- CN120179249B CN120179249B CN202510642559.2A CN202510642559A CN120179249B CN 120179249 B CN120179249 B CN 120179249B CN 202510642559 A CN202510642559 A CN 202510642559A CN 120179249 B CN120179249 B CN 120179249B
- Authority
- CN
- China
- Prior art keywords
- type
- simulation model
- target
- deduction
- modeled
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a modeling method, a device, a terminal and a medium of an object process relation, which comprise the steps of responding to modeling operation aiming at a to-be-modeled requirement, determining a simulation model corresponding to the to-be-modeled requirement based on a type element, a process element and a relation element, wherein the simulation model is used for expressing the to-be-modeled requirement by utilizing a target type element and a corresponding type definition, a design view, a target process element and a corresponding process definition, a design view and a target relation element thereof, responding to scene definition operation aiming at the simulation model, determining a scene corresponding to the simulation model, wherein the scene is used for describing flow control or test cases of the simulation model, determining deduction configuration parameters corresponding to the simulation model, and deducting the simulation model based on the deduction configuration parameters by taking the scene as an entrance to obtain a deduction result corresponding to the to-be-modeled requirement. The invention can effectively alleviate the problem of limitation in the prior art and can describe more abundant requirements.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a method, an apparatus, a terminal, and a medium for modeling an object process relationship.
Background
At present, the existing modeling mode is mainly used for modeling through languages such as SysML, which is a general graphical modeling language and is designed to be used in system engineering so as to support demand analysis, architecture definition, behavior modeling, verification and the like of a system. However, this language has certain limitations, such as complex logic or the inability to describe the requirements.
Disclosure of Invention
In view of the above, the present invention aims to provide a modeling method, apparatus, terminal and medium for object process relationship, which can effectively alleviate the problem of limitation existing in the prior art, and can describe richer requirements.
In a first aspect, the present invention provides a modeling method of an object process relationship, where the method is applied to a terminal, the terminal is configured with a type element, a process element, and a relationship element, and the terminal displays the type element, the process element, and the relationship element through a graphical user interface, and the method includes:
responding to modeling operation aiming at a requirement to be modeled, determining a simulation model corresponding to the requirement to be modeled based on type elements, process elements and relation elements, wherein the simulation model is used for expressing the requirement to be modeled by utilizing target type elements and corresponding type definition views and type design views thereof, target process elements and corresponding process definition views and process design views thereof and target relation elements;
Responding to scene definition operation aiming at the simulation model, determining a scene corresponding to the simulation model, wherein the scene is used for describing flow control or test cases of the simulation model;
Determining deduction configuration parameters corresponding to the simulation model, and deducting the simulation model based on the deduction configuration parameters by taking the scene as an entrance to obtain a deduction result corresponding to the requirement to be modeled.
In a second aspect, the present invention also provides a modeling apparatus for object process relationships, the apparatus being applied to a terminal, the terminal being configured with a type element, a process element, and a relationship element, the terminal displaying the type element, the process element, and the relationship element through a graphical user interface, the apparatus comprising:
The modeling module is used for responding to modeling operation aiming at the requirement to be modeled, determining a simulation model corresponding to the requirement to be modeled based on the type elements, the process elements and the relation elements, wherein the simulation model is used for expressing the requirement to be modeled by utilizing the target type elements and the corresponding type definition views and the type design views thereof, the target process elements and the corresponding process definition views and the process design views thereof and the target relation elements;
The scene definition module is used for responding to scene definition operation aiming at the simulation model, determining a scene corresponding to the simulation model, wherein the scene is used for describing flow control or test cases of the simulation model;
the model deduction module is used for determining deduction configuration parameters corresponding to the simulation model, deducting the simulation model based on the deduction configuration parameters by taking the scene as an inlet, and obtaining a deduction result corresponding to the requirement to be modeled.
In a third aspect, the invention also provides a terminal comprising a processor and a memory, the memory storing computer executable instructions executable by the processor, the processor executing the computer executable instructions to implement the method of any one of the first aspects.
In a fourth aspect, the invention also provides a computer-readable storage medium storing computer-executable instructions that, when invoked and executed by a processor, cause the processor to implement the method of any one of the first aspects.
The modeling method, the device, the terminal and the medium for the object process relation are provided with type elements, process elements and relation elements in advance, firstly respond to modeling operation aiming at the requirement to be modeled, determine a simulation model corresponding to the requirement to be modeled based on the type elements, the process elements and the relation elements, the simulation model is used for expressing the requirement to be modeled by utilizing a target type element and a corresponding type definition view, a type design view, a target process element and a corresponding process definition view, a process design view and a target relation element, then respond to scene definition operation aiming at the simulation model, determine a scene corresponding to the simulation model, the scene is used for describing flow control or test cases of the simulation model, finally determine deduction configuration parameters corresponding to the simulation model, and deduct the simulation model based on the deduction configuration parameters by taking the scene as an entrance to obtain a deduction result corresponding to the requirement to be modeled. According to the method, the requirements to be modeled are abstracted into the types, the processes and the relations, the types are the expression modes of the objects, namely, the simulation models corresponding to the requirements to be modeled are constructed based on the relation of the object processes, the scenes and the deduction configuration parameters corresponding to the simulation models are defined on the basis, and finally, the deduction results corresponding to the requirements to be modeled are obtained through model deduction.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
In order to make the above objects, features and advantages of the present invention more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic flow chart of a modeling method of object process relationship according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of objective, association and development of a thing according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of an interface of a definition type according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an interface after defining type elements according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of an interface after defining a type element according to another embodiment of the present invention;
FIG. 6 is an interface schematic of one type of design view provided by an embodiment of the present invention;
FIG. 7 is a schematic diagram of a definition view of one type of "post" provided by an embodiment of the present invention;
FIG. 8 is a view of a design view of one type of "post" provided by an embodiment of the present invention;
FIG. 9 is a schematic diagram of a definition view of a process "add a tray on top" provided by an embodiment of the present invention;
FIG. 10 is a schematic diagram of a design view of a process "add a tray on top" provided by an embodiment of the present invention;
FIG. 11 is a schematic diagram of a definition view of a process "move a tray overhead" provided by an embodiment of the present invention;
FIG. 12 is a schematic diagram of a design view of a process "top removal of a tray" provided by an embodiment of the present invention;
FIG. 13 is a schematic diagram of a definition view of one type of "Hanotor" provided by an embodiment of the present invention;
FIG. 14 is a schematic diagram of a design view of one type of "Hanotor" provided by an embodiment of the present invention;
FIG. 15 is a diagram of a definition view of a process "initialization" provided by an embodiment of the present invention;
FIG. 16 is a schematic diagram of a design view of a process "initialization" provided by an embodiment of the present invention;
FIG. 17 is a schematic diagram of a definition view of a sub-process "create a tray" provided by an embodiment of the present invention;
FIG. 18 is a schematic diagram of a design view of a sub-process "create a tray" provided by an embodiment of the present invention;
FIG. 19 is a schematic diagram of a definition view of a sub-process "temporary process 2" provided by an embodiment of the present invention;
FIG. 20 is a schematic diagram of a definition view of a process "move a tray" provided by an embodiment of the present invention;
FIG. 21 is a schematic diagram of a design view of a process "move a tray" provided by an embodiment of the present invention;
FIG. 22 is a schematic diagram of a definition view of a process "move" provided by an embodiment of the present invention;
FIG. 23 is a schematic diagram of a process "mobile" involving view provided by an embodiment of the present invention;
FIG. 24 is a schematic diagram of a view of another process "move" provided by an embodiment of the present invention;
FIG. 25 is a diagram showing a definition view of a sub-process "calculate new number of trays" according to an embodiment of the present invention;
FIG. 26 is a schematic diagram of a design view of a sub-process "calculate new number of trays" provided by an embodiment of the present invention;
FIG. 27 is a design view of a scenario provided by an embodiment of the present invention;
FIG. 28 is a schematic diagram of a process "end" provided by an embodiment of the present invention;
FIG. 29 is a schematic diagram of an interface for a desired configuration according to an embodiment of the present invention;
FIG. 30 is a schematic diagram of an interface for a proposed manufacturing according to an embodiment of the present invention;
FIG. 31 is a schematic diagram of a modeling apparatus for modeling object process relationships according to an embodiment of the present invention;
Fig. 32 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described in conjunction with the embodiments, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
At present, based on the prior art scheme, the problems and disadvantages of the prior art are found from an objective view, and the problems and disadvantages are that (1) the prior modeling method is multiple in variety and complex in modeling mode, (2) the prior modeling technology is multiple in variety of each type of primitive, and the user is difficult to use, and (3) the prior modeling method does not support logic modeling or arithmetic modeling. Based on the above, the modeling method, the modeling device, the modeling terminal and the modeling medium for the object process relationship are provided, have the advantages of being more concise, small in element number and the like, can effectively relieve the problem of limitation in the prior art, and can describe richer requirements.
For the understanding of the present embodiment, first, a modeling method of an object process relationship disclosed in the present embodiment of the present invention is described in detail, where the method is applied to a terminal, the terminal is configured with a type element, a process element, and a relationship element, and the terminal displays the type element, the process element, and the relationship element through a graphical user interface, and referring to a flow chart of the modeling method of an object process relationship shown in fig. 1, the method mainly includes steps S102 to S106:
step S102, responding to modeling operation aiming at the requirement to be modeled, and determining a simulation model corresponding to the requirement to be modeled based on the type elements, the process elements and the relation elements.
The simulation model is used for expressing requirements to be modeled by utilizing a target type element and a corresponding type definition view and a type design view thereof, a target process element and a corresponding process definition view and a process design view thereof, wherein the type definition view of the target type element is used for expressing members of the requirements to be modeled, the process definition view of the target process element is used for expressing behaviors of the target type element, the target relationship element is used for describing type relationships among the target type elements, process relationships among the target process elements and type-process relationships among the target type element and the target process element, the type design view is a view for describing an internal structure of the target type element through the type relationships and the type-process relationships, and the process design view is a view for describing operation control logic among sub-processes contained by the target process element through the process relationships.
In one example, the type elements, the process elements and the relation elements can be displayed through a graphical user interface, the type elements are usually used in a modeling tool to express the objects, namely, the type elements are carriers of the objects, the modeling is performed based on an object process relation set, specifically, the modeling is performed in response to the defining operation of a modeler on the type elements, the defining operation of the process elements, the defining operation of the relation elements, the realizing operation of the type elements and the realizing operation of the process elements, so as to construct a simulation model corresponding to the requirement to be modeled, wherein the simulation model can be operated, and the operation simulation model can be in a code form or a primitive form.
Step S104, responding to scene definition operation aiming at the simulation model, and determining a scene corresponding to the simulation model.
The scene is used for describing the flow control or the test case of the simulation model, namely the scene can be regarded as one flow control or one test case. In one example, a scenario corresponding to a simulation model may be generated in response to a modeler's defining operations for the scenario, for performing flow control or test cases on the simulation model.
Step S106, determining deduction configuration parameters corresponding to the simulation model, and deducting the simulation model based on the deduction configuration parameters by taking the scene as an entrance to obtain deduction results corresponding to the requirements to be modeled.
The deduction configuration parameters may include a desired name, stepping accuracy, start time, stop condition, pause condition, deduction speed, initial attribute values of members of the requirements to be modeled, and the like. In one embodiment, the modeling is responded to perform operations such as configuration and fabrication of the simulation model to obtain a deduction configuration parameter, and the deduction is performed on the simulation model based on the scene and the deduction configuration parameter in response to deduction triggering operation of the modeling, wherein the deduction is based on a defined logic of a scene defined in the simulation model, a target type element and a target process element used in the scene, from a given initial attribute value, evolution and operation step by step, and finally, the deduction is terminated when a stopping condition is reached, and the value of each instance after the deduction is stopped and the value of the member attribute thereof are regarded as a deduction result.
According to the modeling method for the object process relation, which is provided by the embodiment of the invention, the requirements to be modeled are abstracted into the types, the processes and the relation, the types are the expression modes of the objects, namely, the simulation model corresponding to the requirements to be modeled is constructed based on the object process relation, the scene and the deduction configuration parameters corresponding to the simulation model are defined on the basis, and finally, the deduction result corresponding to the requirements to be modeled is obtained through model deduction.
The embodiment of the invention firstly explains the basic idea that the world is objective, relevant and developed. An objective, associative, and evolutionary schematic diagram of an Object, such as that shown in fig. 2, is expressed in terms of objects (objects) that are used to carry observable and descriptive information about the Object, an associative relationship (Relation) that is used to describe the associative relationships between objects, between objects and processes, and between processes, and an evolutionary relationship (Process) that is used to describe the evolutionary and variational relationships of objects, and a Process that is used to generate and die.
For easy understanding, the embodiment of the invention provides a specific implementation mode of a modeling method of object process relation.
For the foregoing step S102, the embodiment of the present invention provides a specific implementation manner of determining, in response to a modeling operation for a requirement to be modeled, a simulation model corresponding to the requirement to be modeled based on a type element, a process element and a relationship element, see the following steps 1 to 4:
Step 1, abstract the demand to be modeled based on the type elements, the process elements and the relation elements in response to the abstract operation aiming at the demand to be modeled, so as to determine the type definition view of the target type elements, the process definition view of the target process elements and the target relation elements corresponding to the demand to be modeled. Specifically, the method comprises the steps of defining a target type element, defining a target process element, defining a target relation element and the like.
And 1.1, defining a target type element, wherein the target type element is used for expressing members of requirements to be modeled. In the embodiment of the invention, all descriptions of the requirements to be modeled are performed based on types, and the types are abstractions of the requirements to be modeled. A type may have members and attributes for expressing characteristics of the type and a type may have procedures for expressing behavior of the type.
In one embodiment, the process of a type is defined, i.e., a process that is clear of the members, attributes, and process descriptions that the type has. Referring to the interface schematic diagram of a definition type shown in fig. 3, an initial type can be obtained in response to an operation of adding a type for a type control, and continuing to refer to the interface schematic diagram after a definition type element shown in fig. 4, the type name defaults to be "type 1", and a graphic element of the lower graph can be double-clicked or a pen icon on the right side of the left type tree "type 1" can be clicked for modification, so that a definition view of the type can be obtained.
And 1.2, defining a target process element, wherein the target process element is used for expressing the behavior of the target type element. In an embodiment of the invention, the type of behavior is expressed by a process. The process may have no parameters or parameters. Parameters are one of the mediators of process interactions with the model world, and one of the carriers by which processes affect or change object instances. The members and attributes of the process's belonging type are directly usable in the process, and are the only medium and carrier for the process without parameters to interact with the model world. In one embodiment, the process of defining the process, that is, the process of describing the relationship between the parameters of the process and the members and attributes of the type of the process clearly, finally obtains a defined view of the process.
And 1.3, defining target relation elements, wherein the target relation elements are used for describing type relations among target type elements, process relations among target process elements and type-process relations among the target type elements and the target process elements.
In one embodiment, defining members and properties of a type requires the use of structural relationships, defining parameters of a process requires the use of procedural relationships, and defining interactions of a process with an instance requires the use of procedural relationships. For example, referring to a relationship summary table shown in table 1 below, the relationship summary table is divided into a structural relationship and a program relationship, where the structural relationship includes a composition relationship, a characterization relationship, an inheritance relationship, a attribution relationship, a structural control relationship, a unidirectional tagged relationship, a bidirectional tagged relationship, and the like, and the program relationship includes a consumption relationship, a generation relationship, an input influence relationship, an output influence relationship, a bidirectional influence relationship, a state conversion relationship pair, a dominant relationship, a conditional relationship, a calling relationship, an auto-tuning relationship, a timeout exception calling relationship, a time shortage exception calling relationship, and the like.
TABLE 1 relational summary table
And 2, determining a type design view corresponding to the target type element in response to the implementation operation aiming at the target type element, wherein the type design view is a view describing the internal structure of the target type element through a type relation and a type-process relation. Wherein a definition view of a type specifies the relationship of the type to other types, including the source of the type, i.e., inheritance relationships. In the embodiment of the invention, the implementation of the type corresponds to a design view of the type, and the design view of the type details the relationship and interaction among the components (members, attributes and processes) of the type, including events, calls, parameter bindings and the like. Instances such as "Zhang Sano" of class "need to be automatically started and run its process" grow "continuously after creation, i.e., the presence of an instance triggers the process" grow ", which is defined in the implementation view of the class.
In one embodiment, referring to the interface schematic diagram after another definition type element shown in fig. 5, a "design view" control is displayed at the left "type 1" control, and in response to a clicking operation for the "design view" control, the interface is switched to the type design view, such as the interface schematic diagram of one type of design view shown in fig. 6, and in the tool box indicated by the arrow in fig. 6, the "member m", "attribute a", "process", "constant c" and "remark" controls are displayed from top to bottom, and in response to an editing operation for the above controls, so as to obtain the type design view.
In specific implementation, first, in response to a creation operation of a primary type element aiming at a requirement to be modeled, determining members and processes contained in the primary type element, for each member in the primary type element, the member can serve as a secondary type element, determining the members and processes contained in the secondary type element, and repeating the process until the composition and the behavior contained in the requirement to be modeled are clearly described by using the multi-level element type.
And 3, determining a process design view corresponding to the target process element in response to the implementation operation aiming at the target process element, wherein the process design view is a view for describing operation control logic among sub-processes contained in the target process element through a process relation. In the embodiment of the invention, the process is the definition of the type of behavior, the realization of the process is the detailed description of the type of behavior, the realization of the process corresponds to a process design view, the process can have four sub-processes, and the sources of the sub-processes are 1) a temporary sub-process, 2) other processes of the belonging class, 3) a built-in process predefined by a system and 4) the processes belonging to the examples can be used through temporary variables, parameters, members and attributes of the process.
Further, the operation control logic between the sub-processes is defined by using a suitable program relationship, and the foregoing table 1 can be referred to specifically, which is not described in detail in the embodiment of the present invention.
Furthermore, the sub-process can also have own sub-process, so that a tree structure which is gradually thinned layer by layer, is simple and reasonable in abstraction and encapsulation, has clear global view and enough detail view, and has the capabilities and characteristics of componentization and modularization.
Further, in response to an anchor point connection operation for the process design view, a connection is made between parameters of the sub-process in the process design view and instances required by the sub-process to display an anchor point of the sub-process in the process design view when the process design view uses the sub-process, prompting a user to connect the instances for the sub-process. Taking the type "adder" as an example, the members include "addend 1", "addend 2" and "sum", and the process includes "addition", it is necessary to connect the process "addition" with the members "addend 1" and "addend 2". The representation of the parameters of the process is an anchor point, which is not displayed if the sub-process has no parameters in practice, but is still used. The anchor point is used for displaying in the scene that the sub-process is used, and reminding the user that the sub-process needs to be connected with an instance.
Further, in response to additional binding operations for the process design view, a connection is made between a sub-process and an instance in the process design view. Wherein the additional binding is to establish a relationship between an instance in the parent process design view and the child process, the instance sources are members/attributes of the belonging class, temporary members/constants defined in the parent process design view, parameters of the parent process, predefined internal object instances, etc. In one embodiment, the instances can be additionally connected to the process through relationships outside the anchor point binding, the capability of temporarily expanding the process is maintained outside the process definition function, the type "data preprocessing" is taken as an example, the member comprises "data 1", the process comprises "preprocessing", the member "data 1" and the process "preprocessing" are connected, the process "preprocessing" can be implemented on the member "data 1", on the basis, if the new member "data 2" exists, the process "preprocessing" can be implemented on the member "data 2" through the additional connection of the member "data 2" and the process "preprocessing", and the capability of the process "preprocessing" is expanded.
And 4, obtaining a simulation model corresponding to the requirement to be modeled based on the target type element and the corresponding type design view thereof and the target process element and the corresponding process design view thereof.
In order to facilitate understanding of the foregoing steps 1 to 4, the embodiment of the present invention provides a specific application example of building a simulation model corresponding to a hanota, taking a simple hanota as an example. Comprising the following steps:
(1) Type definition and implementation a schematic diagram of a definition view of a type "post" such as that shown in fig. 7, fig. 7 illustrates that members of a type include posts. A view of a design view of a type "pillar" such as that shown in fig. 8, fig. 8 illustrates a type design view including members and a process, m representing a member "tray list", the members being expressed in rectangular primitives, the member "tray" being explained as an array, the element types being integers, an integer representing a tray being used in the embodiment of the present invention, the process being expressed in oval primitives, the process including "adding a tray on top", "moving a tray on top".
(2) Process definition and implementation:
A schematic diagram of a definition view of a process "add one on top" such as that shown in fig. 9, fig. 9 illustrates the relationship between the member "plate" and the process "add one on top" shown within the definition design view. The explanation of the member 'plate' is shown below, wherein the P in the upper left corner represents a parameter, the name is a plate, and the element type is an integer. A schematic diagram of a design view of a process "add a plate on top" such as that shown in fig. 10, where the process "tail add element" is a predefined process of an array, i.e., a process of a member "plate list", fig. 10 means that an instance of a parameter transfer is bound to an anchor point of the process "tail add element".
A schematic diagram of a definition view of a process "top-up-take-away-one-tray" such as shown in fig. 11, and fig. 11 illustrates a relationship between a member "tray" and a process "top-up-take-one-tray" shown in the definition design view, and a relationship between parameters and a process is a non-null output influence relationship. A schematic diagram of a design view of a process "take one plate off top" such as that shown in fig. 12, using the process "tail remove element" of the member "plate list" to bind the parameter "plate" to the anchor point of the process "tail remove element", which is a non-null influencing output anchor point, would put the removed element instance into the parameter "plate".
Furthermore, the embodiment of the invention takes a complex Hanotor as an example, and provides a specific application example for building a simulation model corresponding to the Hanotor. Comprising the following steps:
(1) Type definition and implementation:
a schematic diagram of a definition view of a type "hanotor" such as that shown in fig. 13, the type "hanotor" has no inheritance relationship.
A schematic diagram of a design view of one type "Hanoto" such as that shown in FIG. 14, includes four members, member "plate number", member "source post", member "auxiliary post" and member "target post". Wherein, the number of plates of the member represents the number of the Hanotor stages, the types are integers, the number of plates of the member represents the three columns in the Hanotor game, the types of the member are all the columns, and each plate of the member is a plate list, a plate is added on the top of the process, and a plate is removed on the top. Three processes are also included, process "initialization", process "move" and process "move one tray". Wherein the process "initializes" i.e. initializes the hanota game, the process "move" i.e. moves the plates all from the parameter source column to the parameter target column, the process "move one plate" is a special movement, moves one plate on top of the parameter source column to the parameter target column.
(2) Process definition and implementation:
A schematic diagram of a definition view of a process "initialization" such as that shown in fig. 15, the relationship of the number of parameter plates to the process "initialization" is a non-null influence input relationship. A schematic diagram of a design view of one process "initialization" such as that shown in fig. 16, includes member "number of trays", member "index", member "source column". Fig. 16 also illustrates that embodiments of the present invention use a system global built-in process with assignments b=a, comparison c=a > b, self-subtraction of a-, addition of a tray "on top of a process using member" source column ", creation of a tray" and a sub-process "temporary process 2" using a sub-process defined internally of the process. It can be seen that this is a loop with the goal of adding the parameter "number of trays" to the member "source column", and with the large trays down and the small trays up, the tray sizes on the source column are arranged in descending order from bottom to top, with the largest tray being equal to the number of trays and the smallest tray being 1.
The embodiment of the invention further explains the temporary process, namely the action range is invisible to the outside inside the father process. The embodiment of the invention relates to two temporary processes, namely a sub-process of creating a plate and a sub-process of temporary process 2.
For a sub-process "create a tray", such as the one shown in FIG. 17, a schematic diagram of a defined view of "create a tray" involves two parameters, "tray size" and "tray", which will create a "tray" from the input parameter "tray size" into the output parameter "tray". A schematic diagram of a design view of a sub-process "create a tray" such as that shown in fig. 18, the execution flow starts from sub-process "temporary process 1", creates an instance "tray" put into parameter "tray", and then calls the system built-in process "assign b=a" to assign the value of parameter "tray size" to parameter "tray". The sub-process "temporary process 1" in the figure has no specific definition view and design view, or its definition view and design view are empty, because it has no specific logic, but the lift has performed a "results" relationship, creating a "plate" instance, so it is an empty process.
For the sub-process "temporary process 2", which has only a definition view, or design view, empty, such as a schematic diagram of a definition view of a sub-process "temporary process 2" shown in fig. 19, the sub-process "temporary process 2" has no parameters, but has java code in the sense that the string "end of initialization" is output using addProblem in the process API.
A schematic diagram of a defined view of a process "move a tray" such as that shown in FIG. 20 involves two parameters, "source column", "target column", and the relationship between both parameters and the process is a non-null bi-directional influencing relationship. A schematic diagram of a design view of a process "move a tray" such as that shown in fig. 21, the process "move a tray overhead" is performed, and the process "add a tray overhead" is invoked. Fig. 21 illustrates that starting with the process "take a plate on top of the parameter" source column ", its output parameters are bound to the input parameters of the process" add a plate on top of the parameter "target column", which is a direct transfer of parameters, since no temporary variables are defined in between.
A schematic diagram of a definition view of a process "move" such as that shown in FIG. 22 involves four parameters, parameter "number of plates", parameter "source column", parameter "auxiliary column", parameter "target column", where parameter "number of plates" represents the number of stages of the Hanot (or small Hanot formed in the process) to be moved, note that the process of Hanot movement is a recursively nested process, so that it is possible that each time the process "move" is performed the facing Hanot is different, parameter "source column", parameter "auxiliary column", parameter "target column" represent the source column, auxiliary column, target column of the current movement, respectively.
A schematic diagram of a view of one process "move" such as shown in fig. 23 and a schematic diagram of a view of another process "move" such as shown in fig. 24, both fig. 23 and 24 illustrate the operation control logic between the various sub-processes in the process "move". Wherein, FIG. 23 illustrates nodes at the beginning of the flow, and marks the process "move" using itself, indicating that the process "move" is a recursive nested process, it should be noted that the parameter "source post", the parameter "auxiliary post", and the parameter "target post" are changed in meaning when bound to different processes, such as role switching when bound to the nested itself, and FIG. 24 illustrates that the parameter "target post" is bound to an anchor "auxiliary post" of the process "move".
Further, the process "move" also involves a temporary sub-process "calculate new number of trays", such as a schematic diagram of a definition view of one sub-process "calculate new number of trays" shown in fig. 25 and a schematic diagram of a design view of one sub-process "calculate new number of trays" shown in fig. 26.
For the foregoing step S104, the embodiment of the present invention provides an implementation manner of determining a scene corresponding to a simulation model in response to a scene definition operation for the simulation model. In one example, a scene may be understood as a type, which expresses the modeler's intent using target type elements defined in a simulation model.
Continuing with the foregoing complex hanotor example, see the design view of a scene shown in fig. 27, fig. 27 illustrates that the scene contains scene members "hanotor" and "number of trays" and the like. Specifically, fig. 27 indicates a flow start node, at which the creation of a member "hanotor" triggers a process "initialization" of the hanotor to be 3-level, the initialization execution finishes the process "move" of the hanotor, the member "plate number", "source column", "auxiliary column" and "target column" of the hanotor are bound to their corresponding parameters, and the movement execution finishes the process "end" which is a process called in the scene. Referring to a schematic of a process "end" shown in FIG. 28, both the definition view and the design view of the process "end" are empty, but there is java code that has the meaning of outputting a question string using addProblem in the process API, move end.
In summary, the whole flow of model drawing is to define a type, a member of the type, a process of the type, a definition of the process, an implementation of the process, a definition and use of a sub-process, a flow of a scene, use of various elements in the flow, binding of an anchor point (parameter) and an instance when the process is used, and writing of process codes (such as JAVA, python and the like).
For the foregoing step S106, the embodiment of the present invention further provides an implementation manner of determining a deduction configuration parameter corresponding to a simulation model, and deducting the simulation model based on the deduction configuration parameter by taking a scene as an entry to obtain a deduction result corresponding to a requirement to be modeled, including the following steps a to b:
Step a, determining deduction configuration parameters corresponding to the simulation model in response to configuration operation aiming at the simulation model, wherein the deduction configuration parameters at least comprise stepping precision, starting time, stopping conditions, deduction speed and initial attribute values of members of requirements to be modeled.
In a specific implementation, the method is divided into two steps of wanted configuration and wanted customization.
Referring to an interface schematic of a desired configuration shown in FIG. 29, the desired configuration includes creating the desired configuration using the built model. Including configuration name, usage model, intended scene, intended way (default form intended), intended way of members and attributes that appear in the intended scene, and data source.
Referring to an interface schematic diagram of a desired preparation shown in fig. 30, the desired preparation includes configuring various data including a desired name, a stepping accuracy, a start time, a stop condition, a pause condition, a speed, a value of a member attribute to be initialized in a desired configuration, and the like, on the basis of the desired configuration.
And b, responding to deduction triggering operation aiming at the simulation model, taking a scene as an entrance, deducting the simulation model by event driving based on stepping precision, starting time, deduction speed and initial attribute values of members of the requirement to be modeled, and stopping deducting the simulation model when a stopping condition is met to obtain a deduction result corresponding to the requirement to be modeled.
The deduction is defined logic according to a scene defined in a model, classes used in the scene and a process, evolution and operation step by step are started from the given initial attribute value, and finally, the deduction is terminated when a stopping condition is reached, and the value of each instance after the deduction is stopped and the value of the member attribute are regarded as a deduction result. In the deduction process, the values of the respective instances before and after each step starts and after the end, and the values of the member attributes thereof, are the deduced step snapshots.
The event comprises one or more of a presence trigger, a value change trigger, an extinction trigger, a state acquisition trigger and a state losing trigger, wherein the presence trigger is a trigger when an instance is generated for a specified target type element, the value change trigger is a trigger when the value of the instance generated for the specified target type element changes, the extinction trigger is a trigger when the instance generated for the specified target type element is subjected to extinction, the state acquisition trigger is a trigger when the instance generated for the specified target type element acquires a state, and the state losing trigger is a trigger when the instance generated for the specified target type element loses a state. Summary table of one program relationship combined with events such as shown in table 2:
Table 2 summary table of program relationships and event combinations
Illustratively, as described in the definition class, the instance "Zhang Sano" of the type "human" needs to be automatically started and continuously run its process "grow" after creation, i.e., the presence of the instance triggers the process "grow". This mechanism is called event driven. Events are supported not only in the class design view, but also in the definition view of the process. Model deduction is not performed according to a predefined flow, but is performed by event-driven. The definition of types and scenes is simply the definition of rules under which the deduced flow trend depends on the event. Event-driven enables the system to support both flow-specific models and model deductions, and flow-ambiguous models and model deductions. The deduction of the explicit flow is performed if the event is not used, and the deduction of the ambiguous flow can be performed by using the event driving mechanism.
Further, the deduction configuration parameter further comprises a pause condition. In an embodiment of the present invention, the method further includes:
and step I, suspending the deduction of the simulation model when a suspension condition is met in the deduction process of the simulation model, or suspending the deduction of the simulation model in response to the deduction suspension operation aiming at the simulation model. And step II, responding to the modification operation of the simulation model and the deduction configuration parameters to obtain a modified simulation model and/or modified deduction configuration parameters. And step III, responding to deduction triggering operation aiming at the simulation model, and continuing deduction of the simulation model based on deduction configuration parameters in the scene. In practical application, in the deduction process, if the suspension condition is met, the deduction also suspends the deduction. In the suspend state, it is convenient to modify the values of the respective instances or instance member attributes, and a new suspend condition may be set. Of course, non-suspended/running is also possible. In addition, during the deduction process, the user can pause/stop the deduction through the monitoring interface and the pause/stop task button. And continuing to run the deduction through a continue operation button. The deduction is pushed forward further/multiple steps by stepping the button once/multiple times.
Further, a query result may be determined in response to a query operation for the simulation model, and the query result may be displayed through a graphical user interface, where the query result includes information of the simulation model, detailed information of deduction of the simulation model, and data generated during deduction of the simulation model. In one example, the deduction interface provides a query for information such as deduction progress summary information, events, questions, and messages. And providing inquiry of various information such as definition information of the class and definition information of the class process in the model used for deduction. In one example, in the deduction process, the query of the instance information of each class is provided, and the execution details of the process of each instance include the information of the process itself, the information of the instance corresponding to the process using parameters, the information of the sub-process, and the like.
Further, the deduction service provides a Restful interface for the front-end interface/other services to actively inquire information and control deduction.
Further, the deduction service pushes deduction information in real time through webSocket and can accept commands to control deduction.
In summary, the embodiment of the present invention has at least the following features:
1. The method is simple, the comprehensive description of the service in the field of system engineering is realized by using a type of view and a simplified modeling primitive, and the learning and use cost is low. The user modeling and reading the model does not need programming experience, but would help modeling and work with the model if having Object Oriented (OO) concepts. 2. Layering, namely satisfying a system thinking mode from macroscopic to microscopic by using a layering mode, and realizing focusing of key problems and layer-by-layer refinement of solutions. 3. The method can generate a natural language model equivalent to the graphic language model, and can be used for realizing model understanding by service users and facilitating the butt joint and the use of LLM. 4. The system is complete in support of logic modeling, flow modeling and arithmetic modeling, and provides comprehensive support for system engineering modeling. 5. The method can run, namely a model which can simulate running without codes can be constructed, and the native has elements for supporting simulation. 6. Code extension, the description logic can be supplemented by codes at any one level, and the model is simplified. 7. And the modularization is realized by supporting the modularization and realizing knowledge sharing, exchange, multiplexing and protection. 8. Localization, namely expressing the familiar terms of the user, and reducing English and translated terms as much as possible. 9. Dominance-all key information is to be explicitly expressed, and implicit rules and logic cannot be provided.
On the basis of the foregoing embodiments, the present invention provides a modeling apparatus for object process relationships, where the apparatus is applied to a terminal, the terminal is configured with a type element, a process element, and a relationship element, and the terminal displays the type element, the process element, and the relationship element through a graphical user interface, and referring to a schematic structural diagram of the modeling apparatus for object process relationships shown in fig. 31, the apparatus mainly includes the following parts:
The modeling module 3102 is configured to determine, in response to a modeling operation for a requirement to be modeled, a simulation model corresponding to the requirement to be modeled based on the type element, the process element, and the relationship element, where the simulation model is configured to express the requirement to be modeled by using the target type element and a type definition view and a type design view corresponding thereto, and the target process element and a process definition view and a process design view corresponding thereto, and a target relationship element;
the scene definition module 3104 is configured to determine a scene corresponding to the simulation model in response to a scene definition operation for the simulation model, where the scene is used to describe a flow control or a test case of the simulation model;
The model deduction module 3106 is configured to determine deduction configuration parameters corresponding to the simulation model, and take the scene as an entry, and deduct the simulation model based on the deduction configuration parameters to obtain a deduction result corresponding to the requirement to be modeled.
According to the modeling device for the object process relation, which is provided by the embodiment of the invention, the requirements to be modeled are abstracted into the types, the processes and the relation, the types are the expression modes of the objects, namely, the simulation model corresponding to the requirements to be modeled is constructed based on the object process relation, the scene and the deduction configuration parameters corresponding to the simulation model are defined on the basis, and finally, the deduction result corresponding to the requirements to be modeled is obtained through model deduction.
The device provided by the embodiment of the present invention has the same implementation principle and technical effects as those of the foregoing method embodiment, and for the sake of brevity, reference may be made to the corresponding content in the foregoing method embodiment where the device embodiment is not mentioned.
The embodiment of the invention provides a terminal, in particular to a terminal comprising a processor and a storage device, wherein the storage device is stored with a computer program which, when being executed by the processor, executes the method according to any one of the embodiments.
Fig. 32 is a schematic structural diagram of a terminal according to an embodiment of the present invention, where the terminal 100 includes a processor 320, a memory 321, a bus 322 and a communication interface 323, where the processor 320, the communication interface 323 and the memory 321 are connected through the bus 322, and the processor 320 is configured to execute executable modules, such as computer programs, stored in the memory 321.
The computer program product of the readable storage medium provided by the embodiment of the present invention includes a computer readable storage medium storing a program code, where the program code includes instructions for executing the method described in the foregoing method embodiment, and the specific implementation may refer to the foregoing method embodiment and will not be described herein.
It should be noted that the foregoing embodiments are merely illustrative embodiments of the present invention, and not restrictive, and the scope of the invention is not limited to the embodiments, and although the present invention has been described in detail with reference to the foregoing embodiments, it should be understood by those skilled in the art that any modification, variation or substitution of some of the technical features of the embodiments described in the foregoing embodiments may be easily contemplated within the scope of the present invention, and the spirit and scope of the technical solutions of the embodiments do not depart from the spirit and scope of the embodiments of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (9)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202510642559.2A CN120179249B (en) | 2025-05-19 | 2025-05-19 | Object-process relationship modeling method, device, terminal and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202510642559.2A CN120179249B (en) | 2025-05-19 | 2025-05-19 | Object-process relationship modeling method, device, terminal and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN120179249A CN120179249A (en) | 2025-06-20 |
| CN120179249B true CN120179249B (en) | 2025-09-02 |
Family
ID=96035758
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202510642559.2A Active CN120179249B (en) | 2025-05-19 | 2025-05-19 | Object-process relationship modeling method, device, terminal and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN120179249B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111880784A (en) * | 2020-08-06 | 2020-11-03 | 中国人民解放军国防大学联合作战学院 | SIMSCRIPT language-oriented discrete event simulation graphical modeling method |
| CN116341205A (en) * | 2023-02-20 | 2023-06-27 | 中国电子科技集团公司第二十八研究所 | Entity model design and construction method |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8156468B2 (en) * | 2008-09-24 | 2012-04-10 | Simio Llc | System and method for creating intelligent simulation objects using graphical process descriptions |
| CN115994981B (en) * | 2023-03-16 | 2023-12-22 | 苏州宁域科技有限公司 | Three-dimensional automatic deduction method for emergency drilling scheme |
| CN117055869B (en) * | 2023-08-24 | 2024-05-28 | 无锡雪浪数制科技有限公司 | Discrete event simulation graphical modeling method based on abacus |
| CN117725719A (en) * | 2023-10-25 | 2024-03-19 | 北京经纬恒润科技股份有限公司 | Simulation method and device for model simulation deduction |
-
2025
- 2025-05-19 CN CN202510642559.2A patent/CN120179249B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111880784A (en) * | 2020-08-06 | 2020-11-03 | 中国人民解放军国防大学联合作战学院 | SIMSCRIPT language-oriented discrete event simulation graphical modeling method |
| CN116341205A (en) * | 2023-02-20 | 2023-06-27 | 中国电子科技集团公司第二十八研究所 | Entity model design and construction method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN120179249A (en) | 2025-06-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Ross et al. | Theoretical foundations for the computer-aided design system | |
| CN101601012B (en) | Producer graph oriented programming framework with scenario support | |
| US10705892B2 (en) | Automatically generating conversational services from a computing application | |
| Liddle | Model-driven software development | |
| CN109189374A (en) | Object formation code generating method and system based on object reference chain | |
| CN117725985B (en) | Reinforced learning model training and service executing method and device and electronic equipment | |
| CN109144511A (en) | Numerical simulation graphic user interface automatic generation method and system | |
| CN115756407A (en) | Meta-universe service development method based on scene-behavior fusion and model driving | |
| CN112755534B (en) | Data processing method, device and storage medium | |
| CN114117645A (en) | Ship overall performance prediction integrated application system | |
| JP3625084B2 (en) | Reuse system for software parts | |
| CN120179249B (en) | Object-process relationship modeling method, device, terminal and medium | |
| CN118567712B (en) | Application publishing method, system and computer storage medium | |
| Brännström et al. | A framework for developing interactive intelligent systems in unity | |
| CN113569080B (en) | Artificial intelligence-based character library processing method, device, equipment and storage medium | |
| Meixner et al. | Udit–a graphical editor for task models | |
| CN114818300B (en) | Unity-based turing machine virtual simulation system | |
| CN117850764A (en) | Design modeling method and device based on integrated model driving architecture | |
| CN116756338A (en) | AR assembly guidance-oriented process knowledge graph construction method and system | |
| Muro-Medrano et al. | Knowledge representation-oriented nets for discrete event system applications | |
| Hillston | A tool to enhance model exploitation | |
| CN119884406B (en) | A large model pre-training method, device, storage medium and electronic device | |
| Chiueh et al. | Papyrus: A history-based VLSI design process management system | |
| Kottmann et al. | Simulation and Computer Aided Control Systems Design Using Object-orientation: Design and Implementation with OMT and Oberon | |
| Vanderdonckt | Current Trends in Computer-Aided Design of User Interfaces |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |