Maturity testing of software in stabilisation phases

When introducing software that has been created individually, at least in part, there is usually always a stabilisation phase after going live. During this time, possible errors and performance restrictions should be rectified to such an extent that compliance with the SLA parameters can then be achieved with "normal" operational effort. In the stabilisation phase, all or some SLA parameters are often not valid or have been extended. In reality, however, a predetermined period of time is always referred to as the stabilisation phase instead, without really taking into account the level of maturity achieved by the software.

The aim of this thesis is to investigate which characteristics and parameters can be used to measure the maturity level of software in the stabilisation phase. These indicators should then make it possible both to continuously present the progress achieved in the stabilisation of the software and to contribute to the realistic determination of the end of the stabilisation phase. Ideally, the indicators should also make it possible to estimate whether the software is still on the expected path to stabilisation or where special measures are required in order to achieve regular operation.

Prof Dr Jorge Marx Gómez