Workarounds arise within each project. The reason is that despite a thoughtful and structured approach to software development, we sometimes encounter situations where we decide to implement a workaround instead of the originally planned permanent solution. There are options for managing workarounds; however, the situation can quickly spiral out of control, especially when a project requires the rapid implementation of numerous functionalities, and the project scope expands rapidly. The increase in the project's scope often (sometimes unintentionally) leads to a greater number of workarounds. The consequence of this can be unnecessary expenditure of time and resources to address errors that may be caused by workarounds. In the context of software development, this phenomenon is referred to as technical debt.
In this thesis, we will present a theoretical foundation of using workarounds while emphasizing the significance of their effective management. The theoretical foundation will serve as the basis for developing a prototype software solution that automates a portion of workaround management.
|
