JP2012256211A - Support device, support method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce time required for evaluation and consideration of countermeasure in software development.SOLUTION: A support device includes: an input unit for accepting an input of action information that shows actions performed in the past for improving quality and progress in software development and the order of the actions performed, history data that includes planned values and actual values in the past of index showing quality and progress in the software development, and support object data that includes the planned values and actual values of index; a determination unit for classifying the history data into any one of multiple categories and grouping the data; a mapping list creation unit for creating a mapping list that shows all of action information included in the history data belonging to the group; a weight value calculation unit for determining a priority of the mapping list; and a proposal unit for classifying the support object data into any one of the multiple categories and outputting the mapping list that corresponds to a group corresponding to the classified categories to the outside so as to recognize the priority.

Description

  The present invention relates to a support device, a support method, and a program that support improvement in quality and progress in software development.

  In software development, a developer sets a quantitative index plan value for managing the quality of software and the progress of software development. Then, the developer compares the set plan value with the actual value, evaluates the quality of software and the progress of software development, and implements measures based on the evaluation result.

  The above evaluation and examination of countermeasures are left to each developer, and a developer without development know-how may make a mistake in evaluation or may not know appropriate countermeasures. In addition, even if the developer performs appropriate evaluation and countermeasures, it may take time to review the evaluation and countermeasures. Nowadays, software development is desired to be completed in a short period of time, and it is not desirable that evaluation and countermeasures take time.

  Therefore, it is required to shorten the time required for evaluation and examination of countermeasures in software development, and a technique for realizing this is disclosed in Patent Document 1, for example.

  In the technique disclosed in Patent Document 1, the test work management support apparatus accepts input of data related to quality reliability and test sufficiency. Next, the test work management support apparatus estimates the reliability of the quality of the software and the sufficiency of the test based on the received data. Then, the test work management support apparatus selects a predetermined message based on the estimation result and a predetermined advice rule, and outputs it as message data.

JP 7-146806 A

  Here, skilled developers in the field of software development analyze not only the quantitative indicators described above but also the know-how possessed by the developers to analyze the quality of software and the progress of software development, and evaluate and take countermeasures. Often implemented.

  The know-how, etc. possessed by individual developers is gradually accumulated. Skilled developers can reduce the time required for evaluation and examination of countermeasures by accumulating know-how and the like.

  In the technique disclosed in Patent Document 1 described above, a predetermined message based on a predetermined advice rule is selected. For this reason, it is not possible to utilize the know-how that is gradually accumulated as described above.

  Therefore, the technique disclosed in Patent Document 1 cannot be said to be sufficient to solve the problem of time required for evaluation and examination of countermeasures in software development.

  An object of the present invention is to provide a support device, a support method, and a program that can reduce the time required for evaluation and examination of countermeasures in software development.

In order to achieve the above object, the support device of the present invention includes behavior information indicating the actions performed in the past for improving quality and progress in software development and the order in which the actions were performed, and the quality and progress in the software development. An input unit that accepts input of historical data including past planned values and actual values of indicators indicating support, and support target data including planned values and actual values of the indicators;
The history data received by the input unit is classified into any of a plurality of predetermined categories based on past plan values and actual values included in the history data, and the classified history data is Based on the behavior information included in the history data, a determination unit that groups into a group associated with the category,
A mapping list generating unit that generates a mapping list that is associated with the group and represents all of the behavior information included in the history data belonging to the group;
A weight value calculator that determines the priority of the mapping list corresponding to the group based on the number of history data belonging to the group;
Based on the plan value and the actual value included in the support target data received by the input unit, the support target data is classified into one of the plurality of categories, and the group corresponding to the classified category is supported. And a proposal unit that outputs the mapping list to the outside so that the priority of the mapping list can be recognized.

In order to achieve the above object, the support method of the present invention is a support method in a support device for supporting software development,
Includes action information that indicates the actions taken in the past and the order in which the actions were taken to improve quality and progress in software development, and past planned and actual values of indicators that indicate the quality and progress in the software development Processing to accept history data;
The received history data is classified into any of a plurality of predetermined categories based on past plan values and actual values included in the history data, and the classified history data is included in the history data. Grouping into groups associated with the category based on
A process of generating a mapping list that is associated with the group and represents all of the behavior information included in the history data belonging to the group;
A process for determining the priority of the mapping list corresponding to the group based on the number of history data belonging to the group;
Processing for receiving input of support target data including the planned value and actual value of the indicator;
Based on the plan value and the actual value included in the received support target data, the support target data is classified into one of the plurality of categories, a mapping list corresponding to the group corresponding to the classified category, And outputting to the outside so that the priority of the mapping list can be recognized.

