|
|
|
Control the quality of your project to reach your objective.
The key to success is adopting a proactive approach that provides everyone involved with the project - the project manager, the architect, internal and outsourced developers - a consistent view of quality and the resources available for achieving it. |
 
|
Adopt such an approach with the Quality Cockpit:
- Establish the quality objective for your project using the Quality Profile,
- Get the technical requirements that translate it into specific and concrete rules,
- Detect deviations as early as possible though regular and automatic analyses of the code,
- Analyze and monitor changes in quality via dashboards,
- Work effectively with targeted improvement plans.
Customer Testimonial
"To ensure that new developments meet the quality needs of the application, Kalistick agreed to set up a quality contract with the team. The Quality Cockpit determines the rules, helps the team to implement them, and automatically verifies that they are followed."
Didier Lajarrige, IT Manager for Issuer Services
More information on the 5 key functions
 |
Quality Profile
Target the objective that addresses your project's current challenges.
- Identify your needs in terms of reliability, maintainability, changeability, efficiency, security, and transferability.
- An embedded application for the A380 does not have the same needs as a transactional web application, with your quality profile, you aim for the level of quality that maximizes your benefits without increasing yours costs.
- Using personality profile techniques, it determines your needs in order to establish key indicators to follow throughout the project.
|
|
 |
Technical Requirements
Implement best practices.
- Those that reflect your needs as rules to apply during development projects.
- Coming from technology communities, these are the best practices to implement, the poor practices to be avoided, structural rules represented by combinations of metrics, documentation objectives, controls to avoid copy/paste, etc.
- Categorized with requirement or tolerance thresholds to fit your profile. These are clearly detailed to be communicated to all internal and external people involved with the projects.
|
|
 |
Automatic Analyses
Detect deviations as soon as possible.
- Throughout the project, the Cockpit analyzes the source code and generated files (Java bytecode, C# assemblies, etc.).
- Unmet technical requirements are automatically detected.
- Anomalies are grouped, correlated, and categorized based on their impact on your quality objective.
|
|
 |
Dashboards
Have a clear and consistent view of quality.
- With each analysis, the results are consolidated for an instant view of development quality.
- Status of quality objectives, changes in key indicators throughout the project, non-compliant classes, critical problems, etc.
- Control the quality of development projects to ensure the success of the project.
|
|
 |
Improvement Plans
Work effectively and avoid falling behind.
- Base your decisions on qualitative and quantitative information to work consistently with the project's priorities.
- Keep from building up problems and minimize the cost of fixing them by acting right away.
- Adopt a continuous improvement process that adapts to the pace of your teams.
|
|
|
|
|
|
|
|
|
|
|
