HOME   Cart(0)   Quotation   About-Us Policy PDFs Standard-List
www.ChineseStandard.net Database: 189759 (19 Oct 2025)

DL/T 2015-2019 English PDF

US$559.00 · In stock
Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email.
DL/T 2015-2019: Specification for measurement of power informatization software engineering
Status: Valid
Standard IDContents [version]USDSTEP2[PDF] delivered inStandard Title (Description)StatusPDF
DL/T 2015-2019English559 Add to Cart 5 days [Need to translate] Specification for measurement of power informatization software engineering Valid DL/T 2015-2019

PDF similar to DL/T 2015-2019


Standard similar to DL/T 2015-2019

GB/T 28826.2   YD/T 3746   GB/T 31071   DL/T 2014   DL/T 1730   

Basic data

Standard ID DL/T 2015-2019 (DL/T2015-2019)
Description (Translated English) Specification for measurement of power informatization software engineering
Sector / Industry Electricity & Power Industry Standard (Recommended)
Classification of Chinese Standard L70
Classification of International Standard 35.240
Word Count Estimation 24,230
Date of Issue 2019-06-04
Date of Implementation 2019-10-01
Quoted Standard GB/T 19668-2014; GB/T 22240-2008; SJ/T 11463-2013; HYD41-2015
Issuing agency(ies) National Energy Administration
Summary This standard specifies the measurement principles and content, cost structure and cost measurement methods of each part of the power industry informatization software engineering. This standard is applicable to the cost measurement of the software R&D part of the information software engineering or other projects in the power industry, which is mainly based on software R&D, but not applicable to the cost measurement of projects such as infrastructure construction, software and hardware procurement, and industrial control systems.

DL/T 2015-2019: Specification for measurement of power informatization software engineering

---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Specification for measurement of power informatization software engineering ICS 35.240 L 70 Record number. 63143-2018 People's Republic of China Electric Power Industry Standard Power Information Software Engineering Measurement Specification 2019-06-04 released 2019-10-01 implementation Issued by National Energy Administration

Table of contents

