JP2006085663A - Evaluation device for software development manhour cost - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an evaluation method of a software development manhour cost capable of evaluating the software development manhour cost with an objective and fair technique. <P>SOLUTION: The estimation and evaluation of a development cost of software is carried out by dividing a functional scale (function points) of the software by a productivity coefficient expressed by multiplication of a development language-based productivity value, a productivity adjustment coefficient, a process-based order rate, a work sharing rate and a repair rate, and by multiplying an additional value of the division value thereof and additional work manhours by a system engineer unit cost. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a software development man-hour cost estimation program and a software development man-hour cost estimation program for objectively and rationally evaluating the price (estimated amount) of software development man-hour cost of software constituting a computer system, a network, etc. It relates to the storage medium which memorize | stored.

  Information systems have permeated every corner of business and society, and the investment in information systems has become enormous, and software development costs account for a large percentage. However, because the software development cost (evaluation) estimation process is not structured, the estimates provided by vendors often carry out tasks such as ordering and system construction without showing a clear basis. Is the actual situation.

  Conventionally, when estimating the development man-hour cost of software constituting a computer system, it is common to calculate the development man-hour cost in consideration of the size of the software and the work contents. For this reason, estimation and evaluation work for software development man-hours often depend on the experience and intuition of a specific person such as an expert who has been engaged in software development work for many years.

  The LOC (Lines of Code) method exists as a method for estimating and evaluating software development man-hour costs, but with the advancement of IT technology since the 1990s, system configuration and development methods have become diversified and complicated. The correlation between the number of program lines and the development man-hours and costs has broken, and there is a limit to estimate based on experience and intuition cultivated by the LOC method. In view of this, the FP (Function Point) function has attracted attention instead of the LOC method. The FP method is a technique for measuring the amount of functions of software, and measures the scale of software functions by quantitatively measuring the scale from a system specification as shown in FIG. The evaluation value for the FP used when calculating the software development man-hours and costs is generally a quadratic function as shown in FIG.

  In addition, in the software estimation system disclosed in Japanese Patent Application Laid-Open No. 2002-222080 (Patent Document 1), a function information storage unit storing software function information and a function of a software project developed from the function information stored in the function information storage unit A function information selection unit that selects information and a function amount calculation unit that calculates the function amount of the software project using the function information selected by the function information selection unit are provided. Business area and scale are used to estimate development costs.

  An estimation work support system disclosed in Japanese Patent Application Laid-Open No. 2003-263320 (Patent Document 2) is an estimation work support system that supports an estimation work of a development target system, and inputs a scale estimation condition for estimating a software scale of the development target system. To input software size estimation means for estimating the software scale based on the size estimation conditions, to input the man-hour estimation conditions for estimating the development man-hours, and to estimate the development man-hours for estimating the development man-hours based on the man-hour estimation conditions The person who inputs the cost estimation conditions for the development cost, the development cost estimation means that estimates the development cost based on the cost estimation conditions, and the person who estimates the software scale estimation result, the development man-hour estimation result, and the development cost estimation result And an estimation result presenting means for presenting to the above. In the estimation of development costs, indirect costs are added to the multiplication value of man-hours for man-hours.

