Essays about: "Technical debt"
Showing result 11 - 15 of 45 essays containing the words Technical debt.
-
11. Clean Code in Practice : Developers´ perception of clean code
University essay from Blekinge Tekniska Högskola/Institutionen för programvaruteknikAbstract : Context. There is a need for developers to write clean code and code that adheres to a high-quality standard. We need developers not to introduce technical debt and code smells to the code. READ MORE
-
12. Large Scale Photovoltaic Market Analysis In Italy
University essay from KTH/Skolan för industriell teknik och management (ITM)Abstract : The environmental targets set by Europe of reaching a net zero carbon emission by 2050 and the European Green Deal have increased the environmental targets previously set. The Italian government managed to reach the targets set by 2020 in advance and started to work on the 2030 targets in 2017. READ MORE
-
13. Detecting Enterprise Architecture Smells based on Software Architecture Smells
University essay from KTH/Skolan för elektroteknik och datavetenskap (EECS)Abstract : Software architecture (SA) smells are design problems in the internal structure and behavior of an SA. These can be seen as a specific category under the umbrella concept of technical debt (TD). READ MORE
-
14. Defining Thresholds for Enterprise Architecture Debt
University essay from KTH/Industriell ekonomi och organisation (Inst.)Abstract : A common challenge in organizations is a perception of that different languages are spoken among IT and other departments. Co-workers come from different background, have different knowledge base and sometimes even different objectives which can make an alignment more challenging. READ MORE
-
15. Architectural Technical Debt - can it be prevented with a software project generator?
University essay from Lunds universitet/Institutionen för datavetenskapAbstract : Architectural Technical Debt (ATD) is a challenge that many of today's companies aim to overcome. ATD concerns the overall structure and architecture of a software-intensive system and can be described as the unresolved shortcuts developers take under circumstances of e.g. time pressure and uncertain requirements. READ MORE