JP2005149414A - Retrieval method for project risk, evaluation system and common database utilization method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a database utilization method and an evaluation system, in which potential risk and a problem which should be treated beforehand are evaluated comprehensively and treated in a planning stage of a project, by referring to a past result database . <P>SOLUTION: A risk evaluation sheet 10 and a problem management sheet 11 which a project promoter can refer to/update are stored in a shared data base 3. An evaluation point is inputted in a risk evaluation item in the risk evaluation sheet. Problems, failures generated during project execution and their treating contents are inputted in the problem management sheet. Scale of the project to be examined, and the scale of a project whose evaluation point, etc. is similar are extracted from the past result data base of a past project and displayed in a radar chart system. Candidates for a reference project are displayed, and risk becomes clear, by carrying out risk evaluation at the planning stage of a new project. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an auxiliary means used for examining potential risks or proactive measures at the project planning stage, which is suitable for use in a department that handles a large number of software development projects. However, it is not limited to the project system, development form, development environment, and applied technology.

  Regarding potential risks and proactive measures in software development projects, when considering based on the past experience or intuition of one manager, or referring to similar projects in their department, potential risks and proactive measures In many cases, measures were being considered.

  However, in the above-mentioned conventional technology, 1) Projects that are collected as reference projects are often limited to projects within their own section or department, and the total amount of data tends to be extremely small. 2) Reference projects The selection conditions tend to be limited conditions such as applied technology and development scale, and it is difficult to grasp the problems and countermeasures caused by the risks of the project. 3) There is a similar project to be referred to However, there are many cases where the method of storing information on the problem and the contents of correspondence varies depending on the project, and it is difficult to search and refer to it.

  In this regard, as a technique for solving the above problem, there is a system described in Patent Document 1 that displays a countermeasure result of a project having a similar risk evaluation result.

JP-A-11-66150

  The technique described in Patent Document 1 narrows down the risk items themselves appearing in the risk evaluation result from the failure countermeasure examples of past projects by the system. However, in reality, countermeasure examples searched for a certain risk item are often not appropriate or impossible to execute depending on the state of other risk items. In addition, there is a possibility that a new problem may occur due to the risk evaluation value bias of each risk item. Furthermore, in the above technology, only cases where countermeasures are implemented can be referred to.

  An object of the present invention is to provide a countermeasure case retrieval method and retrieval system based on a composite evaluation of project risks.

  The countermeasure case search system by the composite evaluation of the project risk of the present invention is realized by the following means.

(1) Create and use "risk evaluation sheet" and "problem management sheet" common to development departments (development sections). 1) List risk assessment items on the risk assessment sheet. Organize risk assessment items into major items. In the project planning stage, an evaluation score (in this specification, the higher the evaluation score, the higher the risk is) is entered in the risk evaluation sheet.
2) Provide a corresponding risk item number column in the problem management sheet. During the development to the stable operation stage, when inputting problems and failures found during the development process and corresponding contents, risk item numbers that lead to the cause of the problem are selected and entered.
(2) The input information of the risk evaluation sheet / problem management sheet is stored in a shared DB that can be referenced and updated by each development department.
(3) Once the risk evaluation points for the risk evaluation items on the risk evaluation sheet are entered and extraction conditions are set, a system that extracts a plurality of applicable projects and displays a chart with risk evaluation points for each major item, for example, a radar chart create.

  Furthermore, by selecting the extracted project, the problem management sheet information of the project is displayed in a form linked to the format of the risk management sheet. As an extraction condition, a search key related to characteristics relating to risk evaluation points such as similarity regarding bias of evaluation scores in units of large items and similarity regarding total score of risk evaluation points is used.

  According to the measure case retrieval system based on the composite evaluation of project risk according to the present invention, information is organized based on a common format, so that there is an advantage that reference is easy. In addition, because projects with the same type of risk can be extracted and used as a reference, measures can be taken in advance for high-risk parts, and problems that may occur due to similar risk biases are identified in advance. It is also possible to grasp and take measures.

  Furthermore, when selecting a reference project, the degree of freedom of selection according to the purpose is maintained, such as selecting similarities in risk bias or selecting similarities in risk evaluation scores in specific fields. . If graphing is performed at the time of selection, there is an advantage that it is easy to make a judgment.

  In risk management, it is important to understand detected problems and failures even for problems that have not been solved yet.

  Hereinafter, a countermeasure case search system based on a composite evaluation of project risks according to an embodiment of the present invention will be described with reference to the drawings. At that time, it is divided into three stages of a preparation stage, a data accumulation process, and a utilization stage, and the overall configuration and processing flow are shown in FIG. 1, and detailed examples will be described with reference to FIGS.

1. Preparatory stage First, in the countermeasure case search system 1 (hereinafter referred to as “this system”) based on the composite assessment of project risks shown in FIG. 1, “risk evaluation sheet” and “problem management sheet” Are prepared on the shared DB 3 (risk evaluation sheet database 10 and problem management sheet database 11) that can be referred to and updated by all development departments, and the input person of each project inputs the information on these shared DBs 3 I will do it. The risk evaluation sheet database 10 and the problem management sheet database 11 are associated with each other by a risk evaluation item number 10a and a corresponding risk evaluation item number 11a described later.

An example of a “risk evaluation sheet” 21 and a “problem management sheet” 22 is shown with reference to FIGS.
First, as shown in FIG. 2A, the development department, project name, development scale, and applied technology are registered as the basic information 20 of the project. Here, since the project name is a keyword for identifying the target project in this system, the input check is performed so as to be unique within the system. As for the development scale, any type can be used as long as it can be calculated quantitatively, such as the number of development steps, the number of input / output files, and the number of input / output screens. ). In addition, as for applicable technology, there are a method of classification based on the base technology such as network technology and database management technology, a method of classification according to the type of business of the customer such as manufacturing industry and financial industry, etc. It may be used, and a plurality of classification methods may be used in combination. Also, in order to enable the system to automatically determine that the applied technology is the same type, several options are prepared in advance, and the input person selects and inputs them.

  The risk evaluation sheet 21 is provided with an evaluation score column (column 26) for listing risk evaluation items (column 25) and assigning an evaluation score for each risk evaluation item. In this embodiment, the evaluation score is a five-level evaluation from 1 to 5, and the highest risk evaluation score is 5. However, if the evaluation method can be calculated quantitatively, another evaluation method (how to assign evaluation points) ) For the method of assigning evaluation points, a separate evaluation standard is set up so that it can be referred to as appropriate so that it becomes an objective scale common to all projects regardless of the subjectivity of the input person. For example, with regard to the evaluation item “Is there an actual transaction with the ordering party” in FIG. 2B, 5 points are given when there is no actual transaction, and the points are sequentially reduced one by one depending on the number of transactions and the total transaction amount. Establish an evaluation standard. In addition, regarding the evaluation item “Will the customer select the product of the other company?”, If the customer is completely selected according to the circumstances of the customer, the risk is high and the evaluation score is 5. If the selection is completely left to the Company If the risk is low, the evaluation point is 1, and in the middle case, it is 2-4 depending on the degree of initiative. The risk evaluation items are organized into large items (column 24). A risk item number is assigned to each risk evaluation item (column 23). In addition, all projects that are the targets of this system shall enter evaluation points for common large items and evaluation items.

  On the other hand, in the problem management sheet (22), the discovery process and the problem are simultaneously input, and the corresponding risk item number input field (column 27) is input, and then the countermeasure / effect input field is input. It has become. As the corresponding risk item number, a plurality of risk item numbers may be input.

2. Data Accumulation Process Next, the risk assessment 12 in FIG. 1 will be described. At the project planning stage, input processing is performed for the basic project information 20 and the evaluation score column (column 26) of the risk evaluation sheet.

  Next, regarding the problem 13 and the countermeasure 14 in FIG. 1, in the process of starting development to stable operation, the detected problem and failure and the corresponding contents are input to the problem management sheet 22. At that time, an item that seems to be related to the cause of the problem is selected from the risk evaluation items (fixed items) 25 of the risk evaluation sheet 21, and the corresponding risk item number 23 is input in the column 27. A plurality of correspondence risk item numbers 27 can be selected. If a risk item number is specified so that the corresponding risk item number to be entered does not depend on the subject's subjectivity for problems with the same content, problems that have been input in association with the risk item number in the past May be displayed (not shown). In addition, by specifying a keyword included in the input problem, a list of previously input problems including the keyword and corresponding risk item numbers may be displayed (not shown). By causing the input person to refer to these lists and inputting the corresponding risk item numbers, variations in the corresponding risk item numbers by the input person can be prevented.

  By performing the risk assessment 12, problem extraction 13 and countermeasure examination 14 of FIG. 1 in each project, information on the risk assessment sheet / problem management sheet is accumulated in the shared DB.

3. Utilization process In the risk assessment of FIG. 1, the risk assessment sheet is entered in the assessment score column (FIG. 2: column 26) in the planning stage of the new project. By selecting and specifying the key described below as the search key 16, the project search / display server (computer) 5 searches for similar projects from the storage DB. A plurality of search keys can be selected.

