Methodology
A system is build and delivered incrementally. That means you have working solution after first week. You have a user interface that can be easily evaluated. Often new requirements arise when part of system is visible before final delivery. Continuously view of system being built allows us to correct on the fly requirements. Working data is preserved during installations (often it's a business data).
How our software process guarantees high quality of systems?
- Quality of automated tests (main QA technique) is measured continuously during production process by so-called code coverage analysis. Our systems always have above 80% of code coverage.
- We are using informal code inspections based on version control system. Every change-set that is to be merged to main version is checked by another developer.
- Whenever possible we are using static analysis in order to analyse resources before run (for example: JSP pages in J2EE technology, ZPT templates in Zope/Plone).
- If there is an error in installed version it is reported immediately to developers team. In few minutes developers have got e-mail with stack trace that allows for precise defect localisation.
Real systems require real software environments: