A survey on identifying and addressing business analysis problems

• Autorzy: Jarzębowicz A. , Marciniak P.

Identyfikatory

DOI

10.1515/fcds-2017-0016

• Języki publikacji: EN

Abstrakty

EN

Despite the growing body of knowledge on requirements engineering and business analysis, these areas of software project are still considered problematic. The paper focuses on problems reported by business analysts and on applicability of available business analysis techniques as solutions to such problems. A unified set of techniques was developed on the basis of 3 industrial standards associated with IIBA, REQB and IREB certification schemes. A group of 8 business analysts was surveyed to list problems they encounter in their work and to assess their frequency. Selected problems were further analyzed and most suitable techniques were proposed to address them. These proposals were validated through follow-up discussions with business analysts. The main results of research reported in this paper are: the comparative analysis of techniques included in IIBA, REQB and IREB standards and the list of problems reported by practitioners associated with techniques suggested as effective solutions.

Słowa kluczowe

EN

requirements engineering; business analysis; industrial standards; survey; business analysis techniques; requirements problems; certification scheme

• Wydawca: Wydawnictwo Politechniki Poznańskiej
• Czasopismo: Foundations of Computing and Decision Sciences
• Rocznik: 2017
• Tom: Vol. 42, No. 4
• Strony: 315--337
• Opis fizyczny: Bibliogr. 43 poz., fig., tab.

Twórcy

autor

Jarzębowicz A.

• Department of Software Engineering, Faculty of Electronics, Telecommunications and Informatics, Gdańsk University of Technology, Gdańsk, Poland

autor

Marciniak P.

• Active Code Piotr Marciniak, Gdańsk, Poland

Bibliografia

