Object Points (POs) POs are used in the Cocomo

[sujonkumar6300]

Estimation model under the name Application Points. These are an alternative to UFCs, and are used in object-oriented and scripting languages. They give value to each screen depending on its complexity: simple = 1, moderately complex = 2, very complex = 3. Reports range from 2 to 8 depending on the level of complexity, and modules in imperative languages ​​such as Java or C++ are counted as 10. This can be directly related to the user stories of some agile methodologies, thus facilitating the estimation of the iteration.

Constructive Cost Model: COCOMO II
One of the most widely used estimation models is COCOMO (Constructive Cost Model) created by Dr. Barry Boehm. COCOMO first appeared in his book Software Engineering Economics [1] in 1981. In 1999 the second version of the Bahamas Mobile Database model was defined which takes into account the project, the product, the hardware and the experience of the development team in its cost estimation formulas, including time prediction mechanisms.

Cocomo II provides levels that allow us to make estimates at different times during development, since cost estimation must be a dynamic process throughout development, constantly updating the variables, the evolution of the development team, the tools and languages ​​involved. The different levels are: