扫码阅读
手机扫码阅读
快速学习COSMIC方法之十三:如何识别读和写?
111 2024-10-01
我们非常重视原创文章,为尊重知识产权并避免潜在的版权问题,我们在此提供文章的摘要供您初步了解。如果您想要查阅更为详尽的内容,访问作者的公众号页面获取完整文章。
文章来源:
麦哲思科技任甲林
扫码关注公众号
Summary of Data Interaction in Software Measurement
Understanding the difference between reading and writing data interactions in software is generally straightforward, with a low probability of error. These actions involve the transfer of data between software and storage media. Reading moves data from persistent storage to internal processing, while writing does the opposite.
Key Points to Identify Reading and Writing:
- Data Groups and Interest Objects: Each read or write involves data groups of a single interest object. Multiple reads or writes must be identified if multiple interest objects or different data groups of the same interest object are involved. Repeated reads or writes of the same data group count as a single action, as seen in software that reads exchange rates at regular intervals.
- Do Not Confuse Reading with Input and Writing with Output: Reading and writing refer to data movement to and from persistent storage, respectively. Input and output involve data movement to and from the user of the function. These should not be confused as long as the user and persistent storage are distinguished.
- Temporary Data Exclusions: Reads or writes of temporary data that are not interest objects and are used for implementation purposes do not count towards function points. An example is counting failed login attempts, which is not preserved after the function is completed.
- Single Function Point for Read Requests: Issuing a read command and then receiving the data is counted as a single read function point. If user input is needed, an output followed by an input is counted, but if no specific user data request is necessary, only an input function point is counted.
- Deletion Counts as Writing: Deleting a data group is considered writing, which aligns with common understanding and requires no further explanation.
想要了解更多内容?
文章来源:
麦哲思科技任甲林
扫码关注公众号
麦哲思科技(北京)有限公司总经理 敏捷性能合弄模型评估师 认证的Scrum Master 认证的大规模敏捷顾问SPC CMMI高成熟度主任评估师 COSMIC MPC,IAC 成员,中国分部主席
425 篇文章
浏览 103.5K
麦哲思科技任甲林的其他文章
CMMI 3.0的276条实践中英文对照
CMMI 3.0在2023年4月6日发布了,包含了31个实践域,276条实践。本文试图把276条实践的中英文对照如下。
对需求变更的定量分析
很多公司头疼需求变更,如果我们采用定量的技术该如何分析需求的变更呢?首先定义什么叫需求变更?在客户方与开发方共同认可需求之后的需求修改、增加、删除都是需求变更。需求变更对象可以从多个维度划分: 维度一: 功能需求、非功能性需求、接口需求、界面需求、技术约束等; 维度二:业务逻辑、数据对象、控制逻辑等;其次,可以从3个层次分析需求变更:层次1: 需求变更率分析。需求变更率有多种定义方法。 方法一:需求变更率=需求变更的个数/交付的需求个数;...
你是否真的读懂了回归方程y=ax+b?
当我们对一些现象进行回归分析之后,可以得到回归方程y=ax+b,很简单的一根直线,如果结合我们的实际应用场景,则可以从该方程的2个系数中发现很多问题:1 当b比a大很多时,如何理解?比如,工作量=10*规模+10000此时:b=10000为固定成本, a=10为变动成本。说明在这家公司中,项目一立项就有比较高的固定成本!需要减少无用功,降低很多与直接生产无关的...
COSMIC规模度量案例集三:业务应用软件案例—页面维护
概述展示前台注册及后台新增的用户信息的页面。流程图用户查询界面原型输入: 序号 输入项 类型 字段描述 说明 1. 用户名/姓名 输入框 选填 按照用户名或者姓名模糊查询 2. 机构全称 输入框 ..
我说CMMI2.0之:II点睛
II(implementation infrastructure)可以翻译为:实施基础设施。基础设施包括了资源、资金、培训、流程定义、经验教训总结等方面的实践,总之,就是要建立进行持续过程改进的能力。实践列表: 1.1 Perform processes that address the intent of the Level 1 practices. ...
加入社区微信群
与行业大咖零距离交流学习
软件研发质量管理体系建设
白皮书上线