Project : scilab
The Scilab developement is based on a management plan and a quality policy. We describe below :
The management plan.
The quality assurance plan.
The bug tracking policy.
The qualification procedure and the qualification environment.
- The management plan
A management plan has been written and diffused to the Steering Committee of the Consortium. This document gives the general rules that the operational team sets up for the realization of the development of Scilab software within consortium framework.
Operational organization and regular check (team organization, responsabilities, meetings, etc.)
Road map proposal (calendar and dead-line).
- The quality assurance plan (draft version)
This document gives the general rules that the operational team sets up for the management, the development, the qualification, the diffusion and the maintenance of Scilab software.
Quality plan (organization and follow-up).
Cross procedures to the Scilab activity (documentation management and configuration management).
Qualification procedure (process, referential, non-regression and implementation).
Management procedure of the technical requests (bugs management, means, etc.).
- The bug tracking policy
The choosen policy is to have a complete tracability of all the Scilab bugs and requests. In order to respect the policy, an open source tool (Bugzilla) has been modified and installed to manage and track the Scilab bugs and the Scilab requests (see below the description of the bug tracking system).
- The qualification procedure and the qualification environment
Scilab team has defined and installed a qualification procedure and related environment to ensure the internal acceptance of the scilab software.
This procedure is based upon a reference scale of qualification. Each step of this scale is composed of critical elements and information elements:
critical elements generally correspond to tests which must be successfully passed to achieve acceptance,
information elements corresponds to others tests, documentation checking, etc.
This provides not only criteria for classical acceptance but also thorough information on the final state of the scilab product version to be described in ``released notes'' document as well as known by support team prior to external delivery.
The used methodology should be answer to the constraint of a software product:
heterogenous target machine
regular delivery (major or minor releases)