Adapting function points to object oriented information systems
The object oriented paradigm has become widely used to develop large information systems. This paper presents a method for estimating the size and effort of developing object oriented software. The approach is analogous to function points, and it is based on counting rules that pick up the elements in a static object model and combine them in order to produce a composite measure. Rules are proposed for counting “Object Oriented Function Points” from an object model, and several questions are identified for empirical research.
A key aspect of this method is its flexibility. An organization can experiment with different counting policies, to find the most accurate predictors of size, effort, etc. in its environment.
“Object Oriented Function Points” counting has been implemented in a Java tool, and results on size estimation obtained from a pilot project with an industrial partner are encouraging.
KeywordsObject oriented design metrics function points size estimation
Unable to display preview. Download preview PDF.
- 1.A. J. Albrecht. Measuring application development productivity. In Proc. IBM Applications Development Symposium, pages 83–92. IBM, Oct. 1979.Google Scholar
- 2.G. Caldiera, C. Lokan, G. Antoniol, R. Fiutem, S. Curtis, G. L. Commare, and E. Mambella. Estimating Size and Effort for Object Oriented Systems. In Proc. 4th Australian Conference on Software Metrics, 1997.Google Scholar
- 3.T. Fetcke, A. Abran, and T.-H. Nguyen. Mapping the OO-Jacobson approach to function point analysis. In Proc. IFPUG 1997 Spring Conference, pages 134–142. IFPUG, Apr. 1997.Google Scholar
- 4.E. Gamma, R. Helm, R. Johnson, and J. Vlissides. Design Patterns: Elements of Reusable Object Oriented Software. Addison-Wesley, 1995.Google Scholar
- 5.T. Hastings. Adapting function points to contemporary software systems: A review of proposals. In Proc. 2nd Australian Conference on Software Metrics. Australian Software Metrics Association, 1995.Google Scholar
- 6.IFPUG. Function Point Counting Practices Manual, Release 4.0. International Function Point Users Group, Westerville, Ohio, 1994.Google Scholar
- 7.IFPUG. Function Point Counting Practices: Case Study 3 — Object-Oriented Analysis, Object-Oriented Design (Draft). International Function Point Users Group, Westerville, Ohio, 1995.Google Scholar
- 8.Interactive Development Environments. Software Through Pictures manuals, 1996.Google Scholar
- 9.I. Jacobson, M. Christerson, P. Jonsson, and G. övergaard. Object Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley, 1992.Google Scholar
- 11.B. Kitchenham and K. KÄnsÄlÄ. Inter-item correlations among function points. In Proc. 15th International Conference on Software Engineering, pages 477–480. IEEE, May 1993.Google Scholar
- 13.Rational Software Corporation. Unified Modeling Language, Version 1.0, 1997.Google Scholar
- 14.J. Rumbaugh, M. Blaha, W. Premerlani, F. Eddy, and W. Lorensen. Object Oriented Modelling and Design. Prentice-Hall, 1991.Google Scholar
- 15.M. Schooneveldt. Measuring the size of object oriented systems. In Proc. 2nd Australian Conference on Software Metrics. Australian Software Metrics Association, 1995.Google Scholar
- 16.H. Sneed. Estimating the Costs of Object-Oriented Software. In Proceedings of Software Cost Estimation Seminar, 1995.Google Scholar
- 17.J. Verner, G. Tate, B. Jackson, and R. Hayward. Technology dependence in Function Point Analysis: a case study and critical review. In Proc. 11th International Conference on Software Engineering, pages 375–382. IEEE, 1989.Google Scholar
- 19.S. Whitmire. Applying function points to object-oriented software models. In Software Engineering Productivity Handbook, pages 229–244. McGraw-Hill, 1993.Google Scholar