1. What
   1. Static analysis of any Flash based projects
   2. Detect unused code
   3. Detect nonoptimal code
   4. Detect possible bad design
2. Why
   1. "You can't control what you can't measure" Tom DeMarco
   2. "Any fool can write code that a computer can understand. Good programmers write code that humans can understand" Martin Fowler
   3. Code reviews during engagements
      1. Often finding same bad patterns
      2. If you repeat a task, automate it
   4. Make sure no junior developpers check in bad code
3. Who
   1. Programmer
      1. Integrated in his IDE
         1. FlashDevelop
         2. Flash Builder
      2. Quality insured up-front
   2. QA
      1. Make sure that rules are not broken on a daily basis
      2. Continuous Integration
   3. Project Management
      1. Take decisions to tackle the possible technical debt
   4. Architect
      1. Explain the purpose of each rule and the its priority
      2. Can then refuse a build a rule with a high priority is broken
      3. Build the ruleset with the team agreement
4. Best Practices
   1. Choose the rules you like, and suppress or ignore the ones you don't
   2. Use the ruleset creator to customize your ruleset
   3. Parameterize rule
   4. Ignore a specific violation by appending // NO PMD
   5. Don't try to reach 0 violations. That won't happen
5. When
   1. From the beginning of the project
   2. The latter it is set-up, the least efficient it will be
   3. Continuous Integration
6. How
   1. Command-line
   2. Maven
   3. Ant
   4. Mac OS X automator
   5. IDEs
   6. Hudson plugins
      1. PMD plugin
      2. Violations plugin
7. How it is build
   1. Different kind of rule
      1. AST-based
      2. RegExp based
      3. File based
   2. Load the ruleset
   3. Find Flash files in the source directory
   4. Compute ASTs where it is possible
   5. For each file, run every rule
   6. Produce a XML report
8. FAQ
   1. Flex only?
   2. Eclipse
   3. Viewer
   4. Mobile ruleset
   5. AIR ruleset?
   6. What's next?
      1. Eclipse plugin
      2. Platform specific ruleset
      3. Integration with Sonar
      4. Build new rules
      5. Input form the community