Search key 1: A problem management sheet is input.
Search key 2: Similarity of evaluation score bias for large items.
Search key 3: The total score or average score of risk evaluation points is similar.
Search key 4: The development scale is similar.
Search key 5: Applicable technology is the same type.
Search key 6: The evaluation score of a specific large item is similar.

  Note that “similarity” here refers to the case where the numerical value of the corresponding item of the project in the accumulation DB is within ± 10% with respect to the numerical value such as the development scale / evaluation point of the new project, for example. .

  A reference project selection screen based on the search result of the system is displayed on the project selection screen 17 in FIG.

  FIG. 3A shows a display example of a radar chart. FIG. 3B shows a table corresponding to the radar chart. FIG. 3A is a diagram in which a radar chart display 31 is performed on a project extracted by the system with an evaluation point of a large item unit as an axis 30. FIG. 3B is a table in which the development department, the development scale, and the applied technology 34 are displayed together as the extracted project information 32 for supplementary information for selecting a reference project. This table has a selection check box 33. FIG. 3A and FIG. 3B correspond to each other, and a thick solid line is a new input project, and the other lines are radar chart displays related to past projects a to d. The radar chart has axes corresponding to major items such as orders, customers, difficulty, new technology and novelty, development schedule, development environment, etc., and evaluation points are plotted for each major item for each project. . A project to be displayed can be selected from a plurality of projects. Based on this radar chart, look at similarities or differences at a glance based on the balance, total score, the size of the score centered around the axis, the score of a certain item, the similarity of the shape without the absolute value of the score, etc. I can grasp it.

  For example, with respect to the input project, the project a and the project b have substantially the same evaluation point and a substantially similar shape. The project c has almost the same evaluation point and the shape is almost similar, and the project d is almost similar, but it can be seen that all the evaluation points are smaller than the input project.

  For example, if there is similarity in evaluation point bias, you can know future caution points regarding evaluation items with similar bias, and if there is similarity in overall shape, items of similar past projects as a whole It is necessary to refer to In this way, it becomes easier to predict risk by displaying a large amount of information in a radar chart. That is, there is an advantage that it is possible to provide a user interface that is easy for anyone to understand and does not require specialization.

  3A and 3B, it is possible to easily search past accumulated data based on the similarity of radar charts, so there are no problems when starting a development project. You can easily check whether it can occur.

  In the project selection 18 of FIG. 1, when a selection check box (reference numeral 33 in FIG. 3) of a project to be referred to is checked, the project is selected and a “risk-problem correspondence sheet” (reference numeral in FIG. 4) of the corresponding project. 41, 42).

  In order to simplify the analysis by the radar chart, only the difference of the new risk evaluation points from the average of all projects may be plotted and displayed so that the singular points can be easily understood. In addition, the singularity may be easily understood by normalizing so that the area inside the radar chart is the same. Alternatively, only projects with the same factors such as season, place, year, etc. may be displayed and displayed by project category. When a singular point is pointed, a problem related to the singular point and a countermeasure may be displayed.

  Also, in order to quickly display past radar charts, instead of displaying charts based on tables, a database that stores charts for each project is provided, and radar charts are displayed based on this database. , Can be displayed quickly.

  In the risk-problem correspondence sheet 19 of FIG. 1, the system displays a “risk-problem correspondence sheet” shown in FIG. At this time, information on the risk evaluation sheet is displayed according to the format of the risk evaluation sheet (reference numeral 41), and information on the problem management sheet is displayed for each risk item according to the format of the risk evaluation sheet using the corresponding risk item number as a key. Display (reference numeral 42). As a result, a risk-problem correspondence sheet corresponding to the risk item number can be created. Although the evaluation points can be reviewed as appropriate, posting the difference between the past evaluation points and the current evaluation points is useful for subsequent review. For example, at the time of project planning, if the evaluation item “Is the customer have specification determination capability?” Is set to 3 on the assumption that the customer has normal specification determination capability, the customer situation in the middle of the project If the evaluation score is changed to 5 afterwards due to frequent delays in the process due to frequent changes in specifications, the fact remains that way, so that later projects of the same type (applied technology, development scale, The characteristics of the radar chart are similar). In addition, there may be cases where the risk item number has no description of countermeasures / effects from the discovery process (not applicable).

  If this risk-problem correspondence sheet is used, the risk item number, large item, evaluation item corresponding to the risk item number, its evaluation point (from 1 to 5 in the figure), the discovery process, and the discovery process It is possible to list problems, countermeasures against them, and their effects. It is possible to grasp in advance prior measures for high-risk parts and problems that may occur due to similar risk bias, and take countermeasures. It will be easy.

  Application of the present invention also makes it possible to predict the best way to launch various projects.

