System role function permission configuration method and device, electronic equipment and storage medium

Abstract

This disclosure provides a method, apparatus, electronic device, and storage medium for configuring system role function permissions, relating to the field of software system technology. The method includes: obtaining a system use case diagram of the system to be configured, the system use case diagram containing the following elements: actors, use cases, relationships between actors, relationships between actors and use cases, and relationships between use cases; generating relationships between system roles and a system function list within the system to be configured based on the system use case diagram, where system roles are determined based on actors in the system use case diagram, and the system function list contains one or more system functions determined based on use cases in the system use case diagram; and configuring corresponding function permissions for the system roles within the system to be configured based on the relationships between system roles and the system function list. This disclosure can analyze the function permissions corresponding to each role within the system based on the system use case diagram, thereby quickly generating and automatically updating the system's role function permissions.

Description

Technical Field

[0001] This disclosure relates to the field of software system technology, and in particular to a method, apparatus, electronic device, and storage medium for configuring system role, function, and permission. Background Technology

[0002] As various systems become cloud-based services, their functions and microservices are becoming increasingly complex, leading to higher demands for granular management of system roles. How to simplify the configuration of system role permissions while ensuring the consistency, integrity, and authoritativeness of system role permissions is a pressing issue that needs to be addressed.

[0003] The system role and permission configuration schemes provided in related technologies mainly rely on manual operation by system maintenance personnel. The system maintenance personnel manually design the system role and permission management scheme according to the application requirements and manually enter it into the system. This has problems such as large workload, easy error and incomplete role and permission relationship information.

[0004] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] This disclosure provides a method, apparatus, electronic device, and storage medium for configuring system role and function permissions, which at least to some extent overcomes the technical problems of large workload, error susceptibility, and information incompleteness associated with manually configuring system role permissions in related technologies.

[0006] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0007] According to one aspect of this disclosure, a method for configuring system role function permissions is provided, comprising: obtaining a system use case diagram of a system to be configured, the system use case diagram including the following elements: actors, use cases, relationships between actors, relationships between actors and use cases, and relationships between use cases; generating a relationship between system roles and a system function list within the system to be configured based on the system use case diagram, wherein the system roles are determined based on the actors in the system use case diagram, and the system function list includes one or more system functions determined based on the use cases in the system use case diagram; and configuring corresponding function permissions for the system roles within the system to be configured based on the relationship between the system roles and the system function list within the system to be configured.

[0008] In some embodiments, generating the relationship between system roles and system function lists within the system to be configured, based on the system use case diagram, includes: parsing the elements contained in the system use case diagram to obtain element parsing results; selecting participants contained in the system use case diagram from the element parsing results to determine system roles within the system to be configured, and generating relationships between system roles within the system to be configured based on the relationships between participants in the system use case diagram; selecting use cases contained in the system use case diagram from the element parsing results to determine system functions within the system to be configured, and generating relationships between system functions within the system to be configured based on the relationships between use cases in the system use case diagram; and generating relationships between system roles and system function lists within the system to be configured based on the relationships between system roles, the relationships between system functions, and the relationships between participants and use cases in the system use case diagram.

[0009] In some embodiments, configuring corresponding functional permissions for system roles in the system to be configured based on the relationship between system roles and system function lists within the system to be configured includes: generating a system role permission information table for the system to be configured based on the relationship between system roles and system function lists within the system to be configured, wherein the system role permission information table includes: the relationship between system roles and system function lists within the system to be configured; and configuring corresponding functional permissions for system roles in the system to be configured based on the system role permission information table for the system to be configured.

[0010] In some embodiments, the relationships between actors in the system use case diagram include: generalization relationships between actors; the relationships between use cases in the system use case diagram include: generalization relationships between use cases, inclusion relationships between use cases, and extension relationships between use cases; the relationships between actors and use cases in the system use case diagram include: association relationships between actors and use cases.

[0011] According to another aspect of this disclosure, a system role function permission configuration device is also provided, comprising: a system use case diagram acquisition module, used to acquire a system use case diagram of a system to be configured, the system use case diagram including the following elements: actors, use cases, relationships between actors, relationships between actors and use cases, and relationships between use cases; a system role function relationship determination module, used to generate relationships between system roles and a system function list within the system to be configured based on the system use case diagram, wherein the system roles are determined based on the actors in the system use case diagram, and the system function list includes one or more system functions determined based on the use cases in the system use case diagram; and a permission configuration module, used to configure corresponding function permissions for system roles within the system to be configured based on the relationships between system roles and the system function list within the system to be configured.

[0012] In some embodiments, the system role-function relationship determination module includes: a use case diagram parsing module, used to parse the elements contained in the system use case diagram to obtain element parsing results; a role-relationship determination module, used to filter out the participants contained in the system use case diagram from the element parsing results to determine the system roles in the system to be configured, and generate the relationships between the system roles in the system to be configured based on the relationships between the participants in the system use case diagram; a function-relationship determination module, used to filter out the use cases contained in the system use case diagram from the element parsing results to determine the system functions in the system to be configured, and generate the relationships between the system functions in the system to be configured based on the relationships between the use cases in the system use case diagram; and a role-function relationship determination module, used to generate the relationship between the system roles and the system function list in the system to be configured based on the relationships between the system roles in the system to be configured, the relationships between the system functions, and the relationships between the participants and use cases in the system use case diagram.

[0013] In some embodiments, the permission configuration module is further configured to: generate a system role permission information table for the system to be configured based on the relationship between system roles and system function lists within the system to be configured; and configure corresponding function permissions for system roles within the system to be configured based on the system role permission information table, wherein the system role permission information table includes the relationship between system roles and system function lists within the system to be configured.

[0014] In some embodiments, the relationships between actors in the system use case diagram include: generalization relationships between actors; the relationships between use cases in the system use case diagram include: generalization relationships between use cases, inclusion relationships between use cases, and extension relationships between use cases; the relationships between actors and use cases in the system use case diagram include: association relationships between actors and use cases.

[0015] According to another aspect of this disclosure, an electronic device is also provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the system role function permission configuration method described in any of the preceding claims.

[0016] According to another aspect of this disclosure, a computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a processor, implements the system role function permission configuration method described in any one of the preceding claims.

[0017] According to another aspect of this disclosure, a computer program product is also provided, including a computer program that, when executed by a processor, implements a system role function permission configuration method for any of the above.

[0018] The system role function permission configuration method, apparatus, electronic device and storage medium provided in the embodiments of this disclosure obtain the system use case diagram of the system to be configured, and generate the relationship between system roles and system function list in the system to be configured according to the participants, use cases, relationships between participants, relationships between participants and use cases and relationships between use cases contained in the system use case diagram. Then, according to the relationship between system roles and system function list in the system to be configured, the corresponding function permissions are configured for the system roles in the system to be configured.

[0019] Through the embodiments of this disclosure, the functional permissions corresponding to each role in the system can be analyzed based on the system use case diagram, thereby quickly generating and automatically updating the role functional permissions of the system.

[0020] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0021] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0022] Figure 1 This diagram illustrates an application system architecture according to an embodiment of the present disclosure.

[0023] Figure 2 This diagram illustrates a flowchart of a system role function permission configuration method according to an embodiment of the present disclosure;

[0024] Figure 3 This invention discloses a flowchart illustrating a method for generating the relationship between system roles and a system function list based on a system use case diagram, according to an embodiment of the present disclosure.

[0025] Figure 4 This diagram illustrates the relationship between an actor and a use case in an embodiment of this disclosure.

[0026] Figure 5 This diagram illustrates a relationship between participants in an embodiment of the present disclosure.

[0027] Figure 6 This diagram illustrates the relationship between one use case in an embodiment of the present disclosure.

[0028] Figure 7 This diagram illustrates a system role function permission configuration device according to an embodiment of the present disclosure;

[0029] Figure 8 This diagram illustrates a structural block diagram of an electronic device according to an embodiment of the present disclosure.

[0030] Figure 9 A schematic diagram of a computer-readable storage medium according to an embodiment of the present disclosure is shown. Detailed Implementation

[0031] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0032] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0033] The specific implementation methods of the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0034] Figure 1 A schematic diagram of an exemplary application system architecture to which the methods of the embodiments of this disclosure can be applied is shown. For example... Figure 1 As shown, the system architecture may include terminal device 101, network 102 and server 103.

[0035] Network 102 is a medium used to provide a communication link between terminal device 101 and server 103, and can be a wired network or a wireless network.

[0036] Optionally, the aforementioned wireless or wired networks use standard communication technologies and / or protocols. The network is typically the Internet, but can also be any network, including but not limited to Local Area Networks (LANs), Metropolitan Area Networks (MANs), Wide Area Networks (WANs), mobile, wired or wireless networks, private networks, or any combination of virtual private networks. In some embodiments, technologies and / or formats including Hyper Text Markup Language (HTML), Extensible Markup Language (XML), etc., are used to represent data exchanged over the network. Furthermore, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Networks (VPNs), and Internet Protocol Security (IPSec) can be used to encrypt all or some links. In other embodiments, custom and / or dedicated data communication technologies can be used to replace or supplement the aforementioned data communication technologies.

[0037] Terminal device 101 can be various electronic devices, including but not limited to smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, wearable devices, augmented reality devices, virtual reality devices, etc.

[0038] Optionally, the client of the application installed on different terminal devices 101 may be the same, or the client of the same type of application based on different operating systems. Depending on the terminal platform, the specific form of the application client may also be different; for example, the application client may be a mobile client, a PC client, etc.

[0039] Server 103 can be a server that provides various services, such as a backend management server that supports the device operated by the user using terminal device 101. The backend management server can analyze and process received requests and other data, and feed the processing results back to the terminal device.

[0040] Optionally, the server can be a standalone physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0041] Those skilled in the art will know that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative; any number of terminal devices, networks, and servers can be included depending on actual needs. This disclosure does not limit the scope of the embodiments.

[0042] Under the above system architecture, this disclosure provides a system role function permission configuration method, which can be executed by any electronic device with computing power.

[0043] In some embodiments, the system role function permission configuration method provided in this disclosure can be executed by the terminal device of the above-described system architecture; in other embodiments, the system role function permission configuration method provided in this disclosure can be executed by the server in the above-described system architecture; in still other embodiments, the system role function permission configuration method provided in this disclosure can be implemented by the terminal device and the server in the above-described system architecture through interaction.

[0044] Figure 2 This diagram illustrates a flowchart of a system role function permission configuration method according to an embodiment of the present disclosure, such as... Figure 2 As shown, the system role function permission configuration method provided in this embodiment may include the following steps:

[0045] S202, Obtain the system use case diagram of the system to be configured. The system use case diagram contains the following elements: actors, use cases, relationships between actors, relationships between actors and use cases, and relationships between use cases.

[0046] It should be noted that the system to be configured in this embodiment can be any type of software system, including client application systems and web application systems. A system use case diagram is a visual model diagram describing system functions from the user's perspective. This visual model diagram includes: actors, use cases, and the relationships between them.

[0047] An actor is an entity outside the system that participates in the execution of a use case in some way. Actors trigger the execution of system functions by inputting or requesting certain events from the system functions. Actors are represented by the role they play when participating in a use case. In UML (Unified Modeling Language) documentation, actors are represented by a human-shaped icon with their name written below. Each actor can participate in one or more use cases. It interacts with the use cases by exchanging information, and the actor's internal implementation is independent of the use cases; it can be described by a set of attributes that define its state. Actors can be real users, other systems, or even runnable processes (e.g., time). Time becomes an actor when an event in the system is triggered after a certain amount of time.

[0048] A use case is a description of how a system function responds to external requests; each use case corresponds to a functional unit within the system. In UML documentation, a use case is defined as the definition and description of a coherent functional unit of a system or subsystem without revealing the internal structure of the system or subsystem.

[0049] S204. Based on the system use case diagram, generate the relationship between the system roles and the system function list within the system to be configured. The system roles are determined based on the actors in the system use case diagram, and the system function list contains one or more system functions determined based on the use cases in the system use case diagram.

[0050] It should be noted that, since each use case in the system use case diagram corresponds to a system function, and each actor in the system use case diagram is an entity that triggers the execution of the system function, and the system use case diagram contains actors, use cases, and the relationships between them, the relationship between system roles and the list of system functions within the configuration system can be generated based on the system use case diagram of the system to be configured. The system roles in this embodiment of the disclosure can be, but are not limited to, user roles.

