Have a personal or library account? Click to login
A Survey on Identifying and Addressing Business Analysis Problems Cover

A Survey on Identifying and Addressing Business Analysis Problems

Foundations of Computing and Decision Sciences
Volume 42 (2017): Issue 4 (December 2017)
By: Aleksander Jarzębowicz and  Piotr Marciniak  
Open Access
|Dec 2017

References

  1. [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.10.1109/APSEC.2010.16
    Search in Google ScholarBack to article
  2. [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.10.1109/ICCOINS.2014.6868446
    Search in Google ScholarBack to article
  3. [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.
    Search in Google ScholarBack to article
  4. [4] Charette R.N., Why software fails, IEEE Spectrum 42, 9, 2005, 42-49.10.1109/MSPEC.2005.1502528
    Open DOISearch in Google ScholarBack to article
  5. [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.10.1109/FOSE.2007.17
    Search in Google ScholarBack to article
  6. [6] Chrabski B., Zmitrowicz K., Requirements engineering in practice (in Polish: Inżynieria wymagań w praktyce), Wydawnictwo Naukowe PWN, Warsaw, 2015.
    Search in Google ScholarBack to article
  7. [7] Davey B., Parker K., Requirements elicitation problems: a literature analysis, Issues in Informing Science and Information Technology, 12, 2015, 71-82.10.28945/2211
    Search in Google ScholarBack to article
  8. [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.10.5381/jot.2007.6.1.c2
    Search in Google ScholarBack to article
  9. [9] IEEE, A Guide to Software Engineering Body of Knowledge 3.0, 2014.
    Search in Google ScholarBack to article
  10. [10] IEEE Standard 830-1998, IEEE Recommended Practice for Software Requirements Specifications, 1998.
    Search in Google ScholarBack to article
  11. [11] IEEE Standard 1233-1998, IEEE Guide for Developing System Requirements Specifications, 1998.
    Search in Google ScholarBack to article
  12. [12] International Institute of Business Analysis, A Guide to the Business Analysis Body of Knowledge (BABOK Guide) v2.0, 2009.
    Search in Google ScholarBack to article
  13. [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].
    Search in Google ScholarBack to article
  14. [14] International Requirements Engineering Board, IREB CPRE Advanced Level Elicitation and Consolidation syllabus ver. 1.0, 2012.
    Search in Google ScholarBack to article
  15. [15] International Requirements Engineering Board, IREB CPRE Advanced Level Requirements Modeling syllabus ver. 2.2, 2016.
    Search in Google ScholarBack to article
  16. [16] International Requirements Engineering Board, IREB CPRE Foundation Level Syllabus ver. 2.2, 2015.
    Search in Google ScholarBack to article
  17. [17] International Requirements Engineering Board, IREB CPRE Foundation Level syllabus ver. 2.2.2, 2017.
    Search in Google ScholarBack to article
  18. [18] International Requirements Engineering Board, https://www.ireb.org/en/service/statistics [Accessed 12, October, 2017].
    Search in Google ScholarBack to article
  19. [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]
    Search in Google ScholarBack to article
  20. [20] ISO/IEC/IEEE Standard 29148-2011, Systems and Software Engineering - Life Cycle Processes - Requirements Engineering, 2011.
    Search in Google ScholarBack to article
  21. [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.10.1007/s10270-007-0055-y
    Search in Google ScholarBack to article
  22. [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.10.1016/j.infsof.2007.02.008
    Open DOISearch in Google ScholarBack to article
  23. [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.
    Search in Google ScholarBack to article
  24. [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.10.1109/ITSIM.2008.4631895
    Search in Google ScholarBack to article
  25. [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.10.1109/RE.2010.45
    Search in Google ScholarBack to article
  26. [26]Maalem S., Zarour N., Challenge of validation in requirements engineering, Journal of Innovation in Digital Ecosystems, 3, 1, 2016, 15-21.10.1016/j.jides.2016.05.001
    Search in Google ScholarBack to article
  27. [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.
    Search in Google ScholarBack to article
  28. [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.10.1109/MS.2015.122
    Search in Google ScholarBack to article
  29. [29]Project Management Institute, Business Analysis for Practitioners. A Practice Guide, 2015.
    Search in Google ScholarBack to article
  30. [30]Requirements Engineering Qualifications Board, REQB CPRE Advanced Level Requirements Manager ver. 1.0, 2011.
    Search in Google ScholarBack to article
  31. [31]Requirements Engineering Qualifications Board, REQB CPRE Advanced Level Requirements Manager ver. 2.0, 2015.
    Search in Google ScholarBack to article
  32. [32]Requirements Engineering Qualifications Board, REQB CPRE Foundation Level Syllabus ver. 2.1, 2014.
    Search in Google ScholarBack to article
  33. [33]Requirements Engineering Qualifications Board, http://reqb.org/index.php/aboutreqb/facts-and-figures [Accessed 19, May, 2017].
    Search in Google ScholarBack to article
  34. [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.10.1007/978-3-642-31128-4_2
    Search in Google ScholarBack to article
  35. [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.
    Search in Google ScholarBack to article
  36. [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.10.1007/978-3-642-10619-4_9
    Search in Google ScholarBack to article
  37. [37]The Standish Group International, Chaos Report 2014, 2014.
    Search in Google ScholarBack to article
  38. [38]Vestola M., A comparison of nine basic techniques for requirements prioritization, Helsinki University of Technology, Report, 2010.
    Search in Google ScholarBack to article
  39. [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.10.1016/j.procir.2014.03.121
    Search in Google ScholarBack to article
  40. [40]Wiegers K., Beatty J., Software Requirements (3rd Edition), Microsoft Press, 2013.
    Search in Google ScholarBack to article
  41. [41]Yousuf M., Asger M., Comparison of various requirements elicitation techniques, International Journal of Computer Applications, 116, 4, 2015.10.5120/20322-2408
    Search in Google ScholarBack to article
  42. [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.
    Search in Google ScholarBack to article
  43. [43] Żeliński J., Business analysis: organizational modeling in practice (in Polish: Analiza biznesowa: praktyczne modelowanie organizacji), Helion, 2016.
    Search in Google ScholarBack to article
DOI: https://doi.org/10.1515/fcds-2017-0016 | Journal eISSN: 2300-3405 | Journal ISSN: 0867-6356
Journal RSS Feed
Language: English
Page range: 315 - 337
Submitted on: May 31, 2017
Accepted on: Sep 21, 2017
Published on: Dec 9, 2017
Published by: Poznan University of Technology
In partnership with: Paradigm Publishing Services
Publication frequency: 4 issues per year
Keywords:
requirements engineering,
business analysis,
certification schemes,
industrial standards,
survey,
business analysis techniques,
requirements problems
Related subjects:
Computer sciences,
Artificial intelligence,
Software development

© 2017 Aleksander Jarzębowicz, Piotr Marciniak, published by Poznan University of Technology
This work is licensed under the Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 License.

Previous articleVolume 42 (2017): Issue 4 (December 2017)Next article