Abstract
Even today, software projects still suffer from delays and budget overspending. The causes for this problem are compounded when the project team is distributed across different locations and generally attributed to the decreasing ability to communicate well (due to cultural, linguistic, and physical distance). Many projects, especially those with off-shoring component, consist of small iterations with changes, deletions and additions, yet there is no formal model of the flow of iterations available. A number of commercially available project prediction tools for projects as a whole exist, but the model adaptation process by iteration, if it exists, is unclear. Furthermore, no project data is available publicly to train on and understand the iterative process. In this work, we discuss parameters and formulas that are well founded in the literature and demonstrate their use within a simulation tool. Project timeline prediction capability is demonstrated on various scenarios of change requests. On a real-world example, we show that iteration-based data collection is necessary to train both the parameters and formulas to accurately model the software engineering process to gain a full understanding of complexities in software engineering process.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Abran, A., Robillard, P.N.: Function Points: A Study of Their Measurement Processes and Scale Transformations. Journal of Sistems and Software 25, 171–184 (1994)
Abran, A., Robillard, P.N.: Identification of the structural weakness of Function Point metrics. In: 3rd Annual Oregon Workshop on Metrics, pp. 1–18 (1991)
Albrecht, A.J.: Measuring application development productivity. In: IBM Corp. (ed.) IBM Application Develop Symp. (1979)
Albrecht, A.J., Gaffney, J.E.: Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation. IEEE Transactions on Software Engineering SE-9(9), 639 (1983)
Angelis, L., Stamelos, I., Morisio, M.: Building a Software Cost Estimation Model Based on Categorical Data. In: Pro. of the Seventh International Software Metrics Symposium METRICS, pp. 4–15 (2001)
Boehm, B., Englewood Cliffs, N. (eds.): Software Engineering Economics. Prentice-Hall, Englewood Cliffs (1981)
Datta, S.: A Mechanism For Tracking The Effects of Requirement Changes In Enterprise Software Systems, Master’s thesis, Florida State University (2006)
Datta, S., van Engelen, R.: Effects of Changing Requirements: A Tracking Mechanism for the Analysis Workflow, pp. 1739–1744 (2006)
Drappa, A., Ludewig, J.: Quantitative modeling for the interactive simulation of software projects. Journal of Systems and Software 46(2-3), 113–122 (1999)
Fairley, D.: Making Accurate Estimates. IEEE Software, 61–63 (2002)
Fetcke, T.: A Generalized Structure for Function Point Analysis. In: International Workshop on Software Measurement, pp. 143–153 (1999)
Freburger, K., Basili, V.: The Software Engineering Laboratoy: Relationship Equations, Report TR764, Technical report, University of Maryland (1979)
Ho, V.T., Abran, A., Oligny, S.: Using COSMIC -FFP to Quantify Functional Reuse in Software Development. In: Proc. of the ESCOM-SCOPE, pp. 299–306 (2000)
Huang, J.C., Chang, C.K., Christensen, M.: Event-Based Traceability for Managing Evolutionary Change. IEEE Transactions on Software Engineering Journal 29, 796–810 (2003)
IBM, Rational Unified Process Best Practices for Software Development Teams, Technical report, IBM (1998)
Jones, C.: Software Estimating Rules of Thumb, 116–119 (2007)
Jones, T.: Program Quality and Programmer Productivity, Technical report, IBM, IBM TR 02.764 (1977)
Lawrie, R., Radford, P.: Using Function Points in Early Life Cycle estimation. In: Proc. of the 4th European Conference on Software Measurement and ICT Control, pp. 197–210 (2001)
MacDonell, S.G.: Comparitive review of functional complexity assessment methods for effort estimation. In: Software Engineering Journal, pp. 107–116 (1994)
Nelson, R.: Software Data Collection and Analysis at RADC, Technical report, Rome Air Development Center (1978)
Paton, K., Abran, A.: A Formal Notation for the Rules of Function Point Analysis. Research Report 247, University of Quebec, pp. 1–49 (1995)
Ramesh, B.: Process Knowledge Management with Traceability. IEEE Software, 50–52 (2002)
Ramesh, B., Jarke, M.: Toward Reference Models for Requirements Traceability. IEEE Transanction on Software Engineering Journal 27(1), 58–93 (2001)
Schneider, V.: Prediction of Software Effort and Project Duration: Four New Formulas. In: ACM SIGPLAN Notices (1978)
Symons, C.: Come Back Function Analysis (Modernised) - All Is Forgiven!. In: Proc. of the 4th European Conference on Software Measurement and ICT Control, pp. 413–426 (2001)
Walston, C., Felix, C.: A Method of Programming Measurement and Estimation(1), Technical report, IBM System (1977)
Watkins, R., Neal, M.: Why and How of Requirements Tracing. IEEE Software 11, 104–106 (1994)
http://www.engin.umd.umich.edu/CIS/course.des/cis525/js/f00/harvey/FP_Calc.html
SMEF 2005 proceedings, http://realcarbonneau.com/Publications/Carbonneau2005_SoftDevProd_SMEF.pdf
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2009 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Berkling, K., Kiragiannis, G., Zundel, A., Datta, S. (2009). Timeline Prediction Framework for Iterative Software Engineering Projects with Changes. In: Berkling, K., Joseph, M., Meyer, B., Nordio, M. (eds) Software Engineering Approaches for Offshore and Outsourced Development. SEAFOOD 2008. Lecture Notes in Business Information Processing, vol 16. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-01856-5_2
Download citation
DOI: https://doi.org/10.1007/978-3-642-01856-5_2
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-01855-8
Online ISBN: 978-3-642-01856-5
eBook Packages: Computer ScienceComputer Science (R0)