Object point explained

Object points are an approach used in software development effort estimation under some models such as COCOMO II.[1] [2]

Object points are a way of estimating effort size, similar to source lines of code (SLOC) or function points. They are not necessarily related to objects in object-oriented programming, the objects referred to include screens, reports, and modules of the language. The number of raw objects and complexity of each are estimated and a weighted total Object-Point count is then computed and used to base estimates of the effort needed.[3]

See also

Notes and References

  1. Web site: Software Measurement, Cost Estimation, SLIM, COCOMO. 22 Aug 2016. 5 November 2016. https://web.archive.org/web/20161105012701/http://yunus.hun.edu.tr/~sencer/cocomo.html. dead.
  2. Web site: The Comparison of the Software Cost Estimating Methods. 22 Aug 2016. 27 August 2016. https://web.archive.org/web/20160827104940/http://www.computing.dcu.ie/~renaat/ca421/LWu1.html. dead.
  3. Web site: Software Measurement Page, COCOMO II, object points. 22 Aug 2016. 8 November 2007. https://web.archive.org/web/20071108072906/http://yunus.hun.edu.tr/~sencer/objectp.html. dead.

This article is licensed under the GNU Free Documentation License. It uses material from the Wikipedia article "Object point".

Except where otherwise indicated, Everything.Explained.Today is © Copyright 2009-2026, A B Cryer, All Rights Reserved. Cookie policy.