Furthermore, the system development estimation support system disclosed in Japanese Patent Application Laid-Open No. 2003-308449 (Patent Document 3) includes scale calculation information for calculating system scale information, which is information on the scale of a system to be developed, personnel required for system development, Information receiving means for receiving development man-hour calculation information for calculating development man-hour information that is a period from a client machine, and storage means for storing the scale calculation information and the development man-hour calculation information received by the information receiving means , Scale calculation function information for calculating system scale information based on the scale calculation information stored in the storage means, and development manhour calculation function information for calculating development manhour information based on the development manhour calculation information Calculation function information storage means for storing, estimate calculation means for calculating the development man-hour information, and the estimate calculation means Therefore, development man-hour information storage means for storing the calculated development man-hour information and the scale calculation information in association with each other, and information transmission means for transmitting the development man-hour information stored in the development man-hour information storage means to the client machine; A system development estimation support system comprising a processing device for controlling the operation of each of the means, wherein the processing device stores the scale calculation function information stored in the calculation function information storage means in the estimate calculation means. And the scale calculation information stored in the storage means, the system scale information is calculated based on the information, the development manhour calculation function information stored in the calculation function information storage means, and The system scale information and the development man-hour calculation information stored in the storage means are acquired, and the development man-hour information is obtained based on the information. It is intended to be calculated.
JP2002-2222080 JP 2003-263320 A JP 2003-308449 A

  As described above, in the conventional general evaluation method, there is no objective and rational basis for the evaluation value, and it is a question whether it is an appropriate evaluation amount. The evaluation of the software development man-hour cost is objective. Both the orderer and the ordering party strongly wanted to be able to execute with reasonableness. The same applies to the evaluation method using the FP value.

  In the software estimation system described in Patent Document 1, information necessary for FP calculation is prepared in advance for each development field, and the information is called up and used for software estimation, and information management is complicated. There is. Productivity by development language is not considered, productivity adjustment is impossible, and cost estimation is incomplete.

  In addition, the estimation work support system described in Patent Document 2 can support the entire series of estimation work of estimating the development man-hours and the development cost, but the size estimation condition for estimating the software scale of the development target system Enter the cost estimation conditions to estimate the software scale based on the scale estimation conditions, enter the effort estimation conditions to estimate the development man-hours, estimate the development man-hours based on the man-hour estimation conditions, and enter the development costs However, since the development cost is estimated based on the cost estimation condition, the development cost cannot be obtained quickly. There is a problem that productivity values by development language are not taken into account, and the productivity adjustment factor is for the providing side, and the procurement side cannot use it.

  Patent Document 3 has a problem that the adjustment coefficient has a strong viewpoint for the provider (developer) and is different from the viewpoint of the procurement side (user company). For example, if the provider's efforts such as the development language experience of the provider, the project management experience of the leader, and the proficiency level of the development support tool are reflected in the estimation of the development man-hour cost, this will be transferred from the provider to the procurement side. It will be a cost pass-through. In the system development estimation support system described in Patent Document 3, the productivity value for each development language is not considered. Also, there is a need for an objective setting method in which the adjustment factor is set subjectively, and the adjustment factor setting is complicated, simpler in practice, and the same result can be set by anyone. It has been.

  Furthermore, all of those described in Patent Documents 1 to 3 are estimates for new projects, and there is a problem that it is impossible to deal with repair projects. In practice, it is said that about 60 to 80% of system projects are maintenance projects, and if this cannot be handled, the business effect will be halved.

  The present invention has been made under the circumstances as described above, and an object of the present invention is to provide software development man-hours that can be used to evaluate software development man-hour costs in an objective and fair manner and with a simple system with reasonableness. An object is to provide a cost evaluation method, an evaluation value calculation device, and a program. In other words, the present invention is compatible with various environments and various development languages, is used by many companies, can be objectively compared and verified, has a logical viewpoint, and is not affected by the implementation. Software development man-hour cost estimation program that can be understood and understood by the user, can be measured at an early stage of system construction, and can be approached without personality, and a storage medium that stores the software development man-hour cost estimation program The purpose is to do.

  The present invention relates to a software development man-hour cost evaluation method, and the above object of the present invention is to provide a computer for estimating software development man-hour cost, and means for inputting a function scale of the software as a FP value. Means to input the development possible scale per month as the productivity value by development language, Means to input the productivity adjustment coefficient to adjust the productivity value by development language, basic design, detailed design, program design / manufacturing, software Means for inputting an order rate for each process in the air test and system test, means for inputting a work sharing ratio as a work sharing ratio, means for inputting a repair ratio for each process of the software as a development repair ratio, Productivity value by development language in each process, productivity adjustment factor, order rate by process, A means for calculating the productivity value per month as a productivity coefficient by multiplying the work sharing rate and the development and repair rate, respectively, and calculating the standard development man-hour by dividing the FP value in each process by the productivity coefficient Means for inputting an incidental work man-hour, means for inputting an amount of system engineer unit price, and calculating a development cost by multiplying the sum of the standard development man-hour and the incidental operation man-hour in each step by the system engineer unit price. This is achieved by functioning as a means.

  The above object of the present invention is to provide a computer for estimating the software development man-hour cost, a means for inputting the function scale of the software as an FP value, Means for inputting as a separate productivity value, means for inputting a productivity adjustment coefficient for adjusting the productivity value for each development language, and each process in basic design, detailed design, program design / manufacturing, software test and system test Means for inputting the order rate, means for inputting the work sharing ratio as the work sharing ratio, and inputting the development and repair ratio of the software in each development process of the basic design, the detailed design, and the program design / manufacturing as the development repair ratio Means in each test step of means, software test and system test Means for inputting a software test repair rate as a test repair rate, the productivity value for each development language in each step, the productivity adjustment factor, the ordering rate for each step, the work sharing rate and the development repair rate or the test Means for calculating the productivity value per month by multiplying the repair rate as a productivity coefficient; means for calculating the standard development man-hour by dividing the FP value in each process by the productivity coefficient; , Means for inputting the system engineer unit price, and means for calculating the development cost by multiplying the sum of the standard development man-hour and the incidental work man-hour in each step by the system engineer unit price. Achieved by:

  Further, the above object of the present invention is to provide means for inputting one or a plurality of development languages for using the computer for the input productivity value for each development language, means for inputting a utilization ratio for each development language, Productivity value table storage means for each development language that stores the productivity value per month for each development language, and the productivity value corresponding to the development language input from the productivity value table for each development language is read out , Multiplying the productivity value by the utilization ratio corresponding to the productivity value, and calculating the sum as a productivity value for each development language, or by inputting the productivity adjustment A computer for calculating a coefficient, a system means for inputting a system environment coefficient, a system means for inputting a system scale coefficient, a means for inputting a processing load coefficient, Means for inputting quality requirement coefficient, means for inputting document coefficient, productivity adjustment table in which coefficient values are recorded in advance for each item of the system environment coefficient, the system scale factor, the processing load coefficient, and the quality requirement coefficient By functioning as a storage means, a means for calculating the productivity adjustment coefficient by reading and multiplying the corresponding coefficient values of the system environment coefficient, the system scale coefficient, the processing load coefficient, and the quality requirement coefficient, Alternatively, with respect to the development and renovation rate that is input, means for inputting the number of existing lines of the software as the number of parent lines before modification, means for inputting the number of modified lines of an existing system using the software, and the existing system Means for inputting the number of externally added function lines to be added separately, and Means for calculating the first work rate by multiplying the work ratio performed in the confirmation work for the number of parent lines before renovation after software renovation as R1%, and confirming the number of renovation lines after the software refurbishment The development work by adding the means for calculating the second work rate by multiplying the work ratio performed in the work as R2%, the first work rate multiplication means, the second work rate multiplication means, and the number of externally added function rows A means for calculating a rate, a means for inputting the number of modified lines of the software as a number of parent lines after modification, and a means for calculating the development / repair rate by dividing the development work rate by the number of modified mother lines Or a means for inputting the number of data item types of the software as the number of parent DETs before the modification, the number of parent DETs before the modification, A means for calculating the third work rate by multiplying the work ratio performed in the confirmation work on the number of parent DETs before repair after the repair as R3%, and the number of modified data item types for modifying the software as the modified DET number Means for inputting, means for calculating the sum of the third work rate and the number of modified DETs as a development work rate, means for inputting the number of data item types after modification of the software as the number of parent DETs after modification, the development work rate Is divided by the post-repair matrix DET number to calculate the development refurbishment rate, or the computer is renewed for the test renovation rate inputted, and the number of test items at the time of new development of the software is refurbished Means to input as the number of test items at the time of previous development / new development, the number of test items at the time of previous development / new development Means for multiplying the work ratio performed in the confirmation work with respect to the number of test items at the time of occurrence as R4% and calculating as a first test work ratio, means for inputting the number of test items performed at the time of repair, the first test work ratio and the Means for calculating the total test work rate by adding the number of test items; means for inputting the number of test items at the time of new development after the software has been renovated; By functioning as a means for calculating the test renovation rate by dividing the work rate by the number of test items at the time of the remodeling base / new development, or for estimating the software development man-hour cost, the computer By making it function as a means to calculate the total order rate by process in the process as the total order rate, or software development man-hours In order to estimate the software development man-hours, or to cause the computer to estimate the software development man-hour cost Means for inputting a contractor-provided price provided by a client who requested the software modification in the above, means for calculating a sum of the contractor-presented prices in each step as a total contractor-presented price, and the contractor-provided price in each step Is more effectively achieved by functioning as a means for calculating the price disparity ratio by dividing the development cost and a means for calculating the total price disparity ratio by dividing the total contractor presented price by the total development cost. Is done.

