Rule management apparatus and rule management method

Abstract

To facilitate searching for a rule and enable appropriate operation thereof.SOLUTION: An operation rule management server 100 includes: a rule registration unit 101 which registers various kinds of rules to be applied to a user who belongs a group; a rule search unit 102 which searches for a desired rule from among the various kinds of rules registered by the rule registration unit 101; a rule content display unit 103 which displays the content of the rule searched by the rule search unit 102 on a display unit of a user information terminal 300 operated by the user; and a rule evaluation registration unit 104 which receives, from the user information terminal 300, and registers an evaluation made by the user on the rule.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a rule management device and a rule management method. [Background technology]

[0002] In recent years, as the business activities of companies have become more diverse, activities to define business rules such as departmental rules and company rules (including document templates and writing formats) have become more active. Companies are required to properly manage the various business rules that have been defined in this way. Employees refer to the established business rules and carry out the tasks assigned to them while complying with the business rules (for example, see Patent Document 1).

[0003] Due to the diversification of corporate activities as described above, employees are spending more time searching for and understanding the business rules that apply to the tasks they are trying to perform, which creates the problem of an increase in the time spent on tasks other than the execution of their core tasks (non-core work time). In addition, various business rules are established based on the management's ideas, and do not fully reflect the employees' ideas, so it is common for unnecessary rules or rules that lack rationality to be applied for long periods of time. This leads to a decrease in work efficiency and a decline in employee morale. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2003-99570 A Summary of the Invention [Problem to be solved by the invention]

[0005] An object of the present invention is to provide a rule management device and a rule management method that facilitates the search for rules and enables their appropriate operation. [Means for solving the problem]

[0006] In order to solve the above problems, the rule management device of the present invention comprises a rule registration unit that registers various rules to be applied to users belonging to a group, a rule search unit that searches for a desired rule from among the various rules registered by the rule registration unit, a rule content display unit that displays the contents of the rules searched for by the rule search unit on a display unit of a terminal device operated by the user, and a rule evaluation registration unit that accepts and registers user evaluations of the rules from the terminal device.

[0007] In addition, the rule management method of the present invention includes registering various rules to be applied to users belonging to a group, searching for a desired rule from among the various registered rules, displaying the contents of the searched rule on a display unit of a terminal device operated by the user, and accepting and registering the user's evaluation of the rule from the terminal device. Effect of the Invention

[0008] According to the present invention, it is possible to provide a rule management device and a rule management method that facilitates rule searches and enables appropriate operation of the rules. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an overall configuration of a business rule management system. [Diagram 2] 2 shows an example of a data structure of rule information 111a related to business rules stored in a rule information storage unit 111. [Diagram 3] 2 shows an example of a data structure of tag information 112a stored in a tag information storage unit 112. [Figure 4] 2 shows an example of a data structure of user information 113a stored in a user information storage unit 113. [Diagram 5] 1 shows an example of a data structure of favorite information 114a stored in favorite information storage unit 114. [Figure 6]2 shows an example of a data structure of rule evaluation information 115a stored in the rule evaluation information storage unit 115. [Figure 7] 1 shows an example of a data structure of setting information 116a stored in setting information storage unit 116. [Figure 8] 2 is a block diagram showing a hardware configuration of a control unit 800 of the business rule management server 100. FIG. [Figure 9] This is a flowchart showing the overall process from registration to evaluation of business rules. [Figure 10] 13 is an example of a rule registration screen. [Figure 11] 13 is a flowchart illustrating an example of a procedure for registering a business rule. [Figure 12] 13 is an example of a rule search screen. [Figure 13] 13 is a flowchart showing an example of a procedure for displaying frequent rules. [Figure 14] 13 is a flowchart showing an example of a procedure for displaying frequently-used tags. [Figure 15] 13 is a flowchart showing an example of a keyword search. [Figure 16] 13 is a flowchart illustrating an example of a procedure for displaying a business rule registered in a favorites. [Figure 17] 17 is an example of a tag-specific rule display screen 1700. [Figure 18] 17 is a flowchart showing an example of a display procedure for a tag-specific rule display screen 1700. [Figure 19] 19 is an example of a rule content display screen 1900. [Figure 20] 19 is a flowchart showing an example of a display procedure of a rule content display screen 1900. [Figure 21] 21 is an example of a rule evaluation registration screen 2100. [Figure 22] 21 is a flowchart showing an example of a display procedure of a rule evaluation registration screen 2100. [Diagram 23] 23 shows an example of a rule evaluation reference screen 2300. [Figure 24]23 is a flowchart showing an example of a display procedure of a rule evaluation reference screen 2300. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, the present embodiment will be described with reference to the accompanying drawings. In the accompanying drawings, functionally identical elements may be indicated by the same numbers. Note that the accompanying drawings show embodiments and implementation examples according to the principles of the present disclosure, but these are for understanding the present disclosure and are not to be used to interpret the present disclosure in a limiting manner. The description in this specification is merely a typical example and does not limit the scope or application of the present disclosure in any sense.

[0011] In the present embodiment, the description is given in sufficient detail for a person skilled in the art to implement the present disclosure, but it should be understood that other implementations and forms are possible, and that changes in configuration and structure and substitutions of various elements are possible without departing from the scope and spirit of the technical ideas of the present disclosure. Therefore, the following description should not be interpreted as being limited thereto.

[0012] (Business rule management system 1) The overall configuration of a business rule management system according to an embodiment of the present invention will be described with reference to Fig. 1. The business rule management system 1 (hereinafter referred to as system 1) includes a business rule management server 100 that manages business rules, an administrator information terminal 200, a user information terminal 300, and a system server 400. The business rule management server 100, the administrator information terminal 200, the user information terminal 300, and the system server 400 are connected to each other via a network NW so as to be able to communicate with each other. The business rules include document templates, description formats, business flows, and the like.

[0013] (Business rule management server 100) The business rule management server 100 is an example of the rule management device of the present invention. The business rule management server 100 manages various business rules established in a company in a searchable state. The business rule management server 100 also manages evaluation information, which is an evaluation of various business rules. By making the business rules searchable, employees can find business rules related to the business they are going to perform. Furthermore, employees can input their impressions, opinions, suggestions, etc., regarding the searched business rules. This allows employees to be freed from the time-consuming search for business rules and to concentrate on their original work. Furthermore, employees can contribute to the improvement of business rules by evaluating the business rules. Meanwhile, managers can refer to the evaluations (impressions, opinions, suggestions, etc.) regarding the various business rules established and use them to improve the business rules.

[0014] (Administrator information terminal 200, User information terminal 300) The administrator information terminal 200 is an information terminal operated by an administrator (e.g., a manager such as a department manager or section manager) who creates business rules. The administrator information terminal 200 is a general-purpose computer such as a personal computer, smartphone, or tablet. The user information terminal 300 is an information terminal operated by an employee who implements business rules. The user information terminal 300 is a general-purpose computer such as a personal computer, smartphone, or tablet. The administrator information terminal 200 and the user information terminal 300 are examples of the terminal device of the present invention.

[0015] Note that the administrator may not only create business rules but also implement them, and the employees may not only implement business rules but also create business rules. For example, the business rule management server 100 may manage information on administrators who have the authority to create business rules, and permit the creation of business rules when a user with the authority successfully logs in. Note that the information on administrators and employees may be stored in a system server that provides an intranet system or in a Lightweight Directory Access Protocol (LDAP) server connected to the system server.

[0016] (System Server 400) The system server 400 provides an intranet system used within a company. Although one each of the administrator information terminal 200 and the user information terminal 300 is shown in Fig. 1, a plurality of administrator information terminals 200 and a plurality of user information terminals 300 may be connected to the system server 400. In addition, the business rule management server 100 and the system server 400 may also be a plurality of distributed servers.

[0017] (Details of the business rule management server 100) Specifically, the business rule management server 100 includes a rule registration unit 101, a rule search unit 102, a rule content display unit 103, a rule evaluation registration unit 104, a rule evaluation reference unit 105, a rule information storage unit 111, a tag information storage unit 112, a user information storage unit 113, a favorite information storage unit 114, a rule evaluation information storage unit 115, and a setting information storage unit 116.

[0018] (Rule registration unit 101) The rule registration unit 101 registers various rules that are created by an administrator and are applied to users belonging to a group (such as a business entity or an organization (such as a department or section)). The registration of business rules can be executed, for example, through the administrator information terminal 200. Data related to the business rules registered by the rule registration unit 101 is stored in the rule information storage unit 111.

[0019] (Rule search unit 102) The rule search unit 102 searches for a desired rule from among various business rules registered by the rule registration unit 101, according to input from the user information terminal 300, etc. The rule search unit 102 has, as one example, a frequent rule display unit 1021, a frequent tag display unit 1022, a keyword search unit 1023, a favorites display unit 1024, and a tag-specific rule display unit 1025, and is configured to be able to search for business rules in various ways.

[0020] (Frequent rule display section 1021) The frequent rule display unit 1021 identifies a business rule that is frequently viewed based on the number of accesses to the business rule in a predetermined period, and displays information corresponding to the identified business rule (for example, a sticky note-type image including the name of the business rule and a summary of the business rule) on the display of the user information terminal 300. Then, the frequent rule display unit 1021 searches for a business rule corresponding to the information from among various business rules according to the selection of information displayed on the display of the user information terminal 300. For example, the frequent rule display unit 1021 displays information corresponding to business rules (for example, the top five business rules) that have been frequently searched or displayed in the system 1 in the most recent period (for example, the most recent two months) on the display of the administrator information terminal 200 or the user information terminal 300. A user who operates the administrator information terminal 200 or the user information terminal 300 can search for a desired business rule by selecting one of the pieces of information on the frequent rules displayed on the display by the frequent rule display unit 1021.

[0021] (Frequently used tag display section 1022) The frequent tag display unit 1022 identifies a tag with a high access frequency from among tags linked to business rules accessed during a predetermined period, and displays information corresponding to the identified tag (for example, a button-type image including the contents of the tag) on ​​the display of the user information terminal 300. Then, the frequent tag display unit 1022 searches for a business rule to which a tag corresponding to information is linked from various business rules according to the selection of information displayed on the display of the user information terminal 300. For example, the frequent tag display unit 1022 displays information corresponding to a tag linked to a business rule that has been frequently searched or displayed in the system 1 in the last (for example, the last month) (for example, a tag "#quote" linked to a business rule related to creating a quotation) on the display of the user information terminal 300. The user can search for a business rule to which the selected tag is linked by selecting one of the pieces of information displayed on the display by the frequent tag display unit 1022. Information related to the tag is stored in the tag information storage unit 112, for example.

[0022] (Keyword search section 1023) The keyword search unit 1023 searches for a desired business rule by having the user input a keyword related to the business rule to be searched for. The keyword search unit 1023 displays a search window (see FIG. 12) for inputting a keyword on the display of the user information terminal 300 or the like, searches for a business rule containing the keyword from among the multiple business rules stored in the rule information storage unit 111, and displays the search result on the display of the user information terminal 300 or the like.

[0023] (Favorites display section 1024) The favorite display unit 1024 displays information corresponding to a "favorite" business rule registered according to the user's desire on the display of the user information terminal 300. Then, the favorite display unit 1024 can search for a "favorite" business rule corresponding to the information from among various business rules according to the selection of information corresponding to the displayed "favorite" business rule. The business rules registered as "favorites" are stored for each user in the favorite information storage unit 114, for example.