[0051] S206. Based on the relationship between system roles and system function lists within the system to be configured, configure the corresponding function permissions for the system roles within the system to be configured.

[0052] It should be noted that after determining the system functions associated with each system role, a list of system functions that each system role is allowed to operate can be determined based on the relationship between each system role and the list of system functions. This list of system functions contains one or more system functions. Then, based on the list of system functions that each system role is allowed to operate, corresponding function permissions can be configured for each system role.

[0053] In some embodiments, the above-mentioned S206 can be implemented through the following steps: generating a system role permission information table for the system to be configured based on the relationship between system roles and system function lists within the system to be configured, wherein the system role permission information table includes the relationship between system roles and system function lists within the system to be configured; configuring corresponding function permissions for system roles within the system to be configured based on the system role permission information table for the system to be configured.

[0054] As can be seen from the above, the system role function permission configuration method provided in the embodiments of this disclosure, after obtaining the system use case diagram of the system to be configured, generates the relationship between the system roles and the system function list in the system to be configured based on the participants, use cases, the relationship between participants, the relationship between participants and use cases, and the relationship between use cases contained in the system use case diagram, and then configures the corresponding function permissions for the system roles in the system to be configured based on the relationship between the system roles and the system function list in the system to be configured.

[0055] The system role function permission configuration method provided in this embodiment can analyze the function permissions corresponding to each role in the system based on the system use case diagram, thereby quickly generating and automatically updating the role functions of the system.

[0056] The system role function permission configuration method provided in the embodiments of this disclosure requires pre-constructing a system use case diagram of the system to be configured. This system use case diagram must include at least the following elements: actors, use cases, relationships between actors, relationships between actors and use cases, and relationships between use cases. In some embodiments, the relationships between actors are generalization relationships; the relationships between actors and use cases are association relationships; and the relationships between use cases include, but are not limited to, inclusion relationships, extension relationships, and generalization relationships. The inclusion relationships, extension relationships, and generalization relationships between use cases are explained below:

[0057] 1) Inclusion Relationship: This relationship separates the common steps of several use cases into a single included use case. The included use case is called the provider use case, and the including use case is called the client use case. The provider use case provides functionality to the client. The inclusion relationship between use cases allows the behavior of the provider use case to be included in the events of the client use case. Inclusion allows the functionality of one use case to be used by another use case. For example, if two or more use cases have a large amount of consistent functionality, this functionality can be decomposed into another use case. Other use cases can establish inclusion relationships with these two use cases. Another example is when a use case has too much functionality; inclusion relationships can be used to model two smaller use cases. In UML documentation, the inclusion relationship is represented by a dashed arrow with <. <include>The text includes a ">" symbol, with an arrow pointing to the included use case.

[0058] 2) Extension Relationship: A use case can also be defined as an incremental extension of a basic use case. This is called an extension relationship. An extension relationship is a method of inserting new behavior into an existing use case. Several extension use cases of the same basic use case can be applied together. The extension of the basic use case adds to the original semantics; in this case, the basic use case, rather than the extension use case, is used as an example. In UML documentation, an extension relationship is represented by a dashed arrow with <. <extend>The text includes a ">" symbol, with an arrow pointing to the expanded use case.

[0059] 3) Generalization Relationship: A use case can be specifically enumerated as one or more use cases; this is called use case generalization. Any child use case can be used if the parent use case can be used. In UML, use case generalization is represented the same way as other generalization relationships, using a triangular arrow pointing from the child use case to the parent use case. In use case generalization, the child use case represents a special form of the parent use case. Child use cases inherit behavior and attributes from the parent use case and can add, override, or change inherited behavior. Use case generalization is necessary when one or more use cases in the system are specializations of a general use case.

[0060] In some embodiments, after constructing the system use case diagram of the system to be configured, the system role function permission configuration method provided in the embodiments of this disclosure can also standardize the system use case diagram (e.g., determine the compliance of the system use case diagram, record information such as the name and version of the system use case diagram, as well as the number and name of the participants and use cases) so as to analyze the relationship between the system roles and the system function list by parsing the relationship between the elements in the system use case diagram, thereby configuring corresponding functions or data permissions for each role.

