Scene-based modeling method and device

Abstract

The invention provides a scene-based modeling method and device, and relates to the technical field of modeling, and the method comprises the steps: obtaining a target scene type of a target business scene, the target scene type being used for representing a target scene model of the target business scene; a plurality of sub-primitives associated with the target scene type are determined, the sub-primitives are generated based on basic primitives internally provided with corresponding program codes, and the basic primitives comprise composition member primitives, attribute member primitives and process primitives; in response to an arrangement operation for the target scene type, carrying out association relationship arrangement and scene service arrangement between the sub-primitives to obtain a target scene model; wherein the scene business arrangement is used for increasing related scene primitives and carrying out incidence relation arrangement on the related scene primitives, and the related scene primitives belong to component member primitives and are of scene types of related business scenes. According to the method, multi-service scene associated model construction is realized, and meanwhile, the constructed model has an operational characteristic.

Description

Technical Field

[0001] The present invention relates to the technical field of modeling, and in particular to a scenario-based modeling method and device. Background Art

[0002] All things are described through scenarios, and a scenario is an arrangement pattern of things. Business is generated to solve problems. By constructing scenarios, business orchestration is realized, thereby realizing the value of users. In the existing modeling methods, the description of scenarios can only achieve the construction mode of single scenarios, with a single business mode, unable to associate with other business activities, nor able to design business scenarios, making it difficult to support business scenarios with higher complexity and hard to effectively and quickly express such business scenarios.

[0003] Under the existing scenario design technical solutions, requirements analysts design scenario requirements based on the business information provided by users, and complete the design of user scenarios through modeling tools. One set of user scenarios designs one set of business logics. To express the connection between scenarios, a connection can only be forcibly established, but it can only be associated in the same dimension. Moreover, the modeling method designed with this scenario can only be used for conceptual modeling, and the built model cannot run. Summary of the Invention

[0004] The purpose of the present invention is to provide a scenario-based modeling method and device to achieve the construction of a model with multi-business scenario association, and at the same time, the built model has the characteristics of being operable.

[0005] In a first aspect, the present invention provides a scenario-based modeling method, including:

[0006] Obtain the target scenario type of the target business scenario, where the target scenario type is used to represent the target scenario model of the target business scenario;

[0007] Determine multiple sub-graph elements associated with the target scenario type. The sub-graph elements are generated based on basic graph elements with corresponding program codes built in. The basic graph elements include component member graph elements, attribute member graph elements, and process graph elements. Different types of component member graph elements are used to represent different entities of things that do not depend on time, attribute member graph elements are used to represent the attributes of things that do not depend on time, and process graph elements are used to represent things that depend on time;

[0008] In response to the orchestration operation for the target scenario type, perform the association relationship orchestration and scenario business orchestration among the sub-graph elements to obtain the target scenario model; wherein, the scenario business orchestration is used to add relevant scenario graph elements and perform the association relationship orchestration for the relevant scenario graph elements to realize the association between the target business scenario and its relevant business scenarios; the relevant scenario graph elements belong to the component member graph elements and are of the scenario type of the relevant business scenario.

[0009] In an alternative embodiment, obtaining the target scenario type of the target business scenario includes:

[0010] When a scenario type addition instruction is obtained, add an initial scenario type under the scenario type in the transaction list area;

[0011] In response to a naming operation for the initial scenario type, modify the name of the initial scenario type based on the name of the target business scenario carried by the naming operation to obtain the target scenario type.

[0012] In an alternative embodiment, determining multiple sub-graphic elements associated with the target scenario type includes:

[0013] In response to a selection operation for the target scenario type, display a model editing area corresponding to the target scenario type, and a basic graphic element is displayed in the model editing area;

[0014] In response to an addition operation for the first basic graphic element in the model editing area, generate the first basic graphic element in the model editing area;

[0015] In response to an attribute editing operation for the first basic graphic element, modify the basic attributes of the first basic graphic element to obtain a sub-graphic element.

[0016] In an alternative embodiment, each relationship type in the relationship arrangement represents a type of function or a scenario activity. By invoking the relationship type, the invocation of the scenario activity is completed, which serves as a precondition for other scenario activities.

[0017] In an alternative embodiment, in response to an arrangement operation for the target scenario type, perform an association relationship arrangement and a scenario business arrangement among the sub-graphic elements to obtain a target scenario model, including:

[0018] In response to a first connection operation for the first sub-graphic element and the second sub-graphic element among the sub-graphic elements, display a first relationship type selection page corresponding to the first connection operation;

[0019] In response to a first selection operation for the first relationship type selection page, generate a corresponding connection line between the first sub-graphic element and the second sub-graphic element.

[0020] In an alternative embodiment, in response to an arrangement operation for the target scenario type, perform an association relationship arrangement and a scenario business arrangement among the sub-graphic elements to obtain a target scenario model, further including:

[0021] In response to a supplement operation for the third sub-graphic element among the sub-graphic elements, display a supplementary graphic element page, and the supplementary graphic element page shows supplementary graphic elements associated with the third sub-graphic element;

