JP2003263320A - Estimating operation support system, method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To support a series of estimating operations entirely, including estimation of software scales, estimation of man hours for development, and estimation of development costs. <P>SOLUTION: A control part 2 outputs to a display part 4 or the like a screen urging an operator to designate the scale of software and techniques for the estimation of man hours for development, according to an estimating operation support program 10. Once the operator has designated the estimating techniques, the control part 2 outputs to the display part 4 or the like input screens for the information needed to do estimations using the designated techniques. The operator then inputs the information to the screens displayed one by one. The control part 2 estimates the scale of software and the man hours for development, using the input information and information previously retained in a management database 21. Further, the operator is also urged to input the information needed for the estimation of development costs, and the development costs are calculated from the input information. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a quotation work support system, a quotation work support method, and a quotation work support program for supporting a quotation work of a development target system.

[0002]

2. Description of the Related Art In developing a system using software, the scale of the software, the number of development steps, and the development cost are estimated. However, whether or not a highly accurate estimate can be made depends largely on the experience of the person making the estimate.
It was difficult to estimate properly unless you were an advanced information engineer with experience. Therefore, various devices and methods for supporting the estimation work have been proposed. For example, Japanese Patent Laid-Open No. 4-6
Japanese Patent No. 0833 describes an apparatus for estimating the man-hours and development costs of software development. Further, JP-A-7-191839 discloses a method of estimating the total number of steps of a program to be developed. Japanese Unexamined Patent Publication No. 11-203351 describes an apparatus, a method, and the like for estimating the number of work steps.

[0003]

However, the conventionally proposed apparatus and method cannot support the entire series of estimation work such as estimation of software scale, estimation of development man-hours, and estimation of development cost. . For example, the device described in Japanese Patent Laid-Open No. 4-60833 cannot support the estimation of the software scale. Further, in the method described in Japanese Patent Laid-Open No. 7-191839, the total number of steps of the program is only estimated, and the development cost and the like cannot be estimated. JP-A-11-
The development cost cannot be estimated with the device and method described in Japanese Patent No. 203351.

As described above, the conventionally proposed apparatus and method only support a part of the estimation work from estimation of software scale to estimation of development cost. Therefore, in the estimation of the software scale, the development man-hour, and the development cost, there is a portion that can be estimated with high accuracy only by an experienced person.

In addition, the worker who performs the estimation work may be present at a place distant from the device that supports the estimation.
Even if the worker is in a remote place, it is preferable to be able to proceed with the work by using the common data.

Further, the operator may change the estimation conditions and the like. However, if the worker redoes the estimation work from the beginning, the burden on the worker will increase.

There is not only one method for estimating the software scale and development man-hours but also a plurality of methods. It is preferable for the operator to be able to select one from a plurality of estimation methods and receive assistance for the estimation work by that method.

An object of the present invention is to be able to support the entire series of estimation work such as estimation of software scale, estimation of development man-hours, and estimation of development cost. It also aims to enable the worker to proceed with the estimation work even in a remote location. Further, it is an object of the present invention to enable the operator to correct the estimation result without burdening the operator even if the estimation conditions are changed. Moreover, it aims at enabling a worker to select an estimation method.

[0009]

A quotation work support system according to the present invention is a quotation work support system for supporting a quotation work of a development target system, and inputs a scale estimation condition for estimating the software scale of the development target system. Then, enter the software scale estimation means for estimating the software scale based on the scale estimation conditions and the man-hour estimation conditions for estimating the development man-hours, and the development man-hour estimation means for estimating the development man-hours based on the man-hour estimation conditions and the development cost. Enter the cost estimation conditions for estimation and estimate the development cost based on the cost estimation conditions. Estimate the software cost estimation result, software scale estimation result, development man-hour estimation result, and development cost estimation result. It is characterized by including an estimation result presenting means for presenting to an operator To.

The scale estimation condition, the man-hour estimation condition, and the cost estimation condition are input through the communication network, and the software scale estimation result, the development man-hour estimation result, and the development cost estimation result are worked through the communication network. It may be configured to be presented to the person. With such a configuration, it is possible to support the estimation work of the worker at the remote place.

As a method for estimating the development man-hours from the worker,
Equipped with an estimation method reception means that accepts any one of the function point method, the method of deriving the software scale by the number of lines and deriving the development man-hours from the number of lines, and the method of deriving the development man-hours from the man-hours for each activity. It is preferable to estimate the development man-hours according to the method specified by the worker. With such a configuration, the worker can select an estimation method from a plurality of estimation methods.

For example, the software scale estimating means is
When the function point method is specified, the number of items of data handled by the software of the development target system and the degree of influence of the system characteristics of the development target system are input as scale estimation conditions, and the software scale is calculated from the number of items and the degree of influence. The number of function points to be calculated is calculated, and when the function point method is specified, the development man-hour estimation means inputs the information of the programming language used for development as man-hour estimation conditions, and the number of function points is a numerical value indicating the productivity of the programming language. Derive the development man-hours by dividing by.

Further, for example, when the estimating method receiving means inputs at least information about the development target system, and the software scale estimating means designates a method for estimating the software scale by the number of lines and deriving the development man-hours from the number of lines is designated. , Input the number of software lines expected in each subsystem of the development target system as a scale estimation condition, calculate the total number of software lines of the development target system from the number of lines of each subsystem, and the development man-hour estimation means is When the method of deriving the development scale from the number of lines by estimating the software scale with the number of lines is specified,
Developed by inputting the information of the programming language used for development as the man-hour estimation condition, dividing the total number of lines of the software by the numerical value showing the productivity of the programming language, and multiplying by the coefficient according to the information input by the estimation method reception means Derive the man-hours.

Further, for example, the estimation method accepting means inputs at least information on the development target system, and the development man-hour estimating means is expected for each activity when a method for deriving the development man-hour from the man-hour for each activity is designated. Input the quantity of the delivered product as the man-hour estimation condition, multiply the entered product quantity by the standard work man-hour per product unit for each activity, and use the estimation method to calculate the total of the multiplication results for each activity. The development man-hours are derived by multiplying the coefficient according to the information input by the reception means.

The development cost estimation means inputs, for example, the expected cost for each cost item and information on the skill level of the person in charge of development as a cost cost estimation condition, and multiplies the unit cost of the personnel cost according to the skill level by the development man-hours. The personnel cost is calculated by calculating the development cost from the personnel cost and each cost entered.

[0016] Further, the estimation condition holding means for holding the input scale estimation condition, man-hour estimation condition, and cost estimation condition, and whether or not the scale estimation condition, man-hour estimation condition, or cost estimation condition is changed The change information acquisition means for inquiring about the changes and inputting the changes when there is a change, and the size estimation conditions, the man-hour estimation conditions, and the cost estimation conditions held by the estimation condition holding means, and the changes input by the change information acquisition means. Based on the content
It is preferable to modify part or all of the software scale estimation result, the development man-hour estimation result, and the development cost estimation result. According to such a configuration, even if the estimation condition is changed, it is not necessary to input the estimation condition again from the beginning, and only the change content needs to be input. Therefore, the burden on the operator is reduced.

The estimate work support method according to the present invention is an estimate work support method for assisting the estimate work of the development target system, and includes an estimate method accepting step of accepting designation of a method for estimating the development man-hours from a worker who performs the estimate work. , Input the man-hour estimation condition for estimating the development man-hour by the method specified by the worker, and estimate the development man-hour using the man-hour estimation condition according to the method specified by the worker. Enter the cost estimation conditions for the development cost estimation process to estimate the development cost based on the cost estimation conditions, and present the estimation results of the development man-hours and the development cost estimation to the workers who perform the estimation work. And a process.

For example, as a method for estimating the development man-hour in the estimation method receiving step, a function point method, a method for estimating the software scale by the number of lines and a method for deriving the development man-hour from the number of lines, and a method for deriving the development man-hour from the man-hours for each activity If either the function point method or the method of estimating the software scale by the number of lines and deriving the development man-hours from the number of lines is specified, the scale estimation conditions for estimating the software scale of the development target system are specified. Input and include the software scale estimation process to estimate the software scale based on the scale estimation conditions.

For example, when the function point method is specified, the number of items of data handled by the software of the development target system and the degree of influence of the system characteristics of the development target system are input as the scale estimation conditions in the software scale estimation process. Calculate the number of function points, which represents the software scale, from the number of items and the degree of impact, and enter the information of the programming language used for development as the man-hour estimation condition in the development man-hour estimation process to determine the number of function points as the programming language productivity. The development man-hours are derived by dividing by the indicated value.

Further, for example, in the estimation method receiving step, if at least the information about the development target system is input and the method for estimating the software scale by the number of lines and deriving the development man-hour from the number of lines is specified, the software scale estimating step is performed. , Input the number of software lines expected in each subsystem of the development target system as the scale estimation condition, calculate the total number of software lines of the development target system from the number of lines of each subsystem, and in the development man-hour estimation process, Developed by inputting the information of the programming language used for development as the man-hour estimation condition, dividing the total number of lines of the software by the numerical value showing the productivity of the programming language, and multiplying by the coefficient according to the information input in the estimation method acceptance process Derive the man-hours.

Further, for example, when the method for deriving the development man-hours from the man-hours for each activity is specified by inputting at least the information on the development target system in the estimation-method receiving step, it is estimated in each activity in the development man-hour estimating step. Input the quantity of the delivered product as the man-hour estimation condition, multiply the entered product quantity by the standard work man-hour per product unit for each activity, and use the estimation method to calculate the total of the multiplication results for each activity. The development man-hours are derived by multiplying by the coefficient according to the information input in the acceptance process.

In the development cost estimation process, for example, information on the expected cost for each expense item and the skill level of the person in charge of development is input as a cost estimation condition, and the unit cost of the personnel cost corresponding to the skill level is multiplied by the development man-hours. The labor cost is calculated, and the development cost is calculated from the labor cost and each input cost.

Enter information via the communication network,
It is preferable to present each estimation result to the worker via the communication network. According to such a method, it is possible to support the estimation work of the worker at the remote place.

Before the estimation result presentation process, the operator is inquired whether there is a change in the information input up to the development cost estimation process. If there is a change, the change content is input and the input change content is entered. It is preferable to correct at least one or both of the estimation result of the development man-hour and the estimation result of the development cost based on the basis. According to such a method, the worker does not have to redo the work from the beginning even if the information is changed, so the work load is reduced.

The estimation work support program according to the present invention has a function of inputting a scale estimation condition for estimating the software scale of the development target system into a computer and estimating the software scale based on the scale estimation condition.
A function to input the man-hour estimation condition for estimating the development man-hour and to estimate the development man-hour based on the man-hour estimating condition, a function to enter the cost estimation condition to estimate the development cost and estimate the development cost based on the cost estimation condition, And software scale estimation results, development man-hour estimation results,
And the function of outputting the development cost estimation result.

[0026]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of an estimation work support system according to the present invention.
The quotation work support system of this example is a quotation processing server 1.
, Management database 21, and intermediate result table 31
And a client computer (hereinafter referred to as a client) 41. The quotation processing server 1 and the client 41 are connected via a communication network.
In this example, it is assumed that the connection is made via the Internet 51. The management database 21 is the quotation processing server 1.
Manages the data required when the various estimation processes are executed, and the estimation conditions input by the operator. The intermediate result table 31 is a storage area for storing the estimation result and data such as the conditions used when the estimation is performed. In this example, the management database 21 and the intermediate result table 31 are provided as devices different from the estimation processing server 1, but the management database 21 and the intermediate result table 31 are provided inside the estimation processing server 1. May be

FIG. 2 is an explanatory diagram showing an outline of the processing of the estimation processing server 1. The quotation processing server 1 acquires information about the development target system and the like from the worker (step S101). At this time, the estimation processing server 1 also specifies a method for estimating the software scale and the development man-hours according to the instruction of the worker. As a method of estimating the software scale and the development man-hour, there is, for example, a function point method (hereinafter referred to as FP method). In addition, the software scale is the number of program lines (number of steps)
There is a method to estimate the number of man-hours and to derive the development man-hour from the result. As a method of estimating the development man-hour, there is an activity accumulation method.

In the FP method, the number of function points (FP number) indicating the software scale is calculated based on the number of data items handled by the software of the development target system and the degree of influence by the system characteristics, and the development man-hour is calculated from the FP number. It is a method to guide. In the FP method, first, the number of data items is determined for each of the five categories of "internal logic file", "external interface file", "external input", "external output", and "external reference". The unadjusted FP number is calculated from Also, the degree of influence of the system characteristics is evaluated for each of 14 types of fields such as “data communication function” and “distributed data processing”, and the adjustment count is determined from the evaluation result.
The value obtained by multiplying the unadjusted FP number by the adjusted count becomes the FP number indicating the software scale. Development man-hours are calculated using the FP number.