The above object of the present invention is achieved by providing a computer readable storage medium storing the above software development man-hour cost estimation program.

  According to the present invention, it is a relatively simple system, and the development of the software development man-hour cost and the factors considering the environment are rationally input as the evaluation conditions, so the software development man-hour cost can be evaluated. It can be done in an objective and fair manner. Further, according to the present invention, it is possible to eliminate the ambiguity of the estimated price through quantification of the software function scale not only for a new case but also for a repair case, and improve the rationality, validity, and transparency of evaluation.

  The present invention uses FP (function point) as a basis for software evaluation, weights the factors considering the software development status and system environment as evaluation conditions, and uses them for evaluation value calculation. Since the input conditions have a reasonable reason, an objective and fair evaluation of software development costs can be obtained without resorting to personal experience or intuition.

  The present invention targets both new and modified software development projects, but does not include hardware, network, middleware design, and installation work costs. In addition, among the system development processes, SLCP (Software Life Cycle Process: Visualization of software life cycle processes from conception of software or system to operation and maintenance for the purpose of clarifying system development and transactions centering on software. In addition, an estimation of a development process (preparation for starting a development process to support for software acceptance), which defines a common framework and is called a “common frame”, is the target of FP method estimation evaluation. Other consulting work such as planning and drafting, estimation of incidental work such as data migration and operation support work is evaluated by the work accumulation method, but is not subject to FP evaluation. Further, in the present invention, both new projects and repair projects are targeted for development cost evaluation.

  Estimated input information when the premise of the estimation is before the completion of the basic design is a requirement definition document, a slip, a form, a screen, and a master file list, and the estimation is performed by the NESMA proposed approximate method. That is, referring to the contents of the requirement definition document based on the master file list, ILF (Internal Logical File: logical master maintained by the local system that is the measurement target system) and EIF (External Interface File) from a business viewpoint : Identify the other system (logical master that maintains and manages the system related to the measurement target system) referenced by the own system, and calculate the FP scale. NESMA is a FP law promotion organization in Poland, and NESMA proposed an approximate method that can be applied to the early stages of system development by improving the IFPUG method.

  Estimate input information when the premise of the estimate is after the completion of the basic design is the required specifications and basic design document, screen list and screen specification, form list and form specification, master file list and master file specification, interface file list and Interface file specification. As an estimation method, functions are identified by an IFPUG (International Function Point Users Group) method, the complexity of each function is evaluated, and an unadjusted function scale (FP) is calculated.

  Automating business operations (computerization) of companies has been completed, and currently there are few newly developed projects (20-40%) among the systemized projects, most of which are maintenance projects (60-80%). For this reason, estimating and estimating maintenance costs is an important task. However, in the FP method (IFPUG method), the scale measurement in the maintenance project can only measure the base of maintenance (target function to be added, changed, or deleted), so even for maintenance on the same system, it is close to minor maintenance and remake The time required for maintenance varies greatly. It is indispensable that the maintenance cost is estimated by clearly measuring the degree of such maintenance, and the procurement side evaluates it. For this reason, in the present invention, not only new projects but also repair projects are targeted for evaluation.

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

  FIG. 3 schematically shows the principle of the present invention. Information on productivity is given from the productivity model to the FP value obtained by a predetermined method, and then the man-month unit price (system engineer unit price of the development man-hour). ) And calculate the software development man-hour cost according to a predetermined arithmetic expression. Since the development man-hours are calculated by adding productivity information based on the productivity model to the FP value, an objective and fair evaluation can be performed.

  Productivity is an indicator that a system of “xxFP” can be developed per person per month, and the productivity model will be described later. (Production value by development language × system environment coefficient × system scale coefficient × (Processing load coefficient x Quality requirement coefficient x Document coefficient x Order rate by process x Work sharing rate x Repair rate).

FIG. 4 shows an example of the configuration of the evaluation value calculation apparatus (computer) of the present invention. FP separately calculated from the input means of the computer is numerically input, and the system development status and system environment are taken into consideration. System environment factor, system scale factor, processing load factor, quality requirement factor, document factor, process-specific order rate, work sharing rate, repair rate, etc. (C _{1 to} C _n ) Further, evaluation data for system evaluation is input as an evaluation data table. The calculation unit 10 calculates an evaluation value (estimation) based on the input FP, each condition data, and the evaluation data table, and displays or prints out the evaluation value. The calculated evaluation value is an objective and fair evaluation value because it is calculated by adding each condition data and the evaluation data table based on the FP. The evaluation data table is data such as a development language-specific productivity value table, a productivity adjustment coefficient table, a development process-specific standard distribution ratio table, and a standard test item number table, which will be described later.

  FIG. 5 shows a detailed configuration example of a computer. A calculation unit (CPU) 10 that executes overall control and calculation includes a ROM 102 that stores an operation program, an input unit 110 that inputs various data, and development. Productivity value table storage unit 1031 for each language, productivity adjustment coefficient table storage unit 1032, distribution ratio table storage unit 1033 for each development process, standard test item number table storage unit 1034, and system engineer unit price (SE unit price) table storage unit The RAM 103 includes 1035, the display unit 120 that displays data and the like, and the printing unit 121 that prints out data and the like.

The development language-specific productivity value table storage unit 1031 stores a productivity value per month set for each language used. The productivity adjustment coefficient table storage unit 1032 stores production values corresponding to input values of a system scale coefficient, a system environment coefficient, a processing load coefficient, a quality requirement coefficient, and a document coefficient, which will be described later. The distribution ratio table storage unit 1033 for each development process stores an order ratio based on general empirical rules for each process of basic design, detailed design, program design / manufacturing, software test, and system test. In the standard test item number table storage means 1034, the number of test items performed in each step of the software test and the system test is stored based on a general rule of thumb.

  In general, the ordering rates based on empirical rules are 16%, 20%, 36%, 15%, and 13%, respectively, but they may be input from the input means 110 based on the software modification status. . In general, the number of test items based on empirical rules is usually that the number of standard items for software testing is FP value x 2.0 and the number of standard items for system test is FP value x 0.5. Since it may differ depending on the software field, the application of the number of software test items described later is expressed using algebra of R5 and R6, respectively. Further, these table storage means are created in advance when the arithmetic unit 10 receives a command from the control program. Of course, the input unit 110 can be operated to change the table values stored in these tables to the input values.

  In such a configuration, the operation will be described with reference to the flowchart of FIG. In the following steps, the calculation unit 10 operates in response to a command from a control program stored in the ROM 102.

  First, the separately obtained FP is input from the input means 110 (step S1), and then based on the language used by the target system, the language-specific productivity value input means 110 and the language-specific productivity values are produced. A sex value is input (step S2), and a productivity adjustment coefficient is input from the input means 110 (step S4). In the present invention, as parameters for calculating the productivity adjustment coefficient, the system environment coefficient indicating the system platform as the productivity adjustment coefficient, the system scale coefficient indicating the scale of the application to be evaluated, and the process indicating the process form (concentration, distribution) The load coefficient, the quality requirement coefficient indicating the degree of system quality requirement (review, test, evaluation work), and the document coefficient indicating the type and quantity of documents to be created may be input and calculated. Details of the calculation of the production growth factor from these parameters will be described later.

  Furthermore, a part of the development process (process) is manufactured in-house, one item is divided into multiple stages (by process), and one item is divided into multiple vendors (by process). Order rate by process (step S4A) indicating the order ratio in the case, work sharing rate (step S4B) indicating the work ratio between the ordering side (procurement side) and the order receiving side (providing side), and the repair rate in the case of functional remodeling ( Step S4C) is set and entered. These input orders may be arbitrary.

  When the condition for calculation and its data are input as described above, the calculation unit 101 executes the calculation according to the program stored in the ROM 102 (step S5), and then the incident work man-hours are input from the input means 110. Input (step S6), and a predetermined calculation is executed (step S7). Then, the system engineer unit price is input from the input means 110 (step S8), a predetermined calculation is executed, and the process ends (step S9). Thereby, the evaluation of the software development man-hour cost can be obtained as a numerical value, the result can be seen on the display means 120, and the printing means 121 can be printed.

  Note that the order rate for each process in step S4A may not be input. In this case, the data of the standard distribution rate (standard order rate) stored in the standard distribution rate table storage unit 1033 for each development process is read, and calculation is performed as the order rate for each process.

  In the above example, the calculation is performed every time the data is input, but the calculation may be performed after all the data is input as shown in FIG. In this case, the order of inputting FP, productivity value by development language, productivity adjustment coefficient, ordering rate by process, work sharing rate, repair rate, incidental work man-hours, and SE unit money is arbitrary.

  FIG. 8 shows in detail the flow of a computer-based calculation method for the development scale, man-hours, and costs of a new development project and a repair project according to the present invention. First, the software scale (FP) is calculated and data is input. However, in the present invention, any of the IFPUG method, the approximate method, the logical file estimation method, or the step back calculation method is used. The IFPUG method has ILF (Internal Logical File) + EIF (External Interface File) + EI (External Input) + EO (External Output) + EQ (External Inquiry), and there is no adjustment of VAF. Is ILF + EIF + EI + EO + EQ, each function is not weighted, and VAF is not adjusted. VAF (Value Adjusted Factor) is an adjustment factor (productivity adjustment factor) presented by the IFPUG method. Further, the logical file estimation method is ILF number × 35 + EIF number × 15, and the step inverse calculation method is language step number / language step number per FP.

  When the FP calculated as described above is input to the arithmetic unit 10, the productivity value and productivity coefficient for each development language are input. In other words, the productivity value for each development language, the productivity adjustment factor (system scale factor, system environment factor, processing load factor, quality requirement factor, document factor), ordering rate for each process, work sharing rate, and repair rate are input. Software languages include COBOL85, Microfocus COBOL, C, C ++, Visual C ++, JAVA / JAVA Script, ABAP / 4, Oracle Developer / 2000, Access, EXCEL, PL / SQL, etc. Is different. Therefore, the man-month productivity for the language used is set in advance in the productivity value table 1031 for each development language, data is read based on the language used for the development system, and the man-month productivity is input. For example, COBOL85 and C have low man-month productivity, and Visual Basic, C ++, etc. have high man-month productivity. In addition, when a plurality of languages are adopted for the development of the same software, the respective ratios are calculated, and the total productivity values for each development language are added up.

  In addition, the system environment factor within the productivity adjustment factor is different in productivity depending on the PC stand-alone form, host centralized form, single platform configuration (ALL UNIX or ALL Windows), and dual platform configuration (UNIX, Windows, LINUX). Set the coefficient based on the system environment. The system scale factor is determined by the value of FP, and the coefficient value is changed according to the size of the scale. The processing load coefficient is determined according to the form of the process. When a small number of people are used in a single department / base (for example, a local system or a small-scale system within a department), or when a large number of people are used at a single department / base (for example, process intensive processing) , Host system), and multiple departments / bases using a large number of people (for example, distributed process, basic system), the productivity differs, so the coefficient value is changed in each case. The quality requirement coefficient is when there is no quality requirement from the user (operation confirmation level), when the quality requirement from the user is normal (master status confirmation), when the quality requirement from the user is severe (large-scale transaction / data performance) Since the productivity differs depending on whether the confirmation is), the coefficient value is changed in each case. Regarding the document coefficient, for example, when the SLCP example document created is less than 50%, when the SLCP example document created is about 51% to 100%, the SLCP example document is created. Since the productivity differs when the amount exceeds 100%, the coefficient value is changed in each case. Note that the productivity adjustment coefficient is stored in the productivity adjustment coefficient table 1032.