[0022] In response to a primitive selection operation for a supplementary primitive page, a target supplementary primitive connected to a third sub-primitive is generated in a model editing area corresponding to a target scenario type;

[0023] In response to a second connection operation for the target supplementary primitive and a fourth sub-primitive in the model editing area, a second relationship type selection page corresponding to the second connection operation is displayed;

[0024] In response to a second selection operation for the second relationship type selection page, a corresponding connection line is generated between the target supplementary primitive and the fourth sub-primitive.

[0025] In an optional implementation manner, in response to an arrangement operation for a target scenario type, association relationship arrangement and scenario service arrangement between each sub-primitive are performed to obtain a target scenario model, and it further includes:

[0026] In response to an addition operation for a composition member primitive in a model editing area corresponding to a target scenario type, an initial composition member primitive is generated in the model editing area;

[0027] In response to a type selection operation for the initial composition member primitive, the type of the initial composition member primitive is modified to the scenario type of a related service scenario to obtain a related scenario primitive;

[0028] In response to a third connection operation for the related scenario primitive and a fifth sub-primitive in the model editing area, a third relationship type selection page corresponding to the third connection operation is displayed;

[0029] In response to a third selection operation for the third relationship type selection page, a corresponding connection line is generated between the related scenario primitive and the fifth sub-primitive.

[0030] In a second aspect, the present invention provides a scenario-based modeling device, including:

[0031] An acquisition module, configured to acquire a target scenario type of a target business scenario, where the target scenario type is used to characterize a target scenario model of the target business scenario;

[0032] A determination module, configured to determine a plurality of sub-primitives associated with the target scenario type, where the sub-primitives are generated based on a basic primitive with corresponding program code built therein, and the basic primitive includes a composition member primitive, an attribute member primitive, and a process primitive. Different types of composition member primitives are used to characterize different entities of things independent of time, the attribute member primitive is used to characterize the attributes of things independent of time, and the process primitive is used to characterize things dependent on time;

[0033] An orchestration module, configured to perform the association relationship orchestration among each sub-graphic element and the scenario service orchestration in response to an orchestration operation for a target scenario type, so as to obtain a target scenario model; wherein, the scenario service orchestration is used to add relevant scenario graphic elements and perform the association relationship orchestration for the relevant scenario graphic elements, so as to realize the association between the target business scenario and its relevant business scenarios; the relevant scenario graphic elements belong to the composition member graphic elements and are of the scenario type of the relevant business scenario.

[0034] In a third aspect, the present invention provides an electronic device, including a memory and a processor. A computer program that can run on the processor is stored in the memory. When the processor executes the computer program, the method for scenario-based modeling according to any one of the foregoing embodiments is implemented.

[0035] In a fourth aspect, the present invention provides a computer-readable storage medium, on which a computer program is stored. When the computer program is run by a processor, the method for scenario-based modeling according to any one of the foregoing embodiments is executed.

[0036] The method and device for scenario-based modeling provided by the present invention can obtain the target scenario type of the target business scenario, where the target scenario type is used to characterize the target scenario model of the target business scenario; determine multiple sub-graphic elements associated with the target scenario type, and the sub-graphic elements are generated based on basic graphic elements with corresponding program codes therein. The basic graphic elements include composition member graphic elements, attribute member graphic elements and process graphic elements. Different types of composition member graphic elements are used to characterize different entities of things independent of time, attribute member graphic elements are used to characterize the attributes of things independent of time, and process graphic elements are used to characterize things dependent on time; in response to an orchestration operation for the target scenario type, perform the association relationship orchestration among each sub-graphic element and the scenario service orchestration, so as to obtain a target scenario model; wherein, the scenario service orchestration is used to add relevant scenario graphic elements and perform the association relationship orchestration for the relevant scenario graphic elements, so as to realize the association between the target business scenario and its relevant business scenarios; the relevant scenario graphic elements belong to the composition member graphic elements and are of the scenario type of the relevant business scenario. In this way, the user requirements are transformed into scenario design and modeled according to programming logic. Under the scenario type of the business scenario, three types of sub-graphic elements, namely composition member graphic elements, attribute member graphic elements and process graphic elements, can be associated. The call of scenario activities can be completed through the association relationship orchestration among the sub-graphic elements. Moreover, the scenario type can characterize the scenario model. By using the scenario type of the relevant business scenario as the type of a composition member graphic element of the target business scenario, the scenario model of the relevant business scenario can be introduced into the target scenario model, and the association between multiple business scenarios can be completed through the scenario service orchestration, thereby realizing the model construction of the association between multiple business scenarios, and at the same time, the constructed model has the operable characteristics. Description of the Drawings

[0037] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the drawings required for the description of the specific embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0038] Figure 1 It is a schematic diagram of an existing scenario design solution;

[0039] Figure 2 It is a schematic flowchart of a scenario-based modeling method provided by an embodiment of the present invention;

[0040] Figure 3 It is a design diagram of a scenario type primitive provided by an embodiment of the present invention;

