Приклади результатів від дії негативних сценаріїв використання програмного забезпечення
Date
2019-03-20
Journal Title
Journal ISSN
Volume Title
Publisher
Видавництво Львівської політехніки
Lviv Politechnic Publishing House
Lviv Politechnic Publishing House
Abstract
Наведено приклади широко відомих випадків настання ризиків, пов’язаних із
негативними сценаріями використання програмного забезпечення, що спричинили
вагомі втрати власників, авторів чи суспільства. Основним критерієм для пошуку та
вибору таких прикладів стали достовірність, вагомість та можливість подати точні дані
про економічні втрати або порядок втрат. Висвітлено основні передумови настання
ризику, перебіг подій та втрати, що стали наслідком. Проведено оцінювання
економічного результату подій. Запропоновано підхід до оцінювання значущості втрат.
This paper represents a list of widely known issues of risk implementation related to specific negative scenarios of software use. The core selection criteria were an opportunity to identify impact areas that led to the core losses for each case. Main preconditions, course of events and consequences are highlighted. In addition, it is explicitly defined which negative scenario was ignored or missed and how it led to the damage. This article is aside from the classical definition of “bug”, but focusing on negative use cases (negative scenarios) ignored or mistreated during requirement engineering, development, and testing. By stating a bug modern software development usually, means a mistake in source code or misalignment of settings between program components. Meanwhile, a negative scenario means something able to be performed using normally operating software. Negative scenario is something average user typically not do. However, basing on experience or logic analysis we can assume negative scenarios able to appear, list them, evaluate possible consequences and enhance the software in a manner preventing scenario execution or consequences. As the study shows, that all listed negative scenarios are typical from the general software development or domain point of view. So all listed consequences were able to be mitigated or avoided at all. All these issues are equipped with a numerical value of economical losses defined based on studies’ data or reports given by different authorities in regards to these cases. All cases belong to different domains, it helps to highlight areas of modern business able to cause similar losses in case if negative scenarios take place. All this data proves the necessity of negative scenarios mitigation during software development. The given examples explicitly show that high impact may take place in various domains. What makes negative use cases a common problem for a variety of applications in the international and domestic economy. However, in some cases possible impact may appear not explicitly and obviously enough. From such a perspective, it is very important to collect, classify and evaluate cases related to negative use cases implementation to provide information important for further development. The study shows the referring field for risk managers, project managers and all risk assessment professionals. It provides examples of negative software use cases appearing and causing damage in an area this software is used in. This referring field should help software development specialists to take a proper decision regarding negative scenarios risks arising. Also, this paper emphasizes the extremely powerful impact of negative scenarios on software related to exchanges, which creates an additional area for perspective research.
This paper represents a list of widely known issues of risk implementation related to specific negative scenarios of software use. The core selection criteria were an opportunity to identify impact areas that led to the core losses for each case. Main preconditions, course of events and consequences are highlighted. In addition, it is explicitly defined which negative scenario was ignored or missed and how it led to the damage. This article is aside from the classical definition of “bug”, but focusing on negative use cases (negative scenarios) ignored or mistreated during requirement engineering, development, and testing. By stating a bug modern software development usually, means a mistake in source code or misalignment of settings between program components. Meanwhile, a negative scenario means something able to be performed using normally operating software. Negative scenario is something average user typically not do. However, basing on experience or logic analysis we can assume negative scenarios able to appear, list them, evaluate possible consequences and enhance the software in a manner preventing scenario execution or consequences. As the study shows, that all listed negative scenarios are typical from the general software development or domain point of view. So all listed consequences were able to be mitigated or avoided at all. All these issues are equipped with a numerical value of economical losses defined based on studies’ data or reports given by different authorities in regards to these cases. All cases belong to different domains, it helps to highlight areas of modern business able to cause similar losses in case if negative scenarios take place. All this data proves the necessity of negative scenarios mitigation during software development. The given examples explicitly show that high impact may take place in various domains. What makes negative use cases a common problem for a variety of applications in the international and domestic economy. However, in some cases possible impact may appear not explicitly and obviously enough. From such a perspective, it is very important to collect, classify and evaluate cases related to negative use cases implementation to provide information important for further development. The study shows the referring field for risk managers, project managers and all risk assessment professionals. It provides examples of negative software use cases appearing and causing damage in an area this software is used in. This referring field should help software development specialists to take a proper decision regarding negative scenarios risks arising. Also, this paper emphasizes the extremely powerful impact of negative scenarios on software related to exchanges, which creates an additional area for perspective research.
Description
Keywords
негативні сценарії, економічний результат, втрати, розроблення програмного забезпечення, negative scenario, economic effect, losses, software development
Citation
Кузьмін О. Є. Приклади результатів від дії негативних сценаріїв використання програмного забезпечення / О. Є. Кузьмін, Н. С. Станасюк, Д. А. Берднік // Менеджмент та підприємництво в Україні: етапи становлення та проблеми розвитку. — Львів : Видавництво Львівської політехніки, 2019. — Том 1. — № 2. — С. 18–32.