It is a block diagram which shows the structural example of the countermeasure example search system by the composite evaluation of the project risk by one embodiment of this invention. FIG. 2A shows an example of basic information, and FIG. 2B shows an example format of a risk evaluation sheet and a problem management sheet. FIG. 3A is a display example of a reference project selection screen. FIG. 3A is a radar chart, and FIG. 3B is a table. It is a figure which shows the example of a display of the risk-problem correspondence sheet | seat of the reference project displayed.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... Risk evaluation sheet DB, 10a ... Risk item number, 11 ... Problem management sheet DB, 11a ... Corresponding risk item number, 12 ... Risk evaluation input, 13 ... Problem input, 14 ... Countermeasure input, 15 ... Risk evaluation input 16 ... Search key selection input, 17 ... Project selection screen display, 18 ... Project selection input, 19 ... Risk-problem correspondence sheet display screen, 20 ... Project basic information, 21 ... Risk assessment sheet, 22 ... Problem management sheet 23 ... Risk item column, 24 ... Large item column, 25 ... Evaluation item column, 26 ... Evaluation point column, 27 ... Corresponding risk item number column, 30 ... Radar chart axis, 31 ... Radar chart, 32 ... Extracted project information, 33 ... Selection check box, 34 ... Project supplement information, 41 ... Risk assessment sheet information, 42 ... Problem management sheet information.

Claims (5)

A risk item number assigned to a risk that has a common format format between different sections and between different projects and is created for each project and can be a risk factor in the execution of the project, and the risk item A risk evaluation sheet managed by an evaluation item related to the numbered risk factor, a risk evaluation point assigned to each evaluation item based on the magnitude of the risk, and a corresponding risk item corresponding to the risk item number The problem management sheet managed by the number, at least one selected from the problem finding process, the problem, the countermeasure, and the effect thereof can be input and referenced in common between the sections. Storing in the common database via input means;
In the planning stage of a new project, a step of inputting an initial risk evaluation point for each risk item number with respect to a new risk evaluation sheet relating to the new project by an input means;
A project risk search method comprising: using a computer to extract a description of a problem management sheet having a corresponding risk item number corresponding to the risk item number, using the risk item number corresponding to the initial evaluation point as a search key.   Further, at least one selected from a problem finding process, a problem, and a countermeasure that occurred between the start time of the new project and the time when the project is in a stable operation state is selected. 2. The project risk search method according to claim 1, wherein the step of inputting by the input means is sequentially performed for each corresponding risk item number. A method of utilizing a common database created based on the search method according to claim 1,
A step of inputting an evaluation point of a risk evaluation sheet at a planning stage of a new project by an input means;
Searching a similar project from the common database by a computer by selecting at least one of the following search keys 1 to 6 as a search key:
And a step of displaying a reference project selection screen based on the search result by a display means.
Search key 1: The problem management sheet is input.
Retrieval key 2: The evaluation item or the evaluation item biases of the large items obtained by collecting the related risk items among the evaluation items are similar.
Search key 3: The total score or average score of the risk evaluation points is similar.
Search key 4: The project development scale is similar.
Search key 5: The technology related to the project is the same.
Search key 6: The evaluation score of a specific large item is similar. A method of utilizing a common database created based on the search method according to claim 1,
The risk assessment of the new project is performed when reference is made to potential risks in the planning stage of the new project or at least one of the problems of other reference project candidates for proactive measures examination, countermeasure examples and their effects. The results and the risk evaluation values of multiple reference project candidates are displayed via the display means using a radar chart with the evaluation items or large items that summarize related items of the evaluation items and evaluation points as variables. And steps to
Based on the radar chart, reference project candidates that are related to the feature points are compared by comparing the feature points including the similarity of the graph shape in which a plurality of risk evaluation values related to the project are plotted or the similarity of the bias of the evaluation points. A common database utilization method including a step of extracting at least one of a problem related to the reference project candidate, a countermeasure example, and its effect through a display means. A risk item number that has a common format format between different sections and between different projects and is created for each project and can be a risk factor in the execution of the project, and the risk factor to which the risk item number is assigned A risk evaluation input unit for inputting a risk evaluation score of a project with respect to a risk evaluation sheet managed by the evaluation item related to the item, a risk evaluation point assigned to each evaluation item based on the magnitude of the risk, and
Each item for a problem management sheet having a corresponding risk item number input field corresponding to the risk item number, a problem finding step, a problem, a countermeasure and an effect Problems to be input and countermeasure input section,
The risk assessment sheet database that accumulates the risk assessment sheet, and the problem management sheet that is associated with the risk assessment sheet in the risk assessment sheet database by the risk item number and the corresponding risk item number Management sheet database,
A project search / display server that searches the risk evaluation sheet database and the problem management sheet database in response to input of a new risk evaluation point to the risk input unit, searches for related projects, and displays the contents thereof. Project risk assessment system.

Images