Public case library management method and system based on dynamic authority control

Abstract

The invention provides a public case library management method and system based on dynamic authority control, and the method comprises the steps: obtaining a department organization structure of an enterprise, setting the management authority of a public case library for each department, and associating a user with the department organization structure; the user selects the use case needing to be collected from the project, whether a collection permission exists or not is judged according to fuzzy matching of a department associated with the user and the use case library module, and if yes, the use case needing to be collected is written into the corresponding use case library module of the public use case library; selecting a reuse case from the public case library by a user, creating a new project case, and inheriting basic information of the case to be reused; the user selects the use case needing to be removed from the public use case library, whether the user has the collection permission or not is judged according to fuzzy matching of the department associated with the user and the use case library module, and if yes, the use case needing to be removed is removed from the corresponding use case library module of the public use case library. According to the method, a centralized public case library is constructed, and accurate classification and efficient maintenance of public cases are realized based on an authority control mechanism.

Description

Technical Field

[0001] The present invention relates to the technical field of knowledge management systems, and in particular to a public use case library management method and system based on dynamic authority control. Background Art

[0002] The public test case library is a system for storing, managing and sharing test cases, documents, templates and other information. Usually, the public test case library is an important resource library established by enterprises or development teams to improve work efficiency and ensure quality assurance. In traditional development and testing processes, the public test case library is often used to store standardized test cases, functional verification cases, performance test templates, etc. for reuse by different projects and teams.

[0003] Currently, most companies and teams still use local document management to build and maintain a public use case library. This means that all public use cases are stored in the local file system, usually a shared network drive or team collaboration platform, and the files exist in common document formats (such as Word, Excel, TXT, etc.), and there is no dedicated management system to uniformly control them.

[0004] In this model, the management of the public use case library usually lacks permission restrictions and is open to all employees. All team members and project managers can edit, delete or add new use cases at any time. Although this method is simple, it lacks effective management and control mechanisms and is prone to the following problems:

[0005] Document formats are not uniform, making information difficult to integrate and use;

[0006] Files are stored in scattered locations, making them difficult to find and access;

[0007] The content lacks traceability and cannot effectively confirm the accuracy and security of assets;

[0008] Unrestricted operation rights make it easy to make mistakes, which increases management risks.

[0009] The use case libraries between different departments and teams lack sharing and reuse mechanisms, resulting in increased duplication of work and low efficiency. Summary of the invention

[0010] In view of this, an embodiment of the present invention provides a public use case library management method and system based on dynamic permission control to eliminate or improve one or more defects existing in the prior art.

[0011] On the one hand, the present invention provides a public use case library management method based on dynamic authority control, which obtains the departmental organizational structure of the enterprise in advance, sets the management authority of the public use case library for each department, and associates the user with the departmental organizational structure. The method comprises the following steps:

[0012] The user selects the use cases to be collected from the project and initiates a collection request; the department associated with the user is fuzzy matched with the corresponding use case library module. If the match is successful, it indicates that the user has the collection authority, and the use cases to be collected are written into the corresponding use case library module of the public use case library;

[0013] The user selects a use case to be reused from the public use case library and initiates a reuse request; creates a new project use case and inherits the basic information of the use case to be reused;

[0014] The user selects the use case to be removed from the public use case library and initiates a removal request; the department associated with the user is fuzzy matched with the corresponding use case library module. If the match is successful, it indicates that the user has the removal authority, and the use case to be removed is removed from the corresponding use case library module of the public use case library.

[0015] In some embodiments of the present invention, obtaining the departmental organizational structure of an enterprise in advance and associating the user with the departmental organizational structure includes:

[0016] The department organization structure is stored in a MySQL database, and the department organization structure is regularly updated according to a preset time interval;

[0017] The user is associated with the department organizational structure to dynamically obtain the management authority of the user in the public use case library through the association relationship.

[0018] In some embodiments of the present invention, the method further comprises:

[0019] The public use case library adopts a tree structure, the root node is the public use case library as a whole, and the nodes are the use case library modules; each node supports adding submodule operations, renaming operations and deleting module operations.

[0020] In some embodiments of the present invention, the department to which the user belongs is fuzzily matched with the corresponding use case library module. If the match is successful, it indicates that the user has the collection authority, including:

[0021] When the user initiates a collection request, the backend provides a first application programming interface for the frontend to obtain information about all use case library modules of the public use case library, and the frontend obtains the names of all first-level use case library modules under the interface response result;

[0022] The backend provides a second application programming interface for the frontend to obtain the current user information, and the frontend obtains the department name associated with the current user in the interface response result;

[0023] Loop through the first-level use case library module name to determine whether it fuzzily matches the department name associated with the current user. If it matches, the current user has management authority over the use case library module and its sub-modules. If it does not match, the current user has no management authority and can only view data.

[0024] In some embodiments of the present invention, writing the use cases to be collected into the use case library module corresponding to the public use case library includes:

[0025] Collect the use cases to be collected in batches or individually into the corresponding use case library modules of the public use case library;

[0026] After the collection is completed, the project use case database table is updated and the fields of the use cases to be collected are set.

[0027] In some embodiments of the present invention, removing the use case to be removed from the use case library module corresponding to the public use case library includes:

[0028] Remove the use cases to be removed in batches or individually from the corresponding use case library modules of the public use case library;

[0029] After the removal is completed, update the project use case database table and set the fields of the use case to be removed.

[0030] In some embodiments of the present invention, the method further comprises:

[0031] Determine the management operations that need to be recorded, where the management operations at least include viewing use cases, grouping use cases, reusing use cases, and removing use cases;

[0032] Setting a log data structure, wherein the data structure includes a plurality of fields to describe relevant information of each management operation;

[0033] The front end captures the user's management operations through event monitoring, sends the monitored data to the back end, records it in the log, and stores it in the preset database.

[0034] On the other hand, the present invention also provides a public use case library management system based on dynamic authority control, the system comprising:

[0035] The organizational structure management module is used to obtain the departmental organizational structure of the enterprise and store it in the MySQL database, set the management authority of the public use case library for each department, and regularly update the departmental organizational structure according to the preset time interval;

[0036] A user management module, used to associate a user with the department organizational structure, so as to dynamically obtain the management authority of the user in the public use case library through the association relationship;

[0037] The public use case library dynamic authority control module is used to fuzzy match the department associated with the user with the corresponding use case library module when the user manages the public use case library. If the match is successful, it indicates that the user has the corresponding management authority;

[0038] A module for collecting public use cases, which is used to select use cases to be collected from a project when a user has collection authority, and write the use cases to be collected into a use case library module corresponding to the public use case library;

[0039] The reuse public use case module is used for users to select a use case to be reused from the public use case library, create a new project use case, and inherit the basic information of the use case to be reused;

[0040] The public use case removal module is used to select a use case to be removed from the public use case library when the user has the removal authority, and remove the use case to be removed from the corresponding use case library module of the public use case library.

[0041] In some embodiments of the present invention, the system further comprises:

[0042] A project use case management module, used to manage and display use cases related to a project, and supports grouping use cases from projects into the public use case library;

[0043] A public use case management module, used to query and manage project use cases marked as public use cases, and display them in a use case library module corresponding to the public use case library;

[0044] The public use case library operation log management module is used to record and manage the relevant behavior data of users managing the public use case library in the system.

[0045] On the other hand, the present invention further provides a computer-readable storage medium having a computer program / instruction stored thereon, which implements the steps of any of the methods mentioned above when executed by a processor.

