Annals of Computer Science and Information Systems, Volume 15

DOI: http://dx.doi.org/10.15439/2018F85

Citation: Proceedings of the 2018 Federated Conference on Computer Science and Information Systems, M. Ganzha, L. Maciaszek, M. Paprzycki (eds). ACSIS, Vol. 15, pages 959–968 (2018)

Full text

Abstract. Requirements Engineering and Business Analysis are known as very important to software project outcome but also difficult activities, coping with many problems and challenges. The work reported in this paper was preceded by a survey which revealed most common requirements-related problems in Polish IT industry. We addressed ten most frequently reported problems by reviewing the literature for recommendations how to cope with those problems. The resulting set of recommendations is included in the paper. Next, we conducted interviews with three experienced IT analysts asking them to assess effectiveness of particular recommendations, based on their experience. The results show significant differences in assessments and indicate that effectiveness is dependent on contextual factors to a large extent. Our conclusion is that a follow-up work is required to document more recommenda-tions and to annotate them with guidelines about applicability, intended context of use and possible pitfalls.

References

1. R. N. Charette, “Why Software Fails”, IEEE Spectrum, vol. 42, no. 9, pp. 42–49, 2005, https://doi.org/10.1109/mspec.2005.1502528
2. J. McManus and T. Wood-Harper, “Understanding the Sources of Information Systems Project Failure - A study in IS project failure”, Manag. Serv., vol. 51, no. 3, pp. 38–43, 2007.
3. D. Mendez Fernández et al., “Naming the pain in requirements engineering: Contemporary problems, causes, and effects in practice”, Empir. Softw. Eng., vol. 22, no. 5, pp. 2298–2338, 2017, https://doi.org/10.1007/s10664-016-9451-7
4. B. H. C. Cheng and J. M. Atlee, “Research Directions in Requirements Engineering”, Proceeding FOSE ’07 2007 Futur. Softw. Eng., pp. 285–303, 2007.https://doi.org/10.1109/fose.2007.17
5. A. Przybyłek, “A Business-oriented Approach to Requirements Elicitation”, in 9th International Conference on Evaluation of Novel Approaches to Software Engineering (ENASE’14), Lisbon, Portugal, pp. 152-163, 2014. https://doi.org/10.5220/0004887701520163
6. A. Przybyłek and M. Zakrzewski, “Adopting Collaborative Games into Agile Requirements Engineering”, in 13th International Conference on Evaluation of Novel Approaches to Software Engineering (ENASE’18), Funchal, Madeira, Portugal, 2018.
7. T. Hall, S. Beecham and A. Rainer, “Requirements problems in twelve software companies: an empirical analysis”, IEE Proc. - Softw., vol. 149, no. 5, p. 153, 2002, https://doi.org/10.1049/ip-sen:20020694.
8. N. K. Sethia and A. S. Pillai, “A study on the software requirements elicitation issues - its causes and effects”, 2013 Third World Congr. Inf. Commun. Technol. (WICT 2013), pp. 245–252, 2013, https://doi.org/10.1109/wict.2013.7113143
9. D. Mendez Fernandez et al., “Naming the Pain in Requirements Engineering: Comparing Practices in Brazil and Germany”, IEEE Softw., vol. 32, no. 5, pp. 16–23, 2015, https://doi.org/10.1109/ms.2015.122
10. D. Firesmith, “Common requirements problems, their negative consequences, and the industry best practices to help solve them”, J. Object Technol., vol. 6, no. 1, pp. 17–33, 2007, https://doi.org/10.5381/jot.2007.6.1.c2
11. B. Davey and K. Parker, “Requirements elicitation problems: a literature analysis”, Issues Informing Sci. Inf. Technol., vol. 12, pp. 71–82, 2015, https://doi.org/10.28945/2137
12. A. Jarzębowicz and W. Ślesiński, “What is Troubling IT Analysts? A Survey Report from Poland on Requirements-related Problems”, in XX KKIO Software Engineering Conference, Springer AISC series (in print), 2018.
13. K. el Emam and N. H. Madhavji, “A field study of requirements engineering practices in information systems development”, Int. Conf. Requir. Eng., pp. 68–80, 1995, https://doi.org/10.1109/isre.1995.512547
14. E. Bjarnason, K. Wnuk, and B. Regnell, “A case study on benefits and side-effects of agile practices in large-scale requirements engineering”, Proc. 1st Work. Agil. Requir. Eng. - AREW ’11, pp. 1–5, 2011, https://doi.org/10.1145/2068783.2068786
15. F. G. De Oliveira Neto, J. Horkoff, E. Knauss, R. Kasauli, and G. Liebel, “Challenges of aligning requirements engineering and system testing in large-scale agile: A multiple case study” Proc. 2017 IEEE 25th Int. Requir. Eng. Conf. Work. REW 2017, p,p. 315–322, 2017, https://doi.org/10.1109/rew.2017.33
16. W. Alsaqaf, M. Daneva, and R. Wieringa, “Quality requirements challenges in the context of large- scale distributed Agile : An thempirical study”, in Proc. of 24 Requirements Engineering: Foundation for Software Quality Conference, pp. 139-154, 2018, https://doi.org/10.1007/978-3-319-77243-1_9
17. A. M. Hickey and A. M. Davis, “Elicitation technique selection: How do experts do it?”, in Proceedings of the IEEE International Conference on Requirements Engineering, 2003, pp. 169–178. https://doi.org/10.1109/icre.2003.1232748
18. L. Cao and B. Ramesh, “Agile requirements engineering practices: An empirical study”, IEEE Softw., vol. 25, no. 1, pp. 60–67, 2008, https://doi.org/10.1109/ms.2008.1
19. D. Paul and L. Y. Tan, “An Investigation Of The Role Of Business Analyst In IS Development”, ECIS 2015 Proc., pp. 1–14, 2015.
20. K. Wiegers and J. Beatty, “Software Requirements”, 3rd ed. Microsoft Press, 2013, ISBN: 978-0735679665.
21. D. Leffingwell and D. Widrig, Managing Software Requirements, Pearson Education, 2003, ISBN:032112247X
22. B. Chrabski and K. Zmitrowicz, Requirements Engineering in Practice (in Polish: Inżynieria Wymagań w Praktyce), Wydawnictwo Naukowe PWN, 2015, ISBN: 9788301180188
23. M. Bartyzel, Tailored software - how to speak to customers who don’t know what they want (in Polish: Oprogramowanie szyte na miarę. Jak rozmawiać z klientem, który nie wie, czego chce). Wydawnictwo Helion, 2012, ISBN: 978-83-246-3932-8
24. E. Bernroider and M. Ivanov, “IT project management control and the Control Objectives for IT and related Technology (CobiT) framework”, Int. J. Proj. Manag., vol. 29 no. 3, pp. 325-336, 2011, https://doi.org/10.1016/j.ijproman.2010.03.002
25. J. Cleland-Huang, R. S. Hanmer, S. Supakkul, and M. Mirakhorli, “The Twin Peaks of Requirements and Architecture”, IEEE Softw., vol. 30, no. 2, pp.24-29, 2013, https://doi.org/10.1109/MS.2013.39
26. E. Bjarnason et al., “Challenges and practices in aligning requirements with verification and validation: a case study of six companies”, Empir. Softw. Eng., vol. 19, no. 6, pp. 1809-1855, 2014, https://doi.org/10.1007/s10664-013-9263-y