Analiza przyczyn problemów jakości oprogramowania na podstawie ankiet osób uczestniczących w procesie wytwarzania systemów informatycznych

• Authors: Pieszczyk Edyta , Werewka Jan

Title variants

EN

Analysis of the reasons for software quality problems based on survey of persons involved in the process of developing of IT systems

• Languages of publication: PL EN

Abstracts

EN

The level of failure of IT projects is high and has not changed over many years despite improvement in software development processes. One of the obvious reasons for this is shortening the delivery time of information systems in the projects and rapidly changing technology. Quality assurance in software development process is a key issue in ensuring the proper operation of an IT system. In order to know the causes of the problems, it is important to know viewpoints of members of the teams developing software. These views were obtained by carrying out the survey. At the beginning categories of reasons are identified using Ishikawa diagram, a tool for quality management. In the next step an analysis was performed using the Pareto principle. The analysis allowed the identification of the most important causes of errors in the software development process. A detailed analysis of the observed results and appropriate conclusions of this analysis will help improve the processes of software development and collaboration between project management and software development processes.

Keywords

EN

project mangement; software development; software quality; cause and effect diagram; Pareto

• Publisher: Wydawnictwo Uniwersytetu Ekonomicznego we Wrocławiu
• Journal: Informatyka Ekonomiczna
• Year: 2015
• Issue: 3(37)
• Pages: 85-102

Contributors

author

Pieszczyk Edyta

author

Werewka Jan

References

• Amber Team, 2015, Zarządzanie testami – AmberPlace, Retrieved February 11, 2016, from http://amberplace.amberteam.pl/Zarz%C4%85dzanie_testami (11.02.2016).
• Diagram Pareto, 2015, http://www.governica.com/Diagram_Pareto (11.02.2016).
• Dlaczego oprogramowanie zawiera defekty?, 2014, http://www.testowanie.net/testowanie/dlaczego-oprogramowanie-zawiera-defekty/ (1.010.2014).
• Eveleens J.L., Verhoef C., 2010, The rise and fall of the Chaos report figures, IEEE Software, 27(1), 30-36, http://doi.org/10.1109/MS.2009.154.
• Hamrol A., 2005, Zarządzanie jakością z przykładami, Warszawa, Wydawnictwo Naukowe PWN.
• Hamrol A., Mantura W., 2012, Zarządzanie jakością: teoria i praktyka, Wydawnictwo Naukowe PWN, Warszawa.
• Holvitie J., Leppanen V., Hyrynsalmi S., 2014, Technical Debt and the Effect of Agile Software Development Practices on It − An Industry Practitioner Survey, Sixth International Workshop on Managing Technical Debt (MTD), s. 35-42, http://doi.org/10.1109/MTD.2014.8.
• Ishikawa K., 1986, Guide to Quality Control, 2nd edition, Quality Resources.
• Jayathilake D., Yaggahavita H., Senanayake U., Elvitigala C., Sriyananda D., 2011, A scalable product quality verifier framework for a outsourcing supplier, 2011 IEEE International Conference on Computer Applications and Industrial Electronics (ICCAIE), s. 390-395, http://doi.org/10.1109/ICCAIE.2011.6162166.
• Kumar S.A., Thangavelu A.K., 2013, Factors affecting the outcome of global software development projects: An empirical study, 2013 International Conference on Computer Communication and Informatics (ICCCI), s. 1-10, http://doi.org/10.1109/ICCCI.2013.6466113.
• Lavallée M., Robillard P.N., 2012, The impacts of software process improvement on developers: A systematic review, 2012 34th International Conference on Software Engineering (ICSE), s. 113-122, http://doi.org/10.1109/ICSE.2012.6227201.
• Mach P., Guaqueta J., 2001, Utilization of the seven Ishikawa tools (old tools) in the six sigma strategy, 24th International Spring Seminar on Electronics Technology: Concurrent Engineering in Electronic Packaging, s. 51-55, http://doi.org/10.1109/ISSE.2001.931009.
• Oyetoyan T.D., Conradi R., Cruzes D.S., 2013, A Comparison of Different Defect Measures to Identify Defect-Prone Components, 2013 Joint Conference of the 23rd International Workshop on Software Measurement and the 2013 Eighth International Conference on Software Process and Product Measurement (IWSM-MENSURA), s. 181-190, http://doi.org/10.1109/IWSM-Mensura.2013.34.
• Port D., Kazman R., Nakao H., Katahira M., 2007, Practicing What is Preached: 80-20 Rules for Strategic IV&V Assessment, IEEE International Conference on Exploring Quantifiable IT Yields, 2007. EQUITY ’07, s. 45-54, http://doi.org/10.1109/EQUITY.2007.13.
• The Standish Group, 2013, CHAOS Manifesto 2013, Think Big, Act Small, www.standishgroup.com.
• The Standish Group, 2014, CHAOS, 2014, The Standish Group Report, Project Smart, www.standishgroup.com.
• Tholons, 2015, 2015 Top 100 Outsourcing Destinations, www.THOLONS.com.
• Tholons_Whitepaper_December_2014.pdf. (n.d.), http://www.tholons.com/nl_pdf/Tholons_Whitepaper_December_2014.pdf (11.02.2016).
• Vilfredo Pareto, Wikipedia, wolna encyklopedia, https://pl.wikipedia.org/w/index.php?title=Vilfredo_Pareto&oldid=42091738 (16.03.2015).
• Wachnik B., 2013, Analiza przedsięwzięć informatycznych w modelach budowania wartości przedsiębiorstw.
• Podsumowanie badań z lat 2011-2012, Informatyka Ekonomiczna, nr 4(30), Wydawnictwo Uniwersytetu Ekonomicznego we Wrocławiu.
• Werewka J., 2015, Investigation of enterprise architecture and software architecture in relation to quality attributes in military applications, Fast Tracked Vehicles, 37(2), http://www.obrum.gliwice.pl/spg/215/01_Werewka_ang.pdf.
• Werewka J., Jamróz K., Pitulej D., 2014, Developing Lean Architecture Governance at a Software Developing Company Applying ArchiMate Motivation and Business Layers, [w:] Kozielski S., Mrozek D., Kasprowski P., Małysiak-Mrozek B., Kostrzewa D. (red.), Beyond Databases, Architectures, and Structures, vol. 424, s. 492-503, Springer International Publishing, http://link.springer.com/10.1007/978-3-319-06932-6_48.
• Źródła błędów w projektach programistycznych, http://blog.wsoczynski.pl/2010/05/02/zrodla-bledow-w-projektach-programistycznych/(2.05.2010).