JP6756337B2 - Estimate support devices, methods and programs - Google Patents

Description

The present invention relates to estimation support devices, methods and recording media.

In the development of information systems for business use (hereinafter referred to as business systems) such as material ordering systems and work management systems, the man-hours required for subsequent development are estimated at the upstream process stage. The estimated man-hours are calculated by multiplying the development scale calculated from the functional requirements of the business system by the coefficient of the productivity fluctuation factor set from the non-functional requirements (the rate of increase in man-hours plus 1).

A software measurement method such as the FP (Function Point) method is generally used as a method for calculating the development scale from functional requirements.

As a method for calculating the coefficient of the productivity fluctuation factor from the non-functional requirements, for example, there is a method described in Non-Patent Document 1. In this method, non-functional requirements are systematically organized in advance as items, and the coefficient of fluctuation factor for each item is set based on actual data. Non-functional requirements in this method relate to the structure (subsystems and functions) of the system such as performance and security. Therefore, even if the non-functional requirements relate only to some subsystems or functions of the system, the correct man-hours can be estimated by multiplying the coefficient of the variable factor of the non-functional requirements by the development scale of the subsystem or functional unit. Is possible.

Based on this idea, Patent Document 1 describes a method of dividing a system into functions and estimating man-hours. In this method, the final estimated man-hours are obtained by multiplying the man-hours calculated from the scale, quality, and development period of the functional unit of the system by the coefficient of the variable factor of the non-functional requirements for each function.

Japanese Unexamined Patent Publication No. 2015-041156

Nobuto Inoguchi, 7 outsiders, "Development and popularization of model / tool for estimating man-hours for system infrastructure construction", [online], 2012, Software Quality Symposium, [Search on October 9, 2015], Internet <http: / / Www. juse. jp / skip / symposium / 2012 / day1 / files / B2-3_r. pdf>

However, when trying to handle non-functional requirements (hereinafter referred to as UI requirements) related to UI (User Interface) in man-hour estimation, the UI requirements cannot be divided into subsystems or functional units to calculate the estimated man-hours. The method of Document 1 cannot be used.

This is because the principle of UI is to ensure consistency throughout the system, and UI requirements define the policy of the entire system, not subsystems or functional units. In other words, the part affected by UI requirements exists in the entire system regardless of subsystems and functions. And the UI requirements affect only a particular UI, not all parts of the system. For example, the UI requirement to "group list information and display text" does not apply to some subsystems or functions, but appears throughout the system across subsystems or functions. Applies only to the UI.

An object of the present invention is an estimation support device, a method, and a recording medium that enable a man-hour estimation that reflects the influence of each requirement even for a requirement related to the entire system such as a UI. Is to provide.

In order to solve the above-mentioned problems, the estimation support device of the present invention classifies each requirement to be satisfied by the system to be estimated into classification items and stores the result of the classification in the classification storage unit. Based on the appearance ratio calculation means that calculates the appearance ratio in the system for each of the classification items and stores the appearance ratio in the appearance ratio storage unit, and the classification result and the appearance ratio, each of the requirements of the requirement The man-hour increase rate is multiplied by the appearance ratio of the classification item corresponding to the requirement, and the result of the multiplication of each requirement is added up to calculate the man-hour increase rate of the entire requirement, and the man-hour increase rate of the entire requirement is calculated. It is characterized by being provided with an increase rate calculation means for outputting the man-hour increase rate.

Further, in the estimation support method of the present invention, each requirement to be satisfied by the system to be estimated is classified into classification items, the result of the classification is stored in the classification storage unit, and the appearance ratio in the system for each of the classification items. Is calculated, the appearance ratio is stored in the appearance ratio storage unit, and based on the classification result and the appearance ratio, the man-hour increase rate of the requirement and the appearance ratio of the classification item corresponding to the requirement are obtained. , And the results of the multiplication of each of the requirements are added up to calculate the man-hour increase rate of the entire requirement, and the man-hour increase rate of the entire requirement is output.

Further, the estimation support program recorded on the computer-readable recording medium of the present invention classifies each requirement to be satisfied by the system to be estimated into classification items and stores the result of the classification in the classification storage unit. Requirement classification function to be performed, an appearance ratio calculation function to calculate the appearance ratio in the system for each of the classification items and store the appearance ratio in the appearance ratio storage unit, and each based on the classification result and the appearance ratio. For the requirement, the man-hour increase rate of the requirement is multiplied by the appearance ratio of the classification item corresponding to the requirement, and the result of the multiplication of each requirement is added up to calculate the man-hour increase rate of the entire requirement. It is characterized by realizing an increase rate calculation function that outputs the man-hour increase rate of the entire requirement.

The estimation support device, method, and recording medium of the present invention make it possible to estimate the man-hours by reflecting the influence only on the part affected by each requirement even for the requirements related to the entire system such as the UI.

