DL/T 2015-2019Specification for measurement of power informatization software engineering (English PDF)

Foreword

In order to standardize the measurement principles and content, cost composition and cost measurement methods of various parts of power information software engineering, standardize information software Cost management in the process of project construction provides a more scientific basis for the investment of power information software engineering, and rationally determines the engineering Price, improve investment efficiency, formulate this standard.

This standard was proposed and interpreted by the Standardization Center of the China Electricity Council.

This standard is under the jurisdiction of the Power Industry Information Standardization Technical Committee (DL/T C27).

Drafting organizations of this standard. China Electric Power Research Institute Co., Ltd., China Electricity Council, Guangdong Power Grid Co., Ltd.

Company, State Power Investment Group Co., Ltd., China Power Construction Co., Ltd., Guodian Nanjing Automation Co., Ltd., State Grid Hebei Electric Power Co., Ltd., State Grid Hubei Electric Power Co., Ltd., State Grid Inner Mongolia Eastern Electric Power Co., Ltd., State Grid Gansu Electric Power Company Co., Ltd., State Grid Xinjiang Electric Power Co., Ltd.

1 Basic principles

In the process of cost measurement, the following principles should be followed.

Make full use of benchmark data, adopt equation method, analogy method or analogy method to measure workload and cost;

In cost measurement, an appropriate estimation method should be selected according to the characteristics of the project and the level of detail required;

The measurement result of workload and cost is a fixed value, but the amount within plus or minus 5% of the measured fixed value is within the allowable range;

Perform cross-validation during the cost measurement process. If the estimation results of different methods produce large differences, the expert review method can be used to determine to estimate the results, a simpler weighted average method can also be used.

2 Cost measurement

According to the engineering feasibility study report and other materials, the feasibility study, preliminary design, development, and third-party the costs of testing, implementation, supervision, and project management are measured to provide support for the budget stage; in addition, according to the actual development of the project in addition, the actual value of the cost of informatization software engineering is measured and analyzed to provide a basis for the improvement of benchmark data.

3 Perfect benchmark data

The improvement of benchmark data refers to the improvement of productivity and labor costs corresponding to related activities of information software engineering according to the actual development of the project.

Rate etc. The improvement of benchmark data can be divided into three stages. data collection, data establishment/maintenance, and data release.

a) In the data collection stage, the cost measurement central management department is organized, and the cost measurement execution department will collect data based on actual project development.

Collect information on the number of personnel, construction period, cost and other information actually invested by the construction unit in the specific construction process;

Note. The cost measurement central management department and the cost measurement execution department should be set according to the organization of the engineering unit.

b) In the data establishment/maintenance stage, the cost measurement executive department organizes and analyzes the collected information, and refers to the industry average level to establish Establish benchmark data; compare it with the measured value according to the actual development of the project, and revise the benchmark data with reference to changes in the industry According to data, and submit the latest benchmark data to the centralized management department for review;

Note. The industry average level and industry data involved in this standard are all derived from the SSM-BK issued by the Software Cost Branch of China Software Industry Association.

c) In the data release stage, the centralized management department releases the latest benchmark data to the entire industry.

Cost structure

The construction of electric power information software engineering in this standard includes the feasibility study and preliminary Design, development, third-party testing, implementation, supervision, project management and other processes. The cost of informatization software engineering should be based on the actual construction of the project the process is calculated, see equation (1). Table 1 briefly describes the various parts of the cost structure.

Development cost measurement

1 Measurement steps

Figure 1 shows the steps of power information software engineering development cost measurement, including scale measurement, workload measurement, construction period measurement and cost

This metric.

Figure 1 Measurement steps of power information software engineering development fee

2 Scale measurement

The scale measurement should follow the following principles.

a) Before scale measurement, the system boundary should be clarified according to the scope of the project. For needs that have not yet been determined, the degree should be determined before the scale measurement Quantity principle

b) The estimator should estimate the software scale based on the determined system boundary and demand description;

c) The method used for scale measurement should be based on the project characteristics and estimation requirements, and the five recommended rules of SJ/T 11463-2013 should be selected.

One of the standard function point analysis methods of modulus, including COSMIC-FFP method, IFPUG method, MkII method, NESMA Method and FiSMA method;

d) When estimating the size, the degree of possible demand changes should be considered, and the results of the size estimation should be appropriately adjusted;

e) For software research and development projects that are based on non-functional requirements, or contain a large number of complex algorithms, or are based on creativity, scale when estimating, you can refer to the first five methods to estimate the functional size, and refer to the SNAP method to estimate the non-functional size; also it is not necessary to estimate the size of the software, refer to the methods described in this standard (such as analogy,) and principles to directly estimate the software development effort the workload and cost of the process.

Note. According to the applicable scope statement of the function point analysis method in relevant international standards, the COSMIC method is suitable for commercial application software and real-time systems; the IFPUG method Functional scale measurement applicable to all types of software; MkII method is applicable to any software type whose logical transaction can be determined; NESMA method and IFPUG the method is very similar, but the NESMA method defines different application scenarios to support the estimation of different granularities, so early estimation (such as budgeting, recruitment Bidding), the indicator function point analysis method or the estimated function point analysis method in the NESMA method should be adopted; the FiSMA method is suitable for all types of software functions Scale measurement, which highlights the concept of "service", no longer emphasizes the concept of "function", and divides the typical functions of software into 28 types of services, thus making the service the classification of service types is more detailed, but it also increases operational inconvenience; the SNAP method is suitable for estimating the scale measurement of non-functional requirements.

Take the NESMA method as an example. The scale estimation process includes identifying system boundaries, identifying function point count items, calculating initial function points, and determining scale 5 parts of adjustment coefficient and calculation of adjusted function points. Among them, the UFP calculation formula of the indicator function point analysis method is shown in formula (5).

If the scope of the project is described as. document management includes document drafting, review, approval, filing, and release. The electronic signature must be verified during approval Using the indicator function point counting method, it can be recognized that the above requirements include an ILF (official document information) and an EIF (electronic signature information).

Therefore, the UFP required for this part is 50FP.

3 Workload measurement