Data production stop (defect prohibiting production) or concealed data corruption (each without possible workaround):
A production stop takes place if all or essential parts of a product do not work. If the problem can be resolved with a workaround the issue has to be downgraded to Prio 2. A concealed data corruption takes place, if data is corrupted unnoticed or if data gets lost unnoticed or if inconsistent data is created.
|- Nothing works anymore or an essential, main functionality doesn’t work anymore.
- Data is being stored wrongly unnoticed and data inconsistencies are created.
|2||A heavy production disruption takes place if an essential function (core functionality) is either not available or delivers wrong results. As a result of this issue considerable time effort needs to be spent to work around the problem or to correct the data. This has a direct business impact.||- an important function (core function) is not available
- Program crashes when executing one of those core functions
- Wrong results need to be corrected with considerable effort
Production disruption with functional limitations:
A production disruption takes place if single functions of a product do not work correctly or fail. There is a workaround available or a different workflow resolves the problem within acceptable time.
|- A function does not work correctly; the objective can nevertheless be reached by a different workflow or with the help of other functions.
- Slightly wrong results are being delivered which can be corrected with reasonable effort.
Slight disturbance of the use of the software without effect on production.
A slight production disruption takes place, if single functions deliver correct results, but its execution leads to unwanted or irritating implications.
|- Spelling errors in a dialog mask
- Incomprehensible or inappropriate message windows.