[0061] In some embodiments, such as Figure 3 As shown, the relationship between system roles and system function lists within the system to be configured can be generated based on the system use case diagram through the following steps:

[0062] S302, parse the elements contained in the system use case diagram to obtain the element parsing results;

[0063] S304: Filter out the actors contained in the system use case diagram from the element parsing results to determine the system roles in the system to be configured, and generate the relationships between the system roles in the system to be configured based on the relationships between the actors in the system use case diagram.

[0064] S306: Filter out the use cases contained in the system use case diagram from the element parsing results to determine the system functions in the system to be configured, and generate the relationship between the system functions in the system to be configured based on the relationship between the use cases in the system use case diagram.

[0065] S308, based on the relationships between system roles and system functions within the system to be configured, as well as the relationships between actors and use cases in the system use case diagram, generates the relationships between the system roles and system functions within the system to be configured.

[0066] In some embodiments, the relationships between actors in the above system use case diagram include: generalization relationships between actors; the relationships between use cases in the above system use case diagram include: generalization relationships between use cases, inclusion relationships between use cases, and extension relationships between use cases; the relationships between actors and use cases in the system use case diagram include: association relationships between actors and use cases.

[0067] For example, taking a library system as an example, the relationship between the participant "reader" and the use cases "borrowing images," "returning books," and "paying fines" is as follows: Figure 4 As shown, the use case "Pay the fine" and the use case "Return the book" have an extension relationship, indicated by a dashed arrow and a <. <extend>The text ">" indicates that the arrow points to the expanded use case; for example... Figure 5 As shown, the relationship between participants "readers", "faculty and staff", "students", "faculty and staff family members", "retired faculty and staff", "undergraduate students", and "graduate students" is a generalization relationship. Generalization relationships are indicated by a triangular arrow pointing from the child participant (lower-level participant) to the parent participant (upper-level participant). For example... Figure 6 As shown, the use case "Pre-borrow books" and the use case "Query books" have an inclusion relationship; the use case "Pre-borrow books" and the use case "Verify identity" also have an inclusion relationship. Inclusion relationships are indicated by a dashed arrow followed by <. <include>The arrow points to the included use case.

[0068] As an optional embodiment, the system role function permission configuration method provided in the embodiments of the present disclosure can include the following steps in specific implementation:

[0069] 1) Import the system use case diagram of the system to be configured: for one or more systems to be configured, record and save the name, version, and other information of each system use case diagram;

[0070] 2) Analyze and store each element included in the system use case diagram: for each element in the system use case diagram, configure a number and record the category, name, and other information of each element to generate system roles and use cases; by recording the relationship between elements, after configuring a number for each element, the relationship between the elements can be analyzed through the connecting line, and the connecting line number, type, direction, associated element number, and other information can be recorded to generate element relationships and relationship types;

[0071] Generally, the participants in the system use case diagram correspond to the system roles in the system, and the relationship between the participants can be converted into the relationship between the system roles. Each use case corresponds to a system function, and the relationship between the use cases can be converted into the relationship between the system functions, including but not limited to: inclusion relationship, extension relationship, generalization relationship, etc.

[0072] 3) Extract the participants from the element analysis results of the system use case diagram to generate corresponding system roles and the relationship between the system roles according to the relationship between the participants; for example, the generalization relationship between the participants is converted into the permission inheritance relationship between the system roles;

[0073] 4) Extract the use cases from the element analysis results of the system use case diagram to generate system functions and data permissions, and generate the relationship between the system functions according to the relationship between the use cases. Each use case corresponds to a system function, and each system function is associated with a corresponding system menu, data entity, and entity operation, etc.

[0074] 5) According to the relationship between the participants and the use cases, the relationship between the system roles, and the relationship between the system functions, the relationship between the system roles and the system function list is analyzed. The generalization relationship between the participants can be converted into the permission inheritance relationship between the system roles; the inclusion relationship between the use cases can be converted into the inclusion relationship between the system functions, for example, the basic use case function includes the included use case function; the extension relationship between the use cases can be converted into the inheritance relationship between the system functions, for example, the extension use case function includes the basic use case function; the generalization relationship between the use cases is converted into the special supplement relationship between the system functions, for example, the child use case function can add, rewrite, or overwrite the function of the parent use case.