In order to achieve the above object, the program of the present invention provides a support device for supporting software development.
Includes action information that indicates the actions taken in the past and the order in which the actions were taken to improve quality and progress in software development, and past planned and actual values of indicators that indicate the quality and progress in the software development A function to accept historical data,
The received history data is classified into any of a plurality of predetermined categories based on past plan values and actual values included in the history data, and the classified history data is included in the history data. Based on the action information to be grouped into a group associated with the category,
A function of generating a mapping list associated with the group and representing all of the behavior information included in the history data belonging to the group;
A function of determining the priority of the mapping list corresponding to the group based on the number of history data belonging to the group;
A function of receiving input of support target data including the planned value and the actual value of the indicator;
Based on the plan value and the actual value included in the received support target data, the support target data is classified into one of the plurality of categories, a mapping list corresponding to the group corresponding to the classified category, And a function of outputting to the outside so that the priority of the mapping list can be recognized.

  Since the present invention is configured as described above, it is possible to provide know-how and the like gradually accumulated by skilled developers to developers who do not have development know-how.

  Therefore, it is possible to shorten the time required for evaluation and examination of countermeasures in software development.

It is a block diagram which shows the structure of one Embodiment of the assistance apparatus of this invention. It is a figure which shows an example of the log | history data memorize | stored in log | history DB with which the accumulation | storage part shown in FIG. 1 is provided. It is a figure which shows an example of a structure of the management table which manages the action information already memorize | stored in log | history DB shown in FIG. 2, (a) is a structure of the structure of the management table in case an action classification is "check" FIG. 8B is a diagram illustrating an example of a configuration of a management table when the action type is “measure”. It is a figure for demonstrating an example of the operation | movement which the determination part shown in FIG. 1 determines the category ID of the log | history data newly memorize | stored in log | history DB. It is a figure which shows an example of a structure of group DB with which the determination part shown in FIG. 1 is provided. It is a flowchart for demonstrating the operation | movement which the determination part shown in FIG. 1 groups the log | history data newly memorize | stored in log | history DB. It is a figure which shows an example of the mapping list | wrist produced | generated by the mapping list production | generation part shown in FIG. It is a figure which shows an example of a structure of the basic data table with which the mapping list production | generation part shown in FIG. 1 is provided.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a block diagram showing the configuration of an embodiment of the support apparatus of the present invention.

  As illustrated in FIG. 1, the support device 10 according to the present embodiment includes an accumulation unit 11, a determination unit 12, a mapping list generation unit 13, a weight value calculation unit 14, an input unit 15, a proposal unit 16, and a display. Part 17.

  The input unit 15 includes a product ID for uniquely identifying software to be developed, action information indicating the actions performed in the past for improving quality and progress in software development, and action information indicating the order of the actions, Shows past planned and actual values for each index that quantitatively indicates quality and progress in software development, priority element information that indicates the elements that are prioritized in the software development, and an evaluation of whether or not the above improvements have been realized Accepts input of history data including evaluation information. Then, the input unit 15 outputs the received history data to the storage unit 11. Further, the input unit 15 receives input of support target data including the above-described planned value and actual value for each index and priority element information. Then, the input unit 15 outputs the received support target data to the suggestion unit 16. Details of the priority element information and the planned value and actual value for each index will be described later.

  The storage unit 11 includes a history DB (Data Base). The accumulation unit 11 receives the history data output from the input unit 15. Then, the storage unit 11 uniquely identifies the received history data, and generates a history ID (Identification) indicating the history data. Then, the storage unit 11 stores the generated history ID and the received history data in association with each other in the history DB.

  FIG. 2 is a diagram illustrating an example of history data stored in the history DB included in the storage unit 11 illustrated in FIG. 1.

  In the history DB, as shown in FIG. 2, a history ID, a product ID, priority element information, a planned value and an actual value for each index, behavior information, and evaluation information are associated with each other.

  As described above, the priority element information is information indicating elements that are prioritized in software development. It is assumed that information that can be stored in the history DB as priority element information is predetermined. Here, as an example, Q (Quality: quality), C (Cost: price), and D (Delivery: delivery date) are set as priority element information that can be stored in the history DB.

  The planned value and actual value for each index are the planned value and actual value of an index that can be expressed as a numerical value in software development, such as bug density and test item density. The number of indices may be any number, but is assumed to be predetermined. Here, as an example, the index 1 and the index 2 are assumed to be two.

  In the action information, an action number indicating the order of actions performed to improve progress and quality in software development, action type information, action detailed information, and check result information are associated with each other.

  In the action type information, either “check”, “measure”, or “no action” is stored. Note that “check” is stored in the action type information corresponding to the action number 1. Further, “measure” or “no action” is stored in the action type information corresponding to the last action number.

  In the detailed action information, when “check” is stored in the corresponding action type information, a check item number indicating the check content is stored. Further, in the detailed action information, when “measure” is stored in the corresponding action type, a countermeasure number indicating the content of the countermeasure is stored. When “no action” is stored in the corresponding action type, nothing is stored in the action detailed information.

  The check result information is information that is stored only when the action type information is “check”. In the check result information, a check result when the check content indicated by the check item number stored in the corresponding action detailed information is performed is stored.

  The evaluation information is information indicating an evaluation as to whether the quality and progress in software development have improved as a result of performing the action indicated by the action information. Information that can be stored as evaluation information is determined in advance. Here, the information that can be stored as the evaluation information is two, ie, ◯ and X. ○ indicates that there was an improvement, and × indicates that there was no improvement. In addition to this, for example, numbers from 1 to 10 may be used as evaluation information in order from the lowest evaluation. In addition, what is necessary is just to make it evaluate based on the improvement degree of the progress before and behind implementation of the action which action information shows, for example, when priority element information is D (delivery date).

  Here, the history data stored in the history DB is data received by the input unit 15. When inputting the same behavior information as the behavior information already stored in the history DB as history data, it is desirable that the input person can select the behavior information stored in the history DB. This is for avoiding an increase in the scale of the history DB and appropriately performing grouping described later. For this purpose, there is a method of generating a management table for centrally managing action information already stored in the history DB.

  FIG. 3 is a diagram showing an example of the configuration of a management table for managing the action information already stored in the history DB shown in FIG. 2. FIG. 3A shows the management when the action type information is “check”. FIG. 6B is a diagram illustrating an example of the configuration of the management table, and FIG. 6B is a diagram illustrating an example of the configuration of the management table when the action type information is “measure”.

  The management table shown in FIG. 3A corresponds to the check item number already stored in the history DB as the action detail information, check content information indicating the check content indicated by the check item number, and the check item number. Information that can be taken as check result information is stored in association with each other. The management table is displayed on the display unit 17 when the history data input person inputs the history data. Thereby, the input person selects any of the check item numbers displayed on the display unit 17 when inputting the same action detail information as the action detail information included in the history data already stored in the history DB. Can do. Further, the input person can select any of the check result information corresponding to the selected check item number. Therefore, it is possible to avoid the same detailed behavior information and check result information from being stored in the history DB as different information.

  In addition, the management table shown in FIG. 3B stores the countermeasure number that is already stored in the history DB as the action detail information in association with the countermeasure content information that represents the countermeasure content indicated by the countermeasure number. Yes. Similar to the management table shown in FIG. 3A, this management table is displayed on the display unit 17 when the history data input person inputs the history data. Thereby, the input person can select the countermeasure number displayed on the display unit 17 when inputting the same action detail information as the action detail information indicated by the history data already stored in the history DB.

  Referring to FIG. 1 again, the determination unit 12 includes a group DB. When new history data is stored in the history DB included in the storage unit 11, the determination unit 12 compares the planned value and the actual value of the index included in the history data. Then, the determination unit 12 classifies the history data into any of a plurality of preset categories according to the comparison result. Specifically, the determination unit 12 determines a category ID for classifying the history data according to the comparison result. As a comparison method, for example, when there are two indices, index 1 and index 2, the determination unit 12 determines whether the actual value is larger than the plan value, whether the actual value and the plan value are equal, Compare whether or not is less than the planned value. In this case, the history data is classified into one of nine categories, and nine category IDs are set in advance. And the determination part 12 determines the category ID of the log | history data newly memorize | stored in log | history DB from nine category ID according to a comparison result.

  FIG. 4 is a diagram for explaining an example of an operation in which the determination unit 12 illustrated in FIG. 1 determines a category ID of history data newly stored in the history DB.

  Here, the number of indices is two, index 1 and index 2, depending on whether the actual value is larger than the planned value, whether the actual value and the planned value are equal, or whether the actual value is smaller than the planned value. Nine category IDs are set.

  The method for comparing the actual value of the index and the planned value is not limited to the method described above. For example, the divergence rate between the planned value and the actual value may be expressed as a percentage, and the category ID may be determined according to the divergence rate expressed as a percentage. In this case, it is possible to classify the history data into more categories than the method described above.

  Next, the determination unit 12 determines whether or not the history data classified into any of the plurality of categories can be grouped, and groups the history data determined to be grouped and stores it in the group DB.

  Here, being able to be grouped means that the detailed action information corresponding to action number 1 is the same, and the combination of the detailed action information corresponding to the subsequent action number and the check result information is not in conflict. Say.

  Also, "no conflict" means that the check result information corresponding to a certain action number is the same and the action corresponding to the next action number is the same, or the check result information corresponding to a certain action number Is different. Note that the same action means that if the action type information is “check”, the action type information matches the detailed action information, and if the action type information is “Countermeasure” or “No action”. Is that the action type information matches.

  In order to efficiently perform the process of determining whether grouping is possible, the determination unit 12 further subgroups the history data belonging to the group and stores the history data in the group DB.

  FIG. 5 is a diagram illustrating an example of the configuration of the group DB included in the determination unit 12 illustrated in FIG.

  In the group DB, as shown in FIG. 5, the category ID, the group ID for uniquely identifying the group, the subgroup ID for uniquely identifying the subgroup, and the subgroup ID identified by the subgroup ID A history ID indicating history data belonging to the group is associated.

  Here, an operation in which the determination unit 12 groups the history data newly stored in the history DB will be described.

  FIG. 6 is a flowchart for explaining the operation of the determination unit 12 shown in FIG. 1 grouping history data newly stored in the history DB. Here, the case where information as shown in FIG. 5 is stored in the group DB will be described.

  First, the determination unit 12 determines the category ID of the history data by comparing the planned value and the actual value of the index included in the history data newly stored in the history DB (step S1).

  Next, the determination unit 12 selects one of the group IDs corresponding to the category ID determined in step S1 from the group DB. Then, the determination unit 12 selects one of the sub group IDs corresponding to the selected group ID from the group DB.

  Next, the determination unit 12 selects any one of the history IDs corresponding to the selected subgroup ID, and extracts the history data indicated by the selected history ID from the history DB (step S2).

  Next, the determination unit 12 defines variables N and M. Then, the determination unit 12 sets N = 1, and sets M as the last action number in the extracted history data (step S3).

  Next, the determination unit 12 checks whether or not the action with the action number N in the history data newly stored in the history DB is the same as the action with the action number N in the extracted history data (step S4). .

  As a result of the confirmation in step S4, when the action of action number N in the history data newly stored in the history DB is not the same as the action of action number N in the extracted history data, the determination unit 12 newly adds to the history DB. It is determined that the history data stored in 1 and the extracted history data are in conflict (step S5). Then, the process ends.

  On the other hand, as a result of the confirmation in step S4, if the action of action number N in the history data newly stored in the history DB is the same as the action of action number N in the extracted history data, It is confirmed whether the check result information corresponding to the action number N in the history data newly stored in the DB is the same as the check result information corresponding to the action number N in the extracted history data (step S6).

  As a result of the confirmation in step S6, when the check result information corresponding to the action number N in the history data newly stored in the history DB is not the same as the check result information of the action number N in the extracted history data, the determination unit 12 Determines that the history data newly stored in the history DB does not conflict with the extracted history data (step S7). Then, the process ends.

  On the other hand, as a result of the confirmation in step S6, the check result information corresponding to the action number N in the history data newly stored in the history DB is the same as the check result information corresponding to the action number N in the extracted history data. In this case, the determination unit 12 sets N = N + 1 (step S8).

  Next, the determination unit 12 confirms whether or not the action with the action number N in the history data newly stored in the history DB is the same as the action with the action number N in the extracted history data (step S9). .

  As a result of the confirmation in step S9, when the action with the action number N in the history data newly stored in the history DB is not the same as the action with the action number N in the extracted history data, the determination unit 12 adds a new one to the history DB. It is determined that the history data stored in the list and the extracted history data are in conflict (step S10). Then, the process ends.

  On the other hand, as a result of the confirmation in step S9, if the action of action number N in the history data newly stored in the history DB is the same as the action of action number N in the extracted history data, = M is confirmed whether it is satisfied (step S11).

  If N = M is established as a result of the confirmation in step S11, the determination unit 12 determines that the history data newly stored in the history DB is not in conflict with the extracted history data, and the extracted history data It is determined that they match (step S12). Then, the process ends.

  On the other hand, if N = M is not satisfied as a result of the determination in step S11, the process proceeds to the operation in step S6.

  Thereafter, the determination unit 12 extracts all the history data indicated by the history ID corresponding to the selected subgroup ID one by one, and repeats the above-described operation. Thereafter, the determination unit 12 selects an unselected subgroup ID among the subgroup IDs corresponding to the selected group ID, and repeats the above-described operation.

  The history data newly stored in the history DB does not conflict with all the history data indicated by the history ID corresponding to the selected group ID, and the history data indicated by the history ID corresponding to the selected sub group ID. When it matches any of the above, the determination unit 12 stores the history ID indicating the history data newly stored in the history DB in the group DB in association with the selected subgroup ID.

  In addition, history data newly stored in the history DB does not conflict with all the history data indicated by the history ID corresponding to the selected group ID, and the history data indicated by the history ID corresponding to all the subgroup IDs. If they do not match, the determination unit 12 generates a new subgroup ID corresponding to the selected group ID. Then, the history ID indicating the history data newly stored in the history DB is stored in the group DB in association with the generated subgroup ID.

  If the history data newly stored in the history DB does not conflict with all the history data indicated by the history ID corresponding to the selected subgroup ID, the determination unit 12 assigns the new group ID to the temporary group ID. And a new subgroup ID corresponding to the generated temporary group ID is generated. Then, the determination unit 12 associates the history ID indicating the history data newly stored in the history DB and the history ID corresponding to the selected subgroup ID with the generated new subgroup ID. Remember me.

  Thereafter, the determination unit 12 selects an unselected group ID among the group IDs corresponding to the category ID determined in step S1, and repeats the above-described operation.

  When the history data newly stored in the history DB is in conflict with all the history data indicated by the history IDs corresponding to all the group IDs, that is, when it cannot be grouped into any group, the determination unit 12 A new group ID is generated, and a sub group ID corresponding to the generated group ID is generated. Then, the determination unit 12 stores the history ID indicating the history data newly stored in the history DB in the group DB in association with the generated subgroup ID.

  When a temporary group ID is generated, the determination unit 12 extracts one of the generated temporary group IDs. Next, the determination unit 12 searches the group DB for a group ID indicating a group including all history IDs corresponding to the sub group ID corresponding to the extracted temporary group ID. And when searched, the determination part 12 deletes the line containing extracted temporary group ID from group DB. On the other hand, when the search is not performed, the determination unit 12 stores the temporary group ID as a new group ID in the group DB. The determination unit 12 executes this for all temporary group IDs.

  When the support device 10 is first introduced and history data is stored in the history DB for the first time, the determination unit 12 generates a new group ID and a new subgroup ID corresponding to the group ID. Then, the determination unit 12 stores the history ID indicating the history data in the group DB in association with the generated subgroup ID.

  One history ID may be associated with a plurality of group IDs in the group DB.

  Referring to FIG. 1 again, the mapping list generation unit 13 generates and stores a mapping list based on the group DB generated by the determination unit 12. The mapping list is generated for each group ID, and represents all the behavior information included in the history data indicated by the history ID corresponding to the group ID in a tree structure so that the developer or the like can visually recognize it.

  FIG. 7 is a diagram illustrating an example of the mapping list generated by the mapping list generation unit 13 illustrated in FIG.

  Below, the operation | movement which the mapping list production | generation part 13 produces | generates a mapping list as shown in FIG. 7 is demonstrated.

  First, the mapping list generation unit 13 selects one of the category IDs stored in the group DB. Next, the mapping list generation unit 13 selects one of the group IDs corresponding to the selected category ID. Next, the mapping list generation unit 13 selects one of the sub group IDs corresponding to the selected group ID. Then, the mapping list generation unit 13 selects one of the history IDs corresponding to the selected subgroup ID.

  Next, the mapping list generation unit 13 extracts action type information and action detailed information corresponding to action number 1 from the history DB from the history data indicated by the selected history ID. The action type information corresponding to action number 1 is “check”.

  Next, the mapping list generation unit 13 extracts check result information corresponding to the check item number indicated by the extracted action detail information from the management table illustrated in FIG. And the mapping list production | generation part 13 arrange | positions the extracted check result information to the lower part of the extracted action classification information and action detailed information, and makes it a tree structure.

  Next, the mapping list generation unit 13 confirms the check result information corresponding to the action number 1 among the history data indicated by the selected history ID, and acquires the action type information corresponding to the action number 2 from the history DB.

  When the acquired action type information is “no action”, the mapping list generation unit 13 generates a basic data ID for uniquely identifying the actions so far. And the mapping list production | generation part 13 arrange | positions the acquired action classification information and produced | generated basic data ID to the lower part of the confirmed check result information among the check result information arrange | positioned at the lowest part in tree structure. .

  Next, the mapping list generation unit 13 adds up the number of history IDs for each of a plurality of priority element information and for each evaluation information from all the history data indicated by the history ID corresponding to the selected subgroup ID. Then, the mapping list generation unit 13 stores the selected group ID, the generated basic data ID, and the number of history IDs for each of the plurality of priority element information and the evaluation information in association with each other in the basic data table provided by itself. Let

  FIG. 8 is a diagram illustrating an example of a configuration of a basic data table provided in the mapping list generation unit 13 illustrated in FIG.

  In the basic data table, as shown in FIG. 8, the group ID, basic data ID, priority element information, evaluation information, and the number of history IDs are associated with each other.

  In addition, when the acquired action type information is “measure”, the mapping list generation unit 13 sets the action type information of all the history data indicated by the history ID corresponding to the selected subgroup ID to the action corresponding to “measure”. Detailed information is acquired from the history DB. Next, the mapping list generation unit 13 generates a basic data ID. Then, the mapping list generation unit 13 includes the acquired action type information and action detailed information and the generated basic data ID below the confirmed check result information among the check result information arranged at the bottom in the tree structure. And place.

  Next, the mapping list generation unit 13 adds up the number of history IDs for each of a plurality of priority element information and for each evaluation information from all the history data indicated by the history ID corresponding to the selected subgroup ID. Then, the mapping list generation unit 13 stores the selected group ID, the generated basic data ID, and the number of history IDs for each of the plurality of priority element information and evaluation information in association with each other in the basic data table.

  When the acquired action type information is “check”, the mapping list generation unit 13 acquires detailed action information corresponding to the acquired action type information from the history DB. And the mapping list production | generation part 13 arrange | positions the acquired action classification information and action detailed information to the lower part of the confirmed check result information among the check result information arrange | positioned at the lowest part in tree structure. Then, the mapping list generation unit 13 increments the action number by 1, and acquires action type information corresponding to the incremented action number from the history DB. Then, the mapping list generation unit 13 repeats the above-described operation depending on whether the acquired action type information is “no action”, “measure”, or “check”.

  Next, the mapping list generator 13 selects an unselected subgroup ID among the subgroup IDs corresponding to the selected group ID, and repeats the above-described operation.

  Then, the mapping list generation unit 13 selects an unselected group ID from among the group IDs corresponding to the selected category ID and repeats the above-described operation.

  In this repetitive operation, the mapping list generation unit 13 does not generate the same tree structure redundantly.

  In addition, when a new group ID, subgroup ID, or history ID is added to the group DB, the mapping list generation unit 13 adds the added group ID, subgroup ID, and history based on the generated tree structure. The operation described above with respect to the ID is performed. As a result, information stored in the mapping list and the basic data table is updated. Also, when the sub group ID corresponding to the group ID is changed or the history ID corresponding to the sub group ID is changed, the information stored in the mapping list and the basic data table is updated.

  In the mapping list shown in FIG. 7, Q, C, and D indicate priority element information, and the parenthesized value calculation unit 14 to be described later is shown in parentheses described after each of Q, C, and D. The value called the weight value calculated at is stored. Therefore, when the mapping list or information stored in the basic data table is updated, the mapping list generation unit 13 notifies the weight value calculation unit 14 described later.

  In addition, here, actions for improving progress and quality in software development are represented by a tree structure as shown in FIG. 7, and the number of history IDs for each priority element information and evaluation information is as shown in FIG. Although stored in the basic data table, this method is an example.

  Referring to FIG. 1 again, the weight value calculation unit 14 calculates a weight value for each of a plurality of priority element information from the information stored in the basic data table shown in FIG. The weight value is a value given to the mapping list, and is a value indicating the priority of actions to be performed in order to improve quality and progress in software development. That is, the weight value calculation unit 14 determines the priority of the mapping list for each of a plurality of pieces of priority element information. Here, it is assumed that the priority is higher in a mapping list having a larger assigned weight value.

  Here, an example of an operation in which the weight value calculation unit 14 calculates the weight value will be described.

  First, the weight value calculation unit 14 extracts information stored in the basic data table stored in the mapping list generation unit 13. Here, for example, in the basic data table, it is assumed that the number of history IDs of evaluation information ◯ corresponding to the priority element information Q is 20, and the number of history IDs of evaluation information × is 3.

  Assume that the history ID of evaluation information ○ has twice the weight as compared to the history ID of evaluation information x, and the product of the number of history IDs and the weight of evaluation information is the weight value assigned to the mapping list The weight value of the priority element information Q in the mapping list can be calculated as follows, for example.

