View synchronous modification method and device

Abstract

The invention provides a synchronous modification method and device for views, the method is applied to a modeling tool, and the method comprises the following steps: when a canvas area of a user interaction interface displays a current use view of a first type, in response to a reference operation of a user on a second type, adding object primitives of a target object of the second type in the displayed current use view, assigning an object identifier to the referenced target object; in response to a supplementary operation of a user on the object primitive of the target object in the canvas area, acquiring a supplementary object which is appointed by the user and has an object relationship with the target object and corresponding supplementary object information from a defined view or a design view of the configured target object; and in response to a modification operation of a user on any object in the current use view of the first type, synchronously modifying the source object corresponding to the object identifier of the object based on modification information of the modification operation on the object. According to the method, related information of the same object in different views can be updated in real time.

Description

Technical Field

[0001] This application relates to the technical field of view synchronization modification, and in particular, to a method and device for synchronously modifying views. Background Art

[0002] In existing systems and methods for synchronizing and using three-dimensional views with block diagram models, changes in the block diagram model data are reflected in two views to the extent that the views contain a corresponding point. Changes made by the user to the block diagram view of the system being modeled result in changes to the underlying model data. The view generator examines the model data to determine whether there is a corresponding point in the three-dimensional view that is equivalent to the changed part of the block diagram view. If there is a corresponding point in the three-dimensional view, the view is updated to reflect the changes in the block diagram view. Similarly, changes selected by the user in the three-dimensional view result in changes to the underlying block diagram model data. The view generator examines the model data to determine whether there is a corresponding point in the block diagram view that is equivalent to the changed part of the three-dimensional view. If a corresponding point is found, the block diagram view is updated.

[0003] However, the inventors have found that the above-mentioned prior art can only be modified based on equivalent corresponding points, which has certain limitations. Summary of the Invention

[0004] The purpose of the embodiments of this application is to provide a method and device for synchronously modifying views to update the relevant information of the same thing (object or process) in different views in real time.

[0005] In a first aspect, a method for synchronously modifying a view is provided, which is applied to a language for object-oriented object-relationship process modeling and in a modeling tool created by using object-oriented modeling techniques. The modeling tool includes a database, and the database stores a definition view for describing the structure between things and a design view for describing the relationship between things established based on object-relationship process modeling techniques. The things include objects or processes belonging to different classes, and the relationships between things include object association relationships or process relationships. The method may include: when a current used view of a first type is displayed in the canvas area of the user interface, in response to a user's reference operation on a second type, adding a thing primitive of the target thing of the second type to the currently displayed used view, and assigning a thing identifier to the referenced target thing; the thing identifier represents the source of the referenced target thing; the target thing is a thing not included in the current used view; in response to the user's supplementary operation on the thing primitive of the target thing in the canvas area, obtaining, from the configured definition view or design view of the target thing, supplementary things and corresponding supplementary thing information that have a thing relationship with the target thing specified by the user; the supplementary thing information includes a thing identifier representing the source of the supplementary thing; in response to the user's modification operation on any thing in the current used view of the first type, synchronously modifying the source thing corresponding to the thing identifier of the thing based on the modification information of the thing in the modification operation.

[0006] In a possible implementation, the user's reference operation on the second type is a drag-and-drop operation of the second type displayed in the navigation area of the user interface to the canvas area; or, the user's reference operation on the second type is an operation of selecting the source of the second type for a new thing with a specified member type added by the user in the currently displayed used view in the canvas area in the configuration area of the user interface.

[0007] In a possible implementation, the target thing is a target object of the second type, and the reference operation is the drag-and-drop operation; before assigning a thing identifier to the referenced target thing, the method further includes: in response to the user's configuration operation on the second type, determining the member type of the second type in the current used view as the target member type selected by the user; the target member type includes a component member and an attribute member.

[0008] In a possible implementation, after assigning a thing identifier to the referenced target thing, the method further includes: displaying the assigned thing identifier in the navigation area of the user interface, and the display position is in the area of the first type to which the current used view belongs.