The order rate for each process differs in productivity depending on cases such as when a part of the development process is manufactured in-house, one item is divided into multiple stages, and one item is divided into multiple providers. Therefore, the entire development process is put together and the ratio when placing an order with the provider is 100%, and the ratio in each case is input. The work sharing rate may be that some work in the development process is made in-house, or one project is divided into multiple providers and placed in order. In such cases, the degree of work sharing between the two (in principle, man-hour basis) It is effective to set the work sharing rate taking this into consideration. The work sharing rate is 100% when all work in the development process is ordered from the provider (complete contract). Refurbishment means adding, changing, or deleting functions from an existing system. Estimating and evaluating a renovation project assumes that the existing parent system (target system) is newly developed and the repair rate is 100%. Quantify the rate of additions, changes, and deletions to and evaluate the estimated number of repair project man-hours. The scale of renovation is defined by the following formula (1).

Repair scale = repair base scale x repair rate (1)

After inputting the productivity value and productivity adjustment coefficient by development language, and the order rate, work sharing ratio, and repair rate by process, the calculation unit 10 inputs these input FP, productivity value by productivity language, and productivity adjustment coefficient. In addition, the standard development work man-hour A is calculated according to the following equation (2) with respect to the order-by-process rate, work sharing rate, and repair rate.

