快速学习COSMIC方法之十三:如何识别读和写?
发布于 2024-10-01
1826
版权声明
我们非常重视原创文章,为尊重知识产权并避免潜在的版权问题,我们在此提供文章的摘要供您初步了解。如果您想要查阅更为详尽的内容,访问作者的公众号页面获取完整文章。
麦哲思科技任甲林
扫码关注公众号
扫码阅读
手机扫码阅读
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 成员,中国分部主席
471 篇文章
浏览 1071.1K
还在用多套工具管项目?
一个平台搞定产品、项目、质量与效能,告别整合之苦,实现全流程闭环。
查看方案
麦哲思科技任甲林的其他文章
白话SCRUM 之三:sprint backlog
Sprint Backlog就是任务列表,如果映射到传统的项目管理理论中就是WBS(work breakdown structure),而且是典型的采用面向交付物的任务分解方法得到的WBS。比如有一个Product backlog 条目为: 作为系统的合法用户,可以通过录入账号和密码登录到系统中。为了实现此需求,team member识别出了的任务,进行了工作量的估计,进行了任务了领用,其结
还是“师徒制”吧
很多客户都面临如何培养新员工的问题,如何更好的培养开发人员也一直是我思考的问题。琢磨来琢磨去,最终发现还是“师徒制”最有效。 在学校里教授的大多是书本知识,和实践有很大差别。社会上的各种速成班仍然是停留在表面,可以让开发人员入门,但是不能深入。在公司里办各种培训,时间不可能太长久。其实以前在通软的时候已经尝试过师傅带徒弟的方式,只是我不喜欢称为“师徒制”。“师”在我心目中是比较神圣的称呼,为“师”
代码评审的速度与缺陷密度是啥关系?
某企业采集了8个项目的代码评审数据,虽然样本数量不多,但是仍然可以发现一些规律原始的度量数据如下,包括了代码评审发现的缺陷密度与代码评审的速度。这2者是什么关系呢? 表一:8个项目的代码评审缺陷密度与评审速度 ...
哈哈,新开了微博:http://weibo.com/measures
哈哈,新开了微博:http://weibo.com/measures,欢迎访问。
图解敏捷性能合弄结构APH之:valuing合弄
图一:valuing合弄的目的与性能等级图二:valuing合弄的活动各种敏捷方法的原则参见博客:https://blog.csdn.net/dylanren/article/details/87184790。 图三:valuing合弄使用的敏捷仪式和技术说明:为便于图形化表达,每种敏捷仪式或技术没有映射到具体的活动,敏捷活动与敏捷仪式是多对多的映射关系。 ...
加入社区微信群
与行业大咖零距离交流学习
PMO实践白皮书
白皮书上线
白皮书上线