[0009] In a possible implementation, in response to a user's supplementary operation on the thing primitive of the target thing in the canvas area, obtain the supplementary thing specified by the user and the corresponding supplementary thing information that has a thing relationship with the target thing from the configured definition view or design view of the target thing, including: in response to the user's supplementary operation on the thing primitive of the target thing in the canvas area, display a supplementary selection pop-up window in the user interface, and obtain at least one supplementary thing selected by the user and the thing relationship between any selected supplementary thing and the target thing; the supplementary selection pop-up window includes the thing identifier of the supplementary thing to be selected that has a thing relationship with the target thing; display the thing primitive of at least one supplementary thing selected by the user and the relationship primitive of the thing relationship between any supplementary thing and the target thing in the canvas area.

[0010] In a possible implementation, in response to a user's modification operation on any thing in the current usage view of the first category, synchronously modify the source thing corresponding to the thing identifier of the thing based on the modification information of the thing in the modification operation, including: in response to the user's modification operation on the thing identifier of the supplementary thing in the current usage view, query the stored definition view or design view of the supplementary thing; modify the thing identifier of the supplementary thing in the definition view or design view, and display the modified thing identifier of the supplementary thing in the source second category of the supplementary thing in the navigation area.

[0011] In a possible implementation, the method further includes: in response to the user's display operation on the definition view or design view of the supplementary thing in the current usage view, display the definition view or design view of the supplementary thing in the canvas area; in response to the user's modification operation on the thing identifier of the supplementary thing in the definition view or design view of the supplementary thing, obtain a thing modification identifier, and modify the thing identifier of the supplementary thing in the current usage view to the thing modification identifier; in response to the user's switching operation on the current usage view, display the current usage view of the supplementary thing including the thing modification identifier in the canvas area.

[0012] In a possible implementation, the modification operation includes a deletion operation; in response to the user's deletion operation on the thing primitive of the thing referenced in the current usage view, delete the thing identifier of the thing in the area belonging to the first category in the navigation area.

[0013] In a possible implementation, the method further includes: in response to the user's deletion operation on the second category to which the target thing referenced in the current usage view belongs in the navigation area, delete the current usage view of the first category that references the target thing in the canvas area, and delete the information of the second category and the things belonging to the second category referenced in the first category in the navigation area.

[0014] Second aspect, a view synchronous modification device is provided, which is applied to a language for object-oriented object relationship process modeling and in a modeling tool created by using object-oriented modeling technology. The modeling tool includes a database, and the database stores a definition view for describing the structure between things and a design view for describing the thing relationship between things established based on object relationship process modeling technology; the things include objects or processes belonging to different classes, and the thing relationship includes object association relationship or process relationship. The device may include: an adding unit, configured to add a thing primitive of a target thing of the second class in the currently used view displayed when a currently used view of the first class is displayed in the canvas area of the user interface in response to a reference operation of the user on the second class; an allocating unit, configured to allocate a thing identifier to the referenced target thing; the thing identifier represents the source of the referenced target thing; the target thing is a thing not included in the currently used view; an obtaining unit, configured to obtain, in response to a supplementary operation of the user on the thing primitive of the target thing in the canvas area, supplementary things and corresponding supplementary thing information specified by the user and having a thing relationship with the target thing from the definition view or the design view of the configured target thing; the supplementary thing information includes a thing identifier representing the source of the supplementary thing; a modifying unit, configured to, in response to a modification operation of any thing in the currently used view of the first class by the user, synchronously modify the source thing corresponding to the thing identifier of the thing based on the modification information of the thing for the modification operation.

[0015] Third aspect, an electronic device is provided. The electronic device includes a processor, a communication interface, a memory, and a communication bus. Among them, the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0016] The memory is used for storing a computer program;

[0017] The processor is configured to, when executing the program stored on the memory, implement any of the method steps described in the first aspect above.

[0018] Fourth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements any of the method steps described in the first aspect above.

[0019] The method for synchronously modifying views provided by the embodiments of the present application is applied to a modeling tool created by using object-oriented modeling technology based on an object relationship process modeling language. The modeling tool includes a database, which stores a definition view for describing the structure between things and a design view for describing the thing relationships between things established based on object relationship process modeling technology; things include objects or processes belonging to different classes, and thing relationships include object association relationships or process relationships. In this method, when the canvas area of the user interface displays the currently used view of the first type, in response to the user's reference operation on the second type, a thing primitive of the target thing of the second type is added to the currently displayed used view, and a thing identifier is assigned to the referenced target thing; the thing identifier represents the source of the referenced target thing; the target thing is a thing not included in the currently used view; in response to the user's supplementary operation on the thing primitive of the target thing in the canvas area, supplementary things and corresponding supplementary thing information specified by the user and having a thing relationship with the target thing are obtained from the configured definition view or design view of the target thing; the supplementary thing information includes a thing identifier representing the source of the supplementary thing; in response to the user's modification operation on any thing in the currently used view of the first type, based on the modification information of the thing by the modification operation, the source thing corresponding to the thing identifier of the thing is synchronously modified. This method can update the relevant information of the same thing (object or process) in different views in real time, reduce the cross-view operations of modelers, and improve the consistency and accuracy of cross-view information. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] To more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings required to be used in the embodiments of the present application. It should be understood that the following drawings only show some embodiments of the present application and should not be regarded as limiting the scope. For those of ordinary skill in the art, without creative efforts, other relevant drawings can also be obtained based on these drawings.

