CN119903031A - A public use case library management method and system based on dynamic authority control - Google Patents

Abstract

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 inherits the basic information of the reused use case; 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, and realizes accurate classification and efficient maintenance of public use cases based on the authority control mechanism.

Description

Method and system for managing common instance library based on dynamic authority control

Technical Field

The invention relates to the technical field of knowledge management systems, in particular to a method and a system for managing a common instance library based on dynamic authority control.

Background

The common case library is a system for storing, managing and sharing information of test cases, documents, templates and the like. In general, the public use case library is an important resource library established by enterprises or development teams for improving the working efficiency and ensuring the quality assurance. In conventional development and testing processes, a common case library is often used to store standardized test cases, functional verification cases, performance test templates, etc., for reuse by different projects and teams.

Currently, most businesses and teams still employ local document management to build and maintain a common instance library. This means that all common use cases are stored in a local file system, typically a shared network driver or team collaboration platform, and that the files exist in a common document format (e.g., word, excel, TXT, etc.) and there is no specialized management system to control them uniformly.

In this mode, the public use case library management is generally lack of rights restrictions and open to the whole person. All team members and project managers can edit, delete or add new use cases at any time. This approach, while simple, lacks an efficient management and control mechanism, which tends to result in the following problems:

the document formats are not uniform, and the information is difficult to integrate and use;

file storage locations are scattered, and searching and accessing become difficult;

the content lacks traceability, and the accuracy and the safety of the asset cannot be effectively confirmed;

The operation authority is not limited, misoperation is easy to occur, and management risk is increased;

The use case libraries among different departments and teams lack sharing and multiplexing mechanisms, repeated work is increased, and efficiency is low.

Disclosure of Invention

In view of this, embodiments of the present invention provide a method and a system for managing a community library based on dynamic rights control, so as to eliminate or improve one or more drawbacks existing in the prior art.

On one hand, the invention provides a public use case library management method based on dynamic authority control, which acquires the department organization architecture of enterprises in advance, setting management authority of a common instance library for each department, and associating a user with the department organization architecture, wherein the method comprises the following steps:

The user selects the case to be collected from the project and initiates a collection request, the department associated with the user is subjected to fuzzy matching with the corresponding case library module, if the matching is successful, the user is indicated to have collection authority, and the case to be collected is written into the case library module corresponding to the common case library;

the user selects the case to be multiplexed from the public case library and initiates a multiplexing request; creating a new project use case, and inheriting the basic information of the use case needing multiplexing;

And performing fuzzy matching on departments associated with the users and corresponding application case library modules, if the matching is successful, indicating that the users have the removal authority, and removing the application case to be removed from the application case library modules corresponding to the public application case library.

In some embodiments of the present invention, pre-acquiring a department organization architecture of an enterprise and associating a user with the department organization architecture includes:

storing the department organization architecture in a MySQL database, and periodically updating the department organization architecture according to a preset time interval;

And associating the user with the department organization architecture to dynamically acquire the management authority of the user in the public use case library through association relation.

In some embodiments of the invention, the method further comprises:

the public use case library adopts a tree structure, a root node is the whole public use case library, a node is the use case library module, and each node supports sub-module adding operation, renaming operation and module deleting operation.

In some embodiments of the present invention, fuzzy matching is performed between the department to which the user belongs and the corresponding application library module, if matching is successful, the step of indicating that the user has the collection right includes:

when a user initiates a collection request, the rear end provides a first application programming interface for the front end to acquire information of all use case library modules of the public use case library, and the front end acquires names of all first-level use case library modules of the interface response result;

The back end provides a second application programming interface for the front end to acquire the current user information, and the front end acquires the department name associated with the current user under the interface response result;

and circularly traversing the names of the first-level use case library modules, judging whether the names of departments associated with the current user are subjected to fuzzy matching, if so, enabling the current user to have the management authority of the use case library modules and the sub-modules thereof, and if not, enabling the current user to have no management authority and only be capable of checking data.

In some embodiments of the present invention, writing the to-be-collected use cases into the use case library module corresponding to the common case library includes:

the use cases to be collected are collected in batch or single use case library modules corresponding to the public use case library in sequence;

After the collection is completed, the project use case database table is updated, and the field of the use case needing collection is set.

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

Removing the use case batch to be removed or the single use case batch to be removed from the corresponding use case library module of the public use case library in sequence;

After the removal is completed, the project use case database table is updated, and the field of the use case to be removed is set.

In some embodiments of the invention, the method further comprises:

determining management operation to be recorded, wherein the management operation at least comprises a checking use case, a collecting use case, a multiplexing use case and a removing use case;