The activity stacking method is a method of estimating the total man-hours by calculating man-hours for each work item (activity) in software development and obtaining the sum of man-hours of each activity. For the effort of each activity, multiply the number of deliverables of each activity (for example, the number of documents) by the standard work effort for each unit of deliverable (for example, the standard work effort for creating one document). Calculate by

The estimation processing server 1 estimates the software scale by the number of lines or the number of FPs according to the estimation method designated by the operator (steps S102, S10).
3) Estimate the development man-hours from the result (step S10)
4). When the activity stacking method is specified, the development man-hour is estimated according to the method (step S1).
05, S106). Subsequently, the estimation processing server 1 estimates the development cost (step S107). After a series of quotations is made, it is confirmed whether or not the quoting conditions are changed, and if there is any change, the quoting result is corrected (step S108). After that, the estimation result is output as a report (step S109).

Next, the configuration of the estimation processing server 1 will be described. The control unit 2 operates according to the estimation work support program 10 stored in the storage unit 3. The input unit 4 is composed of an input device such as a keyboard and a mouse, and information is input by an operator. The display unit 5 includes an output device such as a display device, and outputs information to the worker. The network interface unit 6 transmits / receives information to / from the client 41 via the Internet 51. The worker uses the input unit 4 and the display unit 5 to proceed with the estimation work. Further, the work may be advanced using the client 41.

The estimation work support program 10 includes programs 11 to 19 shown in FIG. The estimate work navigation gate program 11 is a program that causes the control unit 2 to execute an estimate support process or the like according to an instruction from the operator. According to the estimation work navigation gate program 11, the control unit 2 determines which method should be used for estimation, advances the estimation support process, and outputs the estimation result. In addition, the control unit 2
Estimate work According to the navigation program 11, whether to make an approximate estimate or a detailed estimate is also determined.
The help processing program 11 is a program that causes the control unit 2 to output an answer to an inquiry from an operator.

The FP method scale estimation program 13 is a program that causes the control unit 2 to execute the calculation process of the FP number based on the estimation conditions input by the worker. The FP method man-hour estimation program 15 is a program that causes the control unit 2 to execute a process of calculating a development man-hour from the FP number.

The line number scale estimation program 14 is a program that causes the control unit 2 to execute a process for calculating the number of lines indicating the software scale based on the estimation conditions input by the operator. Line man-hour estimation program 1
Reference numeral 6 is a program that causes the control unit 2 to execute processing for calculating the development man-hours from the number of lines.

The activity stacking man-hour estimation program 17 is a program for causing the control unit 2 to execute the development man-hour calculation process by the activity stacking method.

The cost estimation program 18 includes the control unit 2
Is a program for executing the development cost calculation process. The correction processing program 19 is a program that causes the control unit 2 to perform the correction (re-estimation) of the estimation based on the changed estimation conditions or the like by the worker.

Next, the management database 21 will be described. The help information table 22 holds an answer to be presented to the inquiry from the worker.

In the FP method function number estimation factor and each element weighting table 23, the number of items input by the operator and the weighting information according to the number of items are registered.
FIG. 3 shows an example of the FP method function number estimation factor and data registered in each element weighting table 23. here,
An example of "external output" is shown. For example, it is assumed that there is a “XXX list” as data that the development target system outputs to the outside, and that the “XXX list” includes three items. When the operator inputs “3” as the number of items in the “XXX list”, the control unit 2 registers 3 as the number of items corresponding to the “XXX list”. Then, the control unit 2 determines that the weighting categories are “low”, “average”, and
It is judged whether it is classified as “high” and the judgment result is also registered. Similarly, other external output data such as the “XXY analysis table” is also registered.

Further, in the FP method function number estimation factor and each element weighting table 23, how many external output data such as “XXX list” are stored for each weighting category of “low”, “average” and “high”. Register if there is any. For example,
Only "XXX list" and "XXY analysis table" are "low"
It is assumed that they are classified into the following categories. In this case, as shown in FIG. 4, 2 is registered as the number of external output data corresponding to “low”.

Although the "external output" section is described as an example here, the information regarding "internal logic file", "external interface file", "external input", and "external reference" is also the FP method function. The number estimation factor and each element weighting table 23 are registered.

Further, in the FP method function number estimation factor and each element weighting table 23, as shown in FIG. 5, the degree of influence by the system characteristic is also registered. This degree of influence is evaluated by the operator for each of the 14 types of fields shown in FIG. The worker determines the degree of influence of each field with a score of 0 to 5, and the score is registered as shown in FIG. The adjustment coefficient used in the FP method is determined by the sum of the scores.

FIG. 6 shows an example of the FP number table 24.
In the FP number table 24, five categories of “internal logic file”, “external interface file”, “external input”, “external output”, and “external reference” are stored.
The number of data classified as “low”, “average”, and “high” is registered. In addition, the unadjusted FP number calculated based on the number of weighted data is also registered for each category such as “external output”. It is assumed that the weighting factors are defined as P, Q, and R, corresponding to "low", "average", and "high", respectively. "Low", "Average", "High"
The weighting factors P, Q, and
The unadjusted FP number is calculated by summing the results multiplied by R. The FP number table 24 holds the unadjusted FP numbers of the five sections, and also holds the total of the unadjusted FP numbers. The FP number is obtained by multiplying the total value of the unadjusted FP numbers of each section by the adjustment coefficient.

Actual scale and man-hour table 2 by industry / business
5 holds the results of the software scale and the development man-hours in the systems developed in the past. FIG. 7 shows an example of information held in the industry / business-specific achievement scale and man-hour table 25. As shown in FIG. 7, the results of the software scale and the development man-hours are held for each business type and business to which the software is applied. The industry / business-based actual scale and man-hour table 25 is used when the worker estimates the software scale based on the number of lines.

