Common use of Quality Control and Quality Assurance Testing Clause in Contracts

Quality Control and Quality Assurance Testing. The quality control and quality assurance is documented in the “check-in procedure” as part of the Coding Rules, which are available on the MESSy Consortium Website, and which regulate the required checks to be performed by the developers (and the submodel maintainer, if necessary) before first submission to the CSG. The minimum technical prerequisites of new submodels or new submodel features are: - the new submodel or feature must compile without errors on a reasonable subset of supported compilers, - the new submodel or feature is switched OFF by default, - the new submodel or feature has no side-effects if it is switched OFF. Developers are encouraged to check-in also un-evaluated “alpha-versions” of their new submodels (which fulfil the above-mentioned requirements) to facilitate the beta testing by other users. The usability status of new submodels is defined for each new official Standard Version release by the submodel maintainer and regulated by the traffic-light system, which is documented on the MESSy Consortium Website. Modifications/extensions of existing submodels require the agreement of the submodel maintainer, and therefore require an information/involvement of the maintainer from the very beginning of the development. Before a new submodel or feature can become “operational” (green traffic light), it has to be thoroughly evaluated by the developers (and the submodel maintainer, if necessary) in a process-oriented evaluation approach and documented, preferably in GMD.