It is a figure which shows the structural example of the estimation support apparatus of 1st Embodiment of this invention. It is a figure which shows the operation example of the estimation support apparatus of 1st Embodiment of this invention. It is a figure which shows the structural example of the estimation support apparatus of the 2nd Embodiment of this invention. It is a figure which shows the example of the requirement list. It is a figure which shows the example of the classification rule. It is a figure which shows the example of the classified requirement list. It is a figure which shows the example of the screen list. It is a figure which shows the example of the classified screen list. It is a figure which shows the example of the appearance ratio. It is a figure which shows the example of the calculation of the total man-hour increase rate. It is a figure which shows the structural example of the estimation support apparatus of the 2nd Embodiment of this invention. It is a figure which shows the hardware configuration example of each embodiment of this invention.

[First Embodiment]
The first embodiment of the present invention will be described.

FIG. 1 shows a configuration example of the estimation support device 10 of the present embodiment.

The estimation support device 10 of the present embodiment is composed of a requirement classification unit 11, an appearance ratio calculation unit 12, and an increase rate calculation unit 13.

The requirement classification unit 11 is a part that classifies each requirement to be satisfied by the system to be estimated into classification items and stores the classification result in the classification storage unit 14.

The appearance ratio calculation unit 12 is a part that calculates the appearance ratio in the system to be estimated for each classification item and stores the appearance ratio in the appearance ratio storage unit 15.

The increase rate calculation unit 13 multiplies the man-hour increase rate of the requirement and the appearance ratio of the classification item corresponding to the requirement for each requirement based on the classification result and the appearance ratio, and adds up the multiplication result of each requirement. This is the part that calculates the man-hour increase rate for the entire requirement and outputs the man-hour increase rate for the entire requirement.

By configuring the estimation support device 10 in this way, it is possible to estimate the man-hours by reflecting the influence only on the part affected by each requirement even for the requirements related to the entire system such as the UI.

Next, FIG. 2 shows an example of the operation of the estimation support device 10 of the present embodiment.

First, the requirement classification unit 11 of the estimation support device 10 classifies each requirement to be satisfied by the system to be estimated into classification items and stores the classification result in the classification storage unit 14 (step S101).

Further, the appearance ratio calculation unit 12 calculates the appearance ratio in the system to be estimated for each classification item, and stores the appearance ratio in the appearance ratio storage unit 15 (step S102).

Then, the increase rate calculation unit 13 multiplies the man-hour increase rate of the requirement and the appearance ratio of the classification item corresponding to the requirement for each requirement based on the classification result and the appearance ratio. Then, the result of multiplication of each requirement is added up to calculate the man-hour increase rate of the entire requirement, and the man-hour increase rate of the entire requirement is output (step S103).

By operating the estimation support device 10 in this way, it is possible to estimate the man-hours by reflecting the influence only on the part affected by each requirement even for the requirements related to the entire system such as the UI.

As described above, in the first embodiment of the present invention, each requirement is classified into classification items, and the appearance ratio of each classification item in the system is calculated. As a result, it is possible to regard the classification item in which each requirement is classified as the part affected by each requirement, and the appearance ratio of the classification item in which each requirement is classified as the ratio of the part affected by the requirement to the entire system. become. Therefore, by multiplying the man-hour increase rate of each requirement by the appearance ratio of the classification item in which the requirement is classified, it is possible to calculate the man-hour increase rate for the entire system for each requirement. Then, by adding up the multiplication results for each requirement, it becomes possible to calculate the man-hour increase rate for the entire system when all the requirements are met. Therefore, even for requirements related to the entire system such as UI, it is possible to estimate the man-hours by reflecting the influence only on the part affected by each requirement.

[Second Embodiment]
Next, a second embodiment of the present invention will be described.

In this embodiment, the content of the operation on the data is used as the classification item.

From the user's point of view of using the UI, it can be considered that the business system consists of "data operations", that is, a series of operations on the data handled by the system, such as data search, list, detailed reference, and detailed editing. it can. In addition, the appearance ratio of each data operation is a screen list, screen transition diagram, sequence diagram of representative operations (of the entire operations handled by the business system, some operations that are particularly frequently used and important) even in the initial stage of development. It is possible to measure from such.

Therefore, in the present embodiment, by utilizing the universal property of such a business system, each requirement is classified with respect to data manipulation, and the appearance ratio of each data manipulation is calculated. As a result, the scope of influence of each requirement is regarded as each data operation in which each requirement is classified. Then, the appearance rate of the data manipulation corresponding to each requirement is multiplied by the man-hour increase rate of each requirement, and the multiplication result for each requirement is added up to calculate the man-hour increase rate of the entire requirement.

As the classification item, any item may be used as long as the range affected by each requirement can be specified and the ratio of the affected range to the entire system can be calculated. Not limited.

FIG. 3 shows a configuration example of the estimation support device 20 of the present embodiment. A classification rule storage unit 26 is added to the estimation support device 10 of FIG.

The requirement classification unit 11 is a part that classifies each requirement into classification items and stores the classification result in the classification storage unit 14. The requirement classification unit 11 receives from the user a list of requirements and a list of man-hour increase rates for non-functional requirements (UI requirements) related to the UI that the business system for man-hour estimation should have, and classifies each requirement into classification items. To do.

In the present embodiment, the case where the requirement is a UI requirement will be described, but it is also possible to handle requirements other than the UI that appear in the entire system across functions and subsystems.

FIG. 4 shows an example of a list of requirements. Requirements are described as system-wide UI policies, such as "based on item selection to reduce the load of character input" and "group list information so that it can be identified by color or shape". .. In addition, the man-hour increase rate is described as the rate of increase in man-hours for the part related to each requirement when each requirement is realized. For example, if the development man-hour of the part related to a certain requirement is 2 man-months and the man-hour increase rate for this requirement is 0.15, when this requirement is realized, the development man-hour of the part related to this requirement is 0. .15 x 2 = 0.3 man-month increase.

The classification rule storage unit 26 is a portion that stores a classification rule that is a set of a classification item and a keyword group related to each classification item. FIG. 5 shows an example of the classification rule. Category items include "search", "list", "detailed reference", "detailed edit", and the like. In addition, "search", "condition", "result", "search", etc. are registered as keywords related to "search". The data operations and related keywords listed here are just examples. , Not limited to this.

The requirement classification unit 11 classifies each requirement into classification items according to the classification rule stored in the classification rule storage unit 26, and stores the classification result in the classification storage unit 14. For example, the sentence of each requirement in the requirement list is collated with the keyword of the classification rule, and the classification item corresponding to the keyword matching the word in the sentence is set as the classification item of the requirement.

FIG. 6 shows an example of a list of requirements classified according to the classification rule of FIG. In the case of the requirement of "grouping list information so that it can be identified by color or shape", the keyword "list" matches, so the requirement is classified into "list". In addition, in the case of the requirement of "displaying the search result immediately after inputting the search condition", since the keywords "search" and "condition" match, the requirement is classified into "search".

The appearance ratio calculation unit 12 is a part that calculates the appearance ratio of each classification item in the system to be estimated and stores the appearance ratio in the appearance ratio storage unit 15. The appearance ratio calculation unit 12 calculates the appearance ratio based on a development document that describes the behavior of the system from the viewpoint of data manipulation, such as a screen transition diagram and a sequence diagram of a representative business. The development documents need only describe the behavior of the system from the viewpoint of data manipulation, and are not limited to these documents. Hereinafter, the present embodiment will be described assuming that the screen list is received.

The appearance ratio calculation unit 12 of the present embodiment calculates the appearance ratio of each classification item according to the classification rule stored in the classification rule storage unit 26. For example, by collating each screen name appearing in the screen list with the keyword of the classification rule, classifying each screen into classification items, and counting the number of screens classified into each classification item, each classification item can be classified. It is possible to calculate the appearance ratio.

FIG. 7 shows an example of a screen list. In this example, "document list screen", "document creation screen", and the like are described as screen names. In this example, the transition of each screen is described in addition to the screen name, but if only the screen name is described, it can be used in the present embodiment.

Further, FIG. 8 shows an example of a screen list in which each screen of FIG. 7 is classified into classification items. In this example, the screen "document list screen" is classified into "list", and the screen "document creation screen" is classified into "detailed editing". Further, FIG. 9 shows an example of the appearance ratio of each classification item obtained by dividing the number of screens classified into each classification item by the total number of screens described in the screen list. In the screen list example of FIG. 8, out of the eight screens in total, three screens have the classification item "list", so the appearance ratio of the "list" is 0.375.

The increase rate calculation unit 13 multiplies the man-hour increase rate of the requirement and the appearance ratio of the classification item corresponding to the requirement based on the classification result of the classification storage unit 14 and the appearance ratio of the appearance ratio storage unit 15, and multiplies each requirement. This is the part to calculate the man-hour increase rate for the entire requirement by adding up the results of. The increase rate calculation unit 13 increases the total man-hours based on the classification result of the requirements of the requirement classification unit 11 into the classification items, the man-hour increase rate of each requirement, and the appearance ratio of each classification item calculated by the appearance ratio calculation unit 12. Calculate the rate.

Specifically, for each requirement, the man-hour increase rate for the entire estimated target system for each requirement is obtained by multiplying the man-hour increase rate of the requirement by the appearance rate of the classification item in which the requirement is classified. Can be done. Then, by adding up the man-hour increase rates for the entire system calculated for each requirement, the man-hour increase rate for the entire system for all the requirements can be calculated.