Foreword...III 1 Scope...1 2 Normative references...1 3 Terms and definitions...1 4 Abbreviations...3 5 Principles and content of cost measurement...3 5.1 Basic principles...3 5.2 Cost measurement...3 5.3 Improvement of benchmark data...3 6 Cost composition...3 7 Feasibility study fee measurement...5 7.1 Principles of Measurement...5 7.2 Measurement formula...5 7.3 Parameter value...5 8 Preliminary design cost measurement...6 8.1 Measurement principles...6 8.2 Measurement formula...6 8.3 Parameter value...6 9 Development cost measurement...7 9.1 Measurement steps...7 9.2 Scale measurement...7 9.3 Workload measurement...8 9.4 Duration measurement...10 9.5 Cost measurement...10 10 Third-party testing fee measurement...11 10.1 The content of the third-party test fee...11 10.2 Functional and non-functional testing fees...11 10.3 Security test fee...12 11 Implementation fee measurement...13 11.1 Proportional conversion based on development costs...13 11.2 WBS decomposition method...13 12 Supervision fee measurement...15 12.1 Principles of Measurement...15 12.2 Measurement formula...15 12.3 Parameter value...15 13 Project management fee measurement...16 13.1 Principles of Measurement...16 13.2 Measurement formula...16 13.3 Parameter value...16 Appendix A (informative appendix) Third-party test content...18

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. The main drafters of this standard. Zhang Dahua, Yang Lifang, Zeng Nan, Hao Hanyong, Wang Jinxiong, Li Yun, Qin Ming, Qian Shengpan, Yu Shengchuan, Hao Jihong, Ji Huimin, Wang Hongkui, Zheng Jiesheng, Liu Wenbin, Xu Gang, Wang Ying, Wang Jing, Yang Junhong, Zhu Chen, Zhang Chunlin, Yu Baokun, Wang Zhankui, Liang Fei, Dong Na, Wan Li, Tang Zeyang, Ren Chunlei, Mo Mingfei, Li Fangjun, Wang Yibo, Zhang Jianye, Li Degao. This standard is issued for the first time. The opinions or suggestions during the implementation of this standard are fed back to the Standardization Center of the China Electricity Council (Baiguang Road, Beijing No. 100761). Power Information Software Engineering Measurement Specification range This standard specifies the measurement principles and content, cost composition, and cost measurement methods of various parts of the power industry informatization software engineering. This standard applies to the cost of software research and development in information software engineering or other projects in the power industry, which is mainly software research and development. It does not apply to project cost measurement such as infrastructure construction, software and hardware procurement, and industrial control systems. Normative references The following documents are indispensable for the application of this document. For dated reference documents, only the dated version applies to this article Pieces. For undated references, the latest version (including all amendments) applies to this document. GB/T 19668-2007 Specification for Information Engineering Supervision (not referring to specific terms, year number may not be used) GB/T 22240-2008 Information Security Technology Information System Security Level Protection Rating Guidelines SJ/T 11463-2013 Software R&D Cost Measurement Specification DB44/T 635-2009 Price Evaluation and Calculation Method of Government Investment Application Software Development Project HYD41-2005 Electronic construction project estimate (budget) preparation method and pricing basis SSM-BK China Software Industry Benchmark Data Report Terms and definitions The following terms and definitions apply to this document. Cost measurement The process of estimating the estimated value of information software engineering cost or measuring and analyzing the actual value. Function point A unit to measure the scale of software functions. [SJ/T 11463-2013, definition 3.13] Benchmark One or a group of measurement values or derived measurement values that have been screened and maintained in the database to characterize the target object (such as a project or item) The relationship between the relevant attributes and these measured values. [SJ/T 11463-2013, definition 3.14] Function point analyze method A method of measuring the scale of the software development process from the perspective of users, mainly from the perspective of logic design, The customer's function is quantified. 4.1 Indicated function point analyze method A function point analysis method that focuses on logic files. 4.2 Estimated function point analyze method A function point analysis method that focuses on logic files and operating processes. Work breakdown structure Oriented by deliverables, decompose project deliverables and project work by summarizing and defining the entire scope of the project Into a smaller, easy-to-manage work unit, forming a structured project unit portfolio. Equation method Establish a parameter model based on benchmark data, and determine the workload, duration or cost estimate of the project to be estimated by entering various parameters Methods. [SJ/T 11463-2013, definition 3.9] Analogy comparison Compare some attributes of this project with a similar set of benchmark data to obtain the workload, duration or cost of the project to be estimated Method of estimation. [SJ/T 11463-2013, definition 3.10] Analogy Compare some of the attributes of this project with the data of one or several completed projects that are highly similar, and obtain a pending estimate after appropriate adjustments The method of calculating project workload, duration or cost estimate. [SJ/T 11463-2013, definition 3.11] Internal logical file A group of data or control information that can be identified by the user and has an internal logical association, and is controlled within the boundaries of the system, The main purpose is to accommodate a set of data maintained by one or a set of basic processes in this system. External interface file A group of data or control information that can be identified by the user, is quoted in this system, and has an inherent logical association. The main purpose is to accommodate a group of data referenced by one or a group of basic processes in the system.

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, MkⅡ 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, 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; MkⅡ 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

