Management device and system for model reuse
Through model packaging module and permission configuration, the problems of low efficiency, poor flexibility and insufficient security in the prior art are solved, and efficient and secure model reuse management is achieved.
Patent Information
- Application Number
- CN202510413090.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-03
- Publication Date
- 2025-07-18
AI Technical Summary
In the existing modeling methods, the model reuse process cannot be effectively controlled to the following level of the model, resulting in low reuse efficiency, poor flexibility and insufficient security.
Provide a management device and system for model reuse, obtain business requirements through the model encapsulation module, encapsulate and configure permissions, combine database storage and user interaction page search requests to realize fine control and permission management, and establish a complete reuse and permission control mechanism.
It improves the efficiency, flexibility and security of model reuse, supports fine control of model packaging granularity, and ensures the accuracy and security of the model reuse process.
Smart Images
Figure CN120335795A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the technical field of model management. Specifically, it relates to a management device and system for model reuse. Background Art
[0002] In existing modeling methods, model reuse technology is integrated to form a professional strategy for optimizing software development processes and enhancing efficiency. On this basis, a basic model is constructed, and reusable model components are refined through abstraction and generalization techniques. To ensure reusability, these components need to be standardized to form a standardized component resource library and stored in a model library. Combining with actual requirements, reusable models are selected and integrated and adaptively adjusted to implement the model reuse principle. However, in the process, the details of the reuse process cannot be controlled at a level below the model. Summary of the Invention
[0003] The purpose of the embodiments of this application is to provide a management device and system for model reuse. By combining actual requirements, technical architectures, and security policies, a complete set of reuse and permission control mechanisms is established, effectively improving the efficiency, flexibility, and security of model reuse.
[0004] In a first aspect, a management device for model reuse is provided, which is applied to a management system including a database. The management system is built using a language that supports object-relational process modeling for object orientation. The database is used to store different classes, members and processes under the corresponding classes, as well as member association relationships and process call relationships. The device includes:
[0005] A model encapsulation module, configured to obtain a model encapsulation request, where the model encapsulation request includes current business requirements and corresponding business processing logics; read at least one class, members and processes under the corresponding class, and corresponding member association relationships and process call relationships related to the current business requirements from the database; based on the business processing logics, encapsulate the read classes, members and processes under the corresponding class, corresponding member association relationships and process call relationships to obtain business models corresponding to each class that meet the business processing logics; the business models include multi-level element structures under the corresponding class, and the element structures include members and processes under the corresponding class, as well as corresponding member association relationships and corresponding process call relationships;
[0006] A model permission allocation module, configured to configure reference permissions for element structures at each level in the encapsulated business models respectively, and assign corresponding visibility marks to the corresponding reference permissions;
[0007] A model storage and reference module, which is used to store the encapsulated business models and the mapping relationships between the visibility marks of each level in the corresponding business models and the corresponding reference permissions; in response to a search request input by a user on a user interaction page, obtain the target business model corresponding to the search request, and determine whether to allow the reference of the target business model based on the reference permissions corresponding to the stored target business model and the current business model displayed in the canvas area on the user interaction page;
[0008] A model reuse record module, which is used to record the reuse information of the target business model.
[0009] In some possible implementations, the model encapsulation module is further used to, in response to an encapsulation requirement for the business processing logic input by a user on a user interaction page, encapsulate the classes, members and procedures under the corresponding classes, and the corresponding member association relationships and procedure call relationships involved in the encapsulation requirement among the read various types, members and procedures under the corresponding classes, to obtain a business model that meets the business processing logic and the encapsulation requirement.
[0010] In some possible implementations, the model encapsulation module is further used to, in response to a verification operation triggered by a user on a user interaction page, perform encapsulation verification on the encapsulated business model to obtain an encapsulation verification result.
[0011] In some possible implementations, the search request includes a search keyword;
[0012] The model storage and search module is specifically used to search for at least one business model to be selected from the stored business models based on the search keyword; then, in response to a filtering condition input by a user on a user interaction page, filter the at least one business model to be selected to obtain the target business model corresponding to the access request.
[0013] In some possible implementations, the model storage and reference module is further used to, after determining that the reference of the target business model is not allowed, in response to a forced authorization operation by a user on a user interaction page and after obtaining the forced authorization condition input by the user, allow the reference of the target business model based on the forced authorization condition.
[0014] In some possible implementations, the types of the reference permissions include public permissions, protection permissions and private permissions;
[0015] The public permissions indicate that the business models corresponding to the directories where different classes are located can be referenced to each other;
[0016] The protection permissions indicate that different business models corresponding to the directories where the same class is located can be referenced to each other;
[0017] The private permission indicates that different elements within the same business model corresponding to the directory where the same class is located can be referenced.
[0018] In some possible implementations, the model storage and reference module is specifically configured to determine that the target business model is allowed to be referenced if the permission type of the target business model is a public permission; to determine that the target business model is allowed to be referenced if the target business model and the current business model are in the same directory; and to determine that the target business model is allowed to be referenced if the target business model and the current business model are within the same business model.
[0019] In some possible implementations, the model storage and reference module is specifically configured to store the mapping relationships between the encapsulated business models, the visibility markers of each level and corresponding permissions in the corresponding business models in different regions based on the class information of different classes.
[0020] In some possible implementations, the reuse information of the business model includes recording the acquisition path, version information, and reuse historical data of the target business model.
[0021] In a second aspect, a management system is provided. The management system is constructed using a language that supports object-oriented object-relationship process modeling. The system includes: a database for storing different classes, members and processes under the corresponding classes, as well as the member association relationships between members and the process call relationships between members and processes, a display screen for providing a user interaction page, and the management device for model reuse according to any one of the first aspect.
[0022] In the management device and system for model reuse provided by the embodiments of the present application, the model encapsulation module of the device is used to obtain a model encapsulation request including the current business requirements and the corresponding business processing logic; read at least one class related to the current business requirements, the members and processes under the corresponding class, and the corresponding member association relationships and process call relationships from the database; based on the business processing logic, encapsulate the read classes, the members and processes under the corresponding class, the corresponding member association relationships and process call relationships to obtain business models corresponding to each class that meet the business processing logic; the business model includes a multi-level element structure under the corresponding class, and the element structure includes the members and processes under the corresponding class, and the corresponding member association relationships and the corresponding process call relationships; the model permission allocation module is used to configure reference permissions for the element structures at each level in the encapsulated business model respectively, and assign corresponding visibility marks to the corresponding reference permissions; the model storage and reference module is used to store the encapsulated business models and the mapping relationships between the element structures at each level in the corresponding business models and the visibility marks of the corresponding reference permissions; in response to a search request input by the user on the user interaction page, obtain the target business model corresponding to the search request, and determine whether to allow the reference of the target business model based on the reference permissions corresponding to the stored target business model and the current business model displayed in the canvas area on the user interaction page; the model reuse record module is used to record the reuse information of the target business model. The device supports fine control of the model encapsulation granularity to meet different reuse requirements; combined with the actual requirements, technical architecture and security policies, a complete set of reuse and permission control mechanisms are established, effectively improving the efficiency, flexibility and security of model reuse. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present application, and therefore should not be regarded as limiting the scope. For those of ordinary skill in the art, other related drawings can be obtained based on these drawings without creative efforts.
[0024] Figure 1 FIG. [X] is a schematic structural diagram of a management system provided by an embodiment of the present application;
[0025] Figure 2 FIG. [Y] is a schematic structural diagram of a management device for model reuse provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0026] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to 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 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 scope of protection 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 of ordinary skill in the art to which the present invention pertains. Words such as "including" or "comprising" and the like mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Words such as "connected", "coupled" or "linked" and the like are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect.
[0027] For the convenience of understanding, the following explains the nouns involved in the embodiments of the present application:
[0028] 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, and lays a foundation for the accumulation, utilization, and dissemination of knowledge, promoting a qualitative leap in the breadth, depth, and efficiency of knowledge utilization.
[0029] Class: A template for an object, 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.
[0030] Member: A component of a class. It belongs to a class and is similar to the fields of a class in a programming language.
[0031] Object: An entity or instance in a system.
[0032] Relationship: A bond connecting two or more objects or processes, describing the dependencies and interaction connections between things.
[0033] Process: A unit with specific inputs, outputs, and operation logics, representing a certain function or behavior.
[0034] Scenario View: It is used to display interactions and operations in a specific context, simulate the actual performance of the system in certain scenarios, so as to analyze and optimize the system design. The scenario is essentially a class, but it has one and only one process. It can only use the classes and their public processes defined in the model, or the classes and public processes predefined by the system. It can also call the classes and their public processes included in the imported package. The type of the class instance used in the design view corresponding to the process of the scenario view is a temporary member.
[0035] The management device for model reuse provided by the embodiments of the present application can be applied in Figure 1 the management system shown in the figure. The system may include: a database, a display screen providing a user interaction page, and a management device for model reuse. The system is constructed using an object-relational process modeling language that supports object orientation.
[0036] The database is used to store different classes, members and processes under the corresponding classes, as well as the member association relationships between members and the process call relationships between members and processes.
[0037] As Figure 2 shown in the figure, the management device for model reuse may include a model encapsulation module, a model permission allocation module, a model storage and reference module, and a model reuse record module. Among them:
[0038] The model encapsulation module is used to obtain a model encapsulation request, which may include the current business requirements and the corresponding business processing logic; read at least one class, members and processes under the corresponding class, and the corresponding member association relationships and process call relationships related to the current business requirements from the database; based on the business processing logic, encapsulate the read classes, members and processes under the corresponding class, and the corresponding member association relationships and process call relationships to obtain business models corresponding to various classes that meet the business processing logic; the business model includes a multi-level element structure under the corresponding class, and the element structure includes members and processes under the corresponding class, and the corresponding member association relationships and corresponding process call relationships;
[0039] The model permission allocation module is used to configure reference permissions for each level of the element structure in the encapsulated business model respectively, and assign corresponding visibility marks to the corresponding reference permissions;
[0040] The model storage and reference module is used to store the encapsulated business models and the mapping relationships between the visibility marks of each level of the corresponding business models and the corresponding permissions, that is, to build a comprehensive model library; in response to a search request input by the user on the user interaction page, obtain the target business model corresponding to the search request, and based on the permissions corresponding to the stored target business model and the current business model displayed in the canvas area on the user interaction page, determine whether to allow the reference of the target business model to reuse the business model;
[0041] A model reuse record module is used to record the reuse information of the target business model. The reuse information of this business model may include the acquisition path of the target business model obtained from the model storage and reference module, the version information of the model encapsulated by the model encapsulation module, the reuse historical data of the model, the permission allocation information of the model, etc., to form a complete model reuse record.
[0042] Furthermore, the model encapsulation module is also used to respond to the encapsulation requirements for business processing logic input by the user on the user interaction page. Among the various types read, members and processes under the corresponding classes, and the corresponding member association relationships and process call relationships, it encapsulates the classes, members and processes under the corresponding classes, and the corresponding member association relationships and process call relationships involved in the encapsulation requirements to obtain a business model that meets the business processing logic and encapsulation requirements.
[0043] The above embodiments can support fine control of the model granularity by formulating model encapsulation standards and formats and improving the flexible encapsulation mechanism. Users can adjust the encapsulation scope according to actual needs, such as only encapsulating a specific part of the model.
[0044] In some embodiments, in order to ensure the accuracy and standardization of the encapsulation operation, the monitoring and management of the encapsulation process can be implemented. At this time, the model encapsulation module can also respond to the verification operation triggered by the user on the user interaction page to perform encapsulation verification on the encapsulated business model to obtain an encapsulation verification result.
[0045] In some embodiments, the search request may include a search keyword;
[0046] The model storage and search module is specifically used to rely on an efficient search algorithm combined with an intelligent recommendation system to search for at least one business model to be selected from the stored business models based on the search keyword; then, through detailed model evaluation criteria, it formulates a model screening process, and responds to the screening conditions input by the user on the user interaction page to screen at least one business model to be selected to obtain the target business model corresponding to the access request, so as to ensure the quality and applicability of the selected model.
[0047] In some embodiments, the types of reference permissions may include public permissions, protection permissions, and private permissions; public permissions indicate that business models corresponding to different class directories can be referenced; protection permissions indicate that different business models corresponding to the same class directory can be referenced; private permissions indicate that different elements within the same business model corresponding to the same class directory can be referenced.
[0048] The model storage and reference module is specifically used to determine that the target business model is allowed to be referenced if the permission type of the target business model is public permission; if the target business model and the current business model are in the same directory, it is determined that the target business model is allowed to be referenced; if the target business model and the current business model are within the same business model, it is determined that the target business model is allowed to be referenced.
[0049] Further, after determining that the target business model is not allowed to be referenced, in response to the user's forced authorization operation on the user interaction page and obtaining the forced authorization conditions input by the user on the user interaction interface, based on the forced authorization conditions, the user is allowed to access the target business model.
[0050] In some embodiments, the model storage and reference module can store the mapping relationships between the encapsulated business models, the visibility markers of each level and corresponding permissions in the corresponding business models in different regions based on different types of class information, such as class identifiers.
[0051] In some embodiments, the model permission allocation module can allocate level permissions for different users according to the user levels of different users, such as first-level leaders, second-level leaders, and ordinary team members; the level permissions are used for the hierarchical permissions for changing the reference permissions. For example, the hierarchical permission of a first-level leader is level 2, the hierarchical permission of a second-level leader is level 1, and the hierarchical permission of an ordinary employee is level 0. Among them, the hierarchical permission of level 2 can change both the protection permission and the private permission to public permission for this user; the hierarchical permission of level 1 can change the protection permission to public permission and change the private permission to protection permission for this user; the hierarchical permission of level 0 keeps the original reference permission unchanged.
[0052] The model reuse management device provided by this application designs a complete set of application, approval, release, and update processes for the reuse model by establishing a reuse and permission control mechanism, and establishes a version management mechanism for the reuse model. Adopt mechanisms such as role-based access control or attribute-based access control to finely control the access and use of the model, and provide functions for permission allocation and management. At the same time, formulate a security audit mechanism to record the access and use situations of the model, and provide functions for querying and analyzing audit logs. Adopt technical means such as encryption, signature, and authentication to ensure the security and integrity of the model during transmission and storage, and establish a security backup and recovery mechanism for the model.
[0053] 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 memory, CD-ROM, optical memory, etc.) containing computer-usable program code.
[0054] 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, so 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 or more of the flows Figure 1 or a plurality of flows and / or blocks
[0055] 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, so that the instructions stored in the computer-readable memory generate a manufactured article including instruction means, and the instruction means implement the functions specified in Figure 1 one or more of the flows Figure 1 or a plurality of flows and / or blocks
[0056] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in Figure 1 one or more of the flows Figure 1 or a plurality of flows and / or blocks
[0057] 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 concept. Therefore, the appended claims are intended to be construed as including the preferred embodiments and all changes and modifications falling within the scope of the embodiments of the present application.
[0058] Obviously, those skilled in the art can make various modifications and variations to the embodiments in this application without departing from the spirit and scope of the embodiments in this application. Thus, if these modifications and variations of the embodiments in this application fall within the scope of the claims in this application and their equivalent technologies, then this application also intends to include these modifications and variations.
Claims
1. A management device for model reuse, characterized in that, Applied to a management system including a database, the management system is built using a modeling language that supports an object-oriented object-relational process. The database is used to store different classes, members and processes under the corresponding classes, and corresponding relationships. The corresponding relationships include member association relationships and process call relationships. The apparatus includes: A model encapsulation module, configured to obtain a model encapsulation request, where the model encapsulation request includes a current business requirement and corresponding business processing logic; read at least one class, members and processes under the corresponding class, and corresponding relationships related to the current business requirement from the database; based on the business processing logic, encapsulate the read classes, members and processes under the corresponding class, and corresponding relationships to obtain business models corresponding to each class that meet the business processing logic; the business models include multi-level element structures under the corresponding class, and the element structures include members and processes under the corresponding class, and corresponding relationships; A model permission allocation module, configured to configure reference permissions for element structures at each level in the encapsulated business models respectively, and assign corresponding visibility marks to the corresponding reference permissions; A model storage and reference module, configured to store the encapsulated business models and the mapping relationship between the visibility marks of each level in the corresponding business models and the corresponding reference permissions; in response to a search request input by a user on a user interaction page, obtain a target business model corresponding to the search request, and determine whether to allow the reference of the target business model based on the reference permissions corresponding to the stored target business model and the current business model displayed in the canvas area on the user interaction page; A model reuse record module, configured to record the reuse information of the target business model.
2. The management device according to claim 1, characterized in that, The model encapsulation module is further configured to, in response to an encapsulation requirement for the business processing logic input by a user on a user interaction page, encapsulate the classes, members and processes under the corresponding class, and the corresponding member association relationships and process call relationships involved in the encapsulation requirement among the read classes, members and processes under the corresponding class, and corresponding relationships to obtain a business model that meets the business processing logic and the encapsulation requirement.
3. The management device according to claim 1 or 2, characterized in that, The model encapsulation module is further configured to, in response to a verification operation triggered by a user on a user interaction page, perform encapsulation verification on the encapsulated business model to obtain an encapsulation verification result.
4. The management device according to claim 1, wherein The search request includes a search keyword; The model storage and search module is specifically configured to search for at least one business model to be selected from the stored business models based on the search keyword; then, in response to a filtering condition input by a user on the user interaction page, filter the at least one business model to be selected to obtain a target business model corresponding to the access request.
5. The management device according to claim 1, wherein The model storage and reference module is further configured to, after determining that the reference of the target business model is not allowed, in response to a forced authorization operation by a user on the user interaction page and after obtaining the forced authorization condition input by the user, allow the reference of the target business model based on the forced authorization condition.
6. The management device according to claim 1, wherein The types of the reference permissions include public permissions, protection permissions and private permissions; The described public permission indicates that it can be referenced among business models corresponding to different class directories; The described protection permission indicates that it can be referenced among different business models corresponding to the same class directory; The described private permission indicates that it can be referenced among different elements within the same business model corresponding to the same class directory.
7. The management device according to claim 6, wherein The model storage and reference module is specifically configured to, if the permission type of the target business model is a public permission, determine that the target business model is allowed to be referenced; if the target business model and the current business model are in the same directory, determine that the target business model is allowed to be referenced; if the target business model and the current business model are within the same business model, determine that the target business model is allowed to be referenced.
8. The management device according to claim 1, characterized in that, The model storage and reference module is specifically configured to, based on the class information of different classes, store the encapsulated business models, the mapping relationships between each level in the corresponding business models and the visibility marks of the corresponding permissions in different regions.
9. The management device according to claim 1, wherein The reuse information of the business model includes recording the acquisition path, version information, and reuse historical data of the target business model.
10. A management system, characterized in that, The management system is built using an object-relational process modeling language that supports object orientation. The system includes: a database for storing different classes, members and processes under the corresponding classes, as well as the member association relationships between members and the process call relationships between members and processes, a display screen for providing a user interaction page, and a management device for model reuse according to any one of claims 1-9.