Skip to main content

Architectural Element Points: Estimating Software Development Effort by Analysis of Logical Architectures

  • Conference paper
  • First Online:
Information Systems: Development, Research, Applications, Education (SIGSAND/PLAIS 2016)

Part of the book series: Lecture Notes in Business Information Processing ((LNBIP,volume 264))

Included in the following conference series:

  • 833 Accesses

Abstract

Empirical studies are important in software engineering to evaluate new tools, techniques, methods and technologies. In object-oriented analysis, use case models describe the functional requirements of a software system, so they can be the basis for software measurement and sizing. The purpose of this study is to develop a new metric called Architectural Element Points (AEPoint) that enables to calculate the effort required to develop a software solution, using the 4-Step Rule Set (4SRS) method. This paper describes a case study with 60 undergraduate students grouped in four teams that developed a software system (Web application) for a real customer. In this study, we used the AEPoint metric to estimate the resources needed to develop a software system. The results of the AEPoint and Use Case Points (UCP) metrics and the real software development effort are compared, conclusions drawn and recommendations are proposed.

This work has been supported by COMPETE: POCI-01-0145-FEDER-007043 and FCT – Fundação para a Ciência e Tecnologia within the Project Scope: UID/CEC/00319/2013.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

References

  1. Basili, V., Caldiera, G., McGarry, F., Pajerski, R., Page, G., Waligora, S.: The software engineering laboratory-an operational software experience factory. In: 14th ICSE, pp. 370–381. ACM (1992)

    Google Scholar 

  2. Visaggio, G.: Empirical experimentation in software engineering. In: Lucia, A.D., Ferrucci, F., Tortora, G., Tucci, M. (eds.) Emerging Methods, Technologies and Process Management in Software Engineering, p. 227. Wiley, Hoboken (2008)

    Google Scholar 

  3. Alves, L.M., Ribeiro, P., Machado, R.J.: Project-Based Learning: An Environment to Prepare IT Students for an Industry Career. Overcoming Challenges in Software Engineering Education: Delivering Non-Technical Knowledge and Skills, pp. 230–249. IGI Global (2014)

    Google Scholar 

  4. Machado, R.J., Fernandes, J.M., Monteiro, P., Rodrigues, H.: Transformation of UML models for service-oriented software architectures. In: 12th IEEE International Conference and Workshops on the Engineering of Computer-Based Systems (ECBS 2005), pp. 173–182 (2005)

    Google Scholar 

  5. Karner, G.: Resource Estimation for Objectory Projects. Objectory Systems SF AB (1993)

    Google Scholar 

  6. Karner, G.: Use Case Points: Resource Estimation for Objectory Projects. In: Objective Systems SF AB. (1993)

    Google Scholar 

  7. Pressman, R.S.: Software Engineering: A Practitioner’s Approach. McGraw-Hill, New York (2005)

    Google Scholar 

  8. Fenton, N.E., Neil, M.: Software metrics: roadmap. In: CFSE 2000, pp. 357–370. ACM, 336588 (2000)

    Google Scholar 

  9. Fenton, N.E., Pfleeger, S.L.: Software Metrics: A Rigorous and Practical Approach. PWS Publishing Company, Boston (1997)

    Google Scholar 

  10. University of Houston-Victoria. http://bfpug.com.br/Artigos/UCP/Damodaran-Estimation_Using_Use_Case_Points.pdf

  11. Alves, L.M., Sousa, A., Ribeiro, P., Machado, R.J.: An empirical study on the estimation of software development effort with use case points. In: 2013 Frontiers in Education Conference, pp. 101–107. IEEE (2013)

    Google Scholar 

  12. Ochodek, M., Nawrocki, J., Kwarciak, K.: Simplifying effort estimation based on use case points. Inf. Softw. Technol. 53, 200–213 (2011)

    Article  Google Scholar 

  13. Anda, B., Dreiem, H., Jørgensen, M.: Estimating software development effort based on use cases-experiences from industry. In: Gogolla, M., Kobryn, C. (eds.) UML 2001. LNCS, vol. 2185, pp. 487–502. Springer, Heidelberg (2001)

    Chapter  Google Scholar 

  14. Anda, B., Benestad, H.C., Hove, S.E.: A multiple-case study of software effort estimation based on use case points. In: International Symposium on Empirical Software Engineering, pp. 407–416 (2005)

    Google Scholar 

  15. Yavari, Y., Afsharchi, M., Karami, M.: Software complexity level determination using software effort estimation use case points metrics. In: 5th Malaysian Conference Software Engineering (MySEC 2011), pp. 257–262 (2011)

    Google Scholar 

  16. Albrecht, A.J.: Measuring application development productivity. In: IBM Application Development Symposium, pp. 83–92. IBM Press (1979)

    Google Scholar 

  17. http://www.teamworkpm.net/

Download references

Acknowledgments

The authors would like to thank the referees for their valuable comments.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Luís M. Alves .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2016 Springer International Publishing AG

About this paper

Cite this paper

Alves, L.M., Ribeiro, P., Machado, R.J. (2016). Architectural Element Points: Estimating Software Development Effort by Analysis of Logical Architectures. In: Wrycza, S. (eds) Information Systems: Development, Research, Applications, Education. SIGSAND/PLAIS 2016. Lecture Notes in Business Information Processing, vol 264. Springer, Cham. https://doi.org/10.1007/978-3-319-46642-2_5

Download citation

Publish with us

Policies and ethics