anchor.diff:  +
   
   . [[Runtime-Analysis]]
  -Runtime Analysis:: See <<Profiling>>, <<Performance-Analysis>>.
  +[pattern]#Runtime Analysis#:: See <<Profiling>>, <<Performance-Analysis>> and <<Runtime-Artifact-Analysis>>.
   Category: <<Analyze>>
   +
   
   . [[Runtime-Artifact-Analysis]]
  -Runtime Artifact Analysis:: (aka Log-Analysis, Trace-Analysis, Protocol-Analysis) Inspect artifacts created at runtime (e.g. logfiles, protocolls, system-traces) for information about problems, root-causes or system behavior.
  +[pattern]#Runtime Artifact Analysis#:: (aka Log-Analysis, Trace-Analysis, Protocol-Analysis) Inspect artifacts created at runtime (e.g. logfiles, protocolls, system-traces) for information about problems, root-causes or system behavior.
   Category: <<Analyze>>
   // TODO: perhaps Log-Analysis deserves a separate entry? Especially in security
   // sensitiv environments? MM 2014-03-16 
   +
   
   . [[Sample-For-Improvement]]
  -Sample For Improvement:: Provide concrete code example for typical improvement situations, so that developers can improve existing code easily.
  +[pattern]#Sample For Improvement#:: Provide concrete code example for typical improvement situations, so that developers can improve existing code easily.
   Category: <<Improve>>
   +
   
   . [[Schedule-Work]]
  -Schedule Work:: Schedule refactoring or improvement work, so that all (business and technical) stakeholders know about them. 
  +[pattern]#Schedule Work#:: Schedule refactoring or improvement work, so that all (business and technical) stakeholders know about them. 
   Category: <<Improve>>
   +
   
   . [[Separate-Cause-From-Effect]]
  -Separate Cause From Effect:: See <<Root-Cause-Analysis>>.
  +[pattern]#Separate Cause From Effect#:: See <<Root-Cause-Analysis>>.
   Category: <<Analyze>>
   +
   
  
positive.code: +
  
  . [[Migrate-Data]]
  Migrate Data:: Transform existing data from one structure or representation into another by keeping its original intent or semantic intact.
  Category: <<Improve>>
  +
  
  . [[Mikado-Method]]
  Mikado-Method:: Coordinated <<Refactoring, refactoring>> effort, described in the <<Mikado, Mikado-book>>.
  Category: <<Improve>>
  
  
  . [[Natural-Death]]
  Natural Death:: Keep old system running and only retire it once all objects contained reach end of life according to their life cycle. 
  Category: <<Improve>>
  +
  
  . [[Never-Change-Running-System]]
  Never Change Running System:: TODO: Add description here.
  Category: <<Improve>>
  +
  
  . [[Never-Rewrite-Running-System]]
  Never Rewrite Running System:: Joel Spolsky arguments, <<Spolsky-NeverRewrite, never to rewrite a system from scratch>>, as you will likely make many new mistake and won't generate much added value.
  Category: <<Improve>>
  +
  
  . [[Organizational-Analysis]]
  Organizational Analysis:: Analyse and inspect organization(s) responsible for the system.
  Category: <<Analyze>>
  +
  
  . [[Outside-in-Interfaces]]
  Outside-in Interfaces:: Modularize system in line with external, modular interfaces.
  Category: <<Improve>>
  +
  
  . [[Performance-Analysis]]
  Performance Analysis::
  Category: <<Analyze>>
  +
  
  
negative.code: Systematically prepare and take decisions by finding appropriate options, check assumptions, overcome emotion and prepare to be wrong. See <<heath-decisive, Decisive (by C+D Heath)>>.
  Category: <<Crosscutting>>
   
  
  . [[System-Documentation]]
  [pattern]#System Documentation#:: Document relevant structures, concepts, decisions, interfaces etc. of the system to increase. See <<arc42>>. 
  Category: <<Analyze>>
  +
  
  