anchor.diff:  +
   
   . [[Isolate-Changes]]
  -Isolate Changes:: Introduce interfaces and intra-system borders, so that changes cannot propagate to other areas.
  +[pattern]#Isolate Changes#:: Introduce interfaces and intra-system borders, so that changes cannot propagate to other areas.
   Category: <<Improve>>
   +
   
   . [[Issue-Tracker-Analysis]]
  -Issue Tracker Analysis:: Analyse entries from issue-tracker to identify critical areas, components or stakeholders. 
  +[pattern]#Issue Tracker Analysis#:: Analyse entries from issue-tracker to identify critical areas, components or stakeholders. 
   Category: <<Analyze>>
   +
   
   . [[Keep-Data-Toss-Code]]
  -Keep Data Toss Code:: A strategy to improve systems, keeping the data created with the (old) systems as foundation for a new one. Also described as <<Keller-Migration, Bridge-to-the-New-Town>> (by Wolfgang Keller). This is the opposite of <<Never-Change-Running-System>>.
  +[pattern]#Keep Data Toss Code#:: A strategy to improve systems, keeping the data created with the (old) systems as foundation for a new one. Also described as <<Keller-Migration, Bridge-to-the-New-Town>> (by Wolfgang Keller). This is the opposite of <<Never-Change-Running-System>>.
   Category: <<Improve>>
   +
   
  
positive.code: +
  
  . [[Change-by-Extension]]
  Change by Extension:: Enable efficient change by creating new components instead of modifying existing ones.
  Category: <<Improve>>
  +
  
  . [[Change-by-Copy]]
  Change by Copy:: Isolate competing change necessity by copying and allowing the copies to evolve independently.
  Category: <<Improve>>
  +
  
  
negative.code: Category: <<Crosscutting>> 
  
  . [[Context-Analysis]]
  [pattern]#Context Analysis#:: Analyse external interfaces for risk, technology, business value and other factors.
  Category: <<Analyze>>
  +
  
  . [[Data-Analysis]]
  [pattern]#Data Analysis#:: Analyse and inspect the data created and manipulated by the system for its content, structure, quantity and size.
  Category: <<Analyze>>
  + 
  
  