[0024] (Tag-specific rule display section 1025) The tag-based rule display unit 1025 displays business rules by tag on a display or the like of the user information terminal 300. The tag-based rule display unit 1025 displays a tag and one or more business rules linked to the tag as a set on a display or the like of the user information terminal 300.

[0025] (Rule content display unit 103) The rule content display unit 103 displays the content of the business rule searched for by the rule search unit 102 on the display or the like of the user information terminal 300. The displayed content of the business rule includes, for example, the name of the business rule, the background and reason for creating the business rule, tags associated with the business rule, the name and contact information (e.g., email address) of the contact for inquiries regarding the business rule, and detailed content of the business rule.

[0026] (Rule evaluation registration unit 104) The rule evaluation registration unit 104 accepts and registers evaluations (impressions, opinions, suggestions, etc.) of business rules by employees and the like from the user information terminal 300. The rule evaluation registration unit 104 displays a screen (rule evaluation registration screen (see FIG. 21)) for inputting the employee's evaluation of the business rule on the display or the like of the user information terminal 300, and stores the employee's evaluation of the business rule inputted on the rule evaluation registration screen in the rule evaluation information storage unit 115. Evaluations of business rules include favorable intentions toward the business rule (for example, the presence or absence of "Likes" and the number of "Likes") and comments on the business rule (evaluations, opinions, suggestions).

[0027] (Rule evaluation reference section 105) The rule evaluation reference unit 105 displays a reference screen (rule evaluation reference screen (see FIG. 23)) for referencing the evaluation of the business rule registered by the rule evaluation registration unit 104 on a display or the like of the administrator information terminal 200. The rule evaluation reference unit 105 displays a list of evaluations of the business rule on a display or the like of the administrator information terminal 200. The rule evaluation reference unit 105 may provide the evaluation of the business rule only to the creator of the business rule, to users with predetermined authority, or to all users.

[0028] Next, with reference to Figures 2 to 7, details of rule information 111a stored in rule information storage unit 111, tag information 112a stored in tag information storage unit 112, user information 113a stored in user information storage unit 113, favorite information 114a stored in favorite information storage unit 114, rule evaluation information 115a stored in rule evaluation information storage unit 115, and setting information 116a stored in setting information storage unit 116 will be described.

[0029] (Rule Information 111a) 2 is an example of a data structure of rule information 111a related to a business rule stored in the rule information storage unit 111. The rule information 111a includes rule data 111b indicating the contents of the business rule and rule access history 111c indicating the access history to the business rule. The rule data 111b may include, for example, a rule identifier for identifying the business rule, the rule name of the business rule, the background or reason for the business rule, the contents of the business rule, the type of the business rule, an address for inquiries regarding the business rule, and the like. In addition, the rule access history 111c may include, for example, the date and time of access to the business rule, the rule identifier, a user identifier for identifying a user who accessed the business rule, a group identifier for identifying a group to which the user belongs, and a position identifier for identifying the position of the user.

[0030] (Tag information 112a) 3 is an example of a data structure of tag information 112a stored in the tag information storage unit 112. The tag information 112a has information related to tags. The tag information 112a includes hash tag data 112b including a tag identifier for identifying a tag and a tag name indicated by the tag identifier. The tag information 112a also includes hash tag mapping data 112c including a rule identifier and a tag identifier indicating a tag linked to a business rule indicated by the rule identifier.

[0031] (User information 113a) 4 is an example of a data structure of user information 113a stored in user information storage unit 113. User information 113a includes user data 113b including user information, group data 113c including group information, and position data 113d indicating a position. User data 113b includes, for example, a user identifier, name information indicating the user's name, a group identifier, and a position identifier. Group data 113c includes a group identifier and a name (group name) of the group indicated by the group identifier. Position data 113d includes a position identifier and a name (position name) of the position indicated by the position identifier.

[0032] (Favorite Information 114a) 5 is an example of a data structure of favorite information 114a stored in the favorite information storage unit 114. The favorite information 114a stores business rules that have been registered as favorites by a user. The favorite information 114a includes favorite mapping data 114b that associates a rule identifier, a user identifier, and favorite memo information. The favorite memo information includes information regarding a memo written by a user (employee) who registered the business rule as a favorite.

[0033] FIG. 6 is an example of a data structure of the rule evaluation information 115a stored in the rule evaluation information storage unit 115. The rule evaluation information 115a may include evaluation summary data 115b indicating a summary of the evaluation of the business rule, and evaluation detail data 115c indicating the details of the evaluation of the business rule. The evaluation summary data 115b includes a rule identifier, a total score of the evaluation of the business rule identified by the rule identifier (the number of "Likes" in FIG. 21), and the number of comments on the business rule. The evaluation detail data 115c is information indicating details of each evaluation made on the business rule. The evaluation detail data 115c includes a rule identifier, an evaluation ID for identifying the evaluation of the business rule, an evaluation date and time when the evaluation was made, an evaluation score for the business rule (the number of "Likes" in FIG. 21), an evaluation comment on the business rule, and an evaluator ID (user identifier) ​​for identifying the evaluator.

[0034] Fig. 7 is an example of the data structure of setting information 116a stored in setting information storage unit 116. Setting information 116a includes setting value data 116b including various setting values ​​to be set in the operation of system 1. Setting value data 116b stores an identifier for identifying setting information, a name of setting information, and a setting value in association with each other. In the example of Fig. 7, an identifier (P001) and a frequent detection period (number of months) which is a period for counting and detecting the frequent rules described above, and its value (2 = 2 months) are stored as the name of setting information.

