By Service | 16 August, 2020
Introduction
The acceptance of a COLISH version will depend on how teachers and the end user adopt and accept the planned features. To ensure a high success rate of COLISH adoption, exhaustive testing will be carried out during the lifecycle phases.
Product Features Set
Before the development of a new COLISH version starts, Product Management will define a Product Features Set. This Set will be dependent on the Long Term Release Plan as well as input from the CoForum i.e. Policy Makers.
Testing during ‘Birth’
During the Birth of a new version, teaching concepts will be defined so that the Product Feature Set can be taught. They will be tried out and the effectivity will be tested. The results of these tests will flow back, as feedback, to the Product Feature Set as well as to the teaching methods/concepts.
Pre-Launch Assurance Testing (also called Pre-Assurance), before the version goes ‘live’, will also improve the success rate.
Extensive global field Assurance Testing will be necessary for example for the channels - schools, private, online - as well as for specific system areas such as European, African, Chinese.
Testing during ‘Live’
When the COLISH version goes Live, the teaching footprint will be larger than during Birth and new problems, issues or insights might appear. It will be necessary to perform regular Assurance Testing in the field as well as offline so that the effective use of COLISH can be tracked.
The Assurance Testing results will flowback into improving the version and teaching methods.