[0021] Figure 1 FIG. 9 is a schematic diagram of a user interface provided by an embodiment of the present application;

[0022] Figure 2 FIG. 13 is a schematic flowchart of a method for synchronously modifying views provided by an embodiment of the present application;

[0023] Figure 3a FIG. 17 is an interface diagram when a drag operation is performed on a thing of type 1 to the canvas area and not placed on the canvas area provided by an embodiment of the present application;

[0024] Figure 3b FIG. 21 is an interface diagram for selecting the member type of the composition members of type 1 provided by an embodiment of the present application;

[0025] Figure 3c An interface diagram for assigning a transaction identifier to component member 1 of reference type 1 provided by an embodiment of the present application;

[0026] Figure 4 An interface diagram for view reference provided by an embodiment of the present application;

[0027] Figure 5a An interface diagram for a user-triggered supplementary control provided by an embodiment of the present application;

[0028] Figure 5b An interface diagram for a supplementary selection pop-up window provided by an embodiment of the present application;

[0029] Figure 5c An interface diagram for a used view after supplementation provided by an embodiment of the present application;

[0030] Figure 6 An interface diagram for view modification provided by an embodiment of the present application;

[0031] Figure 7 An interface diagram for view deletion provided by an embodiment of the present application;

[0032] Figure 8 Another interface diagram for view deletion provided by an embodiment of the present application;

[0033] Figure 9 A structural schematic diagram of a view synchronous modification device provided by an embodiment of the present application;

[0034] Figure 10 A structural schematic diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0035] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application. Unless otherwise defined, the technical terms or scientific terms used in the present application shall have the ordinary meaning understood by those with ordinary skills in the field to which the present invention pertains. The "first", "second" and similar terms used in the present application do not denote any order, quantity or importance, but are only used to distinguish different components. The terms such as "including" or "comprising" mean that the elements or objects appearing before this term cover the elements or objects listed after this term and their equivalents, without excluding other elements or objects. The terms such as "upper", "lower", "left", "right" are only used to represent relative positional relationships. When the absolute position of the object being described changes, the relative positional relationship may also change accordingly.

[0036] For the convenience of understanding, the following explains the nouns involved in the embodiments of the present application:

[0037] A language for object - oriented object, relationship, and process modeling in systems engineering, which breaks down the barriers between knowledge models, computer languages, and natural languages, integrates systems engineering, software engineering, and knowledge engineering, enables seamless connection among computers, AI, and humans based on the same language, lays a foundation for the accumulation, utilization, and dissemination of knowledge, and promotes a qualitative leap in the breadth, depth, and efficiency of knowledge utilization.

[0038] Class: A template for objects, defining a set of common attributes and methods for a group of objects. To distinguish it from the class in software code, it can also be called a "type". It should be noted that this "type" does not represent a category.

[0039] Member: A component of a class. It belongs to a class and is similar to the fields of a class in programming languages.

[0040] Object: An entity or instance in a system.

[0041] Instance: The specific implementation of a class, including members, associated objects, and temporary members.

[0042] Reference: An identifier that copies an object or process, allowing access to the object or process in different views.

[0043] Relationship: A bond connecting two or more objects or processes, describing the dependencies and interaction links between things.

[0044] Process: A unit with specific inputs, outputs, and operation logics, representing a certain function or behavior.

[0045] Definition view: A view used to describe and display the structure of things.

[0046] Definition view of a process: The definition view of a process is a view used to describe and display the process definition structure, which is equivalent to the expansion of the process. Only associated objects related to the process will appear in the definition view of the process. At the same time, the view type and path are noted in the title.

