Tutorial - Creating a taxonomy and viewing the results
Tutorial - Creating a taxonomy and viewing the resultsThis tutorial shows you how to:
You need the "Change project settings" permission to perform these tasks. For more information on taxonomies and using the Configuration Editor, see Configuring checkers for the integration build analysis. Tip: Prior to release 9.2, you could filter by issue type on the desktop, or scope by issue type in Klocwork Static Code Analysis. This tutorial explains how you can use taxonomies and views to accomplish the same thing.
Our example company has a policy to flag and eliminate all Null-Pointer Dereference (NPD) issues, all Buffer Overflow (ABR and ABV) issues, and two specific security vulnerabilities: SV.INCORRECT_RESOURCE_HANDLING.URH and SV.INCORRECT_RESOURCE_HANDLING.WRONG_STATUS. Setting up the Company Policy taxonomyFirst, we need to set up the Company Policy taxonomy in the Configuration Editor.
Tip: To learn how to apply a taxonomy to all new projects, see Copying the configuration to all new projects.
Now we'll use our taxonomy in Klocwork Static Code Analysis. Using the taxonomy in Klocwork Static Code Analysis for report and issue managementWe'll create a view, so that you will see only issues in the Company Policy taxonomy.
Grouping and filtering by taxonomy in connected desktopsConnected desktop users can filter and group issues by taxonomy to get a clearer picture of how they're performing against the Company Policy. For this example, we'll use Visual Studio 2008.
Grouping by taxonomyYou can group issues by taxonomy to get a picture of how issues are distributed across multiple taxonomies by clicking the You'll see issues distributed across taxonomies. If the same issue is detected in more than one taxonomy, you'll see it listed under each applicable taxonomy.
Filtering by taxonomyIf you want to see only issues for a specific taxonomy, filtering by taxonomy is the way to do this.
The only issues you see listed are of the types included in the Company Policy taxonomy. |