April 18, 2016
SC2016 Mini-Project: Code Risk Heat Map
Software Craftsmanship 2016 - Mini-Project
Code Risk Heat Map
Estimated Duration: 2-4 hours
Author: Jason Gorman, Codemanship
Create a tool that produces a "heat map" of your code, highlighting the parts (methods, classes, packages) that present the highest risk of failure.
Risk should be classified along 3 variables:
1. Potential cost of failure
2. Potential risk of failure
3. Potential system impact of failure (based on dependencies)
Use colour coding/gradation to visually highlight the hotspots (e.g., red = highest risk, green = lowest risk)
Also, produce a prioritised list of individual methods/functions in the code with the same information.
PLEASE INSTALL ANY METRICS OR CODE ANALYSIS TOOLS YOU MIGHT WANT TO USSE *BEFORE* THE EVENT
Posted 1 year, 10 months ago on April 18, 2016