[0035] (Hardware configuration of the business rule management server 100) 8 is a block diagram showing a hardware configuration of the control unit 800 of the business rule management server 100. The hardware configuration of the control unit 800 of the business rule management server 100 will be described with reference to FIG.

[0036] The control unit 800 includes a processor 801, a main memory unit 802, an auxiliary memory unit 803, a communication interface 804 (hereinafter, the interface is abbreviated as I / F), an input / output I / F 805, and a bus 806 that communicatively connects the above-mentioned modules. The processor 801 is, for example, a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), etc. The processor 801 deploys a program stored in the auxiliary memory unit 803 in an executable manner in a working area of ​​the main memory unit 802. The main memory unit 802 stores a program executed by the processor 801, data processed by the processor 801, etc. The main memory unit 802 is, for example, a flash memory, a random access memory (RAM), a read only memory (ROM), etc. The auxiliary memory unit 803 stores various programs such as an operating system (OS) and various data. The auxiliary storage unit 803 is, for example, a solid state drive (SSD), a hard disk drive (HDD), or a combination thereof. The communication I / F 804 is a device for connecting the control unit 800 to a network such as a local area network (LAN), and is, for example, a network interface controller (NIC). The input / output I / F 805 is, for example, a device controller that inputs and outputs data to and from input / output devices such as a mouse, keyboard, and display connected to the control unit 800.

[0037] The control unit 800 functions as the above-mentioned rule registration unit 101, rule search unit 102, rule content display unit 103, rule evaluation registration unit 104, and rule evaluation reference unit 105. For example, the processor 801 of the control unit 800 executes a program stored in the auxiliary storage unit 803, thereby executing the functions of the above-mentioned rule registration unit 101, rule search unit 102, tag-specific rule display unit 1025, rule content display unit 103, rule evaluation registration unit 104, and rule evaluation reference unit 105, etc.

[0038] Moreover, the auxiliary storage unit 803 functions as the above-mentioned rule information storage unit 111, tag information storage unit 112, user information storage unit 113, favorite information storage unit 114, rule evaluation information storage unit 115, and setting information storage unit 116. The auxiliary storage unit 803 stores the rule information 111a, tag information 112a, user information 113a, favorite information 114a, rule evaluation information 115a, and setting information 116a.

[0039] (Overall flow from business rule registration to evaluation) Next, with reference to the flowchart in FIG. 9, the overall flow from registration to evaluation of business rules in the rule management method in this system 1 will be described.

[0040] In the system 1, first, a rule creator (administrator, etc.) creates business rules using the administrator information terminal 200. The rule registration unit 101 registers the created various business rules in the business rule management server 100 (step S101). The registered business rules are stored in the rule information storage unit 111.

[0041] When step S101 is executed repeatedly and a large number of business rules are accumulated in the rule information storage unit 111 of the business rule management server 100, a practitioner of the rules (such as an employee) searches for a business rule that applies to his or her own business among those business rules and accesses the system 1 to check the contents of that rule (step S102).

[0042] Then, the rule search unit 102 searches for and displays the desired business rule according to a search instruction from the rule practitioner, for example, by a plurality of search methods (1) to (5) as shown below (step S103).

[0043] (1) The rule search unit 102 (frequent rule display unit 1021) identifies frequently viewed business rules based on the number of accesses to the business rules in a specified period of time, and displays information corresponding to the identified business rule (for example, a sticky note-type image including the name of the business rule and a summary of the business rule) on the display of the user information terminal 300.

[0044] (2) The rule search unit 102 (keyword search unit 1023) searches for a business rule including the keyword entered in the search window (see FIG. 12) from among the multiple business rules stored in the rule information storage unit 111, based on the keyword entered in the search window, and displays the search results on the display or the like of the user information terminal 300.

[0045] (3) The rule search unit 102 (frequently accessed tag display unit 1022) identifies tags that are frequently accessed from among the tags linked to business rules accessed during a specified period, and displays information corresponding to the identified tags (for example, a button-type image containing the content of the tag) on ​​the display of the user information terminal 300, etc.

[0046] (4) The rule search unit 102 (favorites display unit 1024) displays on the display of the user information terminal 300 or the like information corresponding to the "favorite" business rules registered in accordance with the user's wishes.

[0047] (5) The rule search unit 102 (tag-based rule display unit 1025) displays business rules by tag on the display of the user information terminal 300 or the like.

[0048] Then, the rule content display unit 103 displays the content of a desired business rule selected from the business rules searched and displayed using the multiple search methods (1) to (5) described above (step S103, (1') to (5')).

[0049] (1') When a rule practitioner selects one business rule from among the frequently used business rules displayed on the display or the like of the user information terminal 300, the rule content display unit 103 displays the content of the selected business rule (step S104-1). The multiple business rules with high frequency rankings displayed are, for example, the top five business rules most frequently searched or displayed in the past two months. The rule practitioner can check the content of one business rule by selecting it on the display from among the multiple business rules displayed on the display.

[0050] (2') When a rule practitioner selects one business rule from among the business rules found by keyword search displayed on the display or the like of the user information terminal 300, the rule content display unit 103 displays the content of the selected business rule (step S104-2). The rule practitioner can check the content of one business rule by selecting it on the display from among the multiple business rules displayed as the search result of the keyword search.

[0051] (3') When a rule practitioner selects one business rule from among the business rules found by the tag search displayed on the display or the like of the user information terminal 300, the rule content display unit 103 displays the content of the selected business rule (step S104-3). The rule practitioner can check the content of the business rule by selecting one business rule on the display from one or more business rules linked to the selected tag.

[0052] (4') When a rule practitioner selects one business rule from among the favorite business rules displayed on the display or the like of the user information terminal 300, the rule content display unit 103 displays the content of the selected business rule (step S104-4). The rule practitioner can check the content of a business rule by selecting one business rule on the display from the list of favorite business rules displayed.

[0053] (5') When a rule practitioner selects one business rule from among the business rules displayed by tags on the display or the like of the user information terminal 300, the rule content display unit 103 displays the content of the selected business rule (step S104-5). The rule practitioner can check the content of a business rule by selecting one business rule on the display from among the displayed business rules by tags.

[0054] Once a business rule has been searched for and its contents confirmed, the contents of the business rule are evaluated by an evaluator (a rule practitioner (employee, etc.)) (step S105). If there are no particular evaluation items, the procedure ends (NO). However, if there is an evaluation (impression, opinion, suggestion, etc.) on the contents of the business rule, the rule evaluation registration unit 104 registers the evaluation of the business rule entered by the evaluator (step S106). The registered evaluation of the business rule is stored in the rule evaluation information storage unit 115.

[0055] In this way, when the evaluations of business rules are accumulated in the system 1, the rule evaluation reference unit 105 searches for the evaluation of the business rule in response to a request from the rule creator or the like, and displays the contents of the evaluation on the display or the like of the terminal device used by the rule creator (step S107).

[0056] An example of a rule registration screen used when registering a business rule in step S101 will be described with reference to FIG. 10, and an example of a procedure for registering a business rule in S101 will be described with reference to the flowchart in FIG.

[0057] (Rule registration screen 1000) 10, the rule registration screen 1000 has a rule name input section 1001 for inputting the name of the rule to be registered, a rule background / reason input section 1002 for inputting the background and reason of the rule to be registered, and a rule tag input section 1003 for inputting a tag to be linked to the rule to be registered. The rule registration screen 1000 also has an inquiry destination name input section 1004 for inputting the name of the inquiry destination for the rule to be registered, and an inquiry destination address input section 1005 for inputting the address of the inquiry destination (e.g., an email address). The rule registration screen 1000 also has a rule content input section 1006 for inputting the content of the rule.

[0058] In addition, the rule registration screen 1000 has a delete button 1007 for deleting the content entered in each input section of the rule registration screen 1000, a register button 1008 for registering a business rule with the content entered in each input section of the rule registration screen 1000, and a close button 1009 for closing the rule registration screen 1000.

[0059] By pressing the register button 1008, the contents entered in each input section of the rule registration screen 1000 are registered as rule data 111b of the rule information 111a.

[0060] (Procedure for registering business rules) The rule registration unit 101 acquires the rule type (e.g., text, HTTP link, file path) of the setting information (step S201), and displays the rule registration screen 1000 on the display of the administrator information terminal 200 (step S202). A rule creator such as an administrator inputs information into each input section of the rule registration screen 1000 (step S203), and presses the delete button 1007, the register button 1008, or the close button 1009.

[0061] When the rule creator presses the delete button 1007, the rule registration unit 101 logically deletes the contents input in each input section of the rule registration screen 1000 (step S204).

[0062] Furthermore, when the rule creator presses the register button 1008, the rule registration unit 101 checks the input contents entered in each input section of the rule registration screen 1000 (step S205). If the check in S205 shows that there is no problem with the input contents (step S207: NO), the rule registration unit 101 assigns a rule identifier and registers the business rule (step S208). The registered business rule is stored in the rule information storage unit 111. Note that if the check in S205 shows that there is a problem with the input contents (step S207: YES), the process returns to step S203.

[0063] Furthermore, when the close button 1009 is pressed, the rule registration unit 101 closes the rule registration screen 1000 that is being displayed (step S206).

[0064] (Rule search screen 1200) Fig. 12 is an example of a rule search screen. A rule search screen 1200 in Fig. 12 includes a frequent rule display field 1021d, a frequent tag display field 1022d, a keyword input field 1023d, and a favorite rule display button 1024d.

[0065] The frequent rule display field 1021d corresponds to the frequent rule display section 1021, and displays a sticky note type image that shows a set of the name of a frequently occurring business rule in the most recent month, for example, and the background / reason for that business rule. When one of the multiple sticky note type images displayed is selected, the details of the business rule corresponding to the selected image can be confirmed.

[0066] The frequent tag display field 1022d corresponds to the frequent tag display section 1022, and displays images of tags that have appeared frequently in the past month, for example. When one of the displayed tag images is selected, a list of business rules linked to the selected tag is displayed.

[0067] The keyword input field 1023d is a search window for inputting a keyword for searching for a business rule, and corresponds to the keyword search unit 1023. When a search is executed using a keyword input in the keyword input field 1023d, business rules with business rule names that include the keyword are displayed as search results.

[0068] The favorite rule display button 1024d is a button for calling up a business rule previously registered in favorites, and corresponds to the favorite display section 1024. When the favorite rule display button 1024d is pressed with a keyword entered in the keyword input field 1023d, a business rule containing the keyword is searched for among the business rules registered in favorites.

[0069] (Procedure for displaying frequent rules) The procedure for displaying frequent rules by the frequent rule display unit 1021 will be described with reference to the flowchart of FIG.

[0070] First, the frequent rule display unit 1021 acquires setting information (frequent detection period (number of months)) set for a frequent rule from the setting information storage unit 116 (step S301).

[0071] Next, the frequent rule display unit 1021 acquires the group identifier and the position identifier of the user who is accessing the business rule management server 100, and identifies the group and the position to which the user belongs (step S302).

[0072] Next, the frequent rule display unit 1021 refers to the rule access history 111c of the rule information 111a in the rule information storage unit 111, identifies a business rule that meets the following conditions, and acquires the rule identifier thereof (step S303). -Business rules that have been accessed during the frequent detection period (number of months) going back from the current date and time -Business rules that match the group identifier of the accessing user -Business rules that match the job title identifier of the accessing user In this way, the frequent rule display unit 1021 can specify the most recent business rules searched for or displayed by users in a group to which the relevant user belongs and by users with the same job title as that of the relevant user.

[0073] In addition, the frequent rule display unit 1021 may identify the most recent business rule searched for or displayed by the user, or may identify the most recent business rule searched for or displayed by a user in a group to which the user belongs, or may identify the most recent business rule referenced by a user with the same job title as the user.

[0074] Then, the frequent rule display unit 1021 sorts the identified business rules in descending order of access frequency, and acquires rule information of the top five business rules with the highest access frequency (step S304).

[0075] Then, the frequent rule display unit 1021 displays the "rule name" and "background and reason" from the rule information of the acquired business rule in the frequent rule display field 1021d (step S305).

[0076] (How to display frequently used tags) Next, a procedure for displaying frequent tags by the frequent tag display unit 1022 will be described with reference to the flowchart of FIG.

[0077] First, the frequent tag display unit 1022 refers to the setting information storage unit 116 and acquires setting information (frequent detection period (number of months)) set for the frequent tag (step S401).

[0078] Next, the frequent tag display unit 1022 acquires the group identifier and the position identifier of the user who is accessing the business rule management server 100, and identifies the group and the position to which the user belongs (step S402).

[0079] Next, the frequent tag display unit 1022 refers to the rule access history 111c of the rule information 111a in the rule information storage unit 111 to identify a business rule that meets the following conditions, and acquires the rule identifier thereof (step S403). -Business rules that have been accessed during the frequent detection period (number of months) going back from the current date and time -Business rules that match the group identifier of the accessing user -Business rules that match the job title identifier of the accessing user In this way, the frequent tag display unit 1022 can identify the most recent business rules searched for or displayed by users in a group to which the relevant user belongs and by users with the same job title as that of the relevant user.

[0080] In addition, the frequent tag display unit 1022 may identify the most recent business rule referenced by the user, or may identify the most recent business rule referenced by a user in the group to which the user belongs, or may identify the most recent business rule referenced by a user with the same job title as the user.

[0081] Then, the frequent tag display unit 1022 reads out the tags linked to the identified business rule from the tag information storage unit 112, aggregates them, sorts them in order of frequency of access, and acquires the top five tag information with the highest frequency of access (step S404).

[0082] Then, the frequent tag display unit 1022 displays the "tag name" of the acquired tag information in the frequent tag display field 1022d (step S405).

[0083] The frequent tag display unit 1022 may display tags with high access frequencies without identifying frequently used business rules.

[0084] (Keyword search) Next, the keyword search performed by keyword search unit 1023 will be described with reference to the flowchart of FIG.

[0085] First, the keyword search unit 1023 acquires a keyword input in the keyword input field 1023d (step S501).

[0086] The keyword search unit 1023 searches the "rule name," "background and reason," and "rule content" of the rule information 111a with the acquired keyword, and acquires rule data containing the keyword (step S502).

[0087] Then, the keyword search unit 1023 displays the "rule name" and "background / reason" of the acquired rule data on the display or the like of the user information terminal 300 (step S503).

[0088] (How to display your favorite rules) Next, a procedure for displaying business rules registered in favorites by the favorites display unit 1024 will be described with reference to the flowchart of FIG.

[0089] First, the favorite display unit 1024 determines whether or not a keyword is input in the keyword input field 1023d (step S601). For example, when the favorite rule display button 1024d is pressed, the favorite display unit 1024 determines whether or not a keyword is input in the keyword input field 1023d.

[0090] When it is determined that a keyword has been input in the keyword input field 1023d (step S601: YES), the favorites display unit 1024 acquires the keyword input in the keyword input field 1023d (step S602).

[0091] The favorite display unit 1024 searches the rule information of the accessing user registered in the favorite mapping data 114b for keywords in the "rule name," "background / reason," and "rule content," and obtains rule information of business rules that include the keywords (step S603).

[0092] On the other hand, if the favorite display unit 1024 determines that no keyword has been entered in the keyword input field 1023d (step S601: NO), it acquires rule information of the business rules of the accessing user registered in the favorite information storage unit 114 (step S604).

[0093] The favorites display unit 1024 displays the "rule name" and "background / reason" of the rule information acquired in S603 or S604 on the display of the user information terminal 300 or the like (step S605).

[0094] (Tag-specific rule display screen 1700) 17 is an example of a tag-specific rule display screen 1700 displayed by the tag-specific rule display unit 1025. This tag-specific rule display screen 1700 displays the contents of the tag (for example, "#Estimate", "#XXX Department", "#Security"), and also displays sticky note-type images of one or more business rules linked to the tag, aligned horizontally. By clicking on the rule name of the business rule, a screen displaying the detailed contents of the business rule can be displayed.

[0095] (Display procedure for tag-specific rule display screen 1700) An example of a procedure for displaying the tag-specific rule display screen 1700 by the tag-specific rule display unit 1025 will be described with reference to FIG.

[0096] First, the tag-specific rule display unit 1025 determines the group to which the accessing user belongs (step S701).

[0097] The tag-specific rule display unit 1025 identifies, in the rule information storage unit 111, rule data related to the group to which the accessing user belongs, and acquires the rule identifier of the identified rule data (step S702).

[0098] The tag-specific rule display unit 1025 searches the hash tag data 112b and the hash tag mapping data 112c of the tag information 112a based on the acquired rule identifier, and acquires the corresponding tag name (step S703).

[0099] Then, the tag-specific rule display unit 1025 displays the tag name, the "rule name" and the "background and reason" of the rule information of the business rule linked to the tag on the tag-specific rule display screen 1700 (step S704).

[0100] (Rule content display screen 1900) 19 is an example of a rule content display screen 1900 displayed by the rule content display unit 103. This rule content display screen 1900 displays details of a business rule. The rule content display screen 1900 displays, for example, the rule name of the business rule, the background and reason for the business rule, tags associated with the business rule, the name and address of the contact for inquiries about the business rule, and the contents of the business rule.

[0101] In addition, the rule content display screen 1900 has a close button 1901 for closing the rule content display screen 1900, an evaluation button 1902 for evaluating the rule, a rule URL 1903 indicating a file path or URL in which details of the rule are described, and a modify button 1904 for modifying the contents of the rule.

[0102] (Display procedure for the rule content display screen 1900) An example of a procedure for displaying the rule content display screen 1900 by the rule content display unit 103 will be described with reference to FIG.

[0103] First, the rule content display unit 103 acquires the rule identifier of the business rule selected by the accessing user (step S801).

[0104] The rule content display unit 103 searches the rule data 111b of the rule information 111a with the acquired rule identifier, and acquires each item of the business rule that matches the rule identifier (step S802).

[0105] Then, the rule content display unit 103 displays each of the acquired items (rule name, background or reason, tag, name of the contact point, contact address, and business rule content) on the rule content display screen 1900 (step S803).

[0106] (Rule evaluation registration screen 2100) 21 is an example of a rule evaluation registration screen 2100 displayed by the rule evaluation registration unit 104. This rule evaluation registration screen 2100 is a screen for registering an evaluation of a business rule. The rule evaluation registration screen 2100 is displayed when the evaluation button 1902 on the rule content display screen 1900 is pressed.

[0107] The rule evaluation registration screen 2100 displays a rule name 2101 of the business rule to be evaluated. The rule evaluation registration screen 2100 also displays an evaluation input field 2102 for selecting an evaluation for the business rule to be evaluated, and a comment input field 2103 for inputting a comment for the business rule to be evaluated. In the evaluation input field 2102, the number of "Likes" (1 to 3) can be selected.

[0108] The rule evaluation registration screen 2100 also displays a button 2104 for closing the rule evaluation registration screen 2100 , and a registration button 2105 for registering the contents entered in the evaluation input field 2102 and the comment input field 2103 .

[0109] (How to register rule evaluation) An example of a procedure for displaying the rule evaluation registration screen 2100 by the rule evaluation registration unit 104 will be described with reference to FIG.

[0110] First, when the evaluation button 1902 on the rule content display screen 1900 is pressed, the rule evaluation registration unit 104 acquires the rule identifier of the business rule displayed on the rule content display screen 1900 and the group identifier to which the accessing user belongs (step S901).

[0111] Then, the rule evaluation registration unit 104 displays the rule evaluation registration screen 2100 (step S902).

[0112] The rule evaluator inputs information into the evaluation input field 2102 and the comment input field 2103 of the rule evaluation registration screen 2100 (step S903).

[0113] When the close button 2104 on the rule evaluation registration screen 2100 is pressed, the rule evaluation registration unit 104 closes the rule evaluation registration screen 2100 (step S904).

[0114] On the other hand, when the registration button 2105 on the rule evaluation registration screen 2100 is pressed, the rule evaluation registration unit 104 checks the contents entered in the evaluation input field 2102 and the comment input field 2103 (step S905).

[0115] If there is an error in the input contents (step S906: YES), the process returns to step S903. If there is no error in the input contents (step S906: NO), the rule evaluation registration unit 104 uses the rule identifier as a key to register the evaluation entered in the evaluation input field 2102 (evaluation score), the contents entered in the comment input field 2103 (evaluation comment), the evaluator's ID (user identifier), the evaluation date and time, and the like in the rule evaluation information 115a (step S907).

[0116] (Rule evaluation reference screen 2300) 23 is an example of a rule evaluation reference screen 2300 displayed by the rule evaluation reference unit 105. This rule evaluation reference screen 2300 is a screen for referring to evaluations of business rules. The rule evaluation reference screen 2300 displays a name 2301 of the business rule to be referenced, a list 2302 of evaluations of the business rule, an analysis result display button 2303 for analyzing the evaluations, and a close button 2304 for closing the rule evaluation reference screen 2300.

[0117] (Rule evaluation reference method) An example of a procedure for displaying the rule evaluation reference screen 2300 by the rule evaluation reference unit 105 will be described with reference to FIG.

[0118] First, the rule evaluation reference unit 105 acquires a list of evaluations for a selected business rule based on the rule identifier of the selected business rule, and displays a rule evaluation reference screen 2300 including the list of evaluations (step S1001).

[0119] In response to pressing of the analysis result display button 2303 (step S1002), the rule evaluation registration unit 104 performs an analysis of the evaluation of the business rule by the analysis tool, and obtains a link to the analysis result (step S1003).

[0120] Then, the rule evaluation registration unit 104 displays a link to the acquired analysis result (step S1004).

[0121] When the close button 2304 is pressed, the rule evaluation registration unit 104 closes the rule evaluation reference screen 2300 (S1005).

[0122] On the other hand, when the displayed link is selected, the rule evaluation registration unit 104 displays the analysis result of the evaluation of the business rule by the analysis tool (step S1006).

[0123] (effect) In this embodiment, various search methods for searching business rules are provided, so rule practitioners can easily search for and check business rules, thereby reducing the time spent on activities other than the execution of core business.

[0124] Furthermore, in this embodiment, since it is possible to evaluate business rules, the evaluation can be fed back to enable appropriate operation of business rules.

[0125] [others] The present invention is not limited to the above-described embodiments, and various modifications are possible. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to an embodiment having all of the configurations described. It is also possible to replace a part of the configuration of one embodiment with the configuration of another embodiment. It is also possible to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to delete a part of the configuration of each embodiment, or to add or replace another configuration.

[0126] For example, in the above embodiment, the search, display and evaluation of business rules have been described as an example of rules of the present invention, but the rules do not have to be business rules, and may be sports rules, game rules or the like. [Explanation of symbols]

[0127] 1. Business rule management system 100: Business rule management server 200: Administrator information terminal 300...User information terminal 400: System server 101…Rule Registration Department 102...Rule search section 1021…Frequently used rules display section 1022…Frequently used tag display section 1023…Keyword search section 1024…Favorites display section 1025…Tag-specific rule display section 103…Rule content display section 104…Rule Evaluation Registration Department 105...Rule evaluation reference section 111...Rule information storage unit 111a…Rule information 111b…Rule data 111c…Rule access history 112...tag information storage unit 112a…Tag information 112b…Hashtag data 112c…Hashtag mapping data 113...user information storage unit 113a...User information 113b...User data 113c…Group Data 113d…Job title data 114...Favorite information storage section 114a…Favorite information 114b…Favorite mapping data 115...Rule evaluation information storage unit 115a…Rule evaluation information 115b…Evaluation summary data 115c…Evaluation details data 116...Setting information storage unit 116a…Setting information 116b...Setting value data 800...Control unit 801...processor 802…Main memory section 803…Auxiliary storage unit 804…Communication I / F 805... Input / Output Interface 806…Bus 1000...Rule registration screen 1200...Rule search screen 1700…Rules display screen by tag 1900…Rule content display screen 2100…Rule evaluation registration screen 2300…Rule evaluation reference screen

Claims

1. a rule registration unit for registering various rules to be applied to users belonging to the group; a rule search unit that searches for a desired rule from among the various rules registered by the rule registration unit; a rule content display unit that displays the content of the rule searched for by the rule search unit on a display unit of a terminal device operated by the user; a rule evaluation registration unit that receives and registers an evaluation of the rule by the user from the terminal device. A rule management device comprising:

2. The rule search unit, identifying a rule that is frequently viewed based on the number of accesses to the rule within a predetermined period of time, and displaying information corresponding to the identified rule on a display unit of the terminal device; According to the selection of the information displayed on the display unit of the terminal device, the rule corresponding to the information is searched for from among the various rules.

2. The rule management device according to claim 1.

3. the rule registration unit registers a rule identifier for identifying the rule and a tag associated with the rule in association with each other; The rule search unit, Identifying a tag having a high access frequency from among the tags linked to the rules accessed within a predetermined period of time, and displaying information corresponding to the identified tag on a display unit of the terminal device; According to the selection of the information displayed on the display unit of the terminal device, the rule associated with the tag corresponding to the information is searched for from among the various rules.

2. The rule management device according to claim 1.

4. The rule search unit, displaying a search box for inputting keywords on a display unit of the terminal device; Searching for the rule containing the keyword from among the various rules 2. The rule management device according to claim 1.

5. a favorite information storage unit that stores any one of the rules as a favorite rule for each of the users, The rule search unit, displaying information corresponding to the user's favorite rules stored in the favorite information storage unit on a display unit of the terminal device; According to the selection of the information displayed on the display unit of the terminal device, the favorite rule corresponding to the information is searched for from among the various rules.

2. The rule management device according to claim 1.

6. The evaluation of the rule includes a favorable intention for the rule and a comment for the rule, The rule evaluation registration unit registers a favorable intention toward the rule and a comment regarding the rule as the user's evaluation of the rule.

6. The rule management device according to claim 5.

7. The rule evaluation reference unit further includes a rule evaluation reference unit that displays the evaluation of the rule registered by the rule evaluation registration unit on a display unit of a terminal device of a user who refers to the rule.

2. The rule management device according to claim 1.

8. Register various rules that apply to users who belong to the group. Searching for a desired rule from among the various registered rules; displaying the contents of the searched rule on a display unit of a terminal device operated by the user; and receiving and registering an evaluation by the user of the rule from the terminal device; A rule management method comprising:

9. Retrieving the rules includes: Identifying a rule that is frequently viewed based on the number of accesses to the rule within a predetermined period of time, and displaying information corresponding to the identified rule on a display unit of the terminal device; and and searching for the rule corresponding to the information from among the various rules in accordance with the selection of the information displayed on the display unit of the terminal device.

9. The rule management method according to claim 8.

10. The registering of the rule includes registering a rule identifier for identifying the rule and a tag associated with the rule in association with each other, retrieving the rules Identifying a tag having a high access frequency from among the tags linked to the rules accessed within a predetermined period of time, and displaying information corresponding to the identified tag on a display unit of the terminal device; and and searching for a rule associated with a tag corresponding to the information from among the various rules in accordance with a selection of the information displayed on the display unit of the terminal device.

9. The rule management method according to claim 8.

11. Retrieving the rules includes: Displaying a search box for inputting keywords on a display unit of the terminal device; and searching for the rule including the keyword from among the various rules.

9. The rule management method according to claim 8.

12. storing any of the rules as a favorite rule for each of the users; Retrieving the rules includes: Displaying information corresponding to the user's favorite rules on a display unit of the terminal device; and and searching for the favorite rule corresponding to the information from among the various rules in accordance with the selection of the information displayed on the display unit of the terminal device.

9. The rule management method according to claim 8.

13. Registering the evaluation of the rule means registering a favorable intention for the rule and a comment on the rule as the evaluation by the user of the rule.

13. The rule management method according to claim 12.

14. The method further includes displaying an evaluation of the registered rule on a display unit of a terminal device of a user who refers to the rule.

9. The rule management method according to claim 8.

Images