Bad design in software architecture refers to a system that is poorly organized, overly complex, and difficult to understand and modify. It manifests through several key characteristics:
Rigidity: This is when the software is difficult to change because any modification affects too many other parts of the system. A small change in one area necessitates changes in many other areas, leading to a cascade of modifications that complicate maintenance and evolution of the software[17].
Fragility: Changes made to the software, even small ones, cause it to break in places that are conceptually unrelated to the part that was modified. This unpredictability makes it risky and challenging to implement new features or fix existing issues[17].
Immobility: The software components are so tightly coupled or intertwined that it becomes difficult to reuse them in different contexts or projects. This lack of reusability hampers efficiency and innovation[17].
Viscosity: Making changes in a way that is architecturally sound and clean is more difficult than hacking together quick fixes. This leads to further degradation of the software quality over time as developers opt for the path of least resistance that introduces more problems[17].
Complexity: The software contains unnecessary complexity, making it hard for developers to understand and work with. This could be due to over-engineering or failure to refactor and simplify the codebase[17].
Poor Communication: Often, bad design stems from poor communication and understanding between the design and development teams. When the design lacks clarity or is not effectively communicated, misunderstandings occur, leading to rework and wasted effort[2].
Technical Debt: Bad design choices often lead to technical debt, where shortcuts and compromises made in the initial design accumulate, creating a tangled web of complexity that slows down deve...
