An empirical study on the estimation of software development effort with use case points

Empirical studies are important in software engineering to evaluate new tools, techniques, methods and technologies in a structured way before they are introduced in the industrial (real) software process. Perform empirical studies in a real context is very difficult due to various obstacles, so, we intend to create a stable environment that allows us to perform reliably empirical studies with students. This paper describes a case study with 104 students grouped in seven teams that developed a software system (Web application) for a real costumer. In this study we used a model based on Use Case Points (UCP) to estimate the resources needed to develop a software system.

[1]  Claes Wohlin,et al.  Using students as subjects - an empirical evaluation , 2008, ESEM '08.

[2]  Genny Tortora,et al.  Empirical Experimentation in Software Engineering , 2007 .

[3]  Tore Dybå,et al.  Conducting realistic experiments in software engineering , 2002, Proceedings International Symposium on Empirical Software Engineering.

[4]  Ricardo J. Machado,et al.  Tailoring RUP to Small Software Development Teams , 2011, 2011 37th EUROMICRO Conference on Software Engineering and Advanced Applications.

[5]  Amela Karahasanovic,et al.  A survey of controlled experiments in software engineering , 2005, IEEE Transactions on Software Engineering.

[6]  David Herron,et al.  Function Point Analysis: Measurement Practices for Successful Software Projects , 2000 .

[7]  Walter F. Tichy,et al.  Hints for Reviewing Empirical Work in Software Engineering , 2000, Empirical Software Engineering.

[8]  Alain Abran,et al.  Software Metrics and Software Metrology: Abran/Software Metrics , 2010 .

[9]  Claes Wohlin,et al.  Using Students as Subjects—A Comparative Study of Students and Professionals in Lead-Time Impact Assessment , 2000, Empirical Software Engineering.

[10]  Alistair Cockburn,et al.  Writing Effective Use Cases , 2000 .

[11]  John E. Gaffney,et al.  Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation , 1983, IEEE Transactions on Software Engineering.

[12]  Mel Damodaran.  Estimation Using Use Case Points , 2002 .

[13]  Ricardo J. Machado,et al.  Mapping RUP Roles to Small Software Development Teams , 2012, SWQD.

[14]  Maria Letizia Jaccheri,et al.  Involving Industry Professionals in Empirical Studies with Students , 2006, Empirical Software Engineering Issues.

[15]  Magne Jørgensen,et al.  Estimating Software Development Effort Based on Use Cases-Experiences from Industry , 2001, UML.

[16]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[17]  Norman E. Fenton,et al.  Software metrics: roadmap , 2000, ICSE '00.

[18]  Computer Staff,et al.  Function Points , 1994 .

[19]  Charles R. Symons,et al.  Software sizing and estimating - Mk II FPA, function point analysis , 1991, Wiley series in software engineering practice.

[20]  Vojislav B. Misic,et al.  Downsizing the estimation of software quality: a small object-oriented case study , 1998, Proceedings Technology of Object-Oriented Languages. TOOLS 27 (Cat. No.98EX224).

[21]  Sean Furey.  Point: Why We Should Use Function Points , 1997, IEEE Softw..

[22]  Gustav Karner,et al.  Resource Estimation for Objectory Projects , 2010 .

[23]  Shari Lawrence Pfleeger,et al.  Software Metrics : A Rigorous and Practical Approach , 1998 .

[24]  Tom DeMarco.  An algorithm for sizing software products , 1984, PERV.

[25]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[26]  Alain Abran,et al.  Software Metrics and Software Metrology , 2010 .

[27]  Victor R. Basili,et al.  The software engineering laboratory - an operational software experience factory , 1992, International Conference on Software Engineering.

[28]  Jeffrey C. Carver,et al.  A checklist for integrating student empirical studies with research and teaching goals , 2010, Empirical Software Engineering.

[29]  S. Furey.  Why we should use function points [software metrics] , 1997 .

[30]  Cemal Yilmaz,et al.  Software Metrics , 2008, Wiley Encyclopedia of Computer Science and Engineering.