setting a log data structure, wherein the data structure comprises a plurality of fields for describing relevant information of each management operation;

The front end captures the management operation of the user through event monitoring, sends the monitored data to the back end, records the data in a log and stores the log in a preset database.

On the other hand, the invention also provides a public use case library management system based on dynamic authority control, which comprises the following steps:

The system comprises an organization architecture management module, a management module and a management module, wherein the organization architecture management module is used for acquiring department organization architectures of enterprises and storing the department organization architectures in a MySQL database, setting management rights of a common instance library for each department, and periodically updating the department organization architectures according to preset time intervals;

the user management module is used for associating a user with the department organization architecture so as to dynamically acquire the management authority of the user in the public use case library through association relation;

The public case library dynamic authority control module is used for carrying out fuzzy matching on departments associated with the user and the corresponding application case library module when the user manages the public case library, and if the matching is successful, the user is indicated to have corresponding management authority;

the system comprises a common case collecting module, a case library module and a user management module, wherein the common case collecting module is used for selecting cases to be collected from projects when a user has a collecting right, and writing the cases to be collected into a corresponding case library of the common case library;

The multiplexing common case module is used for users to select cases to be multiplexed from the common case library, create new project cases and inherit the basic information of the cases to be multiplexed;

And the common case removing module is used for selecting a case to be removed from the common case library when the user has the removing right, and removing the case to be removed from the case library module corresponding to the common case library.

In some embodiments of the invention, the system further comprises:

The project use case management module is used for managing and displaying use cases related to the project and supporting the collection of the use cases from the project to the public use case library;

The public use case management module is used for inquiring and managing the project use cases marked as public use cases and displaying the project use cases in the use case library module corresponding to the public use case library;

and the public use case library operation log management module is used for recording and managing related behavior data of the public use case library managed by a user in the system.

In another aspect, the invention also provides a computer-readable storage medium having stored thereon a computer program/instruction which, when executed by a processor, implements the steps of the method as set forth in any one of the preceding claims.

The invention provides a public example library management method and system based on dynamic authority control, comprising the steps of obtaining a department organization architecture of an enterprise, setting management authority of a public example library for each department, associating a user with the department organization architecture, selecting a to-be-collected example from a project, judging whether the to-be-collected example has the to-be-collected authority according to fuzzy matching of the department associated with the user and an example library module, if so, writing the to-be-collected example into the example library module corresponding to the public example library, selecting a multiplexing example from the public example library by the user, creating a new project example, setting a field, directly inheriting basic information of the to-be-used example, selecting the to-be-removed example from the public example library by the user, and judging whether the to-be-collected example is provided or not according to fuzzy matching of the department associated with the user and the example library module, and if so, removing the to-be-removed example from the example library module corresponding to the public example library. The invention constructs a centralized common case library, manages according to department dimensions, dynamically acquires corresponding management authorities according to departments associated with users based on an authority control mechanism, and effectively realizes accurate classification and efficient maintenance of common cases. And allowing the user to access and operate the use case library according to the authority of the user, and ensuring the safety of the information. Meanwhile, through the intelligent classification function, a user can easily find out required use cases, and the searching and application efficiency is improved. In addition, the management and history tracking of the public use cases are supported, and the accuracy and consistency of the use cases in the whole life cycle are ensured. The comprehensive management mode not only improves the working efficiency, but also reduces the risk caused by human errors, and provides a more reliable basis for team cooperation.

Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and drawings.

It will be appreciated by those skilled in the art that the objects and advantages that can be achieved with the present invention are not limited to the above-described specific ones, and that the above and other objects that can be achieved with the present invention will be more clearly understood from the following detailed description.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate and together with the description serve to explain the application. In the drawings:

FIG. 1 is a schematic diagram illustrating steps of a method for managing a common use case library based on dynamic rights control according to an embodiment of the present invention.

Fig. 2 is a flow chart of a method for managing a public use case library based on dynamic rights control according to an embodiment of the invention.

Detailed Description

The present invention will be described in further detail with reference to the following embodiments and the accompanying drawings, in order to make the objects, technical solutions and advantages of the present invention more apparent. The exemplary embodiments of the present invention and the descriptions thereof are used herein to explain the present invention, but are not intended to limit the invention.

It should be noted here that, in order to avoid obscuring the present invention due to unnecessary details, only structures and/or processing steps closely related to the solution according to the present invention are shown in the drawings, while other details not greatly related to the present invention are omitted.

It should be emphasized that the term "comprises/comprising" when used herein is taken to specify the presence of stated features, elements, steps or components, but does not preclude the presence or addition of one or more other features, elements, steps or components.