[0047] Definition view of a class: Represents the external structure of a class and is a view used to describe and display the overall composition of the class. In this view, the external interfaces of the class in the system and its structural relationships with other classes can be described and displayed. If there are multiple relationships, the fishbone arrangement can be adopted.

[0048] Design view: Applicable to classes and processes, which is equivalent to an enlarged view of classes and processes, mainly reflecting the internal structures of classes and processes. The design view focuses on the specific design of classes and processes, showing the internal structure of classes and the detailed implementation methods of processes.

[0049] Design view of a class: The design view of a class is a view used to describe and display the internal structure of the class. In this view, all defined objects and processes of the class are clearly represented through relationships. The design view of a class not only clarifies the instances of the class and the processes and relationships it contains, but also explains that the processes that can be triggered in this view either do not require associated objects or all associated objects are members of the class.

[0050] Design view of a process: The design view of a process focuses on the internal logic and execution path of the process, which is equivalent to an enlargement of the process. In the design view of the process, the specific steps, conditional judgments, loop structures, etc. of the process are shown, and how the process operates and executes is described in detail.

[0051] Usage view: If an object or process is referenced in the definition view or design view of other objects or processes, then it is a usage view for this object or process. The usage view can be the definition view or design view of an object or process.

[0052] The view synchronization modification method provided by the embodiments of the present application can be applied to an object-oriented object relationship process modeling language and a modeling tool created using object-oriented modeling technology. The modeling tool includes a database that stores a definition view for describing the structure between things and a design view for describing the relationship between things based on the object relationship process modeling technology; things can include objects or processes belonging to different classes, and the thing relationship can include an object association relationship or a process relationship (such as a call relationship for a calling process).

[0053] In the method for synchronously modifying views provided in this application, by referring to processes or objects with the same source, it is possible to modify the referenced source process or source object, or the usage view to which the referenced source process or source object belongs, reducing the cross-view operations of modelers and improving the consistency and accuracy of cross-view information.

[0054] It should be noted that the reference of processes or objects by the modeling tool in this application and the modification of the usage view need to be realized through human-computer interaction by the user in the user interaction interface provided by the modeling tool. For example, Figure 1 As shown, the user interaction interface may include a navigation area, a canvas area, a configuration area, and a primitive toolbar. Among them, different types of identifiers and corresponding primitive flags and identifiers of various affiliated objects or processes are set in the navigation area. For example, in the affiliated area (or "directory") of a class, there are class 1 (or "type 1") and class 2 (or "type 2") with rectangular object primitive flags. Within the affiliated area of class 1 or class 2, there are corresponding different member type objects (such as component members) and class processes (or "processes") with elliptical process primitive flags established. The canvas area is used to display the usage view, and a thing creation floating box is included in the canvas area for adding corresponding primitives of component members, attribute members, or processes in the displayed usage view. In the configuration area, parameters of the process corresponding to the process primitive displayed in the canvas area or the object corresponding to the object primitive can be configured.

[0055] The primitive toolbar may include save operation controls, undo operation controls, return operation controls, view zoom controls, supplement controls, delete controls, etc.

[0056] Among them, the process primitive representing a process is an elliptical primitive; the object primitive representing an object is a rectangular primitive. Class 1 and class 2 are two different classes created.

[0057] It should be noted that for the processes in the view displayed in the canvas area, they can also be called class processes, and classes can also be called types. This appellation is only a custom behavior of designers and does not affect the specific implementation of the solution in this application.

[0058] The following describes the preferred embodiments of this application with reference to the accompanying drawings of the specification. It should be understood that the preferred embodiments described here are only used to illustrate and explain this application and are not used to limit this application. And without conflict, the embodiments in this application and the features in the embodiments can be combined with each other.

[0059] Figure 2 It is a schematic flowchart of a method for synchronously modifying views provided by an embodiment of this application. As Figure 2 shown, the method may include:

[0060] Step S210: When the current usage view of the first type is displayed in the canvas area of the user interface, in response to the user's reference operation on the second type, add the object primitive of the target object of the second type to the currently displayed usage view, and assign an object identifier to the referenced target object.

[0061] Among them, the user's reference operation on the second type (such as class 1 in the figure) is the user's drag operation from the second type displayed in the navigation area of the user interface to the canvas area; or, the user's reference operation on the second type is that after the user adds a new object of the specified member type to the currently displayed usage view in the canvas area, the user performs a source selection operation on the new object for the second type in the configuration area of the user interface.

