17. Managing violations
• For each violation you can
– Comment
– Change its severity
– Declare it as a false-positive
– Assign it to someone
– Assign it to an action plan
19. Technical debt
• Term coined by Ward Cunningham in 1992
• Work that needs done before a job is complete
• Unwritten tests
• Bad design and architecture
• Duplicated code
• …
• The higher you wait to fix, the more expensive it
becomes
20. SQALE
• Based on ISO 9126 Quality Model
• Computes a Technical Debt, measured in days
21. Code quality
“A well-written program is a program where
the cost of implementing a feature is
constant throughout the program's lifetime.”
22. What now?
• What to start with?
– Improving test coverage?
– Removing duplicate code?
– Checking violations?
– …
• Where to start?
– Most critical projects?
– Most « buggy » projects?
– Voluntary teams?
– …
Try it and tell me!