[0041] Figure 4 It is a design diagram of a component member primitive associated with a scenario type provided by an embodiment of the present invention;

[0042] Figure 5 It is a design diagram of an attribute member primitive associated with a scenario type provided by an embodiment of the present invention;

[0043] Figure 6 It is a design diagram of a process primitive associated with a scenario type provided by an embodiment of the present invention;

[0044] Figure 7 It is a schematic diagram of a modeling interface provided by an embodiment of the present invention;

[0045] Figure 8 It is a schematic diagram of the first relationship type selection page provided by an embodiment of the present invention;

[0046] Figure 9 It is a schematic diagram of the first modeling result provided by an embodiment of the present invention;

[0047] Figure 10 It is a schematic diagram of the second relationship type selection page provided by an embodiment of the present invention;

[0048] Figure 11 It is a schematic diagram of the second modeling result provided by an embodiment of the present invention;

[0049] Figure 12 It is a schematic diagram of a supplementary primitive page provided by an embodiment of the present invention;

[0050] Figure 13 It is a schematic diagram of the third modeling result provided by an embodiment of the present invention;

[0051] Figure 14Schematic diagram of the third relationship type selection page provided by an embodiment of the present invention;

[0052] Figure 15 Schematic diagram of the fourth modeling result provided by an embodiment of the present invention;

[0053] Figure 16 Schematic diagram of the structure of a scenario-based modeling device provided by an embodiment of the present invention;

[0054] Figure 17 Schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Detailed implementation manners

[0055] Next, the technical solutions of the present invention will be described clearly and completely in conjunction with the embodiments. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0056] As Figure 1 shown, the user usage scenarios include user scenario 1, user scenario 2, user scenario 3 ··· user scenario n, and each scenario corresponds to a set of scenario designs. For example, user scenario 1 corresponds to scenario design 1, user scenario 2 corresponds to scenario design 2, user scenario 3 corresponds to scenario design 3, and user scenario n corresponds to scenario design n. There are the following problems with this modeling method:

[0057] (1) One set of user scenarios corresponds to one set of scenario design logics. If there are multi-scenario associations, it will lead to particularly chaotic scenario designs. Moreover, scenario designs are person-dependent and have openness without clear standards, making it difficult to understand the scenario construction.

[0058] (2) It can only perform conceptual scenario modeling, and the built scenario models are not executable.

[0059] Based on this, a scenario-based modeling method and device provided by an embodiment of the present invention transform user requirements into scenario designs for modeling. It adopts a multi-scenario series modeling method based on scenario type representation of scenario model design, and uses a minimized general ontology, that is, two things, namely objects (including component members and attribute members) and processes, and the associations between them. Through a unified view, it models the structure, function, and behavior of business scenarios. Unified view modeling is easy to maintain the consistency of model elements and improves the modeler's macro understanding of business scenarios. At the same time, the model constructed based on scenarios has the characteristics of being executable. The logic of constructing scenarios satisfies all the characteristics of simulation deduction, ensuring the executability of scenario modeling.

[0060] To facilitate the understanding of this embodiment, a scenario-based modeling method disclosed in the embodiments of the present invention will be introduced in detail first.

[0061] The embodiments of the present invention provide a scenario-based modeling method, which can be executed by an electronic device with data processing capabilities. The embodiments of the present invention propose a modeling method that converts user requirements into scenarios based on object orientation, abstracts user requirements into objects to establish scenarios, and each scenario is defined by its own attributes and a set of operations it can perform. These scenarios constitute the business of user requirements. To describe the interactions and dynamic behaviors between these scenarios, it is necessary to design the structure according to the scenarios, follow the scenario modeling rules, and construct the constituent members, attribute members, and processes of the scenarios. Each scenario describes a specific user activity or task, as well as the process interactions required to complete the task. By refining these scenarios, the user requirements can be understood more deeply. At the same time, the model constructed based on the scenarios has the characteristics of being operable, and the logic of constructing the scenarios satisfies all the characteristics of simulation deduction, ensuring the executability of scenario modeling.

[0062] See Figure 2 The flowchart of a scenario-based modeling method shown in the figure. This method mainly includes the following steps S210 to S230:

[0063] Step S210, obtain the target scenario type of the target business scenario, and this target scenario type is used to represent the target scenario model of the target business scenario.

[0064] The target scenario type refers to the scenario type of the target business scenario. The essence of a scenario is its type, and the graphic elements of the scenario model are consistent with the type graphic elements. Therefore, the target scenario type can be used to represent the target scenario model of the target business scenario. When associating the target business scenario with other scenarios, constituent member graphic elements can be constructed in other scenarios, the type of the constituent member graphic elements is selected as the target scenario type, and it is associated with the corresponding process in other scenarios, so as to realize the introduction of the target scenario model into other scenario models.