Standard development man-hours A = FP / productivity factor
= FP ÷ (Production value by development language x Productivity adjustment factor x Order rate by process
(Work share rate x repair rate)
= FP ÷ {Production value by development language x System scale factor k1 x System
Environmental coefficient k2 x processing load coefficient k3 x quality requirement coefficient k4 x
Document factor k5 x order rate by process x work share rate x repair rate}
... (2)
Note that k1 to k5 are adjustment values stored in the productivity adjustment table storage unit 1032 shown in FIG. It represents that each adjustment value is applied based on the input from the input means 110.

Thereafter, the incidental work man-hours are input from the input means 110, and the following equation (3) is calculated. “Ancillary work” refers to work commissioned by the orderer to the provider in addition to the standard development work, and the cost incurred for performing these work is defined as “additional work man-hour”. Then, the following equation (3) is calculated.

Development man-hour B = Standard development work man-hour A + incidental work man-hours (3)

Thereafter, the data is further read from the system engineer unit price table storage unit 1035 from the input unit 110, the system engineer unit price is input, and the following equation (4) is calculated. As a result, software development costs (C = development man-hours × SE simple money) are obtained.

Development cost C = Development man-hour B x System engineer unit price ... (4)

That is, the calculation formula of the software development cost is the following formula (5).

Development cost = {Function scale FP ÷ (Production value by development language x Productivity adjustment factor x Order rate by process
X work sharing rate x renovation rate) + incidental man-hours} x system engineer unit price
... (5)

On the other hand, the productivity value for each development language is calculated by, for example, the following expression (6) and stored in advance in the productivity value table storage unit 1031 for each development language. In this case, the productivity (7.5 FP / person month to 40 FP / person month) for each development language is stored in the productivity value table storage means 1031 for each development language, the user selects the development language, and each usage ratio By inputting (the number of functions to be developed), language productivity is automatically given.

Productivity value by development language = (Production value of development language # 1 x usage rate m1)
+ (Development language # 2 productivity value x usage rate m2)
+ (Productivity value of development language # 3 x usage rate m3)
+ (Production value of development language # 4 x usage rate m4)
+ (Production value of development language # 5 x usage rate m5)
(6)

Further, the productivity adjustment coefficient is calculated based on the following equation (7). Each coefficient is set in a range of 0.80 to 1.20, and a predetermined adjustment coefficient is selected and input with reference to the input screen of the display unit 120, whereby the value is uniquely given.

Productivity adjustment factor = system scale factor k1 × system environment factor k2 ×
Processing load coefficient k3 × quality requirement coefficient k4 ×
Document coefficient k5 (7)

In FIG. 6, after inputting the productivity value and productivity adjustment coefficient for each development language, the calculation of formula (2), the calculation of formula (3) after the input of the incidental man-hours, and the input of the system engineer unit price (4) As shown in FIG. 7, (2) to (4) after the input of the productivity value for each development language, the productivity adjustment coefficient, etc., the incidental work man-hours and the system engineer unit price, as shown in FIG. ) Equation may be calculated continuously.

Hereinafter, specific examples of the present invention will be described.

  The present invention targets software development (renovation) projects, and does not evaluate hardware, network, middleware, etc. design and installation work costs. Among the system development processes, the SLCP development process (preparation for starting the development process) Software reception support) is the target of FP method estimation evaluation. Other work such as consulting work such as planning and drafting, and estimation of incidental work such as data migration and operation support work are evaluated by the “work accumulation method”, but are not subject to FP evaluation. The present invention is characterized in that it deals with new projects and repair projects.

  The FP method is one of the methods (scales) for measuring the software scale, and the software function scale (FP value) is calculated by measuring the number and complexity of the software data and functions. FIG. 9 shows an outline of the FP method employed in the present invention.

  Function types are ILF, EIF, EI, EO, EQ, ILF is a set of logical data that can be identified by the user and maintained by the own system (measurement target system), and EIF can be identified by the user to other systems It is a collection of logical data maintained and managed by the system related to the measurement target system and referenced by the own system. EI is a function that inputs data from outside the system boundary and maintains and manages (registers, updates, deletes) the ILF. EO refers to a function that provides information to users and other systems by referring to the ILF and EIF. The provision of information includes calculation formulas and derived data, and EQ is a function of providing information to users and other systems by referring to the ILF and EIF, and the information provision does not include calculation formulas or derived data.

  Since the function scale of software has a strong correlation with the software development man-hours and costs, it is conceivable to estimate the development man-hours and costs using the FP value. For example, it takes 100 man-months to develop a 1000 FP system with a productivity of 10 FP per person. In addition, if the cost per person per month is 900,000 yen, the development cost will be 90 million yen. The ordering side independently measures the FP value, calculates the development man-hour cost, and evaluates the validity of the estimate collected from the provider. In the present invention, the above FP is used and the system using the formula (5) is used. Estimate development costs.

  In order to increase the accuracy of such system development cost estimation, it is necessary to accurately measure the FP value. If the FP is acquired from the providing side, the ordering side must verify whether or not the FP value presented by the provider is correct.

  FIG. 10 shows input information and a calculation method for calculating the development scale (FP). In other words, as the premise of the estimation, there is planning completion # 1, planning completion # 2, requirement definition completion, basic design completion, and planning planning completion # 1 is the number of program lines for each existing system language and source for estimation by the step inverse calculation method Enter the code and system planning details. Plan planning completion # 2 inputs ER list, master data list and system planning contents to estimate by logical file estimation method, and completes functional requirements, current work flow, systematization to estimate requirement definition by estimation method Enter the plan, system function overview and function / screen form / DB list, and the basic design completion can be estimated by the IFPUG method, functional requirements, current work flow, systemization plan, system function overview, system function details and function / screen Enter the form / DB list and layout.

In the present invention, the system development cost estimation evaluation utilizing the FP method is performed. In the present invention, the following four points are particularly noted.
(1) Measure according to the IFPUG method as much as possible.
In addition to the IFPUG, there are a plurality of methods for the FP method. These are generally based on the same concept, but each observing point is different, so the meaning of the measured FP value is also different. In the present invention, the FP measurement method and its granularity conform to the “IFPUG method (international standard ISO 20926: 2003: IFPUG method)”. It is necessary to clarify the relationship between the FP value calculated by applying a method other than the IFPUG method and the FP value of the IFPUG method.
According to the interpretation of “separate from functional requirements and quality technical requirements” in “International Standard ISO 20926: 2003: IFPUG method”, in the present invention, FP is an unadjusted FP. In other words, the scale of the data function and transaction function is FP, and no adjustment is made using the 14 general system characteristics. The quality and technical requirements of the system are evaluated by the system characteristic adjustment factor and reflected in the system development man-hour cost.
(2) Use of multiple methods is recommended.
When measuring the FP by applying the IFPUG method, it is assumed that the basic design of the system has been completed and the input information necessary for measurement is available. In practice, however, estimates are often made earlier. For example, cost estimation at the time of requirement definition completion. When measuring FP at such an early stage, the types and details of the input information (specifications) available to the measurer are limited, and several simple measurement methods have been devised. What we want to emphasize here is (a) applying a method that is as close as possible to the IFPUG method, and (b) using the simplified method to implement and verify as many methods as possible. .
(3) The purpose of estimation evaluation is cost optimization.
The system development cost estimation and evaluation method proposed in the present invention targets the standard industry of the development process. In practical system development projects, it is often necessary to place an order for only a part of the development process, or to order work other than the development process. I must. Focusing on the fact that the system development work of the present invention is a collaborative work between the order-receiving side and the ordering side, and if both do not aim at the same goal, it will not work, and the estimation evaluation work will hit the development cost estimate of the provider cheaply Rather, it is based on providing an objective basis (guideline) for aptitude costs that can be confirmed and understood by both parties.
(4) Quantify as much as possible.
In order to maintain the objectivity of the estimation evaluation work, it is necessary to quantify the basis of evaluation as much as possible. In particular, for renovation projects, no effective estimation evaluation method has been proposed so far, despite the fact that more than 60% of system development costs have been devoted to system renovation. Considering this situation, the information system department cannot fulfill its obligation to explain to the managers and user departments without focusing on the estimation of the renovation project. Therefore, in the present invention, the degree of repair is quantified and the estimated evaluation of the repair project is also dealt with reliably.

  Here, the most important points in estimating and evaluating system development man-hours and costs are 1) obtaining a highly accurate FP value, 2) inputting a highly accurate productivity factor, and 3) clear and bilateral (ordering side) The scope (working range) that the ordering party) can recognize and agree on, and 4) The repair rate of the repair project can be quantified. With these four factors in mind, it is necessary to keep in mind the improvement of accuracy, accumulate original performance data, and seek to improve the accuracy of various coefficients applied in estimation evaluation. The present invention satisfies this need.

  The development cost is calculated as a result of the system development cost estimate. The development cost calculated by the above equation (5) is estimated by the orderer himself and is a so-called standard price for evaluation. On the other hand, the estimate obtained from the contractor is defined as the contractor-provided price, and the standard price for evaluation is compared with the contractor-provided price to verify whether there is a difference. Become.

  FIG. 11 shows the composition of system development costs. The system development costs include hardware costs, middleware, and system development costs. In the present invention, only software development costs within the system development costs are evaluated. And Software development in the present invention refers to the SLCP development process, and the scope of the development process is as shown in FIG. In other words, the scope of the development process includes a planning process, a development process, an operation process, and a maintenance process, and the present invention targets those development processes, preparing for process start, system requirements analysis, system method design, detailed operation design, Software requirements analysis, software method design, detailed software design, software code creation and testing, software integration, software compatibility verification test, system integration, system compatibility verification test, software installation, software acceptance support are evaluated. In addition, the operation and maintenance work of the stable operation system in FIG. 11 has a monthly standard working time of 160 h / month (150 h / month to 170 h / month), the development man-hours are targeted for the development process process work, and the incidental work is It is intended for work other than the development process.

  In the present invention, the development process is divided into five processes of basic design, detailed design, program design / manufacturing, software test, and system test, and the correspondence with each SLCP activity is as shown in FIG. In other words, the basic design includes process start preparation, system requirement analysis, system method design, software requirement analysis, and software method design, and detailed design includes business detail design and software detail design. Program design / manufacturing is software code creation and test, software test is software combination and software compatibility check test, and system test includes system connection, system compatibility check test, software introduction and software acceptance support.

  Here, in the system development work, the mounting process (detailed design to software test) accounts for 60% or more of the total development man-hours. The selection of development languages (including middle and downstream development support tools such as automatic code generation) has a great impact on the work man-hours and costs of the mounting process. Therefore, it is necessary to pay attention to the productivity of the development language when setting the productivity of system development. FIG. 14 shows an example of productivity values by development language. In this example, assuming that the productivity per person-month is 160 hours per person-month, the SLCP development process is the work range. When only a part of the process is ordered, it is necessary to adjust the productivity in consideration of the ratio.

  There are many factors that affect development productivity in addition to the above-mentioned productivity values by language. For example, specific attributes of the target system (scale, system configuration, etc.), order-side requirements (quality requirements, document requirements, etc.), order-side business performance, maturity (similar system construction experience, developer skill, Project management maturity), and dozens or hundreds of elements. In the present invention, non-functional requirements (quality requirements, technical requirements) and procurement that greatly affect system development man-hours are selected from various cost incentives so as not to lose the convenience and speed of operations while maintaining the accuracy of estimation evaluation. The cost driver is set mainly on the elements that the side (ordering side) places particular emphasis on.

