GB/T 42452-2023 English PDFUS$364.00 ยท In stock
Delivery: <= 4 days. True-PDF full-copy in English will be manually translated and delivered via email. GB/T 42452-2023: Systems and software engineering - Functional size measurement - COSMIC method Status: Valid
Basic dataStandard ID: GB/T 42452-2023 (GB/T42452-2023)Description (Translated English): Systems and software engineering - Functional size measurement - COSMIC method Sector / Industry: National Standard (Recommended) Classification of Chinese Standard: L77 Classification of International Standard: 35.080 Word Count Estimation: 20,283 Date of Issue: 2023-03-17 Date of Implementation: 2023-10-01 Issuing agency(ies): State Administration for Market Regulation, China National Standardization Administration GB/T 42452-2023: Systems and software engineering - Functional size measurement - COSMIC method---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.ICS35:080 CCSL77 National Standards of People's Republic of China GB/T 42452-2023/ISO /IEC 19761:2011 System and software engineering functional size measurement COSMIC method COSMIC method (ISO /IEC 19761:2011, Softwareengineering-COSMIC:afunctional Released on 2023-03-17 2023-10-01 implementation State Administration for Market Regulation Released by the National Standardization Management Committee table of contentsPreface I Introduction II 1 Scope 1 2 Normative references 1 3 Terms and Definitions 1 4 Abbreviations5 5 Units of measure5 6 Measurement activities 5 6:1 General 5 6:2 Determining the purpose and scope of FSM5 6:3 Identify User Functional Requirements (FUR) 6 6:4 Identification layer 6 6:5 Identifying functional users 6 6:6 Identifying software boundaries 6 6:7 Identifying functional processes 7 6:8 Identification data set 7 6:9 Identifying data movement 7 6:10 Classification of data movement 7 6:11 Calculation of functional size 8 6:12 Functional Size Calculation for FUR Changes 9 7 Measurement Report 9 7:1 Mark 9 7:2 Documentation of measurement results9 Appendix A (Informative) Extraction of User Functional Requirements 11 Appendix NA (informative) Application cases of this document 13 Reference 15forewordThis document is in accordance with the provisions of GB/T 1:1-2020 "Guidelines for Standardization Work Part 1: Structure and Drafting Rules for Standardization Documents" drafting: This document is equivalent to ISO /IEC 19761:2011 "Software Engineering COSMIC: A Functional Size Measurement Method": This document adds a chapter "Normative References": This document has made the following minimal editorial changes: ---In order to coordinate with the existing standard documents, the name of the standard is changed to "COSMIC method for system and software engineering functional scale measurement Law"; --- Added Appendix NA (informative) "Application Cases of this Document": Please note that some contents of this document may refer to patents: The issuing agency of this document assumes no responsibility for identifying patents: This document is proposed and managed by the National Information Technology Standardization Technical Committee (SAC/TC28): This document was drafted by: Shandong Shanke Digital Economy Research Institute Co:, Ltd:, China Electronics Standardization Research Institute, Shenzhen Saixi Information Technology Co:, Ltd:, Zhejiang Electronic Information Products Inspection and Research Institute, Shanghai Software Industry Association, Magez Technology (Beijing) Co:, Ltd:, Shandong Provincial Computing Center (National Supercomputing Jinan Center), Guangxi Dayi Technology Co:, Ltd:, Shanghai Baosight Software Co:, Ltd:, China General Planning Institute of Petroleum and Natural Gas Co:, Ltd:, CCID Chongqing Information Technology Co:, Ltd:, Guangdong Science and Technology Fundamental Conditions Platform Center, Beijing Software Cost Evaluation Technology Innovation Alliance, Daopu Information Technology Co:, Ltd:, Shanghai Tongsting Software Technology Co:, Ltd:, Yunnan Power Grid Co:, Ltd: Limited Liability Company Information Center, Shanghai Computer Software Technology Development Center, Beijing Zhongji Datalink Technology Co:, Ltd:, Beijing Software and Information Service Exchange Co:, Ltd:, Chengdu Sifang Weiye Software Co:, Ltd:, Shanghai Xuansi Intelligent Technology Co:, Ltd:, China Aerospace Systems Science and Engineering Research Institute: The main drafters of this document: Li Gang, Li Wenpeng, Li Wang, Zhang Yangyang, Zhou Mingle, Ren Jialin, Ji Yongwei, Yang Genxing, Su Wei, Xu Yingmei, Gong Jiayu, Yu Dejun, Li Min, Sun Jinyang, Lou Li, Xu Huashou, Lu Xue, Su Shengjie, Zhang Yi, Li Peisheng, Liu Yiming, Feng Junhong, Li Lingfan, Guo Ling, An Wenwen, Yang Chao, Che Jiangtao, Guo Dong, Wu Dilong, Ouyang Shusheng, Han Mingjun, Feng Kuan, Fude Peng, Gu Meiying, Yao Zufa, Wu Guang, Han Qingliang, Yu Tieqiang, Hao Lin, Liu Lin, Qin Xiaoji, Liu Xiaoping, Qi Zhiming, Liu Fen, Wu Haijun, Jiang Jin, Zhuang Zhuang, Shen Ying, Li Mo, Han Yong, Liu Yongchao:IntroductionIn order to standardize the quantitative evaluation of software in my country and reduce the differences brought about by different scale measurement methods as much as possible, it is necessary to measure the software scale: The calculation method is standardized: Software investment is an important part of many business budgets: Organizations recognize the importance of controlling software costs, analytics in software development and maintenance The importance of performance against budgets for investment in the field of care in order to compare with industry benchmarks in the field: To do this, it is necessary to measure and apply these Quantitative model: Corresponding measurements are needed when analyzing the quality and productivity of software development and maintenance work: On the one hand, from the developer's point of view See, the technical performance of a product or service requires technical measurements to quantify: These technical measures can be used for efficiency analysis, such as improving software design Calculation efficiency: On the other hand, quantifying the performance of a product or service from the perspective of the user or owner requires functional measures such as productivity analysis: analysis: Functional measurements must be independent of the choice of technical means of development and implementation: Only then can these functional measurements be used to compare Comparing productivity when using different methods and techniques: System and software engineering functional size measurement COSMIC method1 ScopeThis document specifies a collection of definitions, conventions and activities for the COSMIC functional size measurement methodology: This document applies to the measurement of software function scale in the following fields: a) application software; Example 1: Banking, insurance, accounting, personnel, purchasing, distribution or manufacturing: b) real-time software; Example 2: Software for telephone exchange and information exchange, embedded in equipment to control devices such as household appliances, elevators, and automobile engines, for process control and automation Dynamic data acquisition, as well as the real-time control part of the software in the computer operating system: c) Software combining the above two types: Example 3: A real-time reservation system for flights or hotels: This document does not apply to functional size measurements of the following types of software segments or parts thereof: ---Software that uses complex mathematical algorithms or other complex professional rules, such as: expert systems, simulation software, self-learning software and weather forecasting system; ---Software that processes continuous variables such as audio, sound or video images, such as: computer game software, music processing software, etc: software:2 Normative referencesThis document has no normative references:3 Terms and DefinitionsThe following terms and definitions apply to this document: 3:1 The basic unit of the user's functional requirements: [Source: ISO /IEC 14143-1:2007, 3:1] 3:2 A defined class of base features: [Source: ISO /IEC 14143-1:2007, 3:2] 3:3 boundary boundary The conceptual interface between the software being measured and the functional user: ......Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 42452-2023_English be delivered?Answer: Upon your order, we will start to translate GB/T 42452-2023_English as soon as possible, and keep you informed of the progress. The lead time is typically 2 ~ 4 working days. The lengthier the document the longer the lead time.Question 2: Can I share the purchased PDF of GB/T 42452-2023_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 42452-2023_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+ countriesQuestion 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 Sales@ChineseStandard.net. 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. |