[0065] The user can construct the target scenario type in the object list area of the modeling interface. Based on this, the target scenario type can be obtained in the following way: when a scenario type addition instruction is obtained, an initial scenario type is added under the scenario type in the object list area; in response to the naming operation for the initial scenario type, based on the name of the target business scenario carried by the naming operation, the name of the initial scenario type is modified to obtain the target scenario type.

[0066] Step S220, determine multiple sub-graphic elements associated with the target scenario type. The sub-graphic elements are generated based on basic graphic elements with corresponding program codes built in. The basic graphic elements include constituent member graphic elements, attribute member graphic elements, and process graphic elements.

[0067] Both the composition member primitive and the attribute member primitive belong to object primitives. An object is a thing that does not depend on time, and users can use objects to describe static things that exist in a scene for a certain period of time. A process is a thing that depends on time, and users can use processes to describe dynamic things used to transform objects in a scene. Different types of composition member primitives are used to represent different entities of things that do not depend on time, attribute member primitives are used to represent the attributes of things that do not depend on time, and process primitives are used to represent things that depend on time.

[0068] Users can create the required basic primitives in the model editing area of the modeling interface by dragging. After selecting the created basic primitives, the basic attributes of the basic primitives can be modified to obtain sub-primitives. Users can modify the basic attributes of the corresponding basic primitives based on actual needs. For example, users can set basic information such as name, description, persistence, essence, and subordination; can set parameter information for the simulation deduction function; can adjust the position of the label; can modify the style of the object. If the required sub-primitives adopt an established model (this model can be a single basic primitive model or a scene model), the type of the corresponding basic primitive can be selected as the type of the corresponding model to achieve the modification of the basic attributes.

[0069] Based on this, the above-mentioned sub-primitives can be obtained in the following way: in response to the selection operation of the target scene type, display the model editing area corresponding to the target scene type, and the model editing area displays basic primitives; in response to the addition operation of the first basic primitive in the model editing area, generate the first basic primitive in the model editing area; in response to the attribute editing operation of the first basic primitive, modify the basic attributes of the first basic primitive to obtain sub-primitives. Among them, the first basic primitive is one of the composition member primitive, the attribute member primitive, and the process primitive.

[0070] Step S230, in response to the choreography operation for the target scene type, perform the association relationship choreography and scene business choreography among the sub-primitives to obtain the target scene model.

[0071] Among them, the scene business choreography is used to add relevant scene primitives and perform association relationship choreography for the relevant scene primitives to realize the association between the target business scene and its relevant business scenes; the relevant scene primitives belong to the composition member primitive and the type is the scene type of the relevant business scene. The relevant business scene is a business scene related to the target business scene, and the relevant business scene can be one or more.

[0072] The association relationship choreography choreographs the relationship types. Each relationship type in the association relationship choreography represents a type of function or a scene activity. By invoking the relationship type, the invocation of the scene activity is completed, which serves as a precondition for other scene activities.

[0073] The above-mentioned association relationship arrangement may include constructing the association relationships between each sub-graphic element. In one possible implementation manner, it specifically includes the following process: in response to a first connection operation on a first sub-graphic element and a second sub-graphic element among each sub-graphic element, display a first relationship type selection page corresponding to the first connection operation; in response to a first selection operation on the first relationship type selection page, generate a corresponding connection line between the first sub-graphic element and the second sub-graphic element. The process graphic element can be connected to the object graphic element to introduce the input and output of the process. When introducing the input and output of the process, the selectable relationship types displayed on the relationship type selection page can be different, and the connection line types corresponding to different relationship types can be different, so as to facilitate the user to distinguish different relationship types.

[0074] The above-mentioned association relationship arrangement may also include adding supplementary graphic elements and their association relationships with other sub-graphic elements. In one possible implementation manner, it specifically includes the following process: in response to a supplementary operation on a third sub-graphic element among each sub-graphic element, display a supplementary graphic element page, and the supplementary graphic element page shows the supplementary graphic elements associated with the third sub-graphic element; in response to a graphic element selection operation on the supplementary graphic element page, generate a target supplementary graphic element connected to the third sub-graphic element in the model editing area corresponding to the target scenario type; in response to a second connection operation on the target supplementary graphic element and a fourth sub-graphic element in the model editing area, display a second relationship type selection page corresponding to the second connection operation; in response to a second selection operation on the second relationship type selection page, generate a corresponding connection line between the target supplementary graphic element and the fourth sub-graphic element. Some sub-graphic elements are associated with one or more supplementary graphic elements, and the introduction of the required supplementary graphic elements can be achieved in this way.

[0075] The above-mentioned scenario service arrangement is used to introduce the scenario model of the relevant business scenario into the target scenario model to realize the association between different business scenarios. In one possible implementation manner, it specifically includes the following process: in response to a new operation on the component member graphic element in the model editing area corresponding to the target scenario type, generate an initial component member graphic element in the model editing area; in response to a type selection operation on the initial component member graphic element, modify the type of the initial component member graphic element to the scenario type of the relevant business scenario to obtain a relevant scenario graphic element; in response to a third connection operation on the relevant scenario graphic element and a fifth sub-graphic element in the model editing area, display a third relationship type selection page corresponding to the third connection operation; in response to a third selection operation on the third relationship type selection page, generate a corresponding connection line between the relevant scenario graphic element and the fifth sub-graphic element.

[0076] The scenario-based modeling method provided by the embodiments of the present invention converts user requirements into scenario designs and models them according to programming logic. Under the scenario type of the business scenario, three types of sub-primitives, namely composition member primitives, attribute member primitives, and process primitives, can be associated. The invocation of scenario activities can be completed through the association relationships between the sub-primitives. Moreover, the scenario type can represent the scenario model. By using the scenario type of a relevant business scenario as the type of a composition member primitive of the target business scenario, the scenario model of the relevant business scenario can be introduced into the target scenario model, and the association between multiple business scenarios can be completed through scenario business orchestration, thereby realizing the construction of a model for the association of multiple business scenarios. At the same time, the constructed model has the characteristics of being operable.

[0077] For ease of understanding, the following provides a detailed introduction to four parts: primitive design, scenario view definition, scenario orchestration, and scenario model operation.

[0078] (1) Primitive design:

[0079] The scenario-based modeling method is an object-oriented design. Among them, the design of types is an important condition for the design of this modeling method. The structure of the scenario type includes four parts: composition member primitives, attribute member primitives, process primitives, and the association relationships between the primitives. An important part of a possible primitive design is as Figures 3 to 6 shown, which are, in sequence, scenario type primitives, composition member primitives, attribute member primitives, and process primitives.

[0080] (2) Scenario view definition:

[0081] The essence of a scenario is a type. The relationship between the same object (or process) and other objects or processes must be consistent and cannot conflict. By ensuring consistency, it is ensured that the definition, design, and implementation of the model are unified and coordinated.

[0082] 1) Since the essence of a scenario is a class, the primitives of the scenario model are the same as the scenario type primitives. The differences are distinguished through the scenario view. When performing scenario modeling, it is necessary to construct a scenario classification in the object navigation (i.e., the object list area), and the primitives constructed under this classification are the main scenario types (i.e., scenario type primitives).

[0083] 2) The construction of a scenario starts from the scenario type. Under the scenario type, three sub-elements, namely composition member primitives, attribute member primitives, and process primitives, can be associated. By constructing the association relationships between the composition member primitives, attribute member primitives, and process primitives, the scenario definition is completed.

[0084] (3) Scenario orchestration:

[0085] Build the components of the scenario by arranging the component members, orchestrate the scenario activities, design the scenario structure, and complete the construction of the scenario. In the scenario modeling method, what is orchestrated is the relationship type. Each relationship type represents a type of function or a scenario activity. By invoking this relationship type, the invocation of the scenario activity is completed, which serves as a prerequisite for other business scenario activities. When performing scenario business orchestration, add the business types to be orchestrated (i.e., the scenario types of related business scenarios) to the types of the component member primitives to complete the scenario orchestration association.

[0086] (4) Scenario model operation:

[0087] The constructed scenario model is inherently runnable. Each scenario model can run independently, drive the business through the scenario model, and complete the construction of user requirements.

[0088] For ease of understanding, the following uses the example of building a car scenario to provide an exemplary introduction to the above scenario-based modeling method.

[0089] See Figure 7 As shown in a schematic diagram of a modeling interface, area 1 is the menu bar tool area, which can include tools such as undo, save, zoom in, and zoom out; area 2 is the thing list area, used to display the things created in the model, including models and components, etc. Components are obtained by encapsulating the model. Under the model, there are type models and scenario models, etc. Figure 7 The type models created in it include wheels, engines, frames, steering wheels, and cars. The engine is associated with the process of starting the engine. The scenario model includes cars; area 3 is the model editing area, used to create and display the model; area 4 is the basic property area, used to set basic properties, such as selecting the type of the component member primitive.

[0090] Take Figure 7 as an example. When building the scenario model of a car, you can first select the car under the scenario, and area 3 will display the model editing area of the car scenario model. The model editing area includes basic primitives that can be dragged, including component member primitives, attribute member primitives, and process primitives; then build the sub-primitives of the car scenario model in the following way: after dragging the corresponding basic primitive, select the basic primitive and select the type in the basic property panel of area 4, so as to directly reference the previously set type model. In this way, 5 component member primitives of car wheels, car steering wheels, car frames, car engines, and a certain brand of car, as well as a process primitive for building a car can be built.

[0091] After that, perform scenario orchestration. Users can establish the association relationship between the sub-primitives in the following way: when adding the input of a process, first select a component member primitive, and then select a process primitive. At this time, it is displayed as Figure 8The "Please select relationship type" page (i.e., the relationship type selection page) shown. This page displays information such as symbols, names, events, text descriptions, and whether to operate corresponding to multiple relationship types, and also sets an exchange direction button and a cancel button; the user only needs to select a relationship type (such as a structural control relationship). Among them, for some relationship types (such as consumption relationship, nullable input influence relationship, non-nullable input influence relationship, etc.), events can also be selected. In this way, the addition of process inputs can be achieved, such as Figure 7 shown in the model editing area of

