-
Notifications
You must be signed in to change notification settings - Fork 16
/
Copy pathmaintainability.theory.txt
20 lines (16 loc) · 1.37 KB
/
maintainability.theory.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
┏━━━━━━━━━━━━━━━━━━━━━┓
┃ MAINTAINABILITY ┃
┗━━━━━━━━━━━━━━━━━━━━━┛
MAINTAINABILITY ==> #Ease to manage by developers (i.e. complexity), i.e. ease to:
# - operability: keep on offering same features
# - transferability: operability for new developers
# - extensibility: offer new features
# - portability: support new environments
# - reusability
# - scalability: increase|decrease demand
#Opposite is "brittleness"
MODULARITY & ABSTRACTION ==> #Usually coupled, increase maintainability:
# - modularity: multiple contexts inside same logic (incoherence) -> move complexity in-between, i.e. horizontal
# - abstraction: multiple contexts using common logic -> move complexity downstream, i.e. vertical
#See their doc
REFACTORING ==> #Increasing maintainability by modifying code design|architecture