Vyron Damasiotis
ABSTRACT
Software projects are among the most complex endeavours today. The increased complexity had led to high numbers of software project failures in terms of time, cost quality etc. Software project complexity is one of the main reasons for these failures. Various approaches to measure software complexity have been proposed focusing on the software product complexity but without considering the complexity of the process. In this paper it is presented the results of an extended literature review and of a statistical analysis followed for identifying the main factors that affect software project complexity taking into account both technical and project management aspects of the software development process.
- Da-wei, E. 2007. The software complexity model and metrics for object-oriented, IEEE International Workshop on Anti-counterfeiting, Security, Identification 2007. p. 464--469.Google Scholar
- The Standish Group 2009. CHAOS Summary 2009 The 10 Laws of CHAOS, The Standish Group InternationalGoogle Scholar
- Charette, R.. 2005. Why Software Fails, IEEE SpectrumGoogle Scholar
- Kitchenham, B. 2010. What's up with software metrics? -- A preliminary mapping study. International Journal of Systems and Software. 83, 37--51. Google ScholarDigital Library
- Fitsilis P., Kameas A. and Anthopoulos, L. 2010. Classification of Software Projects' Complexity, Information Systems Development. 2011, 149--159.Google Scholar
- Laird, L. Brennan, M.. 2006. Software Measurement and Estimation. A Practical Approach, John Wiley and Sons. Google ScholarDigital Library
- Damasiotis, V. and Fitsilis, P. 2013. Assessing Software Project Management Complexity: PMCAT tool. New Trends in Networking, Computing, E-learning, Systems Sciences, and Engineering Vol 312 of the series Lecture Notes in Electrical Engineering pp 235--242 Springer International Publishing,Google Scholar
- Baccarini D. 1996. The concept of project complexity -- A review. International Journal of Project Management, 14(4), 201--204.Google ScholarCross Ref
- Xia, W., Lee, G. 2004. Grasping the complexity of IS development projects. Communications of the ACM. 47(5), 69--74. Google ScholarDigital Library
- Maylor, H., Vidgen, R., Carver, S. 2008. Managerial complexity in project based operations: a grounded model and its implications for practice. Project Management Journal. 39, S15--S26.Google ScholarCross Ref
- Sedaghat-Seresht, A., Fazli, S. and Mozaffari, M. M. 2012. Using DEMATEL Method to Modeling Project Complexity Dimensions. Journal of Basic and Applied Scientific Research. 2(11), 11211--11Google Scholar
- Lu, Y., Luo, L., Wang, H., Le, Y. and Shi, Q. 2014. Measurement model of project complexity for large-scale projects from task and organization perspective. International Journal of Project Management 33(3).Google Scholar
- Vidal, L. A., Marle, F., Bocquet, J.C. 2011. Using a Delphi process and the Analytic Hierarchy Process (AHP) to evaluate the complexity of projects. Expert Systems with Applications. 38, 5388--5405. Google ScholarDigital Library
- Bosch-Rekveldt, M., Jongkind, Y., Mooi, H., Bakker, H. and Verbraeck, A. 2011. Grasping project complexity in large engineering projects: The TOE (Technical, Organizational and Environmental) framework. International Journal of Project Management. 29, 728--739.Google ScholarCross Ref
- PMI, 2013. A Guide to the Project Management Body of Knowledge (PMBOK guide) (5th ed.). Project Management Institute, Inc Google ScholarDigital Library
- Fitsilis, P. and Damasiotis, V. 2015. Software Project's Complexity Measurement: A Case Study. Journal of Software Engineering and Applications. 8, 549--556.Google ScholarCross Ref
- Spearman, C. (1904). ""General intelligence", objectively determined and measured." American Journal of Psychology 15: 201--293Google Scholar
- Cronbach, L. J. 1951. Coefficient alpha and the internal structure of tests. Psychometrika, 16, 297--334.Google ScholarCross Ref
- Field, A. 2009. Discovering Statistics using SPSS. (3rd ed.). London. Sage PublishingGoogle Scholar
- Kaiser, H. F. 1970. A second generation little jiffy. Psychometrika, 35, 401--415.Google ScholarCross Ref
- Hutcheson, G. and Sofroniou, N. 1999. The multivariate social scientist. London, Sage Publishing.Google Scholar
- Snedecor, G. W. and Cochran, W. G. 1989. Statistical Methods, (8th Ed), Iowa State University PressGoogle Scholar
- Tabachnick, B. G. and Fidell, L. S. 2001. Using multivariate statistics (4th ed.). Boston: Allyn & Bacon Publication.Google Scholar
- Beavers, A S., Lounsburny, J. W., Richards, J. K., Huck, S.R W., Skolits, G. J. and Esquivel, S.L. 2013. Practical Considerations for Using Exploratory Factor Analysis in Educational Research. Practical Assessment, Research & Evaluation. Volume 18, Number 6,Google Scholar
- Cattell, R. B. 1966. The scree test for the number of factors. Multivariate Behavioral Research, 1, 245--276.Google ScholarCross Ref
- Costelo, A. B. and Osborne, J.W. 2005. Best Practices in Exploratory Factor Analysis: Four Recommendations for Getting the Most from Your Analysis. Practical Assessment, Research & Evaluation. Vol. 10 (7)Google Scholar
- Pallant, J. 2011. SPSS Survival Manual A step by step guide to data analysis using SPSS 4th ed. Allen & Unwin PublicationsGoogle Scholar
Recommendations
Software Engineering Project Standards
Software Engineering Project Standards (SEPS) and their importance are presented in this paper by looking at standards in general, then progressively narrowing the view to software standards, to software engineering standards, and finally to SEPS. After ...
Correlation of critical success factors with success of software projects: an empirical investigation
Software engineering researchers have, over the years, proposed different critical success factors (CSFs) which are believed to be critically correlated with the success of software projects. To conduct an empirical investigation into the correlation of ...
Software development: what it is, what it should be, and how to get there
Developing large software systems is notoriously difficult and unpredictable. Software projects are often canceled, finish late and over budget, or yield low quality results --- setting software engineering apart from established engineering ...
Comments