FIG. 10 shows an example of calculation of the man-hour increase rate of the entire requirement by the increase rate calculation unit 13. The requirement "grouping list information so that it can be identified by color or shape" is classified into "list" in FIG. The rate of increase in man-hours is 0.1 according to FIG. The appearance ratio of the classification item "list" is calculated to be 0.375 in FIG. Therefore, the rate of increase in man-hours for the entire system of the requirement "grouping list information so that it can be identified by color or shape" is 0.0375 by multiplying 0.1 and 0.375. Since the man-hour increase rate for each requirement in FIG. 4 was the man-hour increase rate for the part related to each requirement, the man-hour increase rate for the entire system is multiplied by the appearance ratio of the classification items corresponding to each requirement. Will be calculated. By calculating the man-hour increase rate for the entire system for each requirement and adding up for all the requirements, the man-hour increase rate for the entire requirement can be calculated.

The estimation support device 20 outputs the man-hour increase rate of the entire requirement calculated by the increase rate calculation unit 13. The user who receives the man-hour increase rate of the entire requirement separately multiplies the man-hour estimated from the non-functional requirements and functional requirements other than the UI by the total man-hour increase rate calculated by the estimation support device 20, and the UI requirement. It becomes possible to calculate the increase in man-hours for.

Further, as in the estimation support device 30 of FIG. 11, the man-hour calculation unit 37 for calculating the increase in man-hours is added, and the man-hours estimated from other than the UI requirements and the man-hours for the entire UI requirement calculated by the increase rate calculation unit 13 are increased. It is also possible to output the increase in man-hours for the entire system multiplied by the rate.

Alternatively, the estimated man-hours for the entire system including the UI requirements are calculated by multiplying the man-hours estimated from other than the UI requirements by the increase rate calculation unit 13 and multiplying the man-hours increase rate for the entire UI requirements by adding 1. It is also possible to output.

By configuring the estimation support device 20 in this way, it is possible to estimate the man-hours by reflecting the influence only on the part affected by each requirement even for the requirements related to the entire system such as the UI.

Next, an example of the operation of the present embodiment will be described with reference to FIG.

First, the requirement classification unit 11 of the estimation support device 20 receives a list of requirements as shown in FIG. 4 from the user. In this example, in the requirement list, "Basically select items to reduce the load of character input", "Group list information so that it can be identified by color and shape", "Automatically save input contents sequentially" , And "Display search results immediately after inputting search conditions" are described. In addition, the man-hour increase rates of 0.15, 0.1, 0.05, and 0.2 are set for each requirement. This requirement and the rate of increase in man-hours are determined by the user in the business system development project to be estimated.

Further, the appearance ratio calculation unit 12 receives a screen list of representative business of the business system to be estimated as shown in FIG. 7 from the user. Eight screens such as "document list screen" and "document creation screen" are defined in the screen list. The screen list is created in the development project in the same way as the requirement list. It is assumed that the estimation support device of this embodiment will be used in the early stage of development, and that there is no detailed screen list covering the entire business system. Therefore, in the present embodiment, only the screen list related to the representative work created in advance is input, but a detailed screen list covering the whole may be input.

Next, the requirement classification unit 11 classifies each requirement into classification items with reference to the classification rules stored in the classification rule storage unit 26. In the example of the classification rule of FIG. 5, four classification items, "search", "list", "detailed reference", and "detailed editing" are defined, and keywords related to each classification item are defined. doing. For example, as keywords related to the classification item "search", "search", "condition", "result", "search" and the like are defined.

The requirement classification unit 11 determines whether or not the keyword of the classification rule is included in the text of each requirement in the requirement list, and if the keyword is included, classifies the requirement into the classification item corresponding to the keyword ( Step S101 in FIG. 2). The result of classifying the requirement list of FIG. 4 according to the classification rule of FIG. 5 is shown in FIG. For example, since the sentence of the requirement "basically item selection to reduce the load of character input" includes the keyword "input", this requirement is classified into "detailed editing".

Here, since it is possible that keywords of a plurality of classification items are included in one requirement, it is desirable to prioritize the classification items and keywords and classify them according to the priority. Alternatively, it is possible to classify one requirement into a plurality of classification items. For example, the requirement "display search results immediately after inputting search conditions" in FIG. 6 includes the keywords "search" and "condition" of the classification item "search" and the keyword "input" of the classification item "detailed editing". .. In the present embodiment, the classification item "search" is a rule that has priority over the classification item "detailed editing", and this requirement is classified into "search".

If the text of the requirement does not include any of the keywords, for example, the requirement may be regarded as a requirement that affects the entire system and classified into the classification item "whole". In this case, the appearance ratio to the "whole" calculated by the appearance ratio calculation unit 12 is 1, which is the ratio of the whole.

The appearance ratio calculation unit 12 refers to the classification rule (FIG. 5) stored in the classification rule storage unit 26. Then, it is determined whether or not the keyword of the classification rule is included for each screen name in the screen list. If the screen name includes a keyword, the screen is classified into the classification items corresponding to the keyword. FIG. 8 shows the results of classifying each screen of the screen list of FIG. 7 into classification items. For example, since the screen name "document creation screen" includes the keyword "creation" of the classification rule, the "document creation screen" is classified into "detailed editing".