[0062] The target object is an object not included in the currently used view, such as the user's reference operation on the composition member 1 belonging to the second type; the object identifier represents the source of the referenced target object.

[0063] In some embodiments, when the target object is the target object of the second type and the reference operation is a drag operation, before assigning an object identifier to the referenced target object, it is also possible to, in response to the user's configuration operation on the second type, determine the member type of the second type in the currently used view as the target member type selected by the user; the target member type may include composition members and attribute members.

[0064] Furthermore, after assigning an object identifier to the referenced target object, the assigned object identifier can be displayed in the navigation area of the user interface, and the display position is in the area of the first type to which the currently used view belongs.

[0065] In an example, taking the target object as the composition member 1 of class 1 and the reference operation as a drag operation as an example, under the usage view (definition view or design view) of class 2 displayed in the canvas area, the user performs a drag operation on type 1 in the navigation area to the canvas area, triggers the configuration of type 1 when placed in the canvas area. After the user selects the member type of type 1 as a composition member, assign an object identifier to the composition member 1 of the referenced type 1: composition member 1 [class 1] to represent the source, and display this identifier in the area of class 1 to which the current usage view belongs, thereby completing the reference to type 1 in the definition view or design view of type 2. Figure 3a Interface diagram when performing a drag operation on an object of type 1 to the canvas area and not placed in the canvas area. Figure 3b Interface diagram for selecting the member type of the composition member of type 1. Figure 3c Interface diagram for assigning an object identifier to the composition member 1 of the referenced type 1.

[0066] In yet another example, taking the class process 1 with the target thing being class 1 and the reference operation being the drag operation as an example, when there are class process 1 and class process 2 under class 1, the design view of class process 2 is displayed in the canvas area. The user performs a drag operation on class process 1 in the navigation area to the canvas area and places it in the canvas area, thereby achieving the reference to class process 1 in the design view of class process 2, as Figure 4 shown.

[0067] Step S220: In response to the user's supplementary operation on the thing primitive of the target thing in the canvas area, obtain the supplementary thing and the corresponding supplementary thing information specified by the user that have a thing relationship with the target thing from the configured definition view or design view of the target thing.

[0068] Among them, the supplementary thing information may include a thing identifier representing the source of the supplementary thing.

[0069] In specific implementation, in response to the user's supplementary operation on the thing primitive of the target thing in the canvas area, a supplementary selection pop-up window is displayed in the user interface, and at least one selected supplementary thing and the thing relationship between any selected supplementary thing and the target thing are obtained. Then, the thing primitive of at least one selected supplementary thing and the relationship primitive of the thing relationship between any supplementary thing and the target thing are displayed in the canvas area. Among them, the supplementary selection pop-up window may include the thing identifier of the supplementary thing to be selected that has a thing relationship with the target thing.

[0070] In an example, the design view of type 2 is displayed in the canvas area, including component member 1 and component member 2 that reference type 1. After the user selects the primitive of component member 1 in the canvas area, a supplementary control (used to supplement the association of the selected thing to the current view) is triggered in the primitive toolbar, and a supplementary selection pop-up window is displayed in the user interface. The supplementary selection pop-up window may include the original component member 1 (the component member 1 in string form) of type 1 associated with the selected component member 1, as well as class process 1 and class process 2 in type 1 that are associated with the original component member 1. After the user confirms the selection of component member 1 and class process 1, the corresponding primitives of the selected component member 1 and class process 1, and the relationship primitives of the relationships between component member 1 and class process 1 and the component member 1 of the referenced type 1 are displayed in the canvas area. Figure 5a Is the interface diagram for the user to trigger the supplementary control, Figure 5b Is the interface diagram of the supplementary selection pop-up window, Figure 5c Is the interface diagram of the usage view after supplementation.

[0071] Step S230: In response to the user's modification operation on any thing in the current usage view of the first type, based on the modification information of the thing for the modification operation, synchronously modify the source thing corresponding to the thing identifier of the thing.

[0072] In specific implementation, in response to a user's modification operation on the thing identifier of a supplementary thing in the currently used view, query the stored definition view or design view of the supplementary thing, modify the thing identifier of the supplementary thing in the definition view or design view, and display the modified thing identifier of the supplementary thing in the second category of the source of the supplementary thing in the navigation area. For example, as Figure 6 shown, taking the supplementary thing as the constituent member 1 of the string and the class process 1 in the design view of type 2 as an example, the user modifies the name in the identifiers of the constituent member 1 of the string and the class process 1. At the same time, the names of the constituent member 1 of the string and the class process 1 in the reference source - the constituent member 1 of the string and the class process 1 in type 1 are also modified.