[0046] The present invention provides a public use case library management method and system based on dynamic authority control, including: obtaining the departmental organizational structure of an enterprise, setting the management authority of the public use case library for each department, and associating the user with the departmental organizational structure; the user selects the use case to be collected from the project, and judges whether the collection authority is available according to the fuzzy matching between the department associated with the user and the use case library module, and if so, writes the use case to be collected into the use case library module corresponding to the public use case library; the user selects the reused use case from the public use case library, creates a new project use case, and directly inherits the basic information of the reused use case after setting the field; the user selects the use case to be removed from the public use case library, and judges whether the collection authority is available according to the fuzzy matching between the department associated with the user and the use case library module, and if so, removes the use case to be removed from the use case library module corresponding to the public use case library. The present invention constructs a centralized public use case library, manages according to the departmental dimension, and dynamically obtains the corresponding management authority according to the department associated with the user based on the authority control mechanism, effectively realizing the accurate classification and efficient maintenance of public use cases. Allowing users to access and operate the use case library according to their authority ensures the security of information. At the same time, through the intelligent classification function, users can easily find the required use cases, which improves the efficiency of search and application. In addition, it supports the management and historical record tracking of public use cases, ensuring the accuracy and consistency of use cases throughout their life cycle. This comprehensive management approach not only improves work efficiency, but also reduces the risk of human errors, providing a more reliable foundation for team collaboration.

[0047] Additional advantages, purposes, and features of the present invention will be described in part in the following description, and will become apparent to those skilled in the art after studying the following, or may be learned from the practice of the present invention. The purposes and other advantages of the present invention may be achieved and obtained by the structures specifically indicated in the specification and the accompanying drawings.

[0048] Those skilled in the art will appreciate that the objectives and advantages that can be achieved with the present invention are not limited to the above specific description, and the above and other objectives that can be achieved by the present invention will be more clearly understood from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] The drawings described herein are used to provide a further understanding of the present invention, constitute a part of the present application, and do not constitute a limitation of the present invention. In the drawings:

[0050] Figure 1 The figure is a schematic diagram of the steps of a public use case library management method based on dynamic permission control in one embodiment of the present invention.

[0051] Figure 2 The figure is a flow chart of a method for managing a public use case library based on dynamic permission control in one embodiment of the present invention. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the embodiments and the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0053] It should also be noted that, in order to avoid obscuring the present invention due to unnecessary details, only structures and / or processing steps closely related to the solutions according to the present invention are shown in the accompanying drawings, while other details that are not closely related to the present invention are omitted.

[0054] It should be emphasized that the term “include / comprises” when used herein refers to the presence of features, elements, steps or components, but does not exclude the presence or addition of one or more other features, elements, steps or components.

[0055] It should also be noted that, unless otherwise specified, the term “connection” herein may refer not only to a direct connection but also to an indirect connection involving an intermediate.

[0056] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the accompanying drawings, the same reference numerals represent the same or similar components, or the same or similar steps.

[0057] It should be emphasized here that the step marks mentioned below are not intended to limit the order of the steps, but it should be understood that the steps can be executed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be executed simultaneously.

[0058] In order to solve the problems of inconsistent document formats, difficult information integration and use, scattered file storage locations, difficult search and access, lack of traceability of content, inability to effectively confirm the accuracy and security of assets, unrestricted operation permissions, easy misoperation, management risks, lack of sharing and reuse mechanism between use case libraries of different departments and teams, much duplication of work and low efficiency in existing public use case library management technical solutions, the present invention provides a public use case library management method based on dynamic permission control, such as Figure 1 As shown, the method includes the following steps S101 to S103:

[0059] Step S101: The user selects the use cases to be collected from the project and initiates a collection request; the department associated with the user is fuzzy matched with the corresponding use case library module. If the match is successful, it means that the user has the collection authority, and the use cases to be collected are written into the corresponding use case library module of the public use case library.

[0060] Step S102: The user selects a use case to be reused from the public use case library and initiates a reuse request; creates a new project use case and inherits the basic information of the use case to be reused.

[0061] Step S103: The user selects the use case to be removed from the public use case library and initiates a removal request; the department associated with the user is fuzzy matched with the corresponding use case library module. If the match is successful, it means that the user has the removal authority, and the use case to be removed is removed from the corresponding use case library module of the public use case library.

[0062] like Figure 2 The figure shows a flowchart of a public use case library management method based on dynamic permission control.

[0063] In some embodiments, before executing the public use case library management method based on dynamic permission control, the departmental organizational structure of the enterprise is obtained in advance, and the management permissions of the public use case library are set for each department. The departmental organizational structure is stored in a MySQL database, and the departmental organizational structure is regularly updated at preset time intervals. Basic data is provided for subsequent user management and permission control.

[0064] Associate users with departmental organizational structures to dynamically obtain users' management permissions in the public use case library through the association relationship. Management permissions include collection permissions, removal permissions, etc., which can be set according to actual conditions.

[0065] In step S101, the user selects the use cases to be collected from the project and initiates a collection request; the department associated with the user is fuzzy matched with the corresponding use case library module. If the match is successful, it means that the user has the collection authority, and the use cases to be collected are written into the corresponding use case library module of the public use case library.

[0066] In some embodiments, the public use case library adopts a tree structure, the root node is the public use case library as a whole, which can be understood as the entrance of the public use case library, may not have actual content, and is used to manage the structure of the entire library; the module node is the use case library module, each module is a node in the tree, and can contain submodules (child nodes). Each module node has some basic information, such as module name, description, parent module, submodule, etc. The front end can display the use case library module tree through a tree control, such as a TreeView component. Each node supports adding submodule operations, renaming operations, deleting module operations, etc.

[0067] In some embodiments, when matching the public use case library management authority, the backend uses Java Spring Boot as a server to provide a RESTful API, where a RESTful API is a Web service interface based on the Representational State Transfer (REST) ​​architectural style, and an API is an Application Programming Interface.

[0068] When the user initiates a collection request (or a removal request in step S103), the backend provides an application programming interface for the frontend to obtain information about all use case library modules in the public use case library. The frontend uses the Vue framework to implement dynamic interaction, thereby obtaining the names of all first-level use case library modules under the interface response result.

[0069] The backend provides another application programming interface for the frontend to obtain the current user information, and the frontend obtains the department name associated with the current user as described in the interface response result.

[0070] Loop through the first-level use case library module name to determine whether it fuzzily matches the department name associated with the current user. If it matches, the current user has management authority over the use case library module and its sub-modules. If it does not match, the current user has no management authority and can only view data.

[0071] In some embodiments, aggregation supports single and batch aggregation.

[0072] In some embodiments, after the collection is completed, the project use case database table is updated, and the fields of the use cases to be collected are set, such as setting case_public=true and public_node_id (pointing to the use case library module to which it is collected).

[0073] In some embodiments, the project use cases marked as public use cases (case_public=true) are queried in the database and displayed in the public use case library. The module for use case display is determined through the associated use case library module (public_node_id) to achieve centralized public use case management.

[0074] In step S102, the user selects the use case to be reused from the public use case library and initiates a reuse request. After the reuse is successful, a new data is created in the project use case database, the id is automatically incremented, the project_id is associated with the newly created project, and the case_public and public_node_id are set to null, and other information of the use case to be reused is directly brought in.

[0075] In step S103, the user selects the use case to be removed from the public use case library and initiates a removal request; the department associated with the user is fuzzy matched with the corresponding use case library module. If the match is successful, it indicates that the user has the removal authority, and the use case to be removed is removed from the corresponding use case library module of the public use case library.

[0076] In some embodiments, removal supports single and batch removal.

[0077] In some embodiments, after the removal is completed, the project use case database table is updated and the fields of the use cases to be aggregated are set, such as setting case_public=false and public_node_id to null.

[0078] In some embodiments, in order to better manage and record the public use case library in the future, a log table is designed to record the user's related behaviors of managing the public use case table, including:

[0079] Determine the management operations that need to be recorded, such as viewing use cases, grouping use cases, reusing use cases, removing use cases, etc.

[0080] Set up a log data structure that contains multiple fields to describe relevant information for each management operation.

