+Since some problems occur multiple times it might be nice if Fortify was able to\r
+generate a clear overview of which components of the application contain detected\r
+problems. This could be very useful in combination with the information about\r
+components/functions which do pass the given security check. This would allow\r
+developers to determine if they suffer from chronically malformed code \r
+(eg. all relevant code fails the check, indicating a very serious problem throughout the entire code-base) \r
+or a single error (eg. most relevant code passes the check except for a few isolated cases).\r
+In the tested code-base there is a clean distinction between an installer component and the\r
+actual web application. If the installer suffers from problems not present in\r
+the web application and Fortify would be able to point out the specific check is\r
+relevant to both components the company would know which team/developer needs some major\r
+reeducation and who would be the best person to teach them.\r