[0073] After the above embodiment is modified in the view where the supplementary thing is located, synchronous modification of the view of the original file where the supplementary thing is located can be achieved.

[0074] In some embodiments, for the supplementary thing in the currently used view, in response to the user's display operation on the definition view or design view of the supplementary thing in the currently used view, display the definition view or design view of the supplementary thing in the canvas area;

[0075] In response to the user's modification operation on the thing identifier of the supplementary thing in the definition view or design view of the supplementary thing, obtain a thing modification identifier, and modify the thing identifier of the supplementary thing in the currently used view to the thing modification identifier;

[0076] In response to the user's switching operation on the currently used view, display the currently used view of the supplementary thing containing the thing modification identifier in the canvas area.

[0077] After the above embodiment is modified in the view of the original file where the supplementary thing is located, synchronous modification in the supplementary view where the supplementary thing is located can be achieved.

[0078] In some embodiments, the modification operation can also be a deletion operation, including: the deletion operation of any thing primitive in the currently used view and the deletion operation of the second category to which the thing referred to in the currently used view belongs.

[0079] (1) For the deletion operation of any thing primitive in the currently used view, it includes: the deletion of the thing primitive of the target thing referred to in the currently used view and the deletion of the thing primitive of the supplementary thing in the currently used view;

[0080] For the deletion of the thing primitive of the target thing referred to in the currently used view, it is necessary to delete the thing identifier of this thing in the area of the source thing's class to which the referred thing belongs in the navigation area; for example, as Figure 7As shown, the user initiates a deletion operation on the constituent member 2 of type 1 referenced in the design view of type 2. After confirming the deletion, the identifier of the referenced constituent member 2 in the area of type 2 in the navigation area is deleted.

[0081] To delete the object primitive of the supplementary thing in the currently used view, it only needs to delete the object primitive of the supplementary thing in the currently used view.

[0082] (2) For the deletion operation on the second type to which the target thing referenced in the currently used view belongs, specifically, in response to the user's deletion operation on the second type to which the target thing referenced in the currently used view belongs in the navigation area, it is necessary to delete the currently used view of the first type that references the target thing in the canvas area, and delete the information of the second type in the navigation area, as well as the things belonging to the second type referenced in the first type. For example, as Figure 8 shown, in the design view of type 2 (including constituent member 1 and constituent member 2 obtained from type 1 by reference, and class process 1 obtained by supplementation), when the user triggers a deletion operation on type 1, the situation of the type being referenced will be prompted (that is, the scenarios and types in which type 1 is used will be prompted). After the user confirms the deletion, constituent member 1 and constituent member 2 obtained from type 1 by reference in type 2, and class process 1 obtained by supplementation are not only deleted in the canvas area, but also the corresponding identifiers in the navigation area are deleted, and type 1 and all the corresponding content are deleted.

[0083] Corresponding to the above method, an embodiment of the present application further provides a device for synchronously modifying views, as Figure 9 shown, the device includes:

[0084] An adding unit 910, configured to add an object primitive of the target thing of the second type in the displayed currently used view in response to the user's reference operation on the second type when the canvas area of the user interface displays the currently used view of the first type;

[0085] An allocating unit 920, configured to allocate an object identifier for the referenced target thing; the object identifier represents the source of the referenced target thing; the target thing is a thing not included in the currently used view;

[0086] An obtaining unit 930, configured to obtain the supplementary thing and the corresponding supplementary thing information specified by the user that have a thing relationship with the target thing from the defined view or design view of the configured target thing in response to the user's supplementation operation on the object primitive of the target thing in the canvas area; the supplementary thing information includes the object identifier representing the source of the supplementary thing;

[0087] The modification unit 940 is configured to, in response to a user's modification operation on any thing in the current usage view of the first type, synchronously modify the source thing corresponding to the thing identifier of the thing based on the modification information of the thing resulting from the modification operation.

[0088] The functions of the functional units of the view synchronous modification device provided in the above embodiments of the present application can be implemented by the above method steps. Therefore, the specific working processes and beneficial effects of each unit in the view synchronous modification device provided in the embodiments of the present application will not be repeated here.