[0092] The output of the process can also be added, such as Figure 9 In Figure 10 the output of building a car is a certain brand of car; the specific operation is similar to adding the input of the process: first select a process primitive, then select a component member primitive, and at this time, the "Please select relationship type" page shown in Figure 9 is displayed. The relationship types displayed on this page include production relationship, output influence relationship, nullable bidirectional influence relationship, and non-nullable bidirectional influence relationship. Among them, the nullable bidirectional influence relationship and the non-nullable bidirectional influence relationship also support event selection; the user only needs to select a relationship type. In this way, the addition of process outputs can be achieved, such as Figure 9 shown in: the relationship type between building a car and a certain brand of car is a production relationship. An exchange direction button and a cancel button are also set on the relationship type selection page. The input and output of the process can be switched by clicking the exchange direction button, and the association between the two can be cancelled by clicking the cancel button.

[0093] The addition of supplementary primitives can also be carried out, such as Figure 11 the start engine primitive in Figure 12 Specifically, the car engine primitive associated with the supplementary primitive can be selected first, and then the supplementary button in the tool area of the menu bar is clicked to display the "Supplementary members and processes" page (i.e., the supplementary primitive page) shown in

[0094] This page can display the supplementary primitive start engine associated with the car engine primitive before. After selecting the start engine and clicking the OK button (the addition of the supplementary primitive can also be cancelled by clicking the cancel button), the start engine can be added to the current model and connected to the selected car engine primitive.

[0094] When the supplementary primitive is a process primitive, the input of the supplementary primitive can also be added, such as Figure 13 in Figure 14The "Please Select Relationship Type" page shown. The relationship types displayed on this page include call relationship, timeout exception relationship, time shortage exception relationship, and unidirectional tagged relationship; the user can select one relationship type. In this way, the addition of supplementary primitive input can be achieved, such as Figure 13 shown in: The relationship type between vehicle manufacturing and starting the engine is a call relationship.

[0095] When the supplementary primitive is a component member primitive or an attribute member primitive, it can also be associated with a process primitive. The specific operation is the same as the addition of the aforementioned process input, which will not be elaborated here.

[0096] It is also possible to introduce relevant business scenarios into the current model, such as Figure 15 shown. First, construct a component member primitive, then select its type as assembly process. The assembly process is the scenario type of the assembly process scenario. Then, associate the assembly process primitive with the vehicle manufacturing primitive, thereby realizing the association between the assembly process scenario and the vehicle scenario.

[0097] In the embodiment of the present invention, by formulating clear scenario primitives, designing a clear scenario structure, establishing an executable scenario model, according to the actual business situation of the user, when constructing a scenario, it changes from a single-business-oriented construction mode to a multi-business configuration construction mode, thus returning to the essence of value and realizing business value through scenarios.

[0098] Corresponding to the above-mentioned scenario-based modeling method, the embodiment of the present invention also provides a scenario-based modeling device. Refer to Figure 16 the structural schematic diagram of a scenario-based modeling device shown. The device includes:

[0099] An acquisition module 1601, configured to acquire the target scenario type of the target business scenario, where the target scenario type is used to characterize the target scenario model of the target business scenario;

[0100] A determination module 1602, configured to determine multiple sub-primitives associated with the target scenario type. The sub-primitives are generated based on basic primitives with corresponding program codes built in. The basic primitives include component member primitives, attribute member primitives, and process primitives. Different types of component member primitives are used to characterize different entities of things that do not depend on time, attribute member primitives are used to characterize the attributes of things that do not depend on time, and process primitives are used to characterize things that depend on time;

[0101] An orchestration module 1603, which is configured to perform the association relationship orchestration and the scenario service orchestration among each sub-graphic element in response to an orchestration operation for a target scenario type, so as to obtain a target scenario model; wherein, the scenario service orchestration is used to add relevant scenario graphic elements and perform the association relationship orchestration for the relevant scenario graphic elements, so as to realize the association between the target business scenario and its relevant business scenarios; the relevant scenario graphic elements belong to the constituent member graphic elements, and the type is the scenario type of the relevant business scenario.

[0102] The scenario-based modeling device provided by the embodiment of the present invention converts user requirements into scenario designs and performs modeling according to programming logic. Under the scenario type of the business scenario, three types of sub-graphic elements, namely constituent member graphic elements, attribute member graphic elements, and process graphic elements, can be associated. The invocation of scenario activities can be completed through the association relationship orchestration among the sub-graphic elements. Moreover, the scenario type can represent the scenario model. By using the scenario type of the relevant business scenario as the type of a constituent member graphic element of the target business scenario, the scenario model of the relevant business scenario can be introduced into the target scenario model, and the association between multiple business scenarios can be completed through the scenario service orchestration, thereby realizing the model construction of the association between multiple business scenarios, and the constructed model has the operable characteristic.

