Project management-Software Value Estimation

The first problem I encountered was that it was difficult to estimate the workload. Some people thought it was almost impossible to estimate the workload of a software project, because the mathematical formula proposed by cocomo was difficult to apply. CodeThe row or function point is used to calculate the person-month, but the software has not yet been developed. How can we know the number of lines of code? How can we estimate the number of functional points? In fact, the demand is constantly changing, as the functional points evolve, there is another difficulty, and the granularity and width of the functional points cannot be consistent. Therefore, using a formula to calculate man-month leads to a paradox.

Computing workload has a very important practical significance. For example, the allocation of funds should be linked to the workload. If your allocation is unreasonable, it will lead to Team division and project failure. The most important thing to manage is the balance, so everyone expects a bowl of water, but I cannot do it now.

You can calculate the general ledger after the project is completed. It is especially suitable for calculating the contributions of everyone in a project. However, I do not know other components of the software project, such as the document (Requirement Analysis Report, design document, UML document,ProgramNote, user manual, etc.) How is the calculation calculated according to the code formula? Or functions? I think this is obviously a joke, and no one will take you.

Still confused!

Software Cost Estimation: metrics and Models
Software Construction Cost Model and calculator