The impact of each system characteristic on development productivity and the evaluation method are shown below. In the present invention, a coefficient is given to the following five systems so that the evaluation is accurately performed.
(1) System scale: In the case of large-scale development, the complexity between operations increases and interests increase, so communication overhead tends to occur and development productivity decreases.
(2) System environment: OS, middleware, DBM to be used if the platform is different
S is also different, and the system design and construction load associated with it changes, and development productivity also changes.
(3) Processing load: Depending on the concentration and distribution of data and processes, the workload for system design and construction such as transaction control and load distribution differs, and development productivity varies.
(4) Quality requirements: In-house data confirmation and external service billing differ in the level of quality requirements, and accordingly, development productivity varies depending on the system design perspective and incorporation into review / test / quality evaluation.
(5) Documents: In the case of large-scale development, when importance is placed on operation and maintenance after production, the level and amount of documents to be created will change, affecting development productivity.

An example of the productivity adjustment coefficient based on the system characteristics as described above is shown in FIG. The system scale factor is classified according to the application to be measured, the system environment factor is classified according to the system platform (system environment configuration), the processing load factor is classified according to the process form (concentration, distribution), and the quality requirement factor is the system quality. The document coefficient is classified according to the type and quantity of documents to be created. The magnitude relationship of the coefficients is K11>K12>K13>K14> K15, K21>K22>K23> K24, K31>K32> K33, K41>K42> K43, and K51>K52>. K53.

When placing an order for the entire development process together with the provider, the order rate for each process is 100%. There are cases where a part of the development process is manufactured in-house, one item is divided into a plurality of stages for ordering, or one item is divided into a plurality of providers for ordering. In such a case, it is necessary to set the order rate for each process with reference to the order rate for each process as shown in FIG. In addition, when all work of the development process is ordered from the provider side (complete contract type), the work sharing ratio at that time is set to 100%. There are cases in which part of the development process is self-made, or one item is divided into multiple providers and ordered. In such a case, it is necessary to set the work sharing rate as shown in FIG. 17 in consideration of the degree of work sharing between the two (in principle, the man-hour pace). For example, it is assumed that the total basic design work is 15 man-months, the operation design work (1.5 man-months) is handled by the procurement side, and the remaining 13.5 man-months are handled by the providing side. In this case, the work sharing ratio on the providing side of the basic design process

13.5 person months ÷ (1.5 person months + 13.5 person months) × 100% = 90%… (8)

And 90%. However, the roles that should be originally played by the ordering side, such as the following, are not subject to the work sharing rate here.
1) Specification presentation: summary of requirements, presentation, etc. 2) Procurement management: RFP creation, estimate evaluation, contractor selection, contract conclusion and management, paperwork upon contract termination, etc. 3) Inspection work: specification, design, implementation Review, approve, and verify results

In the present invention, when evaluating the estimate of a renovation item, the following is performed.
1) If the repair rate exceeds 100%, the repair rate shall be “100%”.
2) Since the software refurbishment location and test scope may differ greatly, the renovation rate is divided into the development renovation rate and the test refurbishment rate. The development improvement rate is applied from the basic design to the programming process, and the test improvement rate is applied to the software test process (software test improvement rate) and the system test process (system test improvement rate).

The method for calculating the repair rate is based on the step method, and is applied to the basic design to programming process by the following equation (9). The number of lines (number of steps) is the number of physical steps including comment lines, and R1% of the number of parent (target system) lines is counted from the viewpoint of the interface with the changed part. The number of modified lines is the number of lines “addition, change, deletion” with respect to the existing system, and the external addition function is a function that is added in a separate frame without changing the existing system. The constants R1%, R3%, and R4% are empirical values, and normally 6% is used, but it may be changed depending on the development type. In addition, the number of parent lines before renovation refers to the number of existing lines in the system to be refurbished (software to be refurbished), and the number of modified lines in the existing system refers to the number of lines that have been modified by renovation. Means the number of rows of the target system (target software) after the refurbishment. R2 indicates the number of lines to be modified, which is a confirmation magnification performed in the confirmation work for the number of modified lines after software modification. Normally, a value of 2 is applied to confirm before and after modification.

Development renovation rate = {(number of parent lines before renovation x R1%) + (number of remodeled lines in existing system x R2)
+ (Number of external additional function lines)} ÷ (number of parent lines after renovation)
... (9)
Note that the number of parent lines before refurbishment x R1% is the number of first work lines, the number of modified lines of the existing system x R2 is the number of second work lines, the number of first work lines, the number of modified lines of the existing system, and external additional function lines The sum of the numbers is defined as the number of development work lines.

In addition, the method for calculating the repair rate for cases where measurement is difficult by the step method follows the following equation (10). In equation (10), DET means a data element type.

Development renovation rate = {(number of parent DETs before renovation x R3%) + (number of DETs added / changed / deleted)}
÷ (number of parent DET after renovation) (10)

The number of base DETs before modification × R3% is defined as the number of work DETs before modification, the number of addition / change / deletion DETs is the number of modified DETs, and the sum of the number of work DETs before modification and the number of modified DETs is defined as the number of development work DETs.

Furthermore, the calculation method of the repair rate in the test process applied to the software test and the system test process is based on the following equation (11). In this case, if the actual data of the number of test items at the time of new development is not recorded, the standard value of the number of standard items of software test = FP value × R5 and the number of standard items of system test = FP value × R6 is applied. If no test renovation rate is presented, it is considered equivalent to the development renovation rate. Note that the number of items input from the input unit 110 may be received for the number of reference items for the software test and the number of reference items for the system test. When no input is made, the data is read from the standard test item number table storage means 1034 and used for calculation.

Test renovation rate = {(number of test items before renovation / number of test items at new development x R4%) + (at renovation)
Number of test items)} ÷ (number of test items at the time of repair and new development)
... (11)

Note that the number of test items before repair / new development × R4% is defined as the number of first test work lines, and the sum of the number of first test work lines and the number of test items at the time of repair is defined as the total number of test work lines.
The following is a typical “accompanying operation”.
(1) Operation test-related work: The operation test is a test that confirms the software, system, and business as a whole in a production environment that is mainly operated by the user. Environment construction accompanying this,
Work such as user support is ancillary work.
(2) Migration-related work: The work, system, and data migration work associated with switching from the old operation mode to the new operation mode is ancillary work. (However, development of transition tools is within the scope of standard development work, and a method of evaluation by FP is adopted.)
(3) Operations related to operations: User training and operations for actual operation and actual operations (operation monitoring, operation information collection, improvement, evaluation, etc.) are incidental operations.
(4) Development support work: Development standardization (work procedures, templates, standards) development and promotion, quality assurance (contracts, processes, requirements, documentation verification and validation), resource management, etc. To do.
(5) Project management: Progress management, problem management, change management, etc. are incidental work. In addition,
In the present invention, the estimated evaluation of incidental work costs is performed by the WBS scrutiny method.

In the present invention, software development engineers are divided into four categories as shown in FIG. 18, and their roles and responsibilities are determined. In other words, development engineer 1 is mainly responsible for basic design and system testing, and plays a central role in formulating the system configuration image, the overall concept of the system development plan, the construction of the project system, and the determination of project management indices in the subsequent processes. Is responsible. Development engineer 2 is mainly in charge of basic design, detailed design, software testing and system testing, and formulates business modeling and information system planning, and plays a central role in system functional design and system implementation. And so on. Development engineer 3 (design) is mainly responsible for detailed design and software testing, and plays a central role in creating detailed designs based on the basic design of the system. Development engineer 4 (manufacturing) is a program. Mainly responsible for design and manufacturing, and plays a central role in programming, testing for each program module and process.

  FIG. 19 shows an example of the input screen of the present invention, and FIG. 20 shows an example of the display screen showing the result of the present invention. In the present invention, both new projects and repair projects can be evaluated, and the only difference between the new project and the repair project is the repair rate of item number 4) in FIG. In the case of new projects, the repair rate is 100%, and in the case of repair projects, the repair rate is less than 100%.

  In the input screen of FIG. 19, since it is assumed that the estimate presented from the provider side is high or low, the provider estimate cost is one of the items to be input. Scroll the web screen and perform input work. Enter the value of incidental work in the “Auxiliary work man-hours” column at the end of the “provider side estimated cost”.

  In the present invention, the estimate is evaluated as shown in FIG. 21 using the calculated function scale (FP) and development cost. In other words, if the scale is too large or too small, the provider carefully examines the FP details to determine whether the scope of development is too large or insufficient, and conversely if the cost is too large or too small, the work estimated by the provider Examine the work contents to see if there are any excesses or deficiencies in the contents. FIG. 21 shows that the case C and the case E are appropriate prices.

  The “development man-hour cost evaluation” column in the result display screen of FIG. 20 compares the development cost estimate calculated by the user company by the FP method with the development cost estimate obtained from the provider, and the provider estimate is not too high. Information for determining whether it is too cheap is displayed.

  The present invention can also be used in a network using the Internet.

  According to the present invention, since the evaluation is performed on the basis of the FP based on the conditions considering the development status and environment of the system, the software development man-hour cost can be evaluated objectively and fairly. It is possible to surely eliminate the ambiguity of estimates in the market (bidding, sales, etc.), and to activate the software industry.

It is a figure which shows how to obtain | require FP. It is a characteristic view which shows the example of a relationship between FP and evaluation amount. It is a schematic diagram which shows the principle of this invention. It is a block block diagram which shows the evaluation value calculation apparatus of this invention. It is a block diagram which shows the structural example of a calculating part. It is a flowchart which shows the operation example of this invention. It is a flowchart which shows the other operation example of this invention. It is a figure which shows the calculation method of the development scale, man-hour, and expense of the new development and renovation project by this invention. It is a figure which shows the outline of FP method. It is a figure which shows the input information and calculation method for development scale calculation. It is a figure which shows the structure of system development expense. It is a figure which shows the range of a development process. It is a figure which shows the comparison with a process division and SLCP. It is a figure which shows an example of the productivity value according to development language. It is a figure which shows the example of a development productivity adjustment coefficient. It is a figure which shows the example of a process distribution ratio. It is a figure which shows the example of a work sharing ratio. It is a figure which shows the occupation classification and role of a software development engineer. It is a figure which shows an example of the input screen of this invention. It is a figure which shows an example of the display screen which shows the result of this invention. It is a figure which shows the example of verification of the reference price using FP.

Explanation of symbols