The language productivity table 26 holds numerical values indicating productivity in system development for each program language. The numerical value showing productivity is used when calculating development man-hours. FIG. 8 is an example of productivity information used when the development man-hours are obtained from the FP number. As shown in FIG. 8, "Visual Basic", "C", "Jav"
Numerical value n indicating productivity according to languages such as "a (registered trademark)"
Holds x, ny, nz, etc. The numerical value of the productivity used when the development man-hour is calculated from the FP number is calculated in consideration of the productivity in each work item such as “software requirement analysis” and “software system design”. When estimating the development man-hour from the FP number, the development man-hour is obtained from the relational expression “FP number / productivity = development man-hour”.

The language-specific productivity table 26 also holds, for each program language, the value of productivity used when estimating the development man-hours from the number of program lines. When estimating development man-hours from the number of lines, "Estimated number of lines ÷
The development man-hour is calculated from the relational expression "productivity x fluctuation count = development man-hour".

As described above, the relationship of "estimated number of lines / productivity * variable count = man-hours for development" is established. In addition, in the activity stacking method, the relationship “man-hours obtained by stacking each activity × variation coefficient = development man-hours” is established. The adjustment coefficient / variation coefficient table 27 holds the variation coefficient that establishes these relationships. Since the coefficient of variation differs between the case of rough estimation and the case of detailed estimation, the adjustment coefficient / variation coefficient table 27
The coefficient of variation for each rough estimate and detailed estimate is retained. Further, the coefficient of variation is determined according to the scale of development, the complexity of the system, the required quality, the degree of experience of the programmer, etc., so the adjustment coefficient / variation coefficient table 27 holds the coefficient of variation for each combination of these conditions. To do. Furthermore, the adjustment coefficient / variation coefficient table 27 holds the variation coefficient used when estimating by the number of lines and the variation coefficient used in the activity stacking method.

Standard man-hour table 28 for each activity
Holds standard work man-hours per unit of deliverable for each activity. For example, in a work item (activity) called "detailed design", a detailed design document is a product. In this case, the standard man-hour table 28 for each activity holds the man-hour required to create one detailed design document in association with the activity "detailed design". For other activities as well, standard work man-hours are held similarly. The standard man-hour table 28 for each activity is used when the worker selects the estimation by the activity accumulation method.

The rank-based average unit price table 29 holds information on unit price of personnel expenses according to the skill level (rank) of a person in charge of development such as a programmer or a system engineer. The unit price is the unit cost of labor cost, and is the labor cost per unit man-hour. The rank-based average unit price table 29 is used when estimating personnel costs. The cost component element table 30 holds information on each expense item that prompts the operator to input the cost. For example, information of each expense item such as material expense, machine expense, travel expense, and travel expense is held. FIG. 9 shows an example of information held by the cost component table 30. If the cost item such as the outsourcing cost is further classified into the expense item such as travel expenses and travel expenses, the cost component table 30 also holds the expense item as the middle classification. As will be described later, the estimation processing server 1 presents each expense item to the worker and prompts the operator to select an expense item to be estimated. The worker
Enter the cost etc. for each of these items. Then, the development cost is estimated based on the input information. When the operator also indicates the content of the expense item, the cost component table 30 also holds information indicating the content of the expense item.

Next, the intermediate result table 31 will be described. The scale estimation result table 33 is a storage area for holding the estimation result of the software scale. Similarly, the man-hour estimation result table 34 and the cost estimation result table 35 are storage areas for holding the development man-hour and development cost estimation results, respectively. The target system specific content table 31 is a storage area that holds data used as estimation conditions.

In the client 41, the control unit 42
Operates according to a program stored in the storage unit 43. The input unit 44 and the display unit 45 have the same configurations as the input unit 4 and the display unit 5 of the estimation processing server 1, respectively. The network interface unit 56 transmits / receives information to / from the estimation processing server 1 via the Internet 51.

The tool activation program 47 stored in the storage unit 43 is a program that causes the control unit 42 to make a request to start the estimation support process for the estimation processing server 1.
The estimation result download program 48 is a program that causes the control unit 2 to acquire each estimation result and the like. The estimation result display program 49 is a program for causing the control unit 2 to display each estimation result and the like.

In the above example, software scale estimating means, development man-hour estimating means, development cost estimating means,
The estimation method acceptance means and the change information acquisition means are realized by the control unit 2 and the input unit 4. The estimation result presenting means is realized by the control unit 2 and the display unit 5. Each of these means may be regarded as realized by the control unit 2, the network interface unit 6, and the client 41. The estimation condition holding means is realized by the intermediate result table 31.

Further, the storage unit 3 inputs into the computer scale estimation conditions for estimating the software scale of the development target system, a function for estimating the software scale based on the scale estimation conditions, and a man-hour estimation for estimating the development man-hours. A function to input conditions and estimate development man-hours based on man-hour estimation conditions, a function to enter cost estimation conditions to estimate development costs, estimate development costs based on cost estimation conditions, and software scale estimation results.
Holds an estimation work support program for realizing the function of outputting the estimation results of development man-hours and the estimation results of development costs.

Next, the operation will be described. Although the control unit 2 actually operates, the operation of each program will be described below. Further, the operator operates the input unit 4 and confirms the display on the display unit 5. Figure 1
0 and 11 are flow charts showing an example of the processing progress of the estimation support processing. First, the Quotation Work Navigate Program 11
Displays a work support guidance screen on the display unit 10 in response to a worker's request. FIG. 12 is an example of the guidance screen. The operator confirms the rough flow of work on this screen. Next, the quotation work navigation gate program 11 is shown in FIG.
The screen illustrated in FIG. 3 is displayed to prompt the operator to make a selection, and it is determined whether the rough estimate or the detailed estimate is made according to the operator's selection (step S111). The operator inputs a selection result by clicking any one of the selection buttons 61 with a mouse.

Subsequently, the estimation work navigation gate program 11 acquires information on the development target system and the like (step S112). At this time, the screens illustrated in FIGS. 14 and 15 are displayed on the display unit 10 to prompt the operator to input information. In step S112, as the information on the development target system and the like, for example, information on the development scale, the complexity of the system, the required quality, the degree of experience of the developer, etc. is acquired. It also acquires information about the estimation method specified by the worker. "Q2", "Q3", "Q4" shown in FIG.
Each adopts the estimation method by the FP method,
This is a question for confirming whether to adopt the estimation method based on the number of lines or the activity accumulation method. The worker inputs an answer and specifies the estimation method. The worker also inputs the scale of development, the complexity of the system, the required quality, the degree of experience of the developer, etc. by answering various other questions. The estimation work navigation gate program 11 follows the information acquired in step S112.
A method for estimating the software scale and the development man-hours is determined (step S113). After step S113, the estimation support is advanced according to the determined method.

First, the case of making an estimation by the FP method will be described. If it is determined in step S113 that the FP method is adopted, the FP method scale estimation program 13
Inputs the number of items of data handled by the development target system for each of the five types of categories: "internal logic file", "external interface file", "external input", "external output", and "external reference" (step S114).

For example, for the category of "external output", F
The P method scale estimation program 13 uses the “X
A screen prompting the user to input the name of output data such as "XX list" and the number of items included in the data is output. When the operator inputs the name and the number of items such as "XXX list", the FP
The legal scale estimation program 13 converts the entered information into F
P-method function number estimation factor and each element weighting table 23
Register with. Further, it is determined whether the weighting category is classified into “low”, “average”, or “high” according to the number of items, and the determination result is also registered as illustrated in FIG. Furthermore, the FP method scale estimation program 13
Check the number of external output data determined as "low", the number of external output data determined as "average", the number of external output data determined as "high", and register as illustrated in FIG. To do. Here, the case of “external output” has been described as an example, but similar processing is performed for other categories such as “internal logical file”.

Next, the FP method scale estimation program 13
Calculates the unadjusted FP number (step S115). F
The P-law scale estimation program 13 registers the information registered as illustrated in FIG. 4 in the FP number table 24. Then, the unadjusted FP is calculated as follows for each of the five types of divisions such as “internal logical file”, and the FP number table 2
Register in 4. In each category, the number of data determined as “low” is multiplied by the weighting coefficient corresponding to “low”.
The same calculation is performed for “average” and “high”.
Then, the sum of the multiplication results regarding “low”, “average”, and “high” is set as the unadjusted FP number. Furthermore, the total of the unadjusted FP numbers of the five types of sections is calculated, and the FP number table 24
Register with.

Next, the FP method scale estimation program 13
About 14 kinds of fields such as "data communication function",
Obtain the degree of influence of the characteristics of each field. The FP method scale estimation program 13 outputs a screen prompting the operator to input the degree of influence. The operator evaluates the degree of influence of the system characteristics in each field with a score of 0 to 5 and inputs the score. The FP method scale estimation program 13 registers each input score as illustrated in FIG. Then, the adjustment coefficient is determined by the total sum of the scores of 14 fields.
Furthermore, the unadjusted FP number calculated in step S115 (5
Multiply the adjustment factor by the sum of the unadjusted FP numbers of the types of categories)
The P number is calculated (step S116). This FP number is the estimation result of the software scale, and the software scale is represented by the FP number. The FP method scale estimation program 13 stores the estimation result of the software scale in the scale estimation result table 33, and also stores the information used for the estimation (estimation condition input by the operator) in the target system characteristic content table 32. .

Next, the FP method man-hour estimation program 15
Displays a screen for prompting the input of the programming language used for development on the display unit 5 to acquire the programming language information. Then, the numerical value indicating the productivity in the programming language is extracted from the language-specific productivity table 26 (step S117). The FP method man-hour estimation program 15 calculates the development man-hour by dividing the FP number obtained in step S116 by a numerical value indicating productivity (step S118). The FP method man-hour estimation program 15 causes the man-hour estimation result table 34 to hold the development man-hour estimation result, and causes the target system characteristic content table 32 to hold the information used for the estimation.

The process flow of steps S114 to S118 is the same in both the rough estimation and the detailed estimation, but the coefficients used in the process are different.

Next, the case of estimating the number of lines will be described. When it is determined in step S113 that the estimation method based on the number of lines is adopted, the line number scale estimation program 14 displays the performance information of the software scale and the development man-hour in the system developed in the past on the display unit 5 (step S119). ). This performance information is extracted from the business / business-specific performance scale and man-hour table 25.
For example, the information illustrated in FIG. 7 is extracted from the industry / business-specific achievement scale and man-hour table 25 and displayed. The line number scale estimation program 14 also displays on the display unit 5 a screen prompting the user to input the number of lines of the program for each subsystem of the development target system.

The worker browses the displayed information and confirms the software scale of the system similar to the development target system. For example, if the system to be developed is a financial system and a process related to deposits and loans is realized, the number of lines of the system developed in the past is confirmed from the information illustrated in FIG. The operator inputs the number of lines for each subsystem by referring to the number of lines of similar systems. The line number scale estimation program 14 acquires the input line number for each subsystem (step S120). Then, the total number of input lines is calculated to obtain the total number of lines in the development target system (step S121). This number of lines is the estimation result of the software scale. The line number scale estimation program 14 stores the software scale estimation result in the scale estimation result table 33, and stores the information used for the estimation in the target system characteristic content table 32.

Subsequently, the program for estimating the number of lines and man-hours 1
In the same way as in step S117, step 6 extracts a numerical value indicating the productivity of the programming language used for development (step S122). Further, the coefficient of variation is extracted from the adjustment coefficient / variation coefficient table 27 (step S123). The coefficient of variation differs depending on the scale of development, the complexity of the system, the required quality, the degree of experience of a programmer, etc., whether it is a rough estimate or a detailed estimate. The line man-hour estimation program 16
The coefficient of variation corresponding to the combination of the conditions (approximate estimation or detailed estimation, development scale, complexity, etc.) input in steps S111 and S112 is extracted.

The line man-hour estimation program 16 calculates the development man-hour by dividing the number of lines obtained in step S121 by a numerical value indicating productivity and multiplying it by the coefficient of variation (step S124). The line-number man-hour estimation program 16 causes the man-hour estimation result table 34 to hold the estimation result of the development man-hour, and causes the target system characteristic content table 32 to hold the information used for the estimation.

Next, the case where the activity stacking method is adopted will be described. When it is determined in step S113 that the activity stacking method is adopted, the activity stacking man-hour estimation program 17
Displays each activity in software development on the display unit 5 and prompts the user to select an activity to be estimated from the displayed activities. For example, each activity such as “requirement analysis” and “detailed design” is displayed. The worker specifies an activity to be estimated, and the activity stacking man-hour estimation program 17 acquires information on the specified activity (step S125).

