扫码阅读
手机扫码阅读
快速学习COSMIC方法之十三:如何识别读和写?
26 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 成员,中国分部主席
379 篇文章
浏览 58.7K
麦哲思科技任甲林的其他文章
需求变更的5W1H分析
why,需求为什么变化? 甲方的特殊原因: 不知道如何说清楚需求; 没有明确的需求; 没有确认乙方描述的需求; 乙方的特殊原因: 理解错了需求; 没有很好的诱导客户的需求; 共性原因: 业务就是变化; 人与人之间的沟通本来就存在障碍; 特殊原因是可以消除的,共性原因是难以消除的。 who : 谁会提出需求变化? 客户:客户方的
用COSMIC方法帮助澄清需求的案例
实施COSMIC方法,除了可以度量软件的规模以外,还可以通过数功能点,识别需求中模糊不清的地方,起到需求澄清、需求验证的作用。下面通过一个简单的例子来说明之。某系统的需求规格说明书中有如下的一个功能需求描述:考勤明细查询功能说明:1展示员工每天的有效打卡记录,清晰展示上下班时间、打卡照片等;2可查看员工每天所有的打卡记录,显示的信息包括:名称、部门、员工状态、工号、日期、上...
理解敏捷思想的63句话!
序号 类别 箴言 解释 1 持续提升 敏捷转型是文化变革,前景美好,道路曲折,,必须领导先行。 冰冻三尺,非一日之寒。要想转型到敏捷文化,需要领导投入、开发人员配合、管理部门理解和支持才可能成功。 敏捷始于领导,死于领导,领导往往会...
COSMIC规模度量方法v4.0度量手册中文版正式发布了!
COSMIC是通用软件度量国际联盟的简写,它成立于1998年,是一个由全球软件度量专家组成的非盈利自愿性组织,致力于软件规模度量方法的研究与推广。2002年1月COSMIC所推出的全功能点规模度量方法成为了ISO的标准,最新标准为ISO/IEC 19761:2011“软件工程—COSMIC—功能规模度量方法”。COSMIC规模度量方法相对于传统的规模度量方法简单实用,学习周期短,易于上手。一经推出
各阶段缺陷检出密度的统计分析案例
某企业积累了10个项目的历史度量数据,积累了5个阶段的缺陷密度,即从需求评审的缺陷密度,直至交付后3个月内的缺陷密度,计量单位统一为缺陷数/KLOC。 需求评审缺陷密度 设计评审缺陷密度 代码评审缺陷密度 测试发现缺陷密度 交付后缺陷密度 P1 ...
加入社区微信群
与行业大咖零距离交流学习
软件研发质量管理体系建设
白皮书上线