Skip to main content

What Is Troubling IT Analysts? A Survey Report from Poland on Requirements-Related Problems

  • Conference paper
  • First Online:
Engineering Software Systems: Research and Praxis (KKIO 2018)

Part of the book series: Advances in Intelligent Systems and Computing ((AISC,volume 830))

Included in the following conference series:

Abstract

Requirements engineering and business analysis are activities considered to be important to software project success but also difficult and challenging. This paper reports on a survey conducted in Polish IT industry, aimed at identifying most widespread problems/challenges related to requirements. The survey was targeted at people performing role of analyst in commercial IT projects. The questionnaire included 64 pre-defined problems gathered from a literature review and a workshop involving a small group of analysts. It was completed by 55 respondents, each of whom assessed the frequency of occurrence for pre-defined problems and optionally could report additional problems based on their work experience. A ranking of most frequent problems is presented in this paper. Additional analyses for more specific contexts: agile projects and smaller/larger development teams are also provided. Final sections of the paper include comparison of our results and results of reported surveys conducted in other countries, followed by a discussion.

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 129.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 169.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. International Organization for Standardization (ISO): ISO/IEC/IEEE 29148: Systems and Software Engineering—Life Cycle Processes—Requirements Engineering. International Organization for Standardization (ISO), Geneva (2011)

    Google Scholar 

  2. International Institute of Business Analysis: A guide to the business analysis body of knowledge (BABOK) 3.0 (2015)

    Google Scholar 

  3. The Standish Group: Chaos report (2014)

    Google Scholar 

  4. Arras People: Project management benchmark report (2010)

    Google Scholar 

  5. McManus, J., Wood-Harper, T.: Understanding the sources of information systems project failure—a study in IS project failure. Manag. Serv. 51, 38–43 (2007)

    Google Scholar 

  6. Charette, R.N.: Why software fails. IEEE Spectr. 42, 42–49 (2005)

    Article  Google Scholar 

  7. Hofmann, H.F., Lehner, F.: Requirements engineering as a success factor in software projects. IEEE Softw. 18, 58–66 (2001)

    Article  Google Scholar 

  8. Damian, D., Chisan, J.: An empirical study of the complex relationships between requirements engineering processes and other processes that lead to payoffs in productivity, quality, and risk management. IEEE Trans. Softw. Eng. 32, 433–453 (2006)

    Article  Google Scholar 

  9. Ellis, K., Berry, D.M.: Quantifying the impact of requirements definition and management process maturity on project outcome in large business application development. Requir. Eng. 18, 223–249 (2013)

    Article  Google Scholar 

  10. Hall, T., Beecham, S., Rainer, A.: Requirements problems in twelve software companies: an empirical analysis. IEE Proc. Softw. 149, 153–160 (2002)

    Article  Google Scholar 

  11. Solemon, B., Sahibuddin, S., Ghani, A.: Requirements engineering problems and practices in software companies: an industrial survey. In: Communications in Computer and Information Science, CCIS, vol. 59, pp. 70–77 (2009)

    Google Scholar 

  12. Liu, L., Li, T., Peng, F.: Why requirements engineering fails: a survey report from China. In: Proceedings of the 18th International Requirements Engineering Conference RE 2010, pp. 317–322 (2010)

    Google Scholar 

  13. Mendez Fernández, D.: Naming the pain in requirements engineering: contemporary problems, causes, and effects in practice. Empir. Softw. Eng. 22, 2298–2338 (2017). https://doi.org/10.1007/s10664-016-9451-7

    Article  Google Scholar 

  14. Mendez Fernandez, D.: Supporting requirements-engineering research that industry needs: the NaPiRE initiative. IEEE Softw. 35, 112–116 (2018)

    Article  Google Scholar 

  15. Frączkowski, K., Dabiński, A., Grzesiek, M.: Raport z Polskiego Badania Projektów IT 2010 (2011). http://pmresearch.pl/wp-content/downloads/raport_pmresearchpl.pdf

  16. Pieszczyk, E., Werewka, J.: Analysis of the reasons for software quality problems based on survey of persons involved in the process of developing of IT systems. Bus. Inf. 3(37), 85–102 (2015)

    Google Scholar 

  17. Przybyłek, A.: A business-oriented approach to requirements elicitation. In: Proceedings of the 9th International Conference on ENASE 2014, pp. 152–163 (2014)

    Google Scholar 

  18. Kopczyńska, S., Nawrocki, J.: Using non-functional requirements templates for elicitation: a case study. In: Proceedings of the 2014 IEEE 4th International Work Required Patterns, RePa 2014, pp. 47–54 (2014)

    Google Scholar 

  19. Marciniak, P., Jarzębowicz, A.: An industrial survey on business analysis problems and solutions. In: Software Engineering: Challenges and Solutions, AISC, vol. 504, pp. 163–176. Springer (2016)

    Google Scholar 

  20. Jarzębowicz, A., Marciniak, P.: A survey on identifying and addressing business analysis problems. Found. Comput. Decis. Sci. 42, 315–337 (2017)

    Article  Google Scholar 

  21. Davey, B., Parker, K.R.: Requirements elicitation problems: a literature analysis. Issues Inf. Sci. Inf. Technol. 12, 71–82 (2015)

    Google Scholar 

  22. Firesmith, D.: Common requirements problems, their negative consequences, and the industry best practices to help solve them. J. Object Technol. 6, 17–33 (2007)

    Article  Google Scholar 

  23. Leffingwell, D., Widrig, D.: Managing Software Requirements. Addison-Wesley, Boston (2003)

    Google Scholar 

  24. Wiegers, K., Beatty, J.: Software Requirements. Microsoft Press, Redmond (2013)

    Google Scholar 

  25. Chrabski, B., Zmitrowicz, K.: Requirements Engineering in Practice (in Polish: Inżynieria Wymagań w Praktyce). Naukowe PWN, Wyd (2015)

    Google Scholar 

  26. Rational Software Corporation: Using rational RequisitePro ® (2000)

    Google Scholar 

  27. Blueprint: The rework tax: reducing software development rework by improving requirements (2015)

    Google Scholar 

  28. Jarzębowicz, A., Ślesiński, W.: Survey dataset. https://www.researchgate.net/publication/324910141_RE_problems_in_Poland_-_survey_dataset

Download references

Acknowledgements

We would like to thank all workshop participants and survey respondents who shared with us with their knowledge and experience. Particular thanks are due to Hanna Tomaszewska from Analizait.pl for disseminating invitations to participate in the survey and to Agnieszka Landowska from Gdańsk University of Technology for advice on data analysis. We are also grateful to anonymous reviewers for their helpful suggestions.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Aleksander Jarzębowicz .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2019 Springer Nature Switzerland AG

About this paper

Check for updates. Verify currency and authenticity via CrossMark

Cite this paper

Jarzębowicz, A., Ślesiński, W. (2019). What Is Troubling IT Analysts? A Survey Report from Poland on Requirements-Related Problems. In: Kosiuczenko, P., Zieliński, Z. (eds) Engineering Software Systems: Research and Praxis. KKIO 2018. Advances in Intelligent Systems and Computing, vol 830. Springer, Cham. https://doi.org/10.1007/978-3-319-99617-2_1

Download citation

Publish with us

Policies and ethics