CN110969401A - Method and device for detecting conflict of project execution schemes - Google Patents
Method and device for detecting conflict of project execution schemes Download PDFInfo
- Publication number
- CN110969401A CN110969401A CN201811140816.9A CN201811140816A CN110969401A CN 110969401 A CN110969401 A CN 110969401A CN 201811140816 A CN201811140816 A CN 201811140816A CN 110969401 A CN110969401 A CN 110969401A
- Authority
- CN
- China
- Prior art keywords
- conflict
- project
- execution
- sod
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Engineering & Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Marketing (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the invention discloses a method and a device for detecting conflict of project execution schemes, which comprises the following steps: in the SOD model constructed based on the principle of separating SOD from duties, the item execution information corresponding to the item execution scheme is input, and then the SOD model can be operated based on the input first item execution information to obtain the output result of the SOD model, so that whether the item execution scheme has conflict or not can be determined and displayed according to the second output result. In this embodiment, the SOD model is used to detect and display conflicts in the project execution schemes, so that the approver can modify the conflicts detected in the project execution schemes, and the modified project execution schemes without conflicts are used in the actual project execution process, thereby avoiding risks in the project execution process.
Description
Technical Field
The present invention relates to the field of data processing, and in particular, to a method and an apparatus for performing conflict detection on a project execution scheme.
Background
In the project execution process, risks such as unclear Duties and overlarge authority need to be avoided according to a Separation of Duties (SOD for short) principle. In particular, when the same executive completes multiple tasks or performs multiple process steps, asset abuse or loss may result, increasing the likelihood of errors and fraud, i.e., conflicts in assignment of tasks by the executive may exist in the project execution scenario, thereby resulting in a risk to the project execution process.
Disclosure of Invention
The technical problem to be solved by the embodiments of the present invention is to provide a method for detecting a conflict in a project execution scheme, so that a conflict existing in the project execution scheme can be detected, and the conflict that can be detected in the project execution scheme can be modified, so that the project execution scheme without a conflict is used in an actual project execution process, so as to avoid a risk existing in the project execution process.
In a first aspect, an embodiment of the present invention provides a method for constructing a duty separation SOD model, including:
determining each object in the project execution scheme; wherein the objects comprise tasks, roles, and responsibilities involved with the project execution scheme;
defining whether the objects have conflict corresponding relation to form the SOD model; whether each object has a conflict corresponding relation or not meets the principle of separating SOD by responsibility.
In some possible embodiments, the conflict includes a task conflict, a role conflict, and/or a responsibility conflict.
In a second aspect, an embodiment of the present invention provides a method for performing conflict detection on a project execution scheme, where the method specifically includes:
inputting first item execution information corresponding to the first item execution scheme in the SOD model constructed by the method for constructing the duty separation SOD model in the first aspect;
running the SOD model based on the input first item execution information to obtain a first output result of the SOD model;
and determining whether the first item execution scheme has conflict or not according to the first output result and displaying.
In some possible embodiments, the first project execution information includes project execution requirement information and execution personnel allocation information corresponding to the first project execution plan;
in the SOD model constructed based on the principle of separating SOD from duties, inputting first item execution information corresponding to the first item execution scheme, the method includes:
inputting the project execution requirement information in the SOD model;
and inputting the executive personnel distribution information into the SOD model according to the project execution requirement information input into the SOD model.
In some possible embodiments, the project execution requirement information includes task information, role information and responsibility information, the task information is used for describing tasks involved in the project, the role information is used for describing roles involved by executives of the tasks in the project, and the responsibility information is used for describing roles involved by the roles in the project in executing the tasks.
In some possible embodiments, the project execution requirement information further includes environment information, and the environment information is used for describing the environment involved by the task in the project.
In some possible embodiments, a correspondence is defined in the SOD model as to whether there is a conflict between objects in the first project execution scheme, the objects including tasks, roles, and responsibilities involved in the first project execution scheme.
In some possible embodiments, the method further comprises:
under the condition that the first project execution scheme has conflict, determining an object corresponding to the conflict in the first project execution scheme according to the first output result and prompting;
the object corresponding to the conflict comprises the task, role and/or responsibility involved in the first project execution scheme.
In some possible embodiments, the method further comprises:
inputting second item execution information corresponding to the second item execution scheme in an SOD model constructed based on a duty separation SOD principle aiming at the second item execution scheme obtained by modifying the first item execution scheme according to the object corresponding to the conflict;
running the SOD model based on the second item execution information which is input to obtain a second output result of the SOD model;
and determining whether the first item execution scheme has conflict or not according to the second output result and displaying.
In a third aspect, an embodiment of the present invention further provides an apparatus for constructing a duty separation SOD model, including:
an object determination unit for determining each object in the project execution plan; wherein the objects comprise tasks, roles, and responsibilities involved with the project execution scheme;
a defining unit, configured to define whether there is a conflict correspondence between the objects to form the SOD model; whether each object has a conflict corresponding relation or not meets the principle of separating SOD by responsibility.
In some possible embodiments, the conflict includes a task conflict, a role conflict, and/or a responsibility conflict.
In a fourth aspect, an embodiment of the present invention further provides an apparatus for performing conflict detection on an item execution scheme, where the apparatus may specifically include:
a first input unit configured to input first item execution information corresponding to the first item execution scenario in the SOD model constructed by the apparatus for constructing a duty separation SOD model according to the third aspect;
a first operation unit, configured to operate the SOD model based on the input first item execution information, so as to obtain a first output result of the SOD model;
and the first display unit is used for determining whether the second project execution scheme has conflict or not according to the first output result and displaying the conflict.
In some possible embodiments, the first project execution information includes project execution requirement information and execution personnel allocation information corresponding to the first project execution plan;
the first input unit includes:
a first input subunit, configured to input the item execution requirement information in the SOD model;
and the second input subunit is used for inputting the executive personnel distribution information in the SOD model according to the project execution requirement information input in the SOD model.
In some possible embodiments, the project execution requirement information includes task information, role information and responsibility information, the task information is used for describing tasks involved in the project, the role information is used for describing roles involved by executives of the tasks in the project, and the responsibility information is used for describing roles involved by the roles in the project in executing the tasks.
In some possible embodiments, the project execution requirement information further includes environment information, and the environment information is used for describing the environment involved by the task in the project.
In some possible embodiments, a correspondence is defined in the SOD model as to whether there is a conflict between objects in the first project execution scheme, the objects including tasks, roles, and responsibilities involved in the first project execution scheme.
In some possible embodiments, the apparatus further comprises:
the determining unit is used for determining and prompting an object corresponding to the conflict in the first project execution scheme according to the first output result under the condition that the first project execution scheme has the conflict;
the object corresponding to the conflict comprises the task, role and/or responsibility involved in the first project execution scheme.
In some possible embodiments, the apparatus further comprises:
a second input unit, configured to input, in an SOD model constructed based on a role separation SOD principle, second item execution information corresponding to a second item execution scheme obtained by modifying the first item execution scheme according to the object corresponding to the conflict;
a second operation unit, configured to operate the SOD model based on the input second item execution information, so as to obtain a second output result of the SOD model;
and the second display unit is used for determining whether the second project execution scheme has conflict or not according to the second output result and displaying the conflict.
In a fifth aspect, an embodiment of the present invention further provides a storage medium, where the storage medium is used to store a program code, and the program code is used to execute the method for performing conflict detection on an item execution scheme according to the second aspect.
In a sixth aspect, an embodiment of the present invention further provides a processor, where the processor is configured to execute a program, where the program executes the method for detecting a conflict of the project execution scheme according to the second aspect.
In the embodiment of the invention, the SOD model constructed based on the principle of separating SOD from duties inputs the item execution information corresponding to the item execution scheme, and then the SOD model can be operated based on the input first item execution information to obtain the output result of the SOD model, so that whether the item execution scheme conflicts or not can be determined and displayed according to the second output result. In this embodiment, the SOD model is used to detect and display conflicts in the project execution schemes, so that the approver can modify the conflicts detected in the project execution schemes, and the modified project execution schemes without conflicts are used in the actual project execution process, thereby avoiding risks in the project execution process.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a schematic diagram of an exemplary application scenario in an embodiment of the present invention;
FIG. 2 is a schematic flow chart of a method for constructing a duty separation SOD model according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating a method for conflict detection of project execution schemes according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an apparatus for constructing a duty separation SOD model according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an apparatus for performing conflict detection on project execution schemes according to an embodiment of the present invention.
Detailed Description
The inventor has found that, during the execution of a project, if a plurality of tasks or a plurality of processes are performed by the same person, the assets of the project can be abused or lost, and the possibility of errors and cheating is increased. For example, during the execution of a project, the same person may be responsible for both the task of writing a project proposal and the task of approving the project proposal, thus increasing the possibility of fraud.
To this end, the embodiment of the present invention provides a method for performing conflict detection on a project execution scheme, which detects a conflict existing in the project execution scheme by using a constructed SOD model. Specifically, in the SOD model constructed based on the principle of separating SOD from duties, the item execution information corresponding to the item execution scheme is input, and then the SOD model is operated based on the input first item execution information to obtain the output result of the SOD model, so that whether the item execution scheme has a conflict or not can be determined and displayed according to the second output result. In this embodiment, the SOD model is used to detect and display conflicts in the project execution schemes, so that the approver can modify the conflicts detected in the project execution schemes, and the modified project execution schemes without conflicts are used in the actual project execution process, thereby avoiding risks in the project execution process.
For example, embodiments of the present invention may be applied to the exemplary scenario shown in FIG. 1. In this scenario, the user 101 may perform an input operation on the terminal 102, the terminal 102 may input item execution information corresponding to an item execution scheme in an SOD model that has been constructed based on the principle of separating SOD from duties based on the input operation of the user, then the terminal 102 may run the SOD model based on the input item execution information to obtain an output result of the SOD model, and then the terminal 102 may determine whether the item execution scheme has a conflict according to the output result and display the conflict to the user 101 through a display screen of the terminal 102.
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the embodiment of the present invention, a pre-constructed duty separation SOD model is used to implement conflict detection on a project execution scheme, and in order to facilitate understanding of the technical scheme of the embodiment of the present invention, a detailed description is first given below on a specific process for constructing the duty separation SOD model.
Referring to fig. 2, fig. 2 is a schematic flow chart illustrating a method for constructing a duty separation SOD model according to an embodiment of the present invention, where the method specifically includes:
s201: objects in a project execution plan are determined, wherein the objects include tasks, roles, and responsibilities involved in the project execution plan.
In this example, the constructed SOD model followed the principle of SOD. The SOD principle is to follow a principle of separating different responsibilities, and can be used to achieve reasonable organization and division of labor, so that the SOD model constructed based on the SOD principle can perform conflict detection on each object in the first project execution scheme to determine whether a conflict exists in the first project execution scheme.
It will be appreciated that there is a conflict with the project execution scheme, i.e., there is a conflict between objects in the project execution scheme, such as a conflict between tasks and/or assumed roles that a role needs to complete, a conflict between roles and assumed roles that the role assumes, etc. For example, during the execution of a project, the same person may be responsible for both the task of writing a project proposal and the task of approving a project proposal, thus increasing the likelihood of fraud and thus the task the user needs to perform and the duties that are assumed to be conflicting. Based on this, when constructing the SOD model for detecting whether there is a conflict in the project execution plan, it is necessary to determine the task, role, responsibility, and the like involved in the project execution plan.
S202: defining whether each object has a corresponding relation of conflict or not to form an SOD model, wherein whether each object has a corresponding relation of conflict or not meets the principle of separating SOD by duty.
In this embodiment, whether a conflict exists in the project execution scheme is detected, that is, whether a conflict exists between objects in the project execution scheme is detected. Based on this, the SOD model can be constructed by defining the correspondence of whether there is a conflict between objects in the project execution plan, and of course, the correspondence is defined based on the SOD principle. For example, a corresponding relationship that the roles of the "design architecture" and the "comment architecture" are in conflict with each other in the same role can be defined, a corresponding relationship that the role of the "program developer" is in conflict with the role of the "system test", a corresponding relationship that the role of the "tester" is in conflict with the role of the "system test", and the like can be defined.
As an example, the defined correspondence relationship includes a correspondence relationship that may include whether there is a conflict between roles, whether there is a conflict between roles and tasks, whether there is a conflict between roles, and of course, whether there is a conflict between roles and tasks, and the like. For example, for the same executive (or role) to perform both the task of writing the document of the requirement and the task of approving the document of the requirement, it may be considered that the task/role to be executed by the role has conflict, and thus, the corresponding relationship among the role, the task and the role is established.
In this way, after the SOD model is constructed, whether the correspondence between the objects involved in the project execution plan is appropriate can be detected by using the SOD model, so as to detect conflicts between the objects in the project execution plan, specifically, task conflicts, role conflicts, and/or responsibility conflicts in the project execution plan.
Specifically, referring to fig. 3, fig. 3 is a schematic flowchart illustrating a method for detecting a conflict of a project execution scheme in an embodiment of the present invention, where the method specifically includes:
s301: in the SOD model constructed based on the principle of separating SOD function, the first item execution information corresponding to the first item execution scheme is input.
In this embodiment, when performing the collision detection by using the constructed SOD model, the input may be the first item execution information corresponding to the first item execution scheme. In some possible embodiments, the first project execution information may include project execution requirement information and execution personnel allocation information corresponding to the first project execution plan. The project execution requirement information is information such as a task, a role, and a responsibility involved in the execution of the first project execution plan, and the executive assignment information is assignment information indicating what role, what task, or what responsibility the first project execution plan is specifically assigned to the worker when the first project execution plan is executed.
Then, in an exemplary embodiment, the item execution requirement information corresponding to the first item execution scheme may be input in the SOD model, and the executive personnel allocation information may be input in the SOD model according to the item execution requirement information already input in the SOD model, thereby completing the input of the first item execution information.
In some possible designs, the project execution requirement information corresponding to the first project execution plan may include task information, role information, and responsibility information. The task information is used for describing tasks involved in the project (namely tasks required to be completed), such as a task of "collecting project results" in the project, a task of "writing required documents", and the like; the role information is used for describing roles related to executives of tasks in the project, such as testers, and is used for executing tasks of 'performing system test'; the responsibility information is used for describing the responsibility involved in the role in the project when performing the task, for example, when the management layer personnel approves the written project proposal, the responsibility of the management layer personnel is to approve the project proposal.
Of course, in addition to the task information, role information and responsibility information, in some possible embodiments, the project execution requirement information may further include environment information for specifying an environment where the role in the SOD model has an access right, such as a production environment, a test environment, and the like.
When the first item execution information corresponding to the first item execution scheme is input into the SOD model, after the SOD model is run, whether a conflict exists in the first item execution scheme can be detected according to the correspondence between the objects defined in the SOD model. In some possible designs, the SOD model may be specifically an SOD matrix model, that is, the correspondence between each object in the SOD matrix model may be arranged in a matrix manner.
S302: and running the SOD model based on the input first item execution information to obtain a first output result input by the SOD model.
In this embodiment, the SOD model may be run after the first item has been executed with the information input value SOD model. In this way, the SOD model can detect whether there is a conflict in the first item execution scenario according to the input first item execution information, and output the obtained detection result as a first output result.
S303: and determining whether the first project execution scheme has conflict or not according to the first output result and displaying.
In this embodiment, the first output result output by the SOD model is a result of detecting a conflict of the SOD model for the first project execution scheme, so that after the SOD model outputs the first output model, the first output result may be analyzed to determine whether a conflict exists in the first project execution scheme, where the conflict includes an existing conflict and a potential conflict. Meanwhile, the determined conflict result can be displayed, so that in practical application, personnel at an approval layer can be prompted to approve the first project execution scheme according to the display condition, and the conflict place in the first project execution scheme is solved. In practice, for these existing conflicts or potential conflicts, the examination and approval level personnel can analyze the various latitudes of the project to determine the root cause of the conflict in the project and resolve the conflict.
It is noted that for conflicts in the first project execution scenario that have been attempted by the approval level personnel but are still unresolved, supplemental controls may be implemented to reduce the risk of the first project execution scenario during execution. The supplementary control means that corresponding measures are taken for conflicts or potential conflicts that have occurred in the project. It can be understood that executing the corresponding supplementary control can ensure that the analysis performed by the SOD model conforms to the task allocation and personnel arrangement of the first project execution scheme, effectively reduce the risk caused by conflict, and ensure that all participating roles and tasks are in duty separation management and control.
In some possible scenarios, when the partial supplementary control cannot be executed due to the limitation of various factors such as conditions, the situation may be listed as a risk, and the risk may be logged in a risk log, so that the risk log may be fed back to the client and/or the project administrator to determine the corresponding risk control measure in the actual application.
Further, after the approval-layer personnel modifies the first project execution scheme, the obtained modified first project execution scheme may still have a conflict (such as a potential conflict), and therefore, in order to further reduce the risk of the modified first project execution scheme in the execution process, in this embodiment, the SOD model may also be continuously utilized to perform conflict detection on the modified first project execution scheme.
Specifically, in an SOD model constructed based on the principle of separating SOD from duties, second item execution information corresponding to a second item execution scheme is input, where the second item execution scheme is obtained by modifying a first item execution scheme according to an object corresponding to a detected conflict, that is, the modified first item execution scheme; then, based on the second item execution information that has been input, the SOD model may be run again to obtain a second output result output by the SOD model, and the result may be analyzed to determine whether the second item execution scheme has a conflict, and the determination result is displayed.
In this embodiment, the constructed SOD model can be used to detect conflicts in the project execution scheme. Specifically, in the SOD model constructed based on the principle of separating SOD from duties, the item execution information corresponding to the item execution scheme is input, and then the SOD model is operated based on the input first item execution information to obtain the output result of the SOD model, so that whether the item execution scheme has a conflict or not can be determined and displayed according to the second output result. In this embodiment, the SOD model is used to detect and display conflicts in the project execution schemes, so that the approver can modify the conflicts detected in the project execution schemes, and the modified project execution schemes without conflicts are used in the actual project execution process, thereby avoiding risks in the project execution process.
In addition, the embodiment of the invention also provides a device for constructing the duty separation SOD model. Referring to fig. 4, fig. 4 is a schematic structural diagram of an apparatus for constructing a duty separation SOD model according to an embodiment of the present invention, where the apparatus 400 may specifically include:
an object determination unit 401 configured to determine each object in the project execution plan; wherein the objects comprise tasks, roles, and responsibilities involved with the project execution scheme;
a defining unit 402, configured to define whether there is a conflict correspondence relationship between the objects to form the SOD model; whether each object has a conflict corresponding relation or not meets the principle of separating SOD by responsibility.
In some possible embodiments, the conflict includes a task conflict, a role conflict, and/or a responsibility conflict.
Thus, after the SOD model is constructed, the SOD model can be used to detect whether the correspondence between the objects involved in the project execution plan is appropriate, so as to detect conflicts between the objects in the project execution plan.
Specifically, the embodiment of the present invention further provides a device for performing conflict detection on a project execution scheme. Referring to fig. 5, fig. 5 is a schematic structural diagram illustrating an apparatus for performing conflict detection on an item execution scheme according to an embodiment of the present invention, where the apparatus 500 may specifically include:
a first input unit 501, configured to input first item execution information corresponding to the first item execution scheme in an SOD model that has been constructed based on a role separation SOD principle;
a first operation unit 502, configured to operate the SOD model based on the input first item execution information, so as to obtain a first output result of the SOD model;
a first display unit 503, configured to determine whether the first item execution scheme has a conflict and display according to the first output result.
In some possible embodiments, the first project execution information includes project execution requirement information and execution personnel allocation information corresponding to the first project execution plan;
the first input unit 501 includes:
a first input subunit, configured to input the item execution requirement information in the SOD model;
and the second input subunit is used for inputting the executive personnel distribution information in the SOD model according to the project execution requirement information input in the SOD model.
In some possible embodiments, the project execution requirement information includes task information, role information and responsibility information, the task information is used for describing tasks involved in the project, the role information is used for describing roles involved by executives of the tasks in the project, and the responsibility information is used for describing roles involved by the roles in the project in executing the tasks.
In some possible embodiments, the project execution requirement information further includes environment information, and the environment information is used for describing the environment involved by the task in the project.
In some possible embodiments, a correspondence is defined in the SOD model as to whether there is a conflict between objects in the first project execution scheme, the objects including tasks, roles, and responsibilities involved in the first project execution scheme.
In some possible embodiments, the apparatus 500 further comprises:
the determining unit is used for determining and prompting an object corresponding to the conflict in the first project execution scheme according to the first output result under the condition that the first project execution scheme has the conflict;
the object corresponding to the conflict comprises the task, role and/or responsibility involved in the first project execution scheme.
In some possible embodiments, the apparatus 500 further comprises:
a second input unit, configured to input, in an SOD model constructed based on a role separation SOD principle, second item execution information corresponding to a second item execution scheme obtained by modifying the first item execution scheme according to the object corresponding to the conflict;
a second operation unit, configured to operate the SOD model based on the input second item execution information, so as to obtain a second output result of the SOD model;
and the second display unit is used for determining whether the second project execution scheme has conflict or not according to the second output result and displaying the conflict.
In the embodiment of the invention, the SOD model constructed based on the principle of separating SOD from duties inputs the item execution information corresponding to the item execution scheme, and then the SOD model can be operated based on the input first item execution information to obtain the output result of the SOD model, so that whether the item execution scheme conflicts or not can be determined and displayed according to the second output result. In this embodiment, the SOD model is used to detect and display conflicts in the project execution schemes, so that the approver can modify the conflicts detected in the project execution schemes, and the modified project execution schemes without conflicts are used in the actual project execution process, thereby avoiding risks in the project execution process.
In addition, an embodiment of the present invention further provides an apparatus for performing conflict detection on a project execution scheme, where the apparatus includes:
a processor and a memory;
the memory is used for storing program codes and transmitting the program codes to the processor;
the processor is configured to execute the method for conflict detection of the project execution scheme according to any one of the embodiments mentioned in the foregoing embodiment shown in fig. 3 according to the instructions in the program code.
Furthermore, an embodiment of the present invention provides a storage medium, where the storage medium is configured to store a program code, and the program code is configured to execute the method for detecting a conflict of an item execution scheme according to any one of the embodiments shown in fig. 3.
Furthermore, an embodiment of the present invention provides a processor, where the processor is configured to execute a program, where the program executes a method for detecting a conflict of an item execution scheme, which is implemented in any one of the embodiments shown in fig. 3.
In the embodiments of the present invention, the "first" in the names of the "first item execution scheme", "first output result", "first input unit", "first operation unit", "first display unit", and the like is used merely as a name identifier, and does not represent the first in sequence. The same applies to "second" etc.
As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps in the above embodiment methods can be implemented by software plus a general hardware platform. With this understanding, the technical solution of the present invention can be embodied in the form of a software product, which can be stored in a storage medium, such as a read-only memory (ROM)/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network communication device such as a router, etc.) to execute the method according to the embodiments or some parts of the embodiments of the present invention.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the method embodiments and apparatus embodiments are substantially similar to the system embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the system embodiments for related points. The above-described embodiments of the apparatus and system are merely illustrative, wherein modules described as separate parts may or may not be physically separate, and parts shown as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only for the preferred embodiment of the present invention and is not intended to limit the scope of the present invention. It should be noted that, for a person skilled in the art, several modifications and refinements can be made without departing from the invention, and these modifications and refinements should be regarded as the protection scope of the present invention.
Claims (13)
1. A method of constructing a duty separation SOD model, comprising:
determining each object in the project execution scheme; wherein the objects comprise tasks, roles, and responsibilities involved with the project execution scheme;
defining whether each object has conflict corresponding relation to form an SOD model; whether each object has a conflict corresponding relation or not meets the principle of separating SOD by responsibility.
2. The method of claim 1, wherein the conflict comprises a task conflict, a role conflict, and/or a role conflict.
3. A method for conflict detection for project execution schemes, comprising:
inputting first item execution information corresponding to the first item execution scheme in the SOD model constructed by claim 1 or 2;
running the SOD model based on the input first item execution information to obtain a first output result of the SOD model;
and determining whether the first item execution scheme has conflict or not according to the first output result and displaying.
4. The method of claim 3, wherein the first project execution information includes project execution demand information and executive assignment information corresponding to the first project execution plan;
in the SOD model constructed based on the principle of separating SOD from duties, inputting first item execution information corresponding to the first item execution scheme, the method includes:
inputting the project execution requirement information in the SOD model;
and inputting the executive personnel distribution information into the SOD model according to the project execution requirement information input into the SOD model.
5. The method of claim 4, wherein the project execution requirement information comprises task information, role information and responsibility information, the task information is used for describing tasks involved in the project, the role information is used for describing roles involved by executives of the tasks in the project, and the responsibility information is used for describing roles involved by the roles in the project in executing the tasks.
6. The method of claim 5, wherein the project execution requirement information further comprises environment information, and the environment information is used for describing the environment involved in the task in the project.
7. A method according to claim 3, wherein a correspondence is defined in the SOD model as to whether there is a conflict between objects in the first project execution scheme, said objects comprising tasks, roles and responsibilities involved in the first project execution scheme.
8. The method of claim 3, further comprising:
under the condition that the first project execution scheme has conflict, determining an object corresponding to the conflict in the first project execution scheme according to the first output result and prompting;
the object corresponding to the conflict comprises the task, role and/or responsibility involved in the first project execution scheme.
9. The method of claim 8, further comprising:
inputting second item execution information corresponding to the second item execution scheme in an SOD model constructed based on a duty separation SOD principle aiming at the second item execution scheme obtained by modifying the first item execution scheme according to the object corresponding to the conflict;
running the SOD model based on the second item execution information which is input to obtain a second output result of the SOD model;
and determining whether the second project execution scheme has conflict or not according to the second output result and displaying the conflict.
10. An apparatus for constructing a duty separation SOD model, comprising:
an object determination unit for determining each object in the project execution plan; wherein the objects comprise tasks, roles, and responsibilities involved with the project execution scheme;
a defining unit, configured to define whether there is a conflict correspondence between the objects to form the SOD model; whether each object has a conflict corresponding relation or not meets the principle of separating SOD by responsibility.
11. An apparatus for conflict detection for project execution schemes, comprising:
a first input unit for inputting first item execution information corresponding to the first item execution scheme in the SOD model constructed by claim 10 or 11;
a first operation unit, configured to operate the SOD model based on the input first item execution information, so as to obtain a first output result of the SOD model;
and the first display unit is used for determining whether the first item execution scheme has conflict or not according to the first output result and displaying the conflict.
12. A storage medium for storing program code for performing the method for conflict detection for project execution schemes of any of claims 3 to 9.
13. A processor configured to run a program, wherein the program when running performs the method for conflict detection for project execution schemes of any of claims 3 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811140816.9A CN110969401A (en) | 2018-09-28 | 2018-09-28 | Method and device for detecting conflict of project execution schemes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811140816.9A CN110969401A (en) | 2018-09-28 | 2018-09-28 | Method and device for detecting conflict of project execution schemes |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110969401A true CN110969401A (en) | 2020-04-07 |
Family
ID=70027780
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811140816.9A Pending CN110969401A (en) | 2018-09-28 | 2018-09-28 | Method and device for detecting conflict of project execution schemes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110969401A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020120482A1 (en) * | 2001-02-26 | 2002-08-29 | International Business Machines Corporation | Separations-of-duties analysis tool for object-oriented integrated enterprise wide computing applications |
| US20100082377A1 (en) * | 2008-09-26 | 2010-04-01 | International Business Machines Corporation | Risk Evaluation of Conflicts in Separation of Duties |
| CN103530106A (en) * | 2012-07-02 | 2014-01-22 | 国际商业机器公司 | Method and system of context-dependent transactional management for separation of duties |
-
2018
- 2018-09-28 CN CN201811140816.9A patent/CN110969401A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020120482A1 (en) * | 2001-02-26 | 2002-08-29 | International Business Machines Corporation | Separations-of-duties analysis tool for object-oriented integrated enterprise wide computing applications |
| US20100082377A1 (en) * | 2008-09-26 | 2010-04-01 | International Business Machines Corporation | Risk Evaluation of Conflicts in Separation of Duties |
| CN103530106A (en) * | 2012-07-02 | 2014-01-22 | 国际商业机器公司 | Method and system of context-dependent transactional management for separation of duties |
Non-Patent Citations (1)
| Title |
|---|
| 李梓: "基于权限职责分离矩阵的ERP系统风险控制", 《中国管理信息化》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8296615B2 (en) | System and method for generating data migration plan | |
| CN107402880B (en) | Test method and electronic equipment | |
| Aranha et al. | An estimation model for test execution effort | |
| CN109901968A (en) | A kind of automation page data method of calibration and device | |
| US20140113257A1 (en) | Automated evaluation of programming code | |
| CN111782551B (en) | Test method and device for block chain item and computer equipment | |
| CN112966438A (en) | Machine learning algorithm selection method and distributed computing system | |
| CN114610620B (en) | Testing method, device, equipment and storage medium of approval process | |
| US20150186195A1 (en) | Method of analysis application object which computer-executable, server performing the same and storage media storing the same | |
| CN110688173B (en) | Positioning method and device of components in cross-platform interface framework and electronic equipment | |
| US9208006B2 (en) | Recovery Maturity Model (RMM) for readiness-based control of disaster recovery testing | |
| CN109542496B (en) | Method, device and system for determining incremental code | |
| CN116737580A (en) | Regression testing range determining method, device, equipment and storage medium | |
| CN112035350B (en) | Test method and device for block chain system and computer equipment | |
| Anand et al. | Testing resource allocation for software with multiple versions | |
| CN115840560A (en) | Management system for software development process | |
| CN112363933A (en) | Automatic verification method and device for word paragraph table, computer equipment and storage medium | |
| CN107229487B (en) | Code processing method and device | |
| CN110674491B (en) | Method and device for real-time evidence obtaining of android application and electronic equipment | |
| CN110414186B (en) | Data asset segmentation verification method and device | |
| CN110969401A (en) | Method and device for detecting conflict of project execution schemes | |
| US9208045B2 (en) | Testing integrated business systems | |
| CN113946514B (en) | Code pre-integration method, device and system | |
| CN115712571A (en) | Interactive service test device, interactive service test device, computer equipment and storage medium | |
| CN110851344B (en) | Big data testing method and device based on complexity of calculation formula and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200407 |