3.1 Measurement principle The workload measurement of development work includes the following principles. a) Fully analyze engineering risks, and consider technology, management, resources, and business factors in risk analysis. According to risk Analyze the results and make reasonable adjustments to the estimation method or model. Such as adjusting the weight or value of the influence factor in the estimation model, or according to wind Risk analysis results define the software integrity level and adjust the workload estimation results according to the integrity level; b) Analyze the reuse of functions to be realized, and identify the reused functions and the degree of reuse. According to the reusable scale and The degree of reuse adjusts the workload estimate; c) Choose an appropriate workload estimation method, and use function point analysis to measure the workload for development work; d) When using the function point analysis method, the main factors that affect the workload should be considered, including (but not limited to) software scale, application scope Domain, quality requirements, etc. In addition, factors that should be considered include (but are not limited to). adopting technology, such as development platform, editing Programming language, system architecture, operating system, etc.; development team, such as the organization type of the developer, team size, personnel capabilities, etc.; Process capabilities, such as the developer’s process maturity level, management requirements, etc.; factors that affect the characteristics of the power industry. The estimation should be based on this These factors make appropriate adjustments to the estimation results; e) Different methods should be used to estimate the workload and cross-validate. If the estimation results of different methods produce large differences, Expert review methods can be used to determine the estimation results, or a simpler weighted average method can be used; f) The project that is difficult to estimate the scale should adopt the analogy method or the analogy method; the project that has already been estimated should adopt the equation method; a) When using analogy, the historical project referenced should be highly similar to the project to be estimated. In the estimation, the Estimate the main differences between the estimated project and reference historical projects and make appropriate adjustments to the estimated results; b) When using the analogy method, the benchmark data should be filtered according to the main project attributes; when the number of projects used for comparison is too small It is advisable to screen and compare according to different project attributes, and comprehensively consider the results of workload estimation; c) When using the equation method, it is advisable to establish a regression equation based on the benchmark data and adopt a regression analysis method. Can be based on the complete Multivariate equation (including all workload influencing factors), directly calculate the estimation result; it can also be based on a simpler equation, Calculate the preliminary workload estimation result, and then adjust the workload estimation result according to other adjustment factors. g) When the workload estimation needs to be re-evaluated due to engineering changes, the workload estimation method and estimation should be based on the scope of the change. Make reasonable adjustments to the calculation results. 3.2 Measurement formula 9.3.2.1 Development effort measurement model The development workload measurement model is shown in equation (7). 9.3.2.2 Development workload adjustment factor The calculation formula of development workload adjustment coefficient is shown in formula (8). 9.3.2.3 Software factor adjustment factor The calculation method of software factor adjustment factor is shown in formula (9). 9.3.2.4 Development factor adjustment factor The calculation method of development factor adjustment factor is shown in equation (10). 3.3 Parameter value 9.3.3.1 Software industry development productivity The productivity parameters are obtained from the newly released SSM-BK, see Table 5. 9.3.3.2 Software factor adjustments and development factors adjustments

4 Duration measurement

4.1 Principles of Measurement The duration measurement includes the following principles. a) Decompose work tasks and formulate work schedules based on the results of workload estimation and resources. Working schedule At the same time, the impact of critical path task constraints on the construction period should be fully considered. Such as the resource input of users participating in demand communication activities, The client’s requirements for the trial operation cycle, etc.; Use benchmark data to estimate a reasonable scope of construction. Baseline data can be used to establish a "workload-duration" model and use equation method to estimate Calculate the reasonable scope of the construction period; you can also use the analogy method to estimate the reasonable scope of the construction period; Compare the expected construction period of the client or the construction period in the work schedule initially formulated by the developer with the estimated results of the construction period; If the client expects the construction period or the construction period in the work schedule to be shorter than the estimated lower limit of the construction period, the reason shall be analyzed, and the personnel shall be Make adjustments to the arrangement of human resources or the scope of the project, then re-estimate the workload and duration, and formulate a new work schedule. 4.2 Measurement formula Refer to equation (11) for the workload-duration measurement model. When the expected construction period is shorter than the lower limit of the estimated construction period, the engineering requirements should be analyzed And adjust appropriately. Usually, shortening the construction period will increase the engineering workload and cost.

5 Cost measurement

5.1 Measurement principle Software development costs should include all direct costs and indirect costs in the software development process. Among them, direct costs include direct labor Costs and direct non-labor costs, indirect costs include indirect labor costs and indirect non-human costs. 5.2 Measurement formula After obtaining the workload estimation result, it is appropriate to use formula (12) to measure the engineering cost. 5.3 Parameter value The person-month rate is obtained from the newly released SSM-BK and revised in time according to the SSM-BK version update, see Table 7.

Tips & Frequently Asked Questions:

Question 1: How long will the true-PDF of DL/T 2015-2019_English be delivered?

Answer: Upon your order, we will start to translate DL/T 2015-2019_English as soon as possible, and keep you informed of the progress. The lead time is typically 3 ~ 5 working days. The lengthier the document the longer the lead time.

Question 2: Can I share the purchased PDF of DL/T 2015-2019_English with my colleagues?

Answer: Yes. The purchased PDF of DL/T 2015-2019_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet.

Question 3: Does the price include tax/VAT?

Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countries

Question 4: Do you accept my currency other than USD?

Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.