[0075] 6) obtain the correspondence between the system role and the system function list, generate the system function permission relationship table according to the correspondence between the system role and the system function list, and then configure the corresponding function permission for each system role according to the system function permission relationship table.

[0076] It can be seen that the system role function permission configuration method provided in the embodiments of the present disclosure generates system roles and the relationship between system roles based on the participants in the system use case diagram, generates system functions and data permission lists based on the use cases in the system use case diagram, determines the relationship between the system roles and the system function list in combination with the association relationship between the participants and the use cases in the system use case diagram, and then determines the function permission and the data permission corresponding to each system role, and automatically generates and updates the permission corresponding to each system role. Through the embodiments of the present disclosure, not only the workload of the operation and maintenance personnel for configuring the corresponding function permission for the system role can be reduced, and the human cost can be saved, but also the consistency (i.e., the consistency of the system permission configuration and the demand analysis), completeness and accuracy of the system permission can be improved, the configuration can be simplified, and the error rate can be reduced.

[0077] Based on the same inventive concept, the embodiments of the present disclosure also provide a system role function permission configuration device, as described in the following embodiments. Since the principles of the device embodiments for solving problems are similar to the above-mentioned method embodiments, the implementation of the device embodiments can be referred to the implementation of the above-mentioned method embodiments, and the repeated parts will not be described here.

[0078] Figure 7 A schematic diagram of a system role function permission configuration device in the embodiments of the present disclosure is shown, as shown in FIG. 7, the system role function permission configuration device 70 includes a system use case diagram acquisition module 701, a system role function relationship determination module 702 and a permission configuration module 703. Figure 7

[0079] The system use case diagram acquisition module 701 is configured to acquire the system use case diagram of the system to be configured, and the system use case diagram includes the following elements: participants, use cases, relationships between participants, relationships between participants and use cases, and relationships between use cases. The system role function relationship determination module 702 is configured to generate the relationship between the system role and the system function list in the system to be configured according to the system use case diagram, wherein the system role is determined according to the participants in the system use case diagram, and the system function list includes one or more system functions determined according to the use cases in the system use case diagram. The permission configuration module 703 is configured to configure the corresponding function permission for the system role in the system to be configured according to the relationship between the system role and the system function list in the system to be configured.

[0080] ​As can be seen from the above, the system role function permission configuration device provided in the embodiments of this disclosure, after obtaining the system use case diagram of the system to be configured through the system use case diagram acquisition module 701, generates the relationship between the system roles and the system function list in the system to be configured through the system role function relationship determination module 702 based on the participants, use cases, the relationship between participants, the relationship between participants and use cases, and the relationship between use cases contained in the system use case diagram. Then, the permission configuration module 703 configures the corresponding function permissions for the system roles in the system to be configured based on the relationship between the system roles and the system function list in the system to be configured.

[0081] The system role function permission configuration device provided in this embodiment can analyze the function permissions corresponding to each role in the system based on the system use case diagram, thereby quickly generating and automatically updating the role functions of the system.

[0082] In some embodiments, the system role-function relationship determination module 702 may specifically include: a use case diagram parsing module 7021, used to parse the elements contained in the system use case diagram to obtain element parsing results; a role-relationship determination module 7022, used to filter out the participants contained in the system use case diagram from the element parsing results to determine the system roles in the system to be configured, and generate the relationship between the system roles in the system to be configured based on the relationship between the participants in the system use case diagram; a function-relationship determination module 7023, used to filter out the use cases contained in the system use case diagram from the element parsing results to determine the system functions in the system to be configured, and generate the relationship between the system functions in the system to be configured based on the relationship between the use cases in the system use case diagram; and a role-function relationship determination module 7024, used to generate the relationship between the system roles and the system function list in the system to be configured based on the relationship between the system roles in the system to be configured, the relationship between the system functions, and the relationship between the participants and use cases in the system use case diagram.

[0083] In some embodiments, the permission configuration module 703 may also be used to: generate a system role permission information table for the system to be configured based on the relationship between system roles and system function lists within the system to be configured, and configure corresponding function permissions for system roles within the system to be configured based on the system role permission information table, wherein the system role permission information table includes the relationship between system roles and system function lists within the system to be configured.

