Key Points regarding the Cockpit The Quality Cockpit does more than just detect quality issues; it enables an entire team to work effectively to achieve the right level of quality and to improve its practices. Quality Objective Determine the optimal objective By scoring a questionnaire, the Cockpit evaluates the appropriate quality objective for your application in order to maximize benefits and minimize costs. The approach is adjustable based on standard objectives or a diagnostic performed from an initial analysis of the existing code. Technical Requirements Translate the objective into concrete requirements Selected from the profile, these rules align all of the technical people (internal, external, and offshore) involved with the project toward a single objective. These rules are appended to a tender to allow a subcontractor to identify the quality objective and comply with it throughout development. Rule Settings and Reset Mode To adjust quality based on the type of code Reset mode lets you ignore existing issues that will not be corrected, while maintaining the rule for new development. By default, a rule applies to the full project, but it can be disabled by component (namespace, package, class, method, etc.), depending on your specific needs. On-Demand Analysis Detect problems quickly An analysis can be launched manually via the Cockpit or automatically as part of a regular process (batch, Ant, Maven, etc.). Add a task to your continuous integration server (Hudson, Continuum, CruiseControl, etc.) The files to be analyzed are very simply produced from your project files (Microsoft Visual Studio, Eclipse, etc.). Indicators Measure how close you are to your objective With each analysis, issues are evaluated against the set objective to identify their relative impact. Changes Monitor trends to detect deviations Each indicator is monitored through the development process, making it possible to quickly detect problems or validate improvement plans. Source of Problems Analyze the source of problems Depending on the problem, the steps toward improvement are more or less complex and may be adapted according to the project priorities. Mapping Go further in your analysis Each indicator is put in perspective by showing its distribution across the full application. Plan improvements gradually in relation to the severity of the problems and the overall project priorities. Classification & Categorization Don't get lost in the details. Staying organized keeps you from being overloaded with minor problems. The navigation helps you to quickly access each problem, identify how it has been detected, list the affected classes, etc. Quick Access to the Code Make corrections faster. A secure view of the code allows you to quickly zoom in on a problem and fix it efficiently. Code can be accessed using encryption on our secure space or directly on your server.