Weight value = 2 × 20 + 1 × 3 = 43
Then, the weight value calculation unit 14 stores the calculated weight value in the mapping list generation unit 13 in association with the mapping list.

  As described above, the weight value calculation unit 14 may calculate the weight value for each basic data ID, that is, for each countermeasure of the mapping list. Here, for example, let us consider a case where the basic data ID 001 corresponds to the countermeasure A and the basic data ID 002 corresponds to the countermeasure B in the basic data table.

  At this time, in the basic data table, it is assumed that the number of evaluation information ◯ corresponding to the priority element information Q of the basic data ID 001 is 15, and the number of history IDs of evaluation information × is 2. Further, it is assumed that the number of history IDs of evaluation information ◯ corresponding to the priority element information Q of the basic data ID 002 is 5, and the number of history IDs of evaluation information × is 1.

  Assume that the history ID with the evaluation information “◯” has a weight twice that of the history ID with the evaluation information “x”, and the product of the number of history IDs and the weight of the evaluation information is the weight value of the countermeasure. The weight value of the priority element information Q of the measure A (basic data ID001) and the weight value of the priority element information Q of the measure B (basic data ID002) can be calculated as follows, for example.

Countermeasure A: Weight value = 2 × 15 + 1 × 2 = 32
Countermeasure B: Weight value = 2 × 5 + 1 × 1 = 11
Then, the weight value calculation unit 14 stores the calculated weight value in the mapping list generation unit 13 in association with the action type information “measure” on the mapping list.

  Referring to FIG. 1 again, the suggestion unit 16 receives support target data output from the input unit 15. Then, the proposing unit 16 compares the planned value and the actual value for each index included in the received support target data, and determines the category ID. Next, the suggestion unit 16 acquires a group ID corresponding to the determined category ID from the group DB stored in the determination unit 12. Next, the proposing unit 16 acquires a mapping list corresponding to the acquired group ID from the mapping list generating unit 13. Then, the suggestion unit 16 causes the display unit 17 to display the acquired mapping list and the weight value assigned to the mapping list. Here, when a plurality of mapping lists are acquired, the proposing unit 16 receives a weight value for each of the plurality of priority element information (Q, C, D) assigned to each of the acquired plurality of mapping lists. The size of the weight value of the same priority element information as the priority element information included in the supported data is confirmed. Then, the proposing unit 16 displays each of the acquired plurality of mapping lists on the display unit 17 so that a developer or the like can recognize the difference in the size of the confirmed weight value. For example, the proposing unit 16 causes the display unit 17 to display each of the acquired plurality of mapping lists in descending order of the confirmed weight values. When a weight value is assigned to the countermeasure, a mapping list including the weight value assigned to the countermeasure may be displayed.

  As described above, in the present embodiment, the support device 10 indicates the behavior performed in the past for improving quality and progress in software development and the behavior information indicating the order of performing the behavior, and the quality and progress in the software development. It has an input unit 15 that receives input of history data including past planned values and actual values of indicators and support target data including planned values and actual values of the above-described indicators.

  Further, the support device 10 classifies the history data received by the input unit 15 into any of a plurality of predetermined categories based on past plan values and actual values included in the history data, The determination unit 12 groups the recorded history data into a group associated with the category based on behavior information included in the history data.

  Further, the support device 10 includes a mapping list generation unit 13 that generates a mapping list that is associated with a group and that represents all of the behavior information included in the history data belonging to the group.

  In addition, the support device 10 includes a weight value calculation unit 14 that determines the priority of the mapping list corresponding to the group based on the number of history data belonging to the group.

  Further, the support device 10 classifies the support target data into one of the plurality of categories based on the plan value and the actual value included in the support target data received by the input unit 15, and the classified category And a proposal unit 16 that outputs a mapping list corresponding to the group corresponding to 1 to the outside so that the priority of the mapping list can be recognized.

  Thereby, it is possible to provide know-how and the like gradually accumulated by skilled developers to developers who do not have development know-how.

  Therefore, it is possible to shorten the time required for evaluation and examination of countermeasures in software development. It is also possible to implement appropriate measures according to the priority factors in individual software development.

  In the present embodiment, the case where the mapping list is notified to the outside using the display unit 17 has been described. In addition, the support apparatus 10 may include a communication unit, for example, and transmit the mapping list to a predetermined terminal or the like via a communication line.

  In the present invention, the processing in the support device is recorded on a recording medium readable by the support device, in addition to the processing realized by the dedicated hardware described above. The program recorded on the recording medium may be read by the support device and executed. The recording medium that can be read by the support device refers to a transfer medium such as a flexible disk, a magneto-optical disk, a DVD, and a CD, as well as an HDD built in the support device.

DESCRIPTION OF SYMBOLS 10 Support apparatus 11 Accumulation part 12 Judgment part 13 Mapping list production | generation part 14 Weight value calculation part 15 Input part 16 Proposal part 17 Display part

Claims (5)

Includes action information that indicates the actions taken in the past and the order in which the actions were taken to improve quality and progress in software development, and past planned and actual values of indicators that indicate the quality and progress in the software development An input unit for receiving input of history data and support target data including the planned value and actual value of the indicator;
The history data received by the input unit is classified into any of a plurality of predetermined categories based on past plan values and actual values included in the history data, and the classified history data is Based on the behavior information included in the history data, a determination unit that groups into a group associated with the category,
A mapping list generating unit that generates a mapping list that is associated with the group and represents all of the behavior information included in the history data belonging to the group;
A weight value calculator that determines the priority of the mapping list corresponding to the group based on the number of history data belonging to the group;
Based on the plan value and the actual value included in the support target data received by the input unit, the support target data is classified into one of the plurality of categories, and the group corresponding to the classified category is supported. And a proposal unit that outputs the mapping list to the outside so that the priority of the mapping list can be recognized. The support apparatus according to claim 1,
The history data and the support target data further include any of a plurality of priority element information indicating each of a plurality of elements prioritized in software development,
The weight value calculation unit determines the priority of the mapping list corresponding to the group for each of the plurality of priority element information based on the number of history data belonging to the group and the priority element information included in the history data. And
The suggestion unit converts the mapping list corresponding to the group corresponding to the classified category into the support target data received by the input unit among the priorities of the plurality of priority element information of the mapping list. A support device that outputs to the outside so that the priority of the same priority element information as the included priority element information can be recognized. The support device according to claim 2,
The historical data further includes evaluation information indicating an evaluation as to whether or not the improvement has been realized as a result of actions performed in the past for improving the quality and progress in the software development,
The weight value calculation unit determines the priority of the mapping list corresponding to the group based on the number of history data belonging to the group and the priority element information and evaluation information included in the history data. Support device to be determined for each. A support method in a support device for supporting software development,
Includes action information that indicates the actions taken in the past and the order in which the actions were taken to improve quality and progress in software development, and past planned and actual values of indicators that indicate the quality and progress in the software development Processing to accept history data;
The received history data is classified into any of a plurality of predetermined categories based on past plan values and actual values included in the history data, and the classified history data is included in the history data. Grouping into groups associated with the category based on
A process of generating a mapping list that is associated with the group and represents all of the behavior information included in the history data belonging to the group;
A process for determining the priority of the mapping list corresponding to the group based on the number of history data belonging to the group;
Processing for receiving input of support target data including the planned value and actual value of the indicator;
Based on the plan value and the actual value included in the received support target data, the support target data is classified into one of the plurality of categories, a mapping list corresponding to the group corresponding to the classified category, And a process of outputting to the outside so that the priority of the mapping list can be recognized. To support devices that support software development,
Includes action information that indicates the actions taken in the past and the order in which the actions were taken to improve quality and progress in software development, and past planned and actual values of indicators that indicate the quality and progress in the software development A function to accept historical data,
The received history data is classified into any of a plurality of predetermined categories based on past plan values and actual values included in the history data, and the classified history data is included in the history data. Based on the action information to be grouped into a group associated with the category,
A function of generating a mapping list associated with the group and representing all of the behavior information included in the history data belonging to the group;
A function of determining the priority of the mapping list corresponding to the group based on the number of history data belonging to the group;
A function of receiving input of support target data including the planned value and the actual value of the indicator;
Based on the plan value and the actual value included in the received support target data, the support target data is classified into one of the plurality of categories, a mapping list corresponding to the group corresponding to the classified category, A program for realizing the function of outputting to the outside so that the priority of the mapping list can be recognized.

Images