[0081] The front end captures the user's management operations through event monitoring (such as click, submit, edit, etc.), and can use AJAX requests or Fetch API to send the monitored data to the back-end server. The back end needs to provide an API interface to receive the data sent by the front end, record the received data in the log and store it in the preset database. A separate log table can be designed to store all management operation records.

[0082] Corresponding to the public use case library management method based on dynamic authority control, the present invention also provides a public use case library management system based on dynamic authority control, the system comprising:

[0083] The organizational structure management module is used to obtain the departmental organizational structure of the enterprise and store it in the MySQL database, set the management permissions of the public use case library for each department, and regularly update the departmental organizational structure at preset time intervals.

[0084] The user management module is used to associate users with department organizational structures so as to dynamically obtain the user's management permissions in the public use case library through the association relationship.

[0085] The public use case library dynamic permission control module is used to fuzzy match the department associated with the user with the corresponding use case library module when the user manages the public use case library. If the match is successful, it indicates that the user has the corresponding management authority.

[0086] The public use case collection module is used to select the use cases to be collected from the project when the user has the collection permission, and write the use cases to be collected into the corresponding use case library module of the public use case library.

[0087] The reuse public use case module is used for users to select the use cases to be reused from the public use case library, create new project use cases, and inherit the basic information of the use cases to be reused.

[0088] The public use case module is removed to select the use case to be removed from the public use case library when the user has the removal permission, and remove the use case to be removed from the corresponding use case library module of the public use case library.

[0089] In order to further improve the public use case library management system based on dynamic authority control, the system may also include:

[0090] The project use case management module is used to manage and display project-related use cases, and supports the aggregation of use cases from projects into a public use case library.

[0091] The public use case management module is used to query and manage project use cases marked as public use cases, and display them in the corresponding use case library module of the public use case library.

[0092] The public use case library operation log management module is used to record and manage the relevant behavior data of users managing the public use case library in the system.

[0093] Corresponding to the above method, the present invention also provides an electronic device, which includes a computer device, the computer device includes a processor and a memory, the memory stores computer instructions, the processor is used to execute the computer instructions stored in the memory, and when the computer instructions are executed by the processor, the electronic device implements the steps of the method described above.

[0094] The embodiment of the present invention also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the aforementioned edge computing server deployment method are implemented. The computer-readable storage medium can be a tangible storage medium, such as a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a floppy disk, a hard disk, a removable storage disk, a CD-ROM, or any other form of storage medium known in the technical field.

[0095] It should be understood by those skilled in the art that the exemplary components, systems and methods described in conjunction with the embodiments disclosed herein can be implemented in hardware, software or a combination of the two. Whether it is performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present invention are programs or code segments used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link via a data signal carried in a carrier.

[0096] It should be clear that the present invention is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present invention is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present invention.

[0097] In the present invention, features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, and / or combined with features of other embodiments or replace features of other embodiments.

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

Claims

1. A public use case library management method based on dynamic authority control, characterized in that: The departmental organizational structure of the enterprise is obtained in advance, the management authority of the public use case library is set for each department, and the user is associated with the departmental organizational structure. The method includes the following steps: The user selects the use cases to be collected from the project and initiates a collection request; the department associated with the user is fuzzy matched with the corresponding use case library module. If the match is successful, it indicates that the user has the collection authority, and the use cases to be collected are written into the corresponding use case library module of the public use case library; The user selects a use case to be reused from the public use case library and initiates a reuse request; creates a new project use case and inherits the basic information of the use case to be reused; The user selects the use case to be removed from the public use case library and initiates a removal request; the department associated with the user is fuzzy matched with the corresponding use case library module. If the match is successful, it indicates that the user has the removal authority, and the use case to be removed is removed from the corresponding use case library module of the public use case library.