[0103] Further, the obtaining module 1601 is specifically configured to: when a scenario type addition instruction is obtained, add an initial scenario type under the scenario type in the transaction list area; in response to a naming operation for the initial scenario type, modify the name of the initial scenario type based on the name of the target business scenario carried by the naming operation, so as to obtain a target scenario type.

[0104] Further, the determining module 1602 is specifically configured to: in response to a selection operation for the target scenario type, display a model editing area corresponding to the target scenario type, where basic graphic elements are displayed in the model editing area; in response to an addition operation for a first basic graphic element in the model editing area, generate a first basic graphic element in the model editing area; in response to an attribute editing operation for the first basic graphic element, modify the basic attributes of the first basic graphic element to obtain a sub-graphic element.

[0105] Further, each relationship type of the above-mentioned association relationship orchestration represents a type of function or a scenario activity. The invocation of the scenario activity is completed by invoking the relationship type, which serves as a precondition for other scenario activities.

[0106] Further, the orchestration module 1603 is specifically configured to: in response to a first connection operation for a first sub-graphic element and a second sub-graphic element among each sub-graphic element, display a first relationship type selection page corresponding to the first connection operation; in response to a first selection operation for the first relationship type selection page, generate a corresponding connection line between the first sub-graphic element and the second sub-graphic element.

[0107] Further, the above arrangement module 1603 is further configured to: in response to a supplement operation on a third sub-graphic element among the sub-graphic elements, display a supplementary graphic element page, where the supplementary graphic element page displays supplementary graphic elements associated with the third sub-graphic element; in response to a graphic element selection operation on the supplementary graphic element page, generate a target supplementary graphic element connected to the third sub-graphic element in the model editing area corresponding to the target scenario type; in response to a second connection operation on the target supplementary graphic element and a fourth sub-graphic element in the model editing area, display a second relationship type selection page corresponding to the second connection operation; and in response to a second selection operation on the second relationship type selection page, generate a corresponding connection line between the target supplementary graphic element and the fourth sub-graphic element.

[0108] Further, the above arrangement module 1603 is further configured to: in response to an addition operation on a component member graphic element in the model editing area corresponding to the target scenario type, generate an initial component member graphic element in the model editing area; in response to a type selection operation on the initial component member graphic element, modify the type of the initial component member graphic element to the scenario type of the relevant business scenario to obtain a relevant scenario graphic element; in response to a third connection operation on the relevant scenario graphic element and a fifth sub-graphic element in the model editing area, display a third relationship type selection page corresponding to the third connection operation; and in response to a third selection operation on the third relationship type selection page, generate a corresponding connection line between the relevant scenario graphic element and the fifth sub-graphic element.

[0109] The scene-based modeling device provided in this embodiment has the same implementation principle and the same technical effects as the foregoing scene-based modeling method embodiment. For the sake of brief description, for the parts not mentioned in the scene-based modeling device embodiment, reference may be made to the corresponding content in the foregoing scene-based modeling method embodiment.

[0110] As Figure 17 shown, an electronic device 1700 provided in an embodiment of the present invention includes: a processor 1701, a memory 1702, and a bus. The memory 1702 stores a computer program that can run on the processor 1701. When the electronic device 400 runs, communication between the processor 1701 and the memory 1702 is carried out through the bus, and the processor 1701 executes the computer program to implement the above-mentioned scene-based modeling method.

[0111] Specifically, the above-mentioned memory 1702 and processor 1701 can be general memories and processors, and no specific limitations are made here.

[0112] An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is run by a processor, it executes the scenario-based modeling method in the foregoing method embodiments. The computer-readable storage medium includes various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM for short), RAMs, magnetic disks, or optical discs.

[0113] As used herein, the term "and / or" is merely a description of the relationship between associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the term "at least one" as used herein represents any one of a plurality or any combination of at least two of a plurality. For example, including at least one of A, B, and C can represent any one or more elements selected from the set composed of A, B, and C.

[0114] In all the examples shown and described herein, any specific value should be construed as merely exemplary and not as a limitation. Therefore, other examples of the exemplary embodiments may have different values.

[0115] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of devices, methods, and computer program products according to multiple embodiments of the present invention. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code, and the module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, as well as the combination of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0116] In several embodiments provided by this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules is only a logical function division. In actual implementation, there may be other division methods. For another example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some communication interfaces. The indirect coupling or communication connection of devices or modules can be in electrical, mechanical or other forms.

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

[0118] In addition, in each embodiment of the present invention, the functional modules can be integrated in a processing module, or each module can exist physically alone, or two or more modules can be integrated in one module.

[0119] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of each embodiment of the present invention.

Claims