[0089] Embodiments of the present application also provide an electronic device, such as Figure 10 shown, including a processor 1010, a communication interface 1020, a memory 1030, and a communication bus 1040. Among them, the processor 1010, the communication interface 1020, and the memory 1030 complete communication with each other through the communication bus 1040.

[0090] The memory 1030 is used to store a computer program;

[0091] When the processor 1010 executes the program stored on the memory 1030, the following steps are implemented:

[0092] When the canvas area of the user interaction interface displays the current usage view of the first type, in response to the user's reference operation on the second type, add a thing primitive of the target thing of the second type to the displayed current usage view, and assign a thing identifier to the referenced target thing; the thing identifier represents the source of the referenced target thing; the target thing is a thing not included in the current usage view;

[0093] In response to the user's supplementary operation on the thing primitive of the target thing in the canvas area, obtain the supplementary thing and the corresponding supplementary thing information specified by the user that have a thing relationship with the target thing from the configured definition view or design view of the target thing; the supplementary thing information includes a thing identifier representing the source of the supplementary thing;

[0094] In response to a user's modification operation on any thing in the current usage view of the first type, synchronously modify the source thing corresponding to the thing identifier of the thing based on the modification information of the thing resulting from the modification operation.

[0095] The aforementioned communication bus can be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience in representation, only a thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0096] The communication interface is used for communication between the aforementioned electronic device and other devices.

[0097] The memory can include a Random Access Memory (RAM), and can also include a Non-Volatile Memory (NVM), such as at least one disk memory. Optionally, the memory can also be at least one storage device located far from the aforementioned processor.

[0098] The aforementioned processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0099] Since the implementation manners and beneficial effects of each device of the electronic device in the above embodiments can be referred to Figure 2 to the steps in the embodiments shown, therefore, the specific working process and beneficial effects of the electronic device provided in the embodiments of the present application will not be elaborated herein.

[0100] In another embodiment provided by the present application, there is also provided a computer-readable storage medium, in which instructions are stored. When it runs on a computer, it enables the computer to execute the view synchronization modification method described in any one of the above embodiments.

[0101] In another embodiment provided by the present application, there is also provided a computer program product containing instructions. When it runs on a computer, it enables the computer to execute the view synchronization modification method described in any one of the above embodiments.

[0102] Those skilled in the art should understand that the embodiments in the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the embodiments in the embodiments of the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments in the embodiments of the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program code.

[0103] The embodiments in the embodiments of the present application are described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments in the embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram, as well as the combination of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0104] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means that implement the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0105] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0106] Although the preferred embodiments in the embodiments of the present application have been described, those skilled in the art can make additional changes and modifications to these embodiments once they know the basic creative concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the embodiments of the present application.

[0107] Obviously, those skilled in the art can make various changes and modifications to the embodiments in the embodiments of the present application without departing from the spirit and scope of the embodiments in the embodiments of the present application. Thus, if these modifications and variations of the embodiments in the embodiments of the present application fall within the scope of the claims in the embodiments of the present application and their equivalent technologies, the embodiments of the present application also intend to include these changes and variations.

Claims

1. A method for synchronously modifying a view, characterized in that, Applied to a language for object-oriented object-relationship process modeling, in a modeling tool created using object-oriented modeling techniques, the modeling tool includes a database that stores a definition view for describing the structure between things and a design view for describing the thing relationships between things established based on object-relationship process modeling; The things include objects or processes belonging to different classes, and the thing relationships include object association relationships or process relationships. The method includes: When the canvas area of the user interface displays the current usage view of the first type, in response to the user's reference operation on the second type, add the thing primitive of the target thing of the second type to the displayed current usage view, and assign a thing identifier to the referenced target thing; the thing identifier represents the source of the referenced target thing; the target thing is a thing not included in the current usage view; In response to the user's supplementary operation on the thing primitive of the target thing in the canvas area, obtain the supplementary thing and the corresponding supplementary thing information specified by the user that have a thing relationship with the target thing from the configured definition view or design view of the target thing; the supplementary thing information includes the thing identifier representing the source of the supplementary thing; In response to the user's modification operation on any thing in the current usage view of the first type, synchronously modify the source thing corresponding to the thing identifier of the thing based on the modification information of the thing by the modification operation.