It is also noted herein that the term "coupled" may refer to not only a direct connection, but also an indirect connection in which an intermediate is present, unless otherwise specified.

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

It should be emphasized that the references to steps below are not intended to limit the order of the steps, but rather should be understood to mean that the steps may be performed in a different order than in the embodiments, or that several steps may be performed simultaneously.

In order to solve the problems that the document formats are not uniform, information is difficult to integrate and use, file storage positions are dispersed, searching access is difficult, content lacks traceability, accuracy and safety of assets cannot be effectively confirmed, operation authorities are not limited, misoperation is easy to occur, management risks exist, use case libraries among different departments and teams lack of sharing and multiplexing mechanisms, repeated work is more, and efficiency is low in the conventional common use case library management technical scheme, the invention provides a common use case library management method based on dynamic authority control, and as shown in fig. 1, the method comprises the following steps S101-S103:

Step S101, a user selects the cases to be collected from the project and initiates a collection request, a department associated with the user and the corresponding case library module are subjected to fuzzy matching, if the matching is successful, the user is indicated to have collection rights, and the cases to be collected are written into the corresponding case library module of the public case library.

Step S102, the user selects the case to be multiplexed from the public case library and initiates a multiplexing request, creates a new project case and inherits the basic information of the case to be multiplexed.

Step 103, the user selects the case to be removed from the public case library and initiates a removal request, the department associated with the user is subjected to fuzzy matching with the corresponding case library module, if the matching is successful, the user is indicated to have the removal authority, and the case to be removed is removed from the corresponding case library module of the public case library.

Fig. 2 is a schematic flow chart of a method for managing a public use case library based on dynamic rights control.

In some embodiments, before executing the public use case library management method based on dynamic authority control, a department organization architecture of an enterprise is obtained in advance, and management authority of the public use case library is set for each department. The department organization architecture is stored in a MySQL database, and the department organization architecture is updated periodically according to preset time intervals. Providing basic data for subsequent user management and rights control.

And associating the user with the department organization architecture to dynamically acquire the management authority of the user in the public use case library through the association relation. The management authority comprises a collection authority, a removal authority and the like, and can be set according to actual conditions.

In step S101, the user selects the case to be collected from the project and initiates a collection request, the department associated with the user is subjected to fuzzy matching with the corresponding case library module, if the matching is successful, the user is indicated to have collection rights, and the case to be collected is written into the corresponding case library module of the public case library.

In some embodiments, the common case library adopts a tree structure, the root node is the whole common case library, and can be understood as an entrance of the common case library, and there may be no actual content for managing the structure of the whole library, the module nodes are case library modules, each module is a node in the tree, and a sub-module (sub-node) can be included. Each module node has some basic information, such as a module name, description, parent module, child module, etc. The front end may expose a library module tree through a tree control, such as a TreeView component. Each node supports add sub-module operations, rename operations, delete module operations, etc.

In some embodiments, when matching the common instance library management rights, the backend uses a Java Spring Boot as a server to provide a RESTful API. The RESTful API is a Web service interface based on a Representational STATE TRANSFER (REST) architecture style, and the API is Application Programming Interface and an application programming interface.

After the user initiates the collection request (or the removal request in step S103), the back end provides an application programming interface for the front end to acquire the information of all the use case library modules of the common case library, and the front end uses the Vue framework to realize dynamic interaction, so as to acquire the names of all the first-level use case library modules of the interface response result.

The back end provides another application programming interface for the front end to acquire the current user information, and the front end acquires the department name associated with the current user under the response result of the interface.

And circularly traversing the names of the first-level use case library modules, judging whether the names of departments associated with the current user are subjected to fuzzy matching, if so, enabling the current user to have the management authority of the use case library modules and the sub-modules thereof, and if not, enabling the current user to have no management authority and only be capable of checking data.

In some embodiments, the collection supports single and batch collections.

In some embodiments, after the completion of the aggregation, the project use case database table is updated, and the fields of the use case to be aggregated are set, such as setting case_public=true and public_node_id (pointing to the use case library module to which the aggregation is to be performed).

In some embodiments, the project use cases marked as common use cases (case_public=true) in the database are queried and displayed in the common use case library, and the use case display module is determined through the associated use case library module (public_node_id), so that centralized common use case management is realized.

In step S102, the user selects a case to be multiplexed from the common case library, and initiates a multiplexing request. After multiplexing is successful, a new piece of data is created in the project use case database, id is self-increased, project_id is related to the newly created project, case_public and public_node_id are set as null, and other information of the use case to be multiplexed is directly brought in.

