Start with your first prediction of total software errors and process timeliness

After having talked a lot about a six-tau software development process, it is time for you to carry out error prediction in your first software project and to determine the performance of CI/CT, i.e., to determine the process timeliness expressed by tau.

The benefit is obvious as you will know in an early stage following information:

1)      Software development process timeliness (tau), i.e., effectiveness of continuous integration, continuous testing, continuous bug fixing

2)      Total predicted errors in your software project

3)      Predicted characteristic cumulated failure curve towards full function (FF) and start of production (SOP)

4)      Predicted software maturity at FF and SOP as well as predicted SOP quality

5)      High transparency in terms of needed actions and measures for a quality SOP

Let me know if you are ready to start. I could support you in your first software project. As a result, you will get charts like listed below. Basically, we will only need as an input the real failure inflow of your software project on a weekly basis. All the rest is automatically calculated, meaning you won’t be confronted with the comprehensive mathematics.