Risk analyzer - calculation methodology

Usually in any project, the end Business requirement is to implement software in production flawless and for that to happen, each modules in the project should have minimum below properties for it to get integrated and automated with other modules. i. Least or no manual intervention while execution of module in production ii. Module uniqueness should be there and to avoid redundancy the same module should called by other modules. This proposition is for easy maintenance. Module redundancy is hard to propagate as the same is costly affair during maintenance. This is mainly design approach. Every time the above issues found during software testing, the same were communicated to stakeholder usually in qualitative form. The issue and impact explanation in qualitative form is tougher because one has to explain the module importance based on which issue priority will be determined. Stakeholders are also liable to understand the domain of module to understand it’s importance and it’s impact factor during failure. The whole process becomes lengthy in acknowledging to issue. It is believed if whole communication would have taken place in quantitative form, then time taken to respond to issue would have been shortened. Taking an scenario which had happened with author in real time, Author will try to share fact how quantitative factors will help to resolve faster in compare to qualitative factors. Once, Author was surprised to found his salary credited was almost halved. Author was stressed of the fact and tried explaining his supervisor and payroll people the importance it carries as he was sole earning member and also not carrying that much amount in bank to address requirements. He went on explaining the impact of not getting full salary by addressing to fact that his corporate card payment will be on hold, his own personnel card payment and other utilities payment will be on hold and impact went on. Getting hold of the nature and gravity of issue, payroll department decided to look into his issue with highest priority. After everything got resolved, Author tried analyzing the situation and felt bad for bringing his personnel stuffs to office. He felt, it could have been explained in numbers by saying, out of scale of 100 the importance the issue carries was 98 and impact factor was 10000. Which says high importance and non zero impact. The quantitative or number system would have been easier from Author perspective to explain and would have been better for other stakeholders to respond. Time taken to respond to issue would have been minimized.