RELREA - An Analytical Approach for Evaluating Release Readiness

As part of incremental and iterative software development, decisions about “Is the software product ready to be released at some given release date?” have to be made at the end of each release, sprint or iteration. While this decision is critically important, so far it is largely done either informally or in a simplistic manner, relying on a small set of isolated metrics. In this paper, we present an analytical approach combining the goal-oriented definition of the most relevant readiness metrics with their individual evaluation and their subsequent analytical integration into an aggregated evaluation measure. The applicability of the proposed approach called RELREA is demonstrated for an ongoing public project hosted on GitHub, a web-based hosting service for software development projects. Initial evidence shows that the method is supportive in evaluating release readiness at any point of the development cycle, making projections on the final release readiness and allows determination of bottleneck factors to achieve readiness. Keywords-release date; release readiness; release criteria; fuzzy set; aggregation; case study

[1]  Witold Pedrycz,et al.  Software cost estimation with fuzzy models , 2000, SIAP.

[2]  Paul W. Oman,et al.  Using metrics to manage the end-game of a software project , 1999, Proceedings Sixth International Software Metrics Symposium (Cat. No.PR00403).

[3]  Steve McConnell,et al.  Best Practices: Gauging Software Readiness with Defect Tracking , 1997, IEEE Softw..

[4]  Wan Azizun Wan Adnan,et al.  An integrated neural-fuzzy system of software reliability prediction , 1994, Proceedings of 1994 1st International Conference on Software Testing, Reliability and Quality Assurance (STRQA'94).

[5]  Swarup Medasani,et al.  An overview of membership function generation techniques for pattern recognition , 1998, Int. J. Approx. Reason..

[6]  Ronald R. Yager,et al.  On ordered weighted averaging aggregation operators in multicriteria decisionmaking , 1988, IEEE Trans. Syst. Man Cybern..

[7]  S. Yamada,et al.  Optimum software-release time considering an error-detection phenomenon during operation , 1990 .

[8]  J.T.S. Quah,et al.  Gauzing software readiness using metrics , 2008, 2008 IEEE Conference on Soft Computing in Industrial Applications.

[9]  Miroslaw Staron,et al.  Release Readiness Indicator for Mature Agile and Lean Software Development Projects , 2012, XP.

[10]  Abhaya Asthana,et al.  Quantifying software reliability and readiness , 2009, 2009 IEEE International Workshop Technical Committee on Communications Quality and Reliability.

[11]  H. D. Rombach,et al.  The Goal Question Metric Approach , 1994 .

[12]  P. Satapathy Evaluation of Software Release Readiness Metric [ 0 , 1 ] across the software development life cycle , 2005 .

[13]  I. Turksen,et al.  Measurement of Membership Functions: Theoretical and Empirical Work , 2000 .

[14]  W. A. Tiao,et al.  House of quality: A fuzzy logic-based requirements analysis , 1999, Eur. J. Oper. Res..

[15]  Ronald R. Yager,et al.  On ordered weighted averaging aggregation operators in multicriteria decision-making , 1988 .

[16]  Ronald R. Yager,et al.  An extension of the Analytical Hierarchy Process using OWA operators , 1999, J. Intell. Fuzzy Syst..

[17]  R. Brettschneider,et al.  Is your software ready for release? , 1989, IEEE Software.