[0084] In some embodiments, the relationships between actors in the above system use case diagram include: generalization relationships between actors; the relationships between use cases in the system use case diagram include: generalization relationships between use cases, inclusion relationships between use cases, and extension relationships between use cases; the relationships between actors and use cases in the system use case diagram include: association relationships between actors and use cases.

[0085] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the content disclosed in the above method embodiments. The above modules, as part of an apparatus, can be executed in a computer system such as a set of computer-executable instructions.

[0086] Those skilled in the art will understand that various aspects of this disclosure can be implemented as a system, method, or program product. Therefore, various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, collectively referred to herein as a "circuit," "module," or "system."

[0087] The following reference Figure 8 To describe an electronic device 800 according to such an embodiment of the present disclosure. Figure 8 The electronic device 800 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

[0088] like Figure 8 As shown, the electronic device 800 is manifested in the form of a general-purpose computing device. The components of the electronic device 800 may include, but are not limited to: at least one processing unit 810, at least one storage unit 820, and a bus 830 connecting different system components (including storage unit 820 and processing unit 810).

[0089] The storage unit stores program code that can be executed by the processing unit 810, causing the processing unit 810 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of this disclosure. For example, the processing unit 810 can perform the following steps of the above method embodiments: obtaining a system use case diagram of the system to be configured, the system use case diagram containing the following elements: actors, use cases, relationships between actors, relationships between actors and use cases, and relationships between use cases; generating relationships between system roles and system function lists within the system to be configured based on the system use case diagram, wherein system roles are determined based on actors in the system use case diagram, and the system function list contains one or more system functions determined based on use cases in the system use case diagram; configuring corresponding functional permissions for system roles within the system to be configured based on the relationships between system roles and system function lists within the system to be configured.

[0090] Storage unit 820 may include a readable medium in the form of a volatile storage unit, such as random access memory (RAM) 8201 and / or cache memory 8202, and may further include a read-only memory (ROM) 8203.

[0091] The storage unit 820 may also include a program / utility 8204 having a set (at least one) of program modules 8205, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0092] Bus 830 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0093] Electronic device 800 can also communicate with one or more external devices 840 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 800, and / or with any device that enables electronic device 800 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 850. Furthermore, electronic device 800 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 860. As shown, network adapter 860 communicates with other modules of electronic device 800 via bus 830. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0094] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0095] In particular, according to embodiments of this disclosure, the process described above with reference to the flowchart can be implemented as a computer program product, which includes a computer program that, when executed by a processor, implements the above-described system role function permission configuration method.

[0096] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, which may be a readable signal medium or a readable storage medium. Figure 9 This illustration shows a schematic diagram of a computer-readable storage medium according to an embodiment of the present disclosure, such as... Figure 9 As shown, the computer-readable storage medium 900 stores a program product capable of implementing the methods described above in this disclosure. In some possible embodiments, various aspects of this disclosure may also be implemented as a program product comprising program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of this disclosure.

[0097] More specific examples of computer-readable storage media in this disclosure may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0098] In this disclosure, a computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of transmitting, propagating, or transmitting a program for use by or in connection with an instruction execution system, apparatus, or device.

[0099] Optionally, the program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0100] In practical implementation, program code for performing the operations of this disclosure can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0101] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0102] Furthermore, although the steps of the method in this disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or a step may be broken down into multiple steps.

[0103] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0104] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the appended claims.< / include> < / extend> < / extend> < / include>

Claims