• [1] Aoyama M., Nakatani T., Saito S., Suzuki M., Fujita K., Nakazaki H., Suzuki R., A model and architecture of REBOK (Requirements Engineering Body of Knowledge) and its evaluation, Proc. of 17th Asia Pacific Software Engineering Conference, IEEE, 2010, 50-59.
• [2] Besrour S., Bin Ab Rahim L., Dominic P., Assessment and evaluation of requirements elicitation techniques using analysis determination requirements framework, In: Proc. of 2014 International Conference on Computer and Information Sciences, 2014, 1-6.
• [3] Bobkowska A., Wyrzykowski K., A model for the activities of business analysts in public administration for the prevention of hidden requirements (in Polish: Model działania analityka biznesowego w administracji publicznej w celu przeciwdziałania ukrytym wymaganiom), Roczniki Kolegium Analiz Ekonomicznych/Szkoła Główna Handlowa, 42, 2016, 13-26.
• [4] Charette R.N., Why software fails, IEEE Spectrum 42, 9, 2005, 42-49.
• [5] Cheng B., Atlee J., Research directions in requirements engineering, In: Proc. of Future of Software Engineering (FOSE 2007), IEEE Computer Society, Washington DC, 2007, 285-303.
• [6] Chrabski B., Zmitrowicz K., Requirements engineering in practice (in Polish: Inżynieria wymagań w praktyce), Wydawnictwo Naukowe PWN, Warsaw, 2015.
• [7] Davey B., Parker K., Requirements elicitation problems: a literature analysis, Issues in Informing Science and Information Technology, 12, 2015, 71-82.
• [8] Firesmith D., Common requirements problems, their negative consequences and the industry best practices to help solve them, Journal of Object Technology, 6, 1, 2007, 17-33.
• [9] IEEE, A Guide to Software Engineering Body of Knowledge 3.0, 2014.
• [10] IEEE Standard 830-1998, IEEE Recommended Practice for Software Requirements Specifications, 1998.
• [11] IEEE Standard 1233-1998, IEEE Guide for Developing System Requirements Specifications, 1998.
• [12] International Institute of Business Analysis, A Guide to the Business Analysis Body of Knowledge (BABOK Guide) v2.0, 2009.
• [13] International Institute of Business Analysis, IIBA Annual Report 2015, available: http://www.iiba.org/About-IIBA/About-IIBA/iiba-annual-report-2015.aspx [Accessed 12, October, 2017].
• [14] International Requirements Engineering Board, IREB CPRE Advanced Level Elicitation and Consolidation syllabus ver. 1.0, 2012.
• [15] International Requirements Engineering Board, IREB CPRE Advanced Level Requirements Modeling syllabus ver. 2.2, 2016.
• [16] International Requirements Engineering Board, IREB CPRE Foundation Level Syllabus ver. 2.2, 2015.
• [17] International Requirements Engineering Board, IREB CPRE Foundation Level syllabus ver. 2.2.2, 2017.
• [18] International Requirements Engineering Board, https://www.ireb.org/en/service/statistics [Accessed 12, October, 2017].
• [19] International Requirements Engineering Board, IREB® and REQB® have decided to join forces, https://www.ireb.org/en/service/news-events/ (2017/01/18 news) [Accessed 12, October, 2017].
• [20] ISO/IEC/IEEE Standard 29148-2011, Systems and Software Engineering - Life Cycle Processes - Requirements Engineering, 2011.
• [21] Jiang L., Eberlein A., Far B., Mousavi M., A methodology for the selection of requirements engineering techniques, Software & Systems Modeling, 7, 3, 2008, 303-328.
• [22] Karlsson L., Dahlstedt Å.G., Regnell B., och Dag J.N., Persson A., Requirements engineering challenges in market-driven software development - an interview study with practitioners, Information and Software Technology, 49, 6, 2007, 588-604.
• [23] Khan H., Asghar I., Ghayyur S., Raza M., An empirical study of software requirements verification and validation techniques along their mitigation strategies, Asian Journal of Computer and Information Systems, 3, 03, 2015.
• [24] Kheirkhah E., Deraman A., Important factors in selecting requirements engineering techniques, In: Proc. of International Symposium on Information Technology (ITSim 2008), 2008, 1-5.
• [25] Liu L., Li T., Peng F., Why requirements engineering fails: A survey report from China, In: Proc. of 18th Requirements Engineering Conference (RE), 2010, 317-322.
• [26] Maalem S., Zarour N., Challenge of validation in requirements engineering, Journal of Innovation in Digital Ecosystems, 3, 1, 2016, 15-21.
• [27] Marciniak P., Jarzębowicz A., An industrial survey on business analysis problems and solutions, In: Madeyski L., Śmiałek M., Hnatkowska B., Huzar Z. (eds) Software Engineering: Challenges and Solutions, Advances in Intelligent Systems and Computing, vol 504. Springer International Publishing, 2016, 163-176.
• [28] Mendez Fernandez D., Wagner S., Kalinowski M., Schekelmann A., Tuzcu A., Conte T., Spinola R., Prikladnicki R., Naming the Pain in Requirements Engineering: Comparing Practices in Brazil and Germany, IEEE Software 32, 5, 2015, 16-23.
• [29] Project Management Institute, Business Analysis for Practitioners. A Practice Guide, 2015.
• [30] Requirements Engineering Qualifications Board, REQB CPRE Advanced Level Requirements Manager ver. 1.0, 2011.
• [31] Requirements Engineering Qualifications Board, REQB CPRE Advanced Level Requirements Manager ver. 2.0, 2015.
• [32] Requirements Engineering Qualifications Board, REQB CPRE Foundation Level Syllabus ver. 2.1, 2014.
• [33] Requirements Engineering Qualifications Board, http://reqb.org/index.php/aboutreqb/facts-and-figures [Accessed 19, May, 2017].
• [34] dos Santos Soares M., Cioquetta D., Analysis of techniques for documenting user requirements, In: Proc. of Computational Science and Its Applications (ICCSA 2012), 2012, 16-28.
• [35] Sethia N.K., Pillai A.S., A study on the software requirements elicitation issues - its causes and effects, In: Proc. of World Congress on Information and Communication Technologies, 2013, 245-252.
• [36] Solemon B., Sahibuddin S., Ghani A., Requirements engineering problems and practices in software companies: an industrial survey, In: Ślęzak D., Kim T.H., Kiumi A., Jiang T., Verner J., Abrahão S. (eds.) Advances in Software Engineering, Communications in Computer and Information Science Vol. 59, Springer Heidelberg, 2009, 70-77.
• [37] The Standish Group International, Chaos Report 2014, 2014.
• [38] Vestola M., A comparison of nine basic techniques for requirements prioritization, Helsinki University of Technology, Report, 2010.
• [39] Wellsandt S., Hribernik K., Thoben K., Qualitative comparison of requirements elicitation techniques that are used to collect feedback information about product use, In: Proc. of 24th CIRP Design Conference, 2014, 212-217.
• [40] Wiegers K., Beatty J., Software Requirements (3rd Edition), Microsoft Press, 2013.
• [41] Yousuf M., Asger M., Comparison of various requirements elicitation techniques, International Journal of Computer Applications, 116, 4, 2015.
• [42] Zhang Z., Effective requirements development - a comparison of requirements elicitation techniques. In: Software Quality Management XV: Software Quality in the Knowledge Society, British Computer Society, 2007, 225-240.
• [43] Żeliński J., Business analysis: organizational modeling in practice (in Polish: Analiza biznesowa: praktyczne modelowanie organizacji), Helion, 2016.

Uwagi

Opracowanie ze środków MNiSW w ramach umowy 812/P-DUN/2016 na działalność upowszechniającą naukę (zadania 2017).