In step S103, the user selects the case to be removed from the public case library and initiates a removal request, the department associated with the user is subjected to fuzzy matching with the corresponding case library module, if the matching is successful, the user is indicated to have the removal authority, and the case to be removed is removed from the corresponding case library module of the public case library.

In some embodiments, removal supports single and bulk removal.

In some embodiments, after removal is complete, the project use case database table is updated, and the fields of the use case to be collected are set, for example, case_public=false and public_node_id are set to null.

In some embodiments, for subsequent better management and record tracking of the common use case repository, a log table is designed for recording the relevant behavior of the user to manage the common use case table, including:

Management operations requiring recording, such as viewing use cases, collecting use cases, multiplexing use cases, removing use cases, and the like, are determined.

A log data structure is provided that contains a plurality of fields to describe information about each management operation.

The front end captures the management operation of the user through event monitoring (such as clicking, submitting, editing and the like), the monitored data can be sent to the back end server in the mode of AJAX request or Fetch API and the like, the back end needs to provide an API interface to receive the data sent by the front end, the received data is recorded in a log and stored in a preset database, and a single log table can be designed for storing all management operation records.

The invention also provides a public use case library management system based on dynamic authority control, which comprises:

the organization architecture management module is used for acquiring department organization architectures of enterprises and storing the department organization architectures in the MySQL database, setting management authorities of a common instance library for each department, and periodically updating the department organization architectures according to preset time intervals.

And the user management module is used for associating the user with the department organization architecture so as to dynamically acquire the management authority of the user in the public use case library through the association relation.

And the public example library dynamic authority control module is used for carrying out fuzzy matching on departments associated with the user and the corresponding application example library module when the user manages the public example library, and if the matching is successful, the user is indicated to have corresponding management authority.

And the common case collecting module is used for selecting the cases to be collected from the project when the user has the collection right, and writing the cases to be collected into the corresponding case library module of the common case library.

And the multiplexing common case module is used for users to select cases to be multiplexed from the common case library, create new project cases and inherit the basic information of the cases to be multiplexed.

And the common case removing module is used for selecting the case to be removed from the common case library when the user has the removing right, and removing the case to be removed from the case library module corresponding to the common case library.

To further refine the public use case library management system based on dynamic rights control, the system may further include:

And the project use case management module is used for managing and displaying the use cases related to the project and supporting the collection of the use cases from the project to the public use case library.

And the public use case management module is used for inquiring and managing the project use cases marked as public use cases and displaying the project use cases in the use case library module corresponding to the public use case library.

And the common instance library operation log management module is used for recording and managing related behavior data of the user management common instance library in the system.

Correspondingly, the invention also provides an electronic device comprising a computer device, the computer device comprising a processor and a memory, the memory having stored therein computer instructions for executing the computer instructions stored in the memory, the electronic device implementing the steps of the method as described above when the computer instructions are executed by the processor.

The embodiments of the present invention also provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the edge computing server deployment method described above. The computer readable storage medium may be a tangible storage medium such as Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, floppy disks, hard disk, a removable memory disk, a CD-ROM, or any other form of storage medium known in the art.

Those of ordinary skill in the art will appreciate that the various illustrative components, systems, and methods described in connection with the embodiments disclosed herein can be implemented as hardware, software, or a combination of both. The particular implementation is hardware or software dependent on the specific application of the solution and the design constraints. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, a plug-in, a function card, or the like. When implemented in software, the elements of the invention are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine readable medium or transmitted over transmission media or communication links by a data signal carried in a carrier wave.

It should be understood that the invention is not limited to the particular arrangements and instrumentality described above and shown in the drawings. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. The method processes of the present invention are not limited to the specific steps described and shown, but various changes, modifications and additions, or the order between steps may be made by those skilled in the art after appreciating the spirit of the present invention.

In this disclosure, features that are described and/or illustrated with respect to one embodiment may be used in the same way or in a similar way in one or more other embodiments and/or in combination with or instead of the features of the other embodiments.

The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, and various modifications and variations can be made to the embodiments of the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. The utility model provides a public use case library management method based on dynamic authority control, which is characterized in that a department organization architecture of an enterprise is obtained in advance, the management authority of a public use case library is set for each department, and a user is associated with the department organization architecture, and the method comprises the following steps:

The user selects the case to be collected from the project and initiates a collection request, the department associated with the user is subjected to fuzzy matching with the corresponding case library module, if the matching is successful, the user is indicated to have collection authority, and the case to be collected is written into the case library module corresponding to the common case library;