1. A scenario-based modeling method, characterized in that Including: Obtain the target scenario type of the target business scenario, where the target scenario type is used to characterize the target scenario model of the target business scenario; Determine multiple sub-graphical elements associated with the target scenario type. The sub-graphical elements are generated based on basic graphical elements with corresponding program codes. The basic graphical elements include component member graphical elements, attribute member graphical elements, and process graphical elements. Different types of component member graphical elements are used to represent different entities of things independent of time, the attribute member graphical elements are used to represent the attributes of things independent of time, and the process graphical elements are used to represent things dependent on time; In response to the orchestration operation for the target scenario type, perform the association relationship orchestration and scenario business orchestration among the sub-graphical elements to obtain the target scenario model; where the scenario business orchestration is used to add relevant scenario graphical elements and perform association relationship orchestration for the relevant scenario graphical elements to realize the association between the target business scenario and its relevant business scenarios; The relevant scenario graphical elements belong to the component member graphical elements and have the scenario type of the relevant business scenario.

2. The method according to claim 1, characterized in that, The obtaining the target scenario type of the target business scenario includes: When a scenario type addition instruction is obtained, add an initial scenario type under the scenario type in the thing list area; In response to the naming operation for the initial scenario type, modify the name of the initial scenario type based on the name of the target business scenario carried by the naming operation to obtain the target scenario type.

3. The method according to claim 1, wherein The determining multiple sub-graphical elements associated with the target scenario type includes: In response to the selection operation for the target scenario type, display the model editing area corresponding to the target scenario type, and the basic graphical elements are displayed in the model editing area; In response to the addition operation for the first basic graphical element in the model editing area, generate the first basic graphical element in the model editing area; In response to the attribute editing operation for the first basic graphical element, modify the basic attributes of the first basic graphical element to obtain the sub-graphical element.

4. The method according to claim 1, characterized in that, Each relationship type of the association relationship orchestration represents a type of function or a scenario activity. By invoking the relationship type, the invocation of the scenario activity is completed, which serves as a precondition for other scenario activities.

5. The method according to claim 1, characterized in that, The performing the association relationship orchestration and scenario business orchestration among the sub-graphical elements in response to the orchestration operation for the target scenario type to obtain the target scenario model includes: In response to the first connection operation for the first sub-graphical element and the second sub-graphical element among the sub-graphical elements, display the first relationship type selection page corresponding to the first connection operation; In response to the first selection operation for the first relationship type selection page, generate a corresponding connection line between the first sub-graphical element and the second sub-graphical element.

6. The method according to claim 1, wherein The performing the association relationship orchestration and scenario business orchestration among the sub-graphical elements in response to the orchestration operation for the target scenario type to obtain the target scenario model further includes: In response to the supplement operation for the third sub-graphical element among the sub-graphical elements, display the supplementary graphical element page, and the supplementary graphical elements associated with the third sub-graphical element are displayed on the supplementary graphical element page; In response to a primitive selection operation for the supplementary primitive page, a target supplementary primitive connected to the third sub-primitive is generated in the model editing area corresponding to the target scenario type; In response to a second connection operation for the target supplementary primitive and a fourth sub-primitive in the model editing area, a second relationship type selection page corresponding to the second connection operation is displayed; In response to a second selection operation for the second relationship type selection page, a corresponding connection line is generated between the target supplementary primitive and the fourth sub-primitive.

7. The method according to claim 1, wherein The step of, in response to an arrangement operation for the target scenario type, performing association relationship arrangement and scenario service arrangement between the sub-primitives to obtain a target scenario model further includes: In response to an addition operation for the component member primitive in the model editing area corresponding to the target scenario type, an initial component member primitive is generated in the model editing area; In response to a type selection operation for the initial component member primitive, the type of the initial component member primitive is modified to the scenario type of the relevant business scenario to obtain the relevant scenario primitive; In response to a third connection operation for the relevant scenario primitive and a fifth sub-primitive in the model editing area, a third relationship type selection page corresponding to the third connection operation is displayed; In response to a third selection operation for the third relationship type selection page, a corresponding connection line is generated between the relevant scenario primitive and the fifth sub-primitive.

8. A scenario-based modeling device, characterized in that, It includes: An acquisition module, configured to acquire a target scenario type of a target business scenario, where the target scenario type is used to characterize the target scenario model of the target business scenario; A determination module, configured to determine a plurality of sub-primitives associated with the target scenario type, where the sub-primitives are generated based on a basic primitive with corresponding program code built in, and the basic primitive includes a component member primitive, an attribute member primitive, and a process primitive. Different types of the component member primitives are used to characterize different entities of things independent of time, the attribute member primitive is used to characterize the attributes of things independent of time, and the process primitive is used to characterize things dependent on time; An arrangement module, configured to, in response to an arrangement operation for the target scenario type, perform association relationship arrangement and scenario service arrangement between the sub-primitives to obtain the target scenario model; wherein, the scenario service arrangement is used to add relevant scenario primitives and perform association relationship arrangement for the relevant scenario primitives to realize the association between the target business scenario and its relevant business scenarios; The relevant scenario primitive belongs to the component member primitive and has the scenario type of the relevant business scenario.

9. An electronic device, comprising a memory and a processor, wherein a computer program capable of running on the processor is stored in the memory, characterized in that When the processor executes the computer program, it implements the scenario-based modeling method according to any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is run by the processor, it executes the scenario-based modeling method according to any one of claims 1-7.

Images