Next, the appearance ratio calculation unit 12 calculates the ratio of the number of screens for each classification item to the total number of screens in the screen list for each classification item (step S102 in FIG. 2). The ratio calculated here is the appearance ratio. The result of calculating the appearance ratio with respect to the classification result of FIG. 8 is shown in FIG. In this example, the total number of screens is eight, and one screen is classified as "search", so the appearance ratio of "search" is 0.125, and the number of screens classified as "list" is three. Therefore, the appearance ratio of the "list" is 0.375.

Here, since it is possible that the name of one screen includes keywords of a plurality of classification items, it is desirable to prioritize the classification items and keywords and classify them according to the priority. Alternatively, one screen can be classified into a plurality of classification items.

If the screen name does not include any of the keywords, the screen is considered to be a screen that does not fit into any of the classification items, and may be classified into the "other" classification item. In this case, it is not necessary to calculate the appearance ratio for "Other" because it is considered that none of the requirements affect the screen classified as "Other" (calculate the appearance ratio for other classification items). Included in the total number used in the case).

Next, the increase rate calculation unit 13 classifies each requirement and the appearance ratio based on the classification result (FIG. 6) of the requirement classification unit 11 and the appearance ratio (FIG. 9) calculated by the appearance ratio calculation unit 12. Correspond as a key. For example, regarding the requirement "Basically select items to reduce the load of character input", the classification item is "Detailed editing" and the appearance ratio of "Detailed editing" is 0.25. The corresponding appearance ratio is 0.25. Further, since the requirement classification unit 11 associates the man-hour increase rate with each requirement in the requirement list received from the user, the appearance rate and the man-hour increase rate are associated with each requirement as shown in FIG. Will be done. For example, the appearance rate of the requirement "based on item selection to reduce the load of character input" is 0.25, and the rate of increase in man-hours is 0.15.

Then, the increase rate calculation unit 13 multiplies the appearance ratio and the man-hour increase rate for each requirement, and calculates the man-hour increase rate for the entire system. For example, with respect to the requirement "basically item selection to reduce the load of character input", the rate of increase in man-hours for the entire system is 0.25 x 0.15 = 0.0375.

In the present embodiment, the classification items in which each requirement is classified are regarded as the part affected by each requirement. Therefore, the appearance ratio of the classification item in which each requirement is classified can be regarded as the ratio of the part affected by the requirement to the entire system. Then, by multiplying the appearance ratio by the man-hour increase rate for each requirement received in the requirement list, the man-hour increase rate for the entire system is calculated.

The increase rate calculation unit 13 calculates the man-hour increase rate of the entire requirement by performing this multiplication for each requirement and adding up all the requirements (step S103 in FIG. 2). In the example of FIG. 10, 0.0375, 0.0375, 0.0125, and 0.025 are obtained as the man-hour increase rate for the entire system of each of the four requirements. Therefore, these are added up and the man-hour increase rate for the entire requirement is obtained. Will be calculated as 0.1125.

The man-hour increase rate R of the entire requirement calculated here can also be calculated by a matrix operation as in Equation 1. From the left, each matrix of Equation 1 shows the man-hour increase rate of each requirement, the correspondence between each requirement and each classification item, and the appearance ratio of each classification item. In the central matrix (correspondence between each requirement and each classification item), each row corresponds to each requirement and each column corresponds to each classification item. Further, for each requirement, the value in the column indicating the classification item in which the requirement is classified is set to 1, and the value in the column indicating the classification item not classified is set to 0. For example, since the first requirement of FIG. 6 is classified into the fourth classification item of FIG. 5, "detailed editing", the fourth column of the first row is set to 1.

Then, the increase rate calculation unit 13 outputs the man-hour increase rate of 0.1125 for the entire calculated requirement and returns it to the user. The user who receives the man-hour increase rate of the entire requirement separately multiplies the man-hour estimated from the non-functional requirements and functional requirements other than the UI by the man-hour increase rate of the entire requirement calculated by the estimation support device 20 to obtain the UI. It becomes possible to calculate the increase in man-hours for requirements.

Further, as in the estimation support device 30 of FIG. 11, the man-hour calculation unit 37 multiplies the man-hours estimated from other than the UI requirements and the man-hour increase rate of the entire requirement calculated by the increase rate calculation unit 13, and the man-hours of the entire system. It is also possible to output the increased amount. Alternatively, the estimated man-hours for the entire system including the UI requirements are calculated by multiplying the man-hours estimated from other than the UI requirements by the man-hours increase rate for the entire requirements calculated by the increase rate calculation unit 13 plus one. It is also possible to output. For example, in the example of FIG. 10, assuming that the development scale estimated from the functional requirements is 60 man-months and the coefficient of the variable factor calculated from the non-functional requirements other than the UI is 1.2, the final estimated man-hours is 60. It can be calculated as × 1.2 × 1.1125 = 80.1 man-months.

By operating the estimation support device 20 in this way, it is possible to estimate the man-hours by reflecting the influence only on the part affected by each requirement even for the requirements related to the entire system such as the UI.

