Software project workload evaluation method COSMIC key notes

If this article is helpful to you, remember to like and follow me!

Cosmic (Common Software Measurement International Consortium) is a basic software scale measurement method that PMO (Project Management Office, a position different from PM project manager) needs to master—estimating function points.

Advantages: simple and easy to use; scientific principle; wide application range, both application software and embedded; objective and accurate; easy to expand; suitable for all stages of software development.

Applies to: business application software; implementation software; platform software; some scientific/engineering software.

I have studied COSMIC by myself for a while, and the learning cost is very low. It only takes about a week to master it. In actual application, the company still has to unify a set of localization rules. The official COSMIC manual does not describe the evaluation plan for all application scenarios, and it is not easy for beginners to learn. It is recommended to read the official manual directly, because it makes simple concepts very complicated, and it is much easier to read the official manual after learning.

Recommended for beginners: "Quick Learning COSMIC Manual" officially produced by Mages Technology (Beijing) Co., Ltd.

You can download it from the official website  http://www.measures.net.cn/d/news/detail?id=5cad572ac6983442f2abf105

It can also be collected in CSDN  https://blog.csdn.net/dylanren/article/details/78614073?locationNum=10&fps=1 

I personally think chapters 5-15 are the most practical, so I put them in my favorites folder, and if I can't get my head right, just turn them over (o°ω°o)

Therefore, I will not repeat the introductory notes of COSMIC, and only show the content that I think is more important in the learning process.


This is my own drawing, easy to understand!

 

Metrics handled by reusable functions:

        When a FUR is implemented in software, any "functional commonality" may or may not be developed into reusable software. When measuring software size, all implementation decisions involving actual or potential software reuse must be ignored. However, when using functional size metrics for project effort analysis or estimation, reuse may need to be considered.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324175675&siteId=291194637