2. The method according to claim 1, wherein The user's reference operation on the second type is the user's drag operation of the second type displayed in the navigation area of the user interface to the canvas area; Or, the user's reference operation on the second type is the user's operation of selecting the source of the second type for the new thing in the configuration area of the user interface after adding a new thing of the specified member type to the current usage view displayed in the canvas area.

3. The method according to claim 2, wherein The target thing is the target object of the second type, and the reference operation is the drag operation; Before assigning the thing identifier to the referenced target thing, the method further includes: In response to the user's configuration operation on the second type, determine the member type of the second type in the current usage view as the target member type selected by the user; the target member type includes component members and attribute members.

4. The method according to claim 1, wherein After assigning the thing identifier to the referenced target thing, the method further includes: Display the assigned thing identifier in the navigation area of the user interface, and the display position is in the area of the first type to which the current usage view belongs.

5. The method according to claim 1, wherein In response to the user's supplementary operation on the thing primitive of the target thing in the canvas area, obtain the supplementary thing and the corresponding supplementary thing information specified by the user that have a thing relationship with the target thing from the configured definition view or design view of the target thing, including: In response to the user's supplementary operation on the thing primitive of the target thing in the canvas area, display a supplementary selection pop-up window in the user interface, and obtain at least one supplementary thing selected by the user and the thing relationship between any selected supplementary thing and the target thing; the supplementary selection pop-up window includes the thing identifiers of the to-be-selected supplementary things that have a thing relationship with the target thing; Display the object diagram of at least one supplementary object selected by the user and the relationship diagram of the relationship between any supplementary object and the target object in the canvas area.

6. The method according to claim 1, characterized in that, In response to a modification operation on any object in the current usage view of the first type by the user, based on the modification information of the object resulting from the modification operation, synchronously modify the source object corresponding to the object identifier of the object, including: In response to a modification operation on the object identifier of a supplementary object in the current usage view by the user, query the stored definition view or design view of the supplementary object; modify the object identifier of the supplementary object in the definition view or design view, and display the modified object identifier of the supplementary object in the source second type of the supplementary object in the navigation area.

7. The method according to claim 1, wherein The method further includes: In response to a display operation by the user on the definition view or design view of a supplementary object in the current usage view, display the definition view or design view of the supplementary object in the canvas area; In response to a modification operation on the object identifier of the supplementary object by the user in the definition view or design view of the supplementary object, obtain an object modification identifier, and modify the object identifier of the supplementary object in the current usage view to the object modification identifier; In response to a switching operation by the user on the current usage view, display the current usage view of the supplementary object including the object modification identifier in the canvas area.

8. The method according to claim 1, wherein The modification operation includes a deletion operation; In response to a deletion operation on the object diagram of an object referenced in the current usage view by the user, delete the object identifier of the object in the area belonging to the first type in the navigation area.

9. The method according to claim 8, wherein The method further includes: In response to a deletion operation by the user on the second type to which the target object referenced in the current usage view belongs in the navigation area, delete the current usage view of the first type that references the target object in the canvas area, and delete the information of the second type and the objects belonging to the second type referenced in the first type in the navigation area.

10. A device for synchronously modifying a view, characterized in that, Applied to a language for object-oriented object relationship process modeling, in a modeling tool created using object-oriented modeling techniques, the modeling tool includes a database that stores a definition view for describing the structure between objects and a design view for describing the object relationships between objects established based on object relationship process modeling techniques; The objects include objects or processes belonging to different classes, the object relationships include object association relationships or process relationships, and the device includes: An adding unit, configured to, when the canvas area of the user interface displays the current usage view of the first type, in response to a reference operation by the user on the second type, add an object diagram of the target object of the second type to the displayed current usage view; An assigning unit, configured to assign an object identifier to the referenced target object; the object identifier represents the source of the referenced target object; the target object is an object not included in the current usage view; An acquisition unit, configured to, in response to a user's supplementary operation on the thing primitive of the target thing in the canvas area, acquire a supplementary thing that has a thing relationship with the target thing specified by the user and corresponding supplementary thing information from the defined view or design view of the configured target thing; the supplementary thing information includes a thing identifier characterizing the source of the supplementary thing. A modification unit, configured to, in response to a user's modification operation on any thing in the current usage view of the first type, synchronously modify the source thing corresponding to the thing identifier of the thing based on the modification information of the thing resulting from the modification operation.

Images