anchor.diff: +:linkattrs:
  +
   [[Analyze]]
   
   == Analyze
  
positive.code: 
  
  . Start <<Capture-Quality-Requirements, capturing current quality requirements>> from the _authoritative_ stakeholders of the systems.
  . Conduct a <<Qualitative-Analysis, qualitative analysis>> of the system, its architecture and surrounding organization, based upon the specific quality requirements 
  . Perform <<Static-Code-Analysis, static code analysis>>
  . Conduct <<Stakeholder-Interview, stakeholder interviews>>
  . Perform a number of *runtime analysis*, e.g. performance and load monitoring, process and thread analysis
  . Inspect the data created, modified and queried by the system, for structure, size, volume or specialities
  . Inspect and analyze all involved organizational processes
  (development, project-management, operations, requirements-analysis)   
  
  
  WARNING: Never start solving problems until you have a thourough understanding of current stakeholder requirements. Otherwise you risk wasting effort in areas that no influential stakeholder cares about.
  
negative.code: === Patterns and Practices for Analysis
  (given in alphabetical order)
  
  * Architecture Analysis, see [pattern]#<<Qualitative-Analysis>># and
  [pattern]#<<ATAM>>#.
  * [pattern]#<<Architecture-Documentation>>#
  * [pattern]#<<ATAM>>#
  * [pattern]#<<Capture-Quality-Requirements>>#
  * [pattern]#<<Context-Analysis>>#
  * [pattern]#<<Data-Analysis>>#
  * [pattern]#<<Debugging>>#
  * [pattern]#<<Development-Process-Analysis>>#
  * [pattern]#<<Documentation-Analysis>>#
  * [pattern]#<<Instrument-System>>#
  * [pattern]#<<Issue-Tracker-Analysis>>#
  * [pattern]#<<Profiling>>#
  * [pattern]#<<Qualitative-Analysis>>#
  * [pattern]#<<Quantitative-Analysis>>#
  * [pattern]#<<Questionnaire>>#, especially [pattern]#<<Pre-Interview-Questionnaire>>#
  * [pattern]#<<Requirements-Analysis>>#
  * [pattern]#<<Root-Cause-Analysis>># - finding the root cause of problems
  * [pattern]#<<Runtime-Artifact-Analysis>>#
  * [pattern]#<<Separate-Cause-From-Effect>>
  * [pattern]#<<Software-Archeology>>#
  * [pattern]#<<Stakeholder-Analysis>>#
  * [pattern]#<<Stakeholder-Interview>>#, see also [pattern]#<<Pre-Interview-Questionnaire>>#.
  * [pattern]#<<Static-Code-Analysis>># (Structural analysis)
  * [pattern]#<<Structural-Analysis>>#
  * [pattern]#<<Take-What-They-Mean>># (not what they say, as it may differ).
  * [pattern]#<<Use-Case-Cluster>>#
  * [pattern]#<<View-Based-Understanding>>#
  
  
  // the detailed description of the analysis-patterns
  