|
|
Keeping the quality of a project consistent
|
Establish the best practices to follow and the worst practices to be avoided, and adopt a continuous improvement process.
Whether for a new development or an application with existing code, use a SaaS platform for quality management and, in your team, implement the best practices from C# and Java development communities into a CMMi process.
|
 
|
|
Securely accessible by Internet, your project's Cockpit is immediately operational and allows you to address quality very quickly with the entire development team.
 |
Rules adapted to your needs
To minimize risks and costs.
- Specific to your project by relying on a quality profile made online.
- Selected from a standard profile.
- Improved learning for your team through documentation and associated with detections in your code.
- Code quality improves during development, and the defect rate continually decreases.
|
|
 |
Pre-existing code with problems?
Set rules to be applied by component.
- Problems in pre-existing code can be fully or partially ignored in order to target actions, while maintaining a quality objective for new classes.
- Rules are set by module (namespace, package), class, or method.
- The most effective: An initial analysis gives you a quality diagnosis within a few hours. With dashboards, you have a clear and immediate view of the situation, and you set rules based directly on the rules.
|
|
 |
Add quality to your software factory
With continuous quality integration.
- No installation, the file to analyze is automatically built from your Microsoft Visual Studio or Eclipse project files, from your Ant, Maven, files, etc.
- Using a continuous integration server (Visual Studio Team System, Hudson, Continuum, CruiseControl, etc) to add the task, which automatically triggers the quality analysis.
- Receive alerts by email or RSS feed, or integrate them into your project portfolios.
|
|
 |
Each developer improves
The overall quality of the project improves.
- More than 300 rules originating from C# and Java communities provide improved learning to help everyone develop their skills.
- Learning best practices promotes the acceptance of quality controls.
- Accessing code via the Cockpit helps to quickly understand problems, efficiently correct them, and no longer repeat them.
|
Focus on new objectives for new developments, and adopt targeted improvement actions for existing code.
1/ Perform a quality diagnostic of the existing code with your Quality Cockpit. Determine the problems to be resolved and ignore the ones you will not change.
2/ For new developments, achieve quality code from the beginning by determining the rules to be applied.
You have your objective, now manage your development projects with the Cockpit!
Customer Testimonial
"We launched a tool early in the development process in order to instill rules and put them into practice right away. This allowed us to eliminate many of these problems later in the development process. It also helped the entire team to develop their skills and quickly identify risky practices."
Loïc R., Technical Manager
|
|
|
|
|
|
|
|
|
|