As described above, in the second embodiment of the present invention, as in the first embodiment, each requirement is classified into classification items, and the appearance ratio of each classification item in the system is calculated. As a result, it is possible to regard the classification item in which each requirement is classified as the part affected by each requirement, and the appearance ratio of the classification item in which each requirement is classified as the ratio of the part affected by the requirement to the entire system. become. Therefore, by multiplying the man-hour increase rate of each requirement by the appearance ratio of the classification item in which the requirement is classified, it is possible to calculate the man-hour increase rate for the entire system for each requirement. Then, by adding up the multiplication results for each requirement, it becomes possible to calculate the man-hour increase rate for the entire system when all the requirements are met. Therefore, even for requirements related to the entire system such as UI, it is possible to estimate the man-hours by reflecting the influence only on the part affected by each requirement.

Furthermore, if it becomes possible to reflect the UI requirements in the estimated man-hours, the following effects are considered.

First, since development costs can be secured for efforts to improve UI and ease of use, it is thought that the development side will be able to benefit from efforts to improve UI and ease of use. If the UI requirements cannot be reflected in the estimated man-hours, the development cost for the efforts to improve the UI and usability cannot be secured, so the cost for the efforts will be borne by the development side and the profit on the development side will decrease. ..

In addition, since efforts to improve UI and ease of use can be started from the early stages of development, it is thought that the risk of rework can be reduced. If the UI requirements cannot be reflected in the estimated man-hours, the development cost for efforts to improve the UI and ease of use cannot be secured, and as a result of not starting the UI improvement as much as possible, the problem of ease of use only occurs in the latter half of development. It will be exposed and rework such as UI improvement will occur.

[Hardware configuration example]
An example of a configuration of hardware resources for realizing the estimation support device (10, 20, 30) in each embodiment of the present invention described above by using one information processing device (computer) will be described. The estimation support device (10, 20, 30) may be realized by using at least two information processing devices physically or functionally. Further, the estimation support device (10, 20, 30) may be realized as a dedicated device. Further, only a part of the functions of the estimation support device (10, 20, 30) may be realized by using the information processing device.

FIG. 12 is a diagram schematically showing a hardware configuration example of an information processing device capable of realizing the estimation support device according to each embodiment of the present invention. The information processing device 40 includes a communication interface 41, an input / output interface 42, an arithmetic unit 43, a storage device 44, a non-volatile storage device 45, and a drive device 46.

The communication interface 41 is a communication means for the estimation support device (10, 20, 30) of each embodiment to communicate with an external device by wire or / and wirelessly. When the estimation support devices (10, 20, 30) are realized by using at least two information processing devices, the devices may be connected so as to be able to communicate with each other via the communication interface 41. ..

The input / output interface 42 is a man-machine interface such as a keyboard which is an example of an input device and a display as an output device.

The arithmetic unit 43 is an arithmetic processing unit such as a general-purpose CPU (Central Processing Unit) or a microprocessor. The arithmetic unit 43 can, for example, read various programs stored in the non-volatile storage device 45 into the storage device 44 and execute processing according to the read programs.

The storage device 44 is a memory device such as a RAM (Random Access Memory) that can be referred to by the arithmetic unit 43, and stores programs, various data, and the like. The storage device 44 may be a volatile memory device.

The non-volatile storage device 45 is, for example, a non-volatile storage device such as a ROM (Read Only Memory), a flash memory, etc., and can record various programs, data, and the like.

The drive device 46 is, for example, a device that processes data reading and writing to a recording medium 47 described later.

The recording medium 47 is any recording medium capable of recording data, such as an optical disk, a magneto-optical disk, or a semiconductor flash memory.

In each embodiment of the present invention, for example, the information processing device 40 illustrated in FIG. 12 constitutes an estimation support device (10, 20, 30), and the estimation support device has the functions described in each of the above embodiments. May be realized by supplying a feasible program. In this case, the embodiment can be realized by the arithmetic unit 43 executing the program supplied to the estimation support device. Further, it is also possible to configure some functions of the information processing device 40, not all of the estimation support devices.

Further, the program may be recorded on the recording medium 47, and the program may be appropriately stored in the non-volatile storage device 45 at the shipping stage, the operation stage, or the like of the estimation support device. In this case, as the supply method of the above program, a method of installing the program in the estimation support device by using an appropriate jig at the manufacturing stage or the operation stage before shipment may be adopted. Further, as the method of supplying the above program, a general procedure such as a method of downloading from the outside via a communication line such as the Internet may be adopted.

Each embodiment of the present invention has been described above. In each embodiment of the present invention, in addition to the development of a general information system for business use having a UI, information for general users such as a ticketing system, a facility reservation system, and a collection search system, which mainly refers to and updates a database. It can also be applied to applications such as system development.

Some or all of the above embodiments may also be described, but not limited to:

(Appendix 1)
A requirement classification means for classifying each requirement to be satisfied by the system to be estimated into classification items and storing the result of the classification in the classification storage unit.
An appearance ratio calculation means that calculates the appearance ratio in the system for each of the classification items and stores the appearance ratio in the appearance ratio storage unit.
Based on the classification result and the appearance ratio, the man-hour increase rate of the requirement is multiplied by the appearance ratio of the classification item corresponding to the requirement, and the result of the multiplication of each requirement is added up. An estimation support device including an increase rate calculation means for calculating the man-hour increase rate of the entire requirement and outputting the man-hour increase rate of the entire requirement.

(Appendix 2)
The estimation support device according to Appendix 1, wherein the classification item is the content of data manipulation.

(Appendix 3)
The estimation support device according to Appendix 1 or Appendix 2, wherein the requirement classification means performs the classification according to a classification rule in which the classification item and a keyword are associated with each other.

(Appendix 4)
The appearance ratio calculation means classifies each screen of at least a part of the screen list into the classification items, and calculates the appearance ratio based on the number of the screens classified into the classification items for each classification item. The estimation support device according to any one of Appendix 1 to Appendix 3, characterized in that the device is used.

(Appendix 5)
The estimation support device according to Appendix 4, wherein the appearance ratio calculating means classifies each screen into the classification items according to a classification rule in which the classification items and keywords are associated with each other.

(Appendix 6)
The description in any one of Supplementary notes 1 to 5, wherein the man-hour calculation means for calculating the man-hour increase by multiplying the man-hour increase rate of the entire requirement by the man-hour estimated from the requirements other than the requirement is provided. Estimate support device.

(Appendix 7)
Addendum 1 to 5 is provided with a man-hour calculation means for calculating the estimated man-hour by multiplying the man-hour increase rate of the entire requirement by adding 1 to the man-hour estimated from the requirements other than the requirement. The estimation support device described in any of.

(Appendix 8)
The estimation support device according to Appendix 1 to Appendix 7, wherein the requirement is a requirement for a UI (User Interface).

(Appendix 9)
Each requirement to be satisfied by the system to be estimated is classified into classification items, the result of the classification is stored in the classification storage unit, the appearance ratio in the system is calculated for each of the classification items, and the appearance ratio is calculated as the appearance ratio. It is stored in a storage unit, and based on the classification result and the appearance ratio, the man-hour increase rate of the requirement is multiplied by the appearance ratio of the classification item corresponding to the requirement, and the appearance ratio of each of the requirements is multiplied. An estimation support method characterized by summing up the results of multiplication, calculating the man-hour increase rate for the entire requirement, and outputting the man-hour increase rate for the entire requirement.

(Appendix 10)
The estimation support method according to Appendix 9, wherein the classification item is the content of data manipulation.

(Appendix 11)
The estimation support method according to Appendix 9 or Appendix 10, wherein the estimation support method performs the classification of each of the requirements according to a classification rule in which the classification item and a keyword are associated with each other.

(Appendix 12)
The estimation support method classifies each screen of at least a part of the screen list into the classification items, and calculates the appearance ratio based on the number of the screens classified into the classification items for each of the classification items. The estimation support method according to any one of Supplementary note 9 to Supplementary note 11, characterized in that.

(Appendix 13)
The estimation support method according to Appendix 12, wherein each of the screens is classified into the classification items according to a classification rule in which the classification items and keywords are associated with each other.

(Appendix 14)
The estimation support method according to any one of Supplementary notes 9 to 13, wherein the man-hour increase is calculated by multiplying the man-hour increase rate of the entire requirement by the man-hour estimated from the requirements other than the requirement.

(Appendix 15)
Described in any of Appendix 9 to Appendix 13, characterized in that the estimated man-hours are calculated by multiplying the rate of increase in man-hours of the entire requirement by 1 and the man-hours estimated from requirements other than the requirements. Estimate support method.

(Appendix 16)
The estimation support method according to Appendix 9 to Appendix 15, wherein the requirement is a requirement for a UI (User Interface).

(Appendix 17)
On the computer
A requirement classification function that classifies each requirement that the system to be estimated should meet into classification items and stores the result of the classification in the classification storage unit.
An appearance ratio calculation function that calculates the appearance ratio in the system for each of the classification items and stores the appearance ratio in the appearance ratio storage unit, and
Based on the classification result and the appearance ratio, the man-hour increase rate of the requirement is multiplied by the appearance ratio of the classification item corresponding to the requirement, and the result of the multiplication of each requirement is added up. An estimation support program characterized by realizing an increase rate calculation function that calculates the man-hour increase rate of the entire requirement and outputs the man-hour increase rate of the entire requirement.

(Appendix 18)
The estimation support program according to Appendix 17, wherein the classification item is the content of data manipulation.

(Appendix 19)
The estimation support program according to Appendix 17 or Appendix 18, wherein the requirement classification function performs the classification according to a classification rule in which the classification item and a keyword are associated with each other.

(Appendix 20)
The appearance ratio calculation function classifies each screen of at least a part of the screen list into the classification items, and calculates the appearance ratio based on the number of the screens classified into the classification items for each classification item. The estimation support program according to any one of Appendix 17 to Appendix 19, which is characterized in that the program is performed.

(Appendix 21)
The estimation support program according to Appendix 20, wherein the appearance ratio calculation function classifies each screen into the classification items according to a classification rule in which the classification items and keywords are associated with each other.

(Appendix 22)
On the computer
Described in any one of Supplementary notes 17 to 21, wherein the man-hour calculation function for calculating the man-hour increase by multiplying the man-hour increase rate of the entire requirement by the man-hour estimated from the requirements other than the requirement is realized. Estimate support program.

(Appendix 23)
On the computer
Addendum 17 to the feature that the man-hour calculation function for calculating the estimated man-hour is realized by multiplying the man-hour increase rate of the entire requirement by 1 and the man-hour estimated from the requirements other than the requirement. The estimation support program described in any of 21.

(Appendix 24)
The estimation support program according to Appendix 17 to Appendix 23, wherein the requirement is a requirement for a UI (User Interface).

(Appendix 25)
A computer-readable recording medium on which the estimation support program according to any one of Supplementary note 17 to Supplementary note 24 is recorded.

The present invention has been described above using the above-described embodiment as a model example. However, the present invention is not limited to the above-described embodiments. That is, the present invention can apply various aspects that can be understood by those skilled in the art within the scope of the present invention.

This application claims priority on the basis of Japanese application Japanese Patent Application No. 2015-205530 filed on October 19, 2015, and the entire disclosure thereof is incorporated herein by reference.

10, 20, 30 Estimate support device 11 Requirements classification unit 12 Appearance ratio calculation unit 13 Increase rate calculation unit 14 Classification storage unit 15 Appearance ratio storage unit 26 Classification rule storage unit 37 Manpower calculation unit 40 Information processing device 41 Communication interface 42 Input / output Interface 43 Computational device 44 Storage device 45 Non-volatile storage device 46 Drive device 47 Recording medium

Claims (10)

A requirement classification means that classifies each requirement that the system to be estimated should meet into classification items and stores the classification result in the classification storage unit.
An appearance ratio calculation means that calculates the appearance ratio in the system for each of the classification items and stores the appearance ratio in the appearance ratio storage unit.
Based on the classification result and the appearance ratio, the man-hour increase rate of the requirement is multiplied by the appearance ratio of the classification item corresponding to the requirement, and the result of the multiplication of each requirement is added up. An estimation support device including an increase rate calculation means for calculating the man-hour increase rate of the entire requirement and outputting the man-hour increase rate of the entire requirement. The estimation support device according to claim 1, wherein the classification item is the content of data manipulation. The estimation support device according to claim 1 or 2, wherein the requirement classification means performs the classification according to a classification rule in which the classification item and a keyword are associated with each other. The appearance ratio calculation means classifies each screen of at least a part of the screen list into the classification items, and calculates the appearance ratio based on the number of the screens classified into the classification items for each of the classification items. The estimation support device according to any one of claims 1 to 3, wherein the estimation support device is characterized. The estimation support device according to claim 4, wherein the appearance ratio calculating means classifies each screen into the classification items according to a classification rule in which the classification items and keywords are associated with each other. One of claims 1 to 5, wherein the man-hour calculation means for calculating the man-hour increase by multiplying the man-hour increase rate of the entire requirement by the man-hour estimated from the requirements other than the requirement is provided. Described estimation support device. Claims 1 to 1 include a man-hour calculation means for calculating the estimated man-hours by multiplying the man-hour increase rate of the entire requirement by adding 1 to the man-hours estimated from the requirements other than the requirements. The estimation support device according to any one of 5. The estimation support device according to any one of claims 1 to 7, wherein the requirement is a requirement for a UI (User Interface). Each requirement to be satisfied by the system to be estimated is classified into classification items, the classification result is stored in the classification storage unit, the appearance ratio in the system is calculated for each of the classification items, and the appearance ratio is stored in the appearance ratio storage unit. Based on the classification result and the appearance ratio, the man-hour increase rate of the requirement is multiplied by the appearance ratio of the classification item corresponding to the requirement, and the multiplication of each of the requirements is performed. An estimation support method characterized by summing up the results, calculating the man-hour increase rate for the entire requirement, and outputting the man-hour increase rate for the entire requirement. On the computer
A requirement classification function that classifies each requirement that the system to be estimated should meet into classification items and stores the classification result in the classification storage unit.
An appearance ratio calculation function that calculates the appearance ratio in the system for each of the classification items and stores the appearance ratio in the appearance ratio storage unit, and
Based on the classification result and the appearance ratio, the man-hour increase rate of the requirement is multiplied by the appearance ratio of the classification item corresponding to the requirement, and the result of the multiplication of each requirement is added up. An estimation support program characterized by realizing an increase rate calculation function that calculates the man-hour increase rate of the entire requirement and outputs the man-hour increase rate of the entire requirement.

Images