1. A method for configuring system role-based functional permissions, characterized in that, include: Obtain the system use case diagram of the system to be configured. The system use case diagram contains the following elements: actors, use cases, relationships between actors, relationships between actors and use cases, and relationships between use cases. Based on the system use case diagram, a relationship between system roles and system function lists within the system to be configured is generated, wherein the system roles are determined based on the actors in the system use case diagram, and the system function list contains one or more system functions determined based on the use cases in the system use case diagram; Based on the relationship between system roles and system function lists within the system to be configured, configure corresponding function permissions for the system roles within the system to be configured. Specifically, based on the system use case diagram, the relationship between the system roles and the system function list within the system to be configured is generated, including: The elements contained in the system use case diagram are parsed to obtain the element parsing results; The participants included in the system use case diagram are filtered from the element parsing results to determine the system roles in the system to be configured, and the relationships between the system roles in the system to be configured are generated based on the relationships between the participants in the system use case diagram. The use cases contained in the system use case diagram are filtered from the element parsing results to determine the system functions in the system to be configured, and the relationships between the system functions in the system to be configured are generated based on the relationships between the use cases in the system use case diagram. Based on the relationships between system roles and system functions within the system to be configured, as well as the relationships between actors and use cases in the system use case diagram, generate a list of relationships between system roles and system functions within the system to be configured. The relationships between actors in the system use case diagram include: generalization relationships between actors; the relationships between use cases in the system use case diagram include: generalization relationships between use cases, inclusion relationships between use cases, and extension relationships between use cases; the relationships between actors and use cases in the system use case diagram include: association relationships between actors and use cases. Specifically, the generalization relationship between participants can be converted into the permission inheritance relationship between system roles; the inclusion relationship between use cases can be converted into the inclusion relationship between system functions; the extension relationship between use cases can be converted into the inheritance relationship between system functions; and the generalization relationship between use cases can be converted into the special supplementary relationship between system functions.

2. The system role function permission configuration method according to claim 1, characterized in that, Based on the relationship between system roles and system function lists within the system to be configured, configure corresponding function permissions for the system roles within the system to be configured, including: Based on the relationship between system roles and system function lists within the system to be configured, a system role permission information table for the system to be configured is generated, wherein the system role permission information table includes: the relationship between system roles and system function lists within the system to be configured; Based on the system role permission information table of the system to be configured, configure the corresponding functional permissions for the system roles in the system to be configured.

3. A system role function permission configuration device, characterized in that, include: The system use case diagram acquisition module is used to acquire the system use case diagram of the system to be configured. The system use case diagram contains the following elements: actors, use cases, relationships between actors, relationships between actors and use cases, and relationships between use cases. The system role-function relationship determination module is used to generate the relationship between system roles and system function lists in the system to be configured based on the system use case diagram. The system roles are determined based on the actors in the system use case diagram, and the system function list contains one or more system functions determined based on the use cases in the system use case diagram. The permission configuration module is used to configure corresponding function permissions for the system roles in the system to be configured based on the relationship between system roles and system function list in the system to be configured. The system role-function relationship determination module includes: The use case diagram parsing module is used to parse the elements contained in the system use case diagram and obtain the element parsing results; The role relationship determination module is used to filter out the participants contained in the system use case diagram from the element parsing results, so as to determine the system roles in the system to be configured, and generate the relationship between the system roles in the system to be configured based on the relationship between the participants in the system use case diagram. The inter-functional relationship determination module is used to filter out the use cases contained in the system use case diagram from the element parsing results, so as to determine the system functions in the system to be configured, and generate the relationship between the system functions in the system to be configured based on the relationship between the use cases in the system use case diagram. The role-function relationship determination module is used to generate the relationship between the system roles and system functions in the system to be configured based on the relationship between system roles, the relationship between system functions, and the relationship between actors and use cases in the system use case diagram. The relationships between actors in the system use case diagram include: generalization relationships between actors; the relationships between use cases in the system use case diagram include: generalization relationships between use cases, inclusion relationships between use cases, and extension relationships between use cases; the relationships between actors and use cases in the system use case diagram include: association relationships between actors and use cases. Specifically, the generalization relationship between participants can be converted into the permission inheritance relationship between system roles; the inclusion relationship between use cases can be converted into the inclusion relationship between system functions; the extension relationship between use cases can be converted into the inheritance relationship between system functions; and the generalization relationship between use cases can be converted into the special supplementary relationship between system functions.

4. The system role function permission configuration device according to claim 3, characterized in that, The permission configuration module is further configured to: generate a system role permission information table for the system to be configured based on the relationship between system roles and system function lists within the system to be configured; and configure corresponding function permissions for system roles within the system to be configured based on the system role permission information table, wherein the system role permission information table includes the relationship between system roles and system function lists within the system to be configured.

5. An electronic device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the system role function permission configuration method according to any one of claims 1 to 2 by executing the executable instructions.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the system role function permission configuration method according to any one of claims 1 to 2.

Images