the user selects the case to be multiplexed from the public case library and initiates a multiplexing request; creating a new project use case, and inheriting the basic information of the use case needing multiplexing;

And performing fuzzy matching on departments associated with the users and corresponding application case library modules, if the matching is successful, indicating that the users have the removal authority, and removing the application case to be removed from the application case library modules corresponding to the public application case library.

2. The method for managing a public use case library based on dynamic rights control according to claim 1, wherein acquiring a department organization architecture of an enterprise in advance and associating a user with the department organization architecture comprises:

storing the department organization architecture in a MySQL database, and periodically updating the department organization architecture according to a preset time interval;

And associating the user with the department organization architecture to dynamically acquire the management authority of the user in the public use case library through association relation.

3. The method for managing a public use case library based on dynamic rights control according to claim 1, wherein the method further comprises:

the public use case library adopts a tree structure, a root node is the whole public use case library, a node is the use case library module, and each node supports sub-module adding operation, renaming operation and module deleting operation.

4. The public use case library management method based on dynamic authority control according to claim 3, wherein the fuzzy matching is performed between the department to which the user belongs and the corresponding use case library module, if the matching is successful, the user is indicated to have the aggregation authority, comprising:

when a user initiates a collection request, the rear end provides a first application programming interface for the front end to acquire information of all use case library modules of the public use case library, and the front end acquires names of all first-level use case library modules of the interface response result;

The back end provides a second application programming interface for the front end to acquire the current user information, and the front end acquires the department name associated with the current user under the interface response result;

and circularly traversing the names of the first-level use case library modules, judging whether the names of departments associated with the current user are subjected to fuzzy matching, if so, enabling the current user to have the management authority of the use case library modules and the sub-modules thereof, and if not, enabling the current user to have no management authority and only be capable of checking data.

5. The method for managing a public use case library based on dynamic rights control according to claim 1, wherein writing the to-be-collected use case into the corresponding use case library module of the public use case library comprises:

the use cases to be collected are collected in batch or single use case library modules corresponding to the public use case library in sequence;

After the collection is completed, the project use case database table is updated, and the field of the use case needing collection is set.

6. The method for managing a public use case library based on dynamic rights control according to claim 1, wherein removing the use case to be removed from the corresponding use case library module of the public use case library comprises:

Removing the use case batch to be removed or the single use case batch to be removed from the corresponding use case library module of the public use case library in sequence;

After the removal is completed, the project use case database table is updated, and the field of the use case to be removed is set.

7. The method for managing a public use case library based on dynamic rights control according to claim 1, wherein the method further comprises:

determining management operation to be recorded, wherein the management operation at least comprises a checking use case, a collecting use case, a multiplexing use case and a removing use case;

setting a log data structure, wherein the data structure comprises a plurality of fields for describing relevant information of each management operation;

The front end captures the management operation of the user through event monitoring, sends the monitored data to the back end, records the data in a log and stores the log in a preset database.

8. A public use case library management system based on dynamic rights control, the system comprising:

The system comprises an organization architecture management module, a management module and a management module, wherein the organization architecture management module is used for acquiring department organization architectures of enterprises and storing the department organization architectures in a MySQL database, setting management rights of a common instance library for each department, and periodically updating the department organization architectures according to preset time intervals;

the user management module is used for associating a user with the department organization architecture so as to dynamically acquire the management authority of the user in the public use case library through association relation;

The public case library dynamic authority control module is used for carrying out fuzzy matching on departments associated with the user and the corresponding application case library module when the user manages the public case library, and if the matching is successful, the user is indicated to have corresponding management authority;

the system comprises a common case collecting module, a case library module and a user management module, wherein the common case collecting module is used for selecting cases to be collected from projects when a user has a collecting right, and writing the cases to be collected into a corresponding case library of the common case library;

The multiplexing common case module is used for users to select cases to be multiplexed from the common case library, create new project cases and inherit the basic information of the cases to be multiplexed;

And the common case removing module is used for selecting a case to be removed from the common case library when the user has the removing right, and removing the case to be removed from the case library module corresponding to the common case library.

9. The dynamic rights control-based public use case library management system of claim 8, further comprising:

The project use case management module is used for managing and displaying use cases related to the project and supporting the collection of the use cases from the project to the public use case library;

The public use case management module is used for inquiring and managing the project use cases marked as public use cases and displaying the project use cases in the use case library module corresponding to the public use case library;

and the public use case library operation log management module is used for recording and managing related behavior data of the public use case library managed by a user in the system.

10. A computer readable storage medium having stored thereon a computer program/instruction which when executed by a processor performs the steps of the method according to any of claims 1 to 7.