2. The public use case library management method based on dynamic authority control according to claim 1 is characterized in that: Pre-acquire the departmental organizational structure of the enterprise and associate the user with the departmental organizational structure, including: The department organization structure is stored in a MySQL database, and the department organization structure is regularly updated according to a preset time interval; The user is associated with the department organizational structure to dynamically obtain the management authority of the user in the public use case library through the association relationship.

3. The public use case library management method based on dynamic authority control according to claim 1 is characterized in that: The method further comprises: The public use case library adopts a tree structure, the root node is the public use case library as a whole, and the nodes are the use case library modules; each node supports adding submodule operations, renaming operations and deleting module operations.

4. The public use case library management method based on dynamic authority control according to claim 3 is characterized in that: Perform fuzzy matching between the department to which the user belongs and the corresponding use case library module. If the match is successful, it indicates that the user has the collection authority, including: When the user initiates a collection request, the backend provides a first application programming interface for the frontend to obtain information about all use case library modules of the public use case library, and the frontend obtains the names of all first-level use case library modules under the interface response result; The backend provides a second application programming interface for the frontend to obtain the current user information, and the frontend obtains the department name associated with the current user in the interface response result; Loop through the first-level use case library module name to determine whether it fuzzily matches the department name associated with the current user. If it matches, the current user has management authority over the use case library module and its sub-modules. If it does not match, the current user has no management authority and can only view data.

5. The public use case library management method based on dynamic authority control according to claim 1 is characterized in that: Writing the use cases to be collected into the use case library module corresponding to the public use case library includes: Collect the use cases to be collected in batches or individually into the corresponding use case library modules of the public use case library; After the collection is completed, the project use case database table is updated and the fields of the use cases to be collected are set.

6. The public use case library management method based on dynamic authority control according to claim 1 is characterized in that: Removing the use case to be removed from the use case library module corresponding to the public use case library includes: Remove the use cases to be removed in batches or individually from the corresponding use case library modules of the public use case library; After the removal is completed, update the project use case database table and set the fields of the use case to be removed.

7. The public use case library management method based on dynamic authority control according to claim 1 is characterized in that: The method further comprises: Determine the management operations that need to be recorded, where the management operations at least include viewing use cases, grouping use cases, reusing use cases, and removing use cases; Setting a log data structure, wherein the data structure includes a plurality of fields to describe relevant information of each management operation; The front end captures the user's management operations through event monitoring, sends the monitored data to the back end, records it in the log, and stores it in the preset database.

8. A public use case library management system based on dynamic authority control, characterized in that: The system comprises: The organizational structure management module is used to obtain the departmental organizational structure of the enterprise and store it in the MySQL database, set the management authority of the public use case library for each department, and regularly update the departmental organizational structure according to the preset time interval; A user management module, used to associate a user with the department organizational structure, so as to dynamically obtain the management authority of the user in the public use case library through the association relationship; The public use case library dynamic authority control module is used to fuzzy match the department associated with the user with the corresponding use case library module when the user manages the public use case library. If the match is successful, it indicates that the user has the corresponding management authority; A module for collecting public use cases, which is used to select use cases to be collected from a project when a user has collection authority, and write the use cases to be collected into a use case library module corresponding to the public use case library; The reuse public use case module is used for users to select a use case to be reused from the public use case library, create a new project use case, and inherit the basic information of the use case to be reused; The public use case removal module is used to select a use case to be removed from the public use case library when the user has the removal authority, and remove the use case to be removed from the corresponding use case library module of the public use case library.

9. The public use case library management system based on dynamic authority control according to claim 8, characterized in that: The system further comprises: A project use case management module, used to manage and display use cases related to a project, and supports grouping use cases from projects into the public use case library; A public use case management module, used to query and manage project use cases marked as public use cases, and display them in a use case library module corresponding to the public use case library; The public use case library operation log management module is used to record and manage the relevant behavior data of users managing the public use case library in the system.

10. A computer-readable storage medium having a computer program / instruction stored thereon, characterized in that: When the computer program / instructions are executed by a processor, the steps of the method as claimed in any one of claims 1 to 7 are implemented.

Images