10 Calculation unit (CPU)
102 ROM
103 RAM
110 Input means 120 Display means 121 Printing means 1031 Development language-specific productivity value table storage means 1032 Productivity adjustment coefficient table storage means 1033 Standard distribution ratio table storage means 1034 by development process Standard test item number table storage means 1035 System engineer unit price Table storage means

Claims (11)

Computer to estimate software development effort costs,
Means for inputting a function scale (function point) of the software as an FP value;
A means of inputting the development potential scale per month as a productivity value by development language,
Means for inputting a productivity adjustment coefficient for adjusting the productivity value for each development language;
Means to input order rate by process in each process of basic design, detailed design, program design / manufacturing, software test and system test,
Means for inputting the work share ratio as the work share ratio;
Means for inputting a repair ratio for each step of the software as a development repair ratio;
The productivity value per month as the productivity coefficient by multiplying the productivity value by development language, the productivity adjustment coefficient, the order rate by process, the work sharing ratio and the development / repair ratio in each process. Means for calculating,
Means for calculating a standard development man-hour by dividing the FP value in each step by the productivity coefficient;
Means to input incidental man-hours,
A means to enter the system engineer unit price,
Means for calculating the development cost by multiplying the sum of the standard development man-hours and the incidental work man-hours in the respective steps by the system engineer unit price amount;
Software development man-hour cost estimation program characterized by functioning as Computer to estimate software development effort costs,
Means for inputting a function scale (function point) of the software as an FP value;
A means of inputting the development potential scale per month as a productivity value by development language,
Means for inputting a productivity adjustment coefficient for adjusting the productivity value for each development language;
Means to input order rate by process in each process of basic design, detailed design, program design / manufacturing, software test and system test,
Means for inputting the work share ratio as the work share ratio;
Means for inputting a development / repair rate of the software in each development process of the basic design, the detailed design and the program design / manufacturing as a development / repair rate;
Means for inputting a test repair ratio of the software in each test step of the software test and the system test as a test repair ratio;
Productivity value per month by multiplying the productivity value by development language, the productivity adjustment factor, the order rate by process, the work sharing rate and the development repair rate or the test repair rate in each process Means for calculating as a productivity factor,
Means for calculating a standard development man-hour by dividing the FP value in each step by the productivity coefficient;
Means to input incidental man-hours,
A means to enter the system engineer unit price,
Means for calculating the development cost by multiplying the sum of the standard development man-hours and the incidental work man-hours in the respective steps by the system engineer unit price amount;
Software development man-hour cost estimation program characterized by functioning as The computer for the input productivity value for each development language,
Means for inputting one or more development languages to be used;
Means for inputting a utilization ratio for each development language;
Development value-specific productivity value table storage means for storing the productivity value per person for each development language in advance,
A productivity value corresponding to the development language input from the productivity value table for each development language is read out, the productivity value is multiplied by the utilization ratio corresponding to the productivity value, and the sum is calculated as the development language. Means for calculating as another productivity value,
The software development man-hour cost estimation program according to claim 1 or 2, which is functioned as A computer for calculating the input productivity adjustment factor;
System means for inputting a system environment factor,
System means for inputting a system scale factor,
Means for inputting the processing load factor,
Means for entering the quality requirement factor,
A means of entering document coefficients,
Productivity adjustment table storage means for recording coefficient values in advance for each item of the system environment coefficient, the system scale coefficient, the processing load coefficient, and the quality requirement coefficient;
Means for calculating the productivity adjustment coefficient by reading and multiplying the corresponding coefficient values of the system environment coefficient, the system scale coefficient, the processing load coefficient, and the quality requirement coefficient;
The software development man-hour cost estimation program according to any one of claims 1 to 3 for functioning as a program. About the development and renovation rate entered, the computer
Means for inputting the number of existing lines of the software as the number of parent lines before renovation;
Means for inputting the number of modified lines of an existing system using the software;
Means for inputting the number of external additional function lines added separately from the existing system;
Means for multiplying the number of parent lines before renovation by multiplying the work ratio performed in the confirmation work for the number of mother lines before refurbishment after renovation of the software as R1%,
Means for multiplying the number of modified lines by R2 as a confirmation magnification performed in the confirmation work on the number of modified lines after the software modification, and calculating a second number of working lines;
Means for calculating the development work line number by adding the first work line number, the second work line number, and the external additional function line number;
Means for inputting the number of lines after the modification of the software as the number of parent lines after the modification;
Means for dividing the number of development work lines by the number of parent lines after the repair to calculate the development repair rate;
The software development man-hour cost estimation program according to any one of claims 1 to 4, wherein About the development and renovation rate entered, the computer
Means for inputting the number of data item types of the software as the number of parent DETs before renovation;
Means for multiplying the number of parent DETs before renovation by multiplying by R3% the work ratio performed in the confirmation work for the number of parent DETs before renovation after renovation,
Means for inputting the number of modified data item types for modifying the software as the number of modified DETs;
Means for calculating the sum of the number of pre-repair work DETs and the number of modified DETs as the number of development work DETs;
Means for inputting the number of data item types after modification of the software as the number of parent DETs after modification;
Means for dividing the development work DET number by the post-remodeling parent DET number to calculate the development / repair rate;
The software development man-hour cost estimation program according to any one of claims 1 to 4, wherein Computer for the test refurbishment rate entered,
Means for inputting the number of test items at the time of new development of the software as the number of test items at the time of new development and parent
The number of test items before the renovation and the number of test items at the time of new development is multiplied by the work ratio performed in the confirmation work for the number of test items before the renovation and the number of test items at the time of the new development as R4% to calculate the number of first test work Means to
A means to input the number of test items to be performed at the time of renovation,
Means for calculating the total number of test work lines by adding the number of first test work lines and the number of test items;
Means for inputting the number of test items at the time of new development after the software has been modified as the number of test items at the time of new development and parent body after the modification;
Means for calculating the test renovation rate by dividing the total number of test work lines by the number of test items at the time of the renewed base / new development;
The software development man-hour cost estimation program according to any one of claims 1 to 6, wherein Computer to estimate software development effort costs,
Means for calculating the total order rate for each process as the total order rate,
The software development man-hour cost estimation program according to any one of claims 1 to 7, wherein Computer to estimate software development effort costs,
Means for calculating the total development cost in each step as a total development cost;
The software development man-hour cost estimation program according to any one of claims 1 to 8, wherein Computer to estimate software development effort costs,
Means for inputting a contractor-provided price provided by a requesting contractor who has requested the renovation of the software in each step;
Means for calculating the sum of the vendor-presented prices in each step as a total vendor-presented price;
Means for calculating a price disparity rate by dividing the supplier-provided price in each step by the development cost;
Means for calculating a total price disparity ratio by dividing the total contractor presented price by the total development cost;
The software development man-hour cost estimation program according to claim 9, which is made to function as: A computer-readable storage medium storing the software development man-hour cost estimation program according to claim 1.

Images