Skip to main content

Development Method of Innovative Projects in Higher Education Based on Traditional Software Building Process

  • Chapter
  • First Online:
  • 698 Accesses

Part of the book series: Lecture Notes on Data Engineering and Communications Technologies ((LNDECT,volume 40))

Abstract

Numerous attempts were taken to define criteria against which to evaluate and measure software project success. The complexity that surrounds it has been recognized by companies, however the scholarly world is yet to follow. In this article, three dimensions of success have been elicited basing on prior industrial studies: project quality, project efficiency as well as social factors (teamwork quality and learning outcomes). Investigation of their assessment in a commercial context enabled the authors to determine and adapt a set of metrics and measures that constitute a structured evaluation scheme for projects developed by student groups. The proposed assessment approach can be applied by researchers appraising applicability of software development processes in an academic setting or carrying out comparative studies of different methodologies. Furthermore, professionalizing appraisal of student project outcomes can contribute to closing a gap between workforce’s expectations towards new graduates and the effects of their university education.

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

Buying options

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

Learn about institutional subscriptions

References

  1. Pierson G (1983) C. Undergraduate studies: Yale college, Yale book of numbers. Historical statistics of the college and university. New Haven, Yale Office of Institutional Research, pp 1701–1976

    Google Scholar 

  2. Postman N (1992) Technopoly the surrender of culture to technology. Alfred A. Knopf, New York

    Google Scholar 

  3. Kupiainen E, Mantylaa M, Itkonen J (2015) Using metrics in agile and lean software development—A systematic literature review of industrial studies

    Google Scholar 

  4. Unterkalmsteiner M, Gorschek T, Moinul Islam, AKM (2011) Evaluation and measurement of software process improvement—a systematic literature review

    Google Scholar 

  5. Dalcherand D, Benediktsson O, Thorbergsson H (2005) Development life cycle management: a multiproject experiment

    Google Scholar 

  6. Metrics in Agile Project Courses. In: 2016 IEEE/ACM 38th IEEE international conference on software engineering Companion

    Google Scholar 

  7. Mkiaho P, Poranen T, Seppi A (2015) Software metrics in students’ software development projects. In: Proceedings of international conference on computer systems and technologies (CompSysTech’15)

    Google Scholar 

  8. Atkinson R (1999) Project management: cost, time and quality, two best guesses and a phenomenon, its time to accept other success criteria. Int J Proj Manag 17(6):337–342

    Article  Google Scholar 

  9. Cooke-Davies T (2002) The real success factors on projects. Int J Proj Manag 20(3):185–190

    Article  Google Scholar 

  10. Ika L (2009) Project success as a topic in project management journals. Proj Manag J 40(4):6–19

    Article  Google Scholar 

  11. Jugdev K, Müller R (2005) A retrospective look at our evolving under-standing of project success. Proj Manag J 36(4):19–31

    Article  Google Scholar 

  12. Baccarini D (1999) The logical framework method for defining project success. Proj Manag J 30(4):25–32

    Article  Google Scholar 

  13. Bannerman P (2008) Defining project success: a multilevel frame-work. In: Proceedings of PMI research conference

    Google Scholar 

  14. Markus M, Mao J (2004) Participation in development and implementation—updating an old, tired concept for today’s IS contexts. J Assoc Inf Syst 5:514–544

    Google Scholar 

  15. Shenhar A, Dvir D (2007) Project management research—the challenge and opportunity. Proj Manag J 38(2):93–99

    Article  Google Scholar 

  16. McLeod L, Doolin B, MacDonel B (2012) A perspective-based understanding of project success. Proj Manag J 43(5):68–86

    Article  Google Scholar 

  17. Ralph P, Kelly P (2014) The dimensions of software engineering success

    Google Scholar 

  18. Buse R, Zimmermann T (2012) Information needs for software development analytics. In: Proceedings of 20th international conference on software engineering. IEEE Press, pp. 987–996

    Google Scholar 

  19. ISO/IEC25010 (2011) Systems and software engineering

    Google Scholar 

  20. Kitchenham B, Pfleeger S (1996) Software quality: the elusive target. IEEE software

    Google Scholar 

  21. Naboulsi Z (2017) Code metrics—cyclomatic complexit. MSDN ultimate visual studio tips and tricks blog. https://blogs.msdn.microsoft.com/zainnab/2011/05/17/code-metrics-cyclomatic-complexity

  22. McCabe Associates (1999) Integrated quality as part of CS699 professional seminar in computer science

    Google Scholar 

  23. Rosenberg L, Hammer T (1998) Software metrics and reliability. NASA GSFC

    Google Scholar 

  24. Rosenberg L, Hammer T (1998) Metrics for quality assurance and risk assessment. In: Proceedings of 11th international software quality week, USA

    Google Scholar 

  25. Brechner E (2003) Things they would not teach me of in college: what microsoft developers learn later. In: ACM SIGPLAN conference on object-oriented programming, systems, languages, and applications

    Google Scholar 

  26. Exter M, Turnage N (2012) Exploring experienced professionals’ reflections on computing education. ACM Trans Comput Educ (TOCE) 12(3)

    Article  Google Scholar 

  27. Bijlsma D, Ferreira M, Luijten B, Visser J (2012) Faster issue resolution with higher technical quality of software. Softw Qual J 20(2):265–285

    Article  Google Scholar 

  28. Baggen R, Correia J, Schill K, Visser J (2012) Standardized code quality benchmarking for improving software maintainability. Softw Qual J 20(2):287–307

    Article  Google Scholar 

  29. Correia J, Kanellopoulos Y, Visser J (2010) A survey-based study of the mapping of system properties to ISO/IEC 9126 maintainability characteristics. In: Proceedings of 25th IEEE international conference on software maintenance (ICSM), pp 61–70, 2009. Relation to software maintainability, Master thesis, University of Amsterdam

    Google Scholar 

  30. Visser J (2016) Building maintainable software: ten guidelines for future-proof code. OReilly Media, Inc

    Google Scholar 

  31. Booch G (1991) Object oriented design: with applications

    Google Scholar 

  32. Bruegge B, Krusche S, Alperowitz L (2015) Software engineering project courses with industrial clients

    Article  Google Scholar 

  33. Olszewska M, Heidenberg J, Weijola M (2016) Quantitatively measuring a large-scale agile transformation. J Syst Softw

    Google Scholar 

  34. Palacin-Silva M, Khakurel J, Happonen A (2017) Infusing design thinking into a software engineering capstone course. In: Proceedings of 30th IEEE conference on software engineering education and training (CSEE&T)

    Google Scholar 

  35. Unterkalmsteiner M, Gorschek T (2012) Evaluation and measurement of software process improvement—a systematic literature review. IEEE Trans Softw Eng

    Google Scholar 

  36. Ilieva S, Ivanov P, Stefanova E (2004) Analyses of an agile methodology implementation. In: Proceedings of 30th EUROMICRO conference

    Google Scholar 

  37. Albrecht A (1979) Measuring application development productivity. In: Proceedings of joint SHARE, GUIDE, and IBM application development symposium, pp 83–92

    Google Scholar 

  38. Ochodek M, Nawrocki J (2011) Simplifying effort estimation based on use case points. Inf Softw Technol

    Google Scholar 

  39. Abrahamsson P (2003) Extreme programming: first results from a controlled case study. In: Proceedings of 29th EUROMICRO conference

    Google Scholar 

  40. Middleton P, Taylor P (2007) Lean principles and techniques for improving the quality and productivity of software development projects: a case study. Int J Prod Qual Manag

    Google Scholar 

  41. Hoegl M, Gemuenden H (2001) Teamwork quality and the success of innovative projects: a theoretical concept and empirical evidence. Organ Sci 12

    Article  Google Scholar 

  42. G. Melnik and F. Maurer, “A Cross-Program Investigation of Students Perceptions of Agile Methods”, International Conference on Software Engineering, 2005

    Google Scholar 

  43. Clark C (2005) Evaluating student teams developing unique industry projects. In: Proceedings of 7th australasian conference on computer education

    Google Scholar 

  44. Casey-Campbell M, Martens M (2008) Sticking it all together: a critical assessment of the group cohesion-performance literature

    Google Scholar 

  45. Carron A, Brawley L (2000) Cohesion: conceptual and measurement issues. Small Group Res 31

    Article  Google Scholar 

  46. Salas E, Grossman R (2015) Measuring team cohesion: observations from the science. Hum Factors 57

    Article  Google Scholar 

  47. Sommerville I (2004) Software engineering. Addison-Wesley

    Google Scholar 

  48. Carron A, Brawley L (2002) G.E.Q. the group environment questionnaire test manual. Fit Inf Technol 1135, Inc

    Google Scholar 

  49. Wellington C, Briggs T (2015) Comparison of student experiences with plan-driven and agile methodologies. In: 35th ASEE/IEEE frontiers in education conference

    Google Scholar 

  50. van Boxmeer F, Verwijs C (2007) A direct measure of morale in the 1140 Netherlands armed forces morale survey: theoretical puzzle, empirical testing and validation. In: Proceedings of international military testing association symposium (IMTA)

    Google Scholar 

  51. van Boxmeer F, Verwijs C, Euwema M (2011) Assessing soldier’s morale in a challenging environment

    Google Scholar 

  52. Verwijs C (2018) Agile teams: don’t use happiness metrics, measure team morale

    Google Scholar 

  53. Begel A, Simon B (2008) Struggles of new college graduates in their first software development job. In: Proceedings of 39th SIGCSE technical symposium on computer science education

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Aneta Poniszewska-Marańda .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2020 Springer Nature Switzerland AG

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Włodarski, R., Poniszewska-Marańda, A. (2020). Development Method of Innovative Projects in Higher Education Based on Traditional Software Building Process. In: Poniszewska-Marańda, A., Kryvinska, N., Jarząbek, S., Madeyski, L. (eds) Data-Centric Business and Applications. Lecture Notes on Data Engineering and Communications Technologies, vol 40. Springer, Cham. https://doi.org/10.1007/978-3-030-34706-2_12

Download citation

Publish with us

Policies and ethics