The activity accumulation man-hour estimation program 17 causes the display unit 5 to display a screen prompting the user to input the quantity of the product for each designated activity. The quantity of this product is referred to as the number of factors. The worker inputs the number of factors for each activity. For example, if it is expected that there will be 100 detailed design documents that are the products of the “detailed design”, the number of factors “100” is input for the activity “detailed design”. For other activities, enter the number of factors in the same way. The activity accumulation man-hour estimation program 17 acquires the number of input factors (step S126).

Subsequently, the activity accumulation man-hour estimation program 17 extracts a standard work man-hour per unit of deliverable for each designated activity.
The standard man-hours are extracted from the standard man-hour table 28 for each activity. For example, for the activity “detailed design”, the number of man-hours required to create one detailed design document is extracted. Then, for each activity, the standard work man-hour is multiplied by the factor number to calculate the man-hour (step S
127). Further, the man-hours of each activity are accumulated (step S128). That is, the sum of man-hours of each activity is calculated.

The activity accumulation man-hour estimation program 17 extracts the coefficient of variation from the adjustment coefficient / variation coefficient table 27, as in the case shown in step S123. Then, the development man-hour is obtained by multiplying the sum of man-hours of each activity by the coefficient of variation (step S12).
9). Activity accumulated man-hour estimation program 1
7 stores the estimation result of the development man-hours in the man-hour estimation result table 34, and holds the information used for the estimation in the target system characteristic content table 32.

After the estimation of the development man-hours is completed, the cost estimation program 18 displays the expense item selection screen on the display unit 5 and prompts the operator to select the expense item to be estimated (step S130). FIG. 16 is an explanatory diagram showing an example of the expense item selection screen. The cost estimation program 18 includes a selection column for each expense item classified in the cost component table 30 in the expense item selection screen. In the example shown in FIG. 16, the portions displayed as “personnel cost”, “outsourcing cost”, “machine cost”, etc. are selection fields. If one expense item is further classified as a middle category as illustrated in FIG. 9, a selection column for expense items classified as a middle category is also included.

When the cost component element table 30 holds information indicating the contents of expense items, that information is also shown on the expense item selection screen. For example, as shown in FIG. 9, if the cost component table 30 holds the information "this personnel cost is the personnel cost of the employee.", This information is also displayed on the expense item selection screen. Also, "personnel cost = man-hour x unit price"
If the calculation formula is stored, information such as "man-hours and unit cost is required." May be displayed based on the information of this calculation formula.

The operator clicks the selection field of each expense item such as "personnel expenses" with the mouse, and then clicks the decision button with the mouse. In addition, when selecting the entire category of expenses,
You may select the higher expense item. For example, instead of mouse-clicking all the selection fields of “travel expenses”, “communication expenses”, “printing expenses”, and “others”, the higher-level “expenses” selection regions may be clicked.

When the labor cost (non-outsourcing cost) is selected in step S130, the cost estimation program 18 estimates the labor cost (step S1).
31). The cost estimation program 18 first displays on the display unit 5 a screen prompting the programmer or system engineer in charge of development to input the skill level. Then, when the information of the skill level is input from the worker, the information of the unit cost of the labor cost corresponding to the skill level is extracted from the rank-based average unit price table 29. Then, the labor cost is calculated by multiplying the development man-hour obtained in step S118 (or step S124 or step S129) by the unit money.

Next, the cost estimation program 18 prompts the operator to input a cost for each of the selected cost items other than the personnel cost (step S13).
2). For example, it is assumed that in addition to “personnel cost”, “material cost”, “travel expense” included in “expense”, and “communication expense” are selected. In this case, a screen prompting the user to input the costs of "travel expenses" and "communication expenses" included in "material expenses" and "expenses" is displayed. Then, the cost of each expense input by the worker is acquired.

When the labor cost included in the "outsourcing cost" is selected, the labor cost may be calculated as in step S131. Alternatively, similarly to the “material cost” or the like, the operator may be prompted to input the cost in step S132.

The cost estimation program 18 totals the personnel cost calculated in step S131 and the cost of each expense input in step S132 to estimate the cost related to the entire development (step S133). The total amount of each item such as personnel expenses is the cost estimation result. The cost estimation program 18 stores the cost estimation result in the cost estimation result table 33, and stores the information used for the estimation in the target system characteristic content table 32.

After calculating the cost estimation result, the correction processing program 19 changes the estimation condition and inquires of the operator whether it is necessary to correct or correct the already obtained estimation result (step S134). The correction processing program 19 displays, for example, a condition change confirmation screen illustrated in FIG. 17A, and prompts designation of whether or not to change the estimation condition, which condition is to be changed, and the like. The condition change confirmation screen is not limited to the screen shown in FIG. For example, changing the rough estimate / detailed estimate, or step S11.
The change of the information input in 2 may be designated. In the case of the screen illustrated in FIG. 17A, the operator mouse-clicks the selection field corresponding to the estimated condition to be changed. If there is no change, "No change in quotation conditions"
Click the selection field of.

When the estimation condition is changed, the correction processing program 19 displays the estimation condition change screen according to the designated selection field. For example, when “change number of items of external output in FP method” is selected, the correction processing program 19 displays the screen illustrated in FIG.
Prompt for the number of items after the change. When the changed estimated condition is input, the correction processing program 19 updates the estimated condition information held in the target system characteristic content table 32. Then, the FP method scale estimation program 13 or the like is called, and part or all of the estimation of the software scale, the estimation of the development man-hour, and the estimation of the development cost are redone. At this time, the estimation is performed again using the estimation conditions held in the target system characteristic content table 32. The corrected estimation result is held in the scale estimation result table 33, the man-hour estimation result table 34, and the cost estimation result table 35 according to the type of the estimation result.

Estimating work Navigate program 11
Output a report of the estimation result (step S13)
6). In step S136, the estimation work navigation gate program 11 determines the target system characteristic content table 3
2. From the scale estimation result table 33, the man-hour estimation result table 33, and the cost estimation result table 35,
Extract the estimation conditions, software scale estimation results, development man-hour estimation results, and development cost estimation results, respectively. Then, the display screen is edited so that the extracted information items can be collectively displayed, and the screen is displayed on the display unit 5. When "No change in estimation condition" is selected in step S134, the report output process is performed without performing the process of step S135.

When the worker performs a predetermined inquiry operation during the work, the help processing program 12
The answer to the inquiry is extracted from the help information table 22 and output to the display unit 4.

According to such an estimation work support system, it is possible to perform work support for the entire series of estimation work such as estimation of software scale, estimation of development man-hours, and estimation of development cost. Then, the work support system prompts the user to sequentially input predetermined items. Therefore, even a person who is not an advanced information engineer can proceed with a series of estimation work by sequentially inputting estimation conditions according to the displayed screen.

Further, the operator can select an estimate by the FP method, an estimate by the number of lines, an estimate by the activity stacking method, and the like. Therefore, the worker can perform the estimation work according to a desired method.

Further, after estimating the software scale, the development man-hour, and the development cost, it is confirmed whether or not the estimation condition is changed. If there is a change, the changed content and the already input estimation are made. Re-estimate using conditions and. Therefore, the operator only needs to input the contents of the change and can reduce the work load at the time of the change.

The display screens shown in the above example are examples, and the screens displayed are not limited to the above screens.

In the above example, the operator operates the input unit 4 and confirms the display on the display unit 5. The worker may operate the client 41. In this case, the control unit 42 of the client 41 requests the estimation processing server 1 to start the estimation support processing according to the tool activation program 47. Quotation processing server 1
In response to this request, transmits the information on the guide screen illustrated in FIG. 12 to the client 41 via the Internet 51. The subsequent operation is the same as the operation in steps S111 to S136. However, presenting information to workers,
The information input by the operator is acquired via the Internet 51.

In step S136, when the operator wants to confirm each estimation result, the control unit 42
According to the estimate result download program 48,
The estimation processing server 1 is requested to transmit the information held in the intermediate result table 31. In response to this request, the estimation processing server 1 uses the intermediate result table 31 to estimate conditions,
Extract the software scale estimation result, development man-hour estimation result, development cost estimation result, and the client 4
Send to 1. The client 41 edits the display screen according to the estimation result display program 49 so that each received information can be displayed collectively, and displays the screen on the display unit 45.
To display.

Since the quotation processing server 1 and the client 41 send and receive information via the Internet 51,
Even if the worker is away from the quotation processing server 1,
You can proceed with the estimation work. Then, even if the worker is in a remote place, it is possible to present the worker with the business / actual achievement scale, the data of the man-hour table 25, and the like.

The client 41 may not be provided if there is no person who estimates at a remote location. On the other hand, when it is premised that the worker's location is a remote place, the estimation processing server 1 may not include the input unit 4 and the display unit 5.

[0089]

According to the estimation work support system of the present invention, the scale estimation condition for estimating the software scale of the development target system is input, the software scale is estimated based on the scale estimation condition, and the development man-hours are estimated. The man-hour estimation condition is input, the development man-hour is estimated based on the man-hour estimation condition, the cost estimation condition for estimating the development cost is input, and the development cost is estimated based on the cost estimation condition. Therefore, it is possible to provide work support for the entire series of estimation work such as estimation of software scale, estimation of development man-hours, and estimation of development cost. As a result, even a person who is not an advanced information engineer can proceed with a series of estimation work.

According to the estimation work support method of the present invention, since the estimation technique receiving step of receiving the designation of the technique for estimating the development man-hours from the worker performing the estimation work is included, the worker can designate the estimation technique.

[Brief description of drawings]

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

FIG. 2 is an explanatory diagram showing an outline of processing of an estimation processing server.

FIG. 3 is an explanatory diagram showing an example of data held in an FP method function number estimation factor and each element weighting table.

FIG. 4 is an explanatory diagram showing an example of data collected for each weighting category.

FIG. 5 is an explanatory diagram showing an example of the degree of influence due to system characteristics.

FIG. 6 is an explanatory diagram showing an example of an FP number table.

FIG. 7 is an explanatory diagram showing an example of information held in a business / actual performance scale and man-hour table.

FIG. 8 is an explanatory diagram showing an example of productivity information.

FIG. 9 is an explanatory diagram showing an example of information held by a cost component element table.

FIG. 10 is a flowchart showing an example of the processing progress of the estimation support processing.

FIG. 11 is a flowchart showing an example of the processing progress of the estimation support processing.

FIG. 12 is an explanatory diagram showing an example of a guide screen.

FIG. 13 is an explanatory diagram showing an example of a screen that prompts the user to specify the type of estimate.

FIG. 14 is an explanatory diagram illustrating an example of a screen that prompts the user to input information about a development target system and the like.

FIG. 15 is an explanatory diagram illustrating an example of a screen that prompts the user to input information about a development target system and the like.

FIG. 16 is an explanatory diagram showing an example of an expense item selection screen.

FIG. 17 is an explanatory diagram showing an example of a screen presented when a condition is changed.

[Explanation of symbols] 1 Quotation processing server 2 control unit 3 storage 10 Estimate work support program 21 Management database 31 Intermediate result table 41 Client computer 51 Internet

Claims (17)

[Claims] 1. Software for estimating a software scale based on the scale estimating condition for estimating the software scale of the development target system by inputting a scale estimating condition for supporting the estimation work of the development target system. Enter the scale estimation means and the man-hour estimation conditions for estimating the development man-hours, enter the development man-hour estimation means for estimating the development man-hours based on the man-hour estimation conditions, and the cost estimation condition for estimating the development cost.
A development cost estimation means for estimating the development cost based on the cost estimation conditions, and an estimation result presentation means for presenting the software scale estimation result, the development man-hour estimation result, and the development cost estimation result to the worker who performs the estimation work. A quotation work support system characterized by having. 2. A scale estimation condition, man-hour estimation condition, and cost estimation condition are input via a communication network, and the software scale estimation result, development man-hour estimation result, and development cost estimation result are transmitted via the communication network. The estimate work support system according to claim 1, which is presented to a worker. 3. A function point method as a method for estimating development man-hours from an operator, a method for estimating software scale in number of lines and deriving development man-hours from the number of lines,
Claim 1 or claim 2 is provided with estimation method receiving means for accepting designation of any one of the methods for deriving development man-hours from the man-hours for each activity, and the development man-hour estimating means estimates the development man-hours according to the method specified by the worker. Estimated work support system described. 4. The software scale estimating means, when the function point method is designated, inputs the number of items of data handled by the software of the development target system and the degree of influence of the system characteristics of the development target system as scale estimation conditions. , The number of function points representing the software scale is calculated from the number of items and the degree of influence, and the development man-hour estimation means inputs the information of the programming language used for development as the man-hour estimation condition when the function point method is specified. The estimation work support system according to claim 3, wherein the development man-hours are derived by dividing the number of points by a numerical value indicating the productivity of the programming language. 5. The estimating method receiving means inputs at least information about the development target system, and the software scale estimating means develops the software scale by the number of lines, and when the method of deriving the development man-hours from the number of lines is specified, the development is performed. Input the number of software lines expected in each subsystem of the target system as the scale estimation condition, calculate the total number of lines of the software of the development target system from the number of lines of each subsystem. When the method of deriving the development man-hours from the estimated number of lines is specified as the number of lines, the information of the programming language used for development is input as the man-hour estimation condition, and the number of lines of the entire software is a numerical value indicating the productivity of the programming language Divide by and calculate according to the information entered by the estimation method reception means. Estimates work support system according to claim 3 or claim 4 derives the number of development processes by multiplying. 6. The estimation method receiving means inputs at least information on the development target system, and the development man-hour estimating means, when a method for deriving the development man-hours from the man-hours for each activity is designated, the expected result of each activity. Input the quantity of the product as the man-hour estimation condition, multiply the entered quantity of the product by the standard work man-hour per product unit for each activity, and add the estimation method acceptance means to the total of the multiplication results for each activity. The estimation work support system according to any one of claims 3 to 5, wherein the development man-hours are derived by multiplying by a coefficient according to the information input by. 7. The development cost estimation means inputs the expected cost for each expense item and information on the skill level of the person in charge of development as a cost estimation condition, and multiplies the unit cost of the personnel cost according to the skill level by the development man-hour. The estimation work support system according to any one of claims 1 to 6, wherein a personnel cost is calculated by calculating the development cost from each cost input as the personnel cost. 8. An operator for checking whether or not the estimated condition holding means for holding the entered scale estimating condition, man-hour estimating condition and cost estimating condition and whether the scale estimating condition, man-hour estimating condition or cost estimating condition is changed. Change information acquisition means for inquiring about the changes and inputting the changes when there is a change, and the size estimation conditions, man-hour estimation conditions, and cost estimation conditions held by the estimation condition holding means, and the changes input by the change information acquisition means. The estimation work according to any one of claims 1 to 7, which corrects part or all of the estimation result of the software scale, the estimation result of the development man-hour, and the estimation result of the development cost based on the contents. Support system. 9. A quotation work support method for supporting a quotation work of a development target system, which comprises a quotation technique acceptance step for accepting designation of a technique for estimating development manpower from a worker performing the quotation work, and a technique designated by the worker. Input the man-hour estimation condition for estimating the development man-hours, and enter the development man-hour estimation process for estimating the development man-hour using the man-hour estimation condition and the cost estimation condition for estimating the development cost according to the method specified by the worker. Then
It is characterized by including the development cost estimation process for estimating the development cost based on the cost estimation condition, and the estimation result presentation process for presenting the estimation result of the development man-hour and the estimation result of the development cost to the worker who performs the estimation work. Estimate work support method. 10. The method for estimating the development man-hours in the estimation method receiving step, the function point method, the method for estimating the software scale by the number of lines and the method for deriving the development man-hours from the number of lines, and the method for deriving the development man-hours from the man-hours for each activity. If either the function point method or the method of estimating the software scale by the number of lines and deriving the development man-hour from the number of lines is specified, the scale estimation conditions for estimating the software scale of the development target system are specified. The estimation work support method according to claim 9, further comprising a software scale estimation step of inputting and estimating the software scale based on the scale estimation condition. 11. When the function point method is specified, the number of items of data handled by the software of the development target system and the degree of influence of the system characteristics of the development target system are input as the scale estimation conditions in the software scale estimation process. Calculate the number of function points, which represents the software scale, from the number of items and the degree of influence, and enter the information of the programming language used for development as the man-hour estimation condition in the development man-hour estimation process, and the number of function points is the productivity of the programming language. The estimation work support method according to claim 10, wherein the development man-hours are derived by dividing by a numerical value indicating. 12. When a method of inputting at least information about a development target system and estimating a software scale by the number of lines and deriving development man-hours from the number of lines is specified in the estimation method acceptance step, development is performed in the software size estimation step. Enter the number of software lines expected in each subsystem of the target system as a scale estimation condition, calculate the total number of software lines of the development target system from the number of lines of each subsystem, and use the development man-hour estimation process for development. Information on the programming language to be used is input as the man-hour estimation condition, the number of lines of the entire software is divided by a numerical value indicating the productivity of the programming language, and the man-hours for development are multiplied by a coefficient according to the information input in the estimation method receiving step. 10. Derivation of
Alternatively, the estimation work support method according to claim 11. 13. When the method for deriving the development man-hours from the man-hours for each activity is specified in the estimation method receiving step and at least the information about the development target system is specified, the expected result of each activity in the development man-hour estimating step. Enter the quantity of the product as the man-hour estimation condition, multiply the entered quantity of the product by the standard work man-hour per unit of the product for each activity, and enter the estimation method acceptance process in the total of the multiplication results for each activity. The estimation work support method according to any one of claims 10 to 12, wherein the development man-hours are derived by multiplying by a coefficient according to the information input in. 14. In the development cost estimation process, information on expected cost for each cost item and skill level of the person in charge of development is input as a cost cost condition, and the unit cost of the personnel cost corresponding to the skill level is multiplied by the development man-hours. The estimation work support method according to any one of claims 9 to 13, wherein a labor cost is calculated, and a development cost is calculated from each cost input as the labor cost. 15. The estimation work support method according to claim 9, wherein information is input via a communication network, and each estimation result is presented to a worker via the communication network. . 16. Before the estimation result presentation step, the operator is inquired whether or not the information input up to the development cost estimation step is changed, and if there is a change, the change content is input and the input change is made. The estimation work support method according to any one of claims 9 to 15, wherein at least one or both of the estimation result of the development man-hour and the estimation result of the development cost are corrected based on the content. 17. A computer is provided with a scale estimation condition for estimating a software scale of a development target system, a function for estimating a software scale based on the scale estimation condition, and a man-hour estimation condition for estimating development man-hours, Input the function to estimate the development man-hour based on the man-hour estimation condition and the cost estimation condition to estimate the development cost,
A function to estimate the development cost based on the cost estimation conditions,
And a function to output the estimation result of the software scale, the estimation result of the development man-hour, and the estimation result of the development cost, and the estimation work support program.