Share This Article:

A New Analysis Concept in Applying Software Reliability Growth Models and Tool Implementation: The SafeMan

Abstract Full-Text HTML Download Download as PDF (Size:2887KB) PP. 396-405
DOI: 10.4236/jsea.2014.75036    3,721 Downloads   4,768 Views   Citations

ABSTRACT

In recent years, many software development organizations have been assessing and analyzing their software product’s reliability/quality and judging whether the software product is releasable by using Software Reliability Growth Models (SRGMs) at the final stage of software development. The usage of SRGMs originates in the advantage that various reliability analysis results based on the SRGMs can be acquired easily. However, it is very difficult for general software project managers to grasp the achievement level of reliability/quality based on its analysis results because some sort of professional knowledge is required in order to understand the information on the attainment progress of software product’s reliability/quality. Moreover, it is also difficult for software project managers and inspectors who do not deeply comprehend the details of their project to evaluate the degree of software reliability and quality, if they assess it without grasping the live development situation and only see the documents submitted from their staff. In this paper, we propose a new analysis concept for assessing the software product’s reliability/quality, and illustrate the output results obtained by a tool, the SafeMan.

Conflicts of Interest

The authors declare no conflicts of interest.

Cite this paper

Fujiwara, T. and Kimura, M. (2014) A New Analysis Concept in Applying Software Reliability Growth Models and Tool Implementation: The SafeMan. Journal of Software Engineering and Applications, 7, 396-405. doi: 10.4236/jsea.2014.75036.

References

[1] Pham, H. (2000) Software Reliability. Springer-Verlag, Singapore.
[2] Kimura, M. and Fujiwara, T. (2011) Software Reliability. JUSE Press, Tokyo.
[3] Ohba, M. (1984) Software Reliability Analysis Models. IBM Journal of Research and Development, 28, 428-443. http://dx.doi.org/10.1147/rd.284.0428
[4] Yamada, S., Isozaki, R. and Osaki, S. (1989) A Software Reliability Evaluation Tool: SRET. Transaction on IEICE, J72-D-1, 24-32.
[5] Ramani, S., Gokhale, S. and Trivedi, K.S. (1998) SREPT: Software Reliability Estimation and Prediction Tool. Performance Evaluation, 39, 37-60.
[6] Fujiwara, T., Yamada, S. and Shiotani, K. (2000) A Software Testing-Management Tool for Reliability of Software Development and Its Application. Proceedings of the 6th International Conference on Reliability and Quality in Design, Orland, 175-179.
[7] Okamura, H., Ando, M. and Dohi, T. (2005) Development of a Software Reliability Assessment Tool on Spreadsheet Software. Transaction on IEICE, J88-D-1, 205-214.
[8] Fujiwara, T. and Yamada, S. (2004) Testing-Management Policies by Using the Software Reliability Assessment Tool. Proceedings of the 2nd International Conference on Project Management, Chiba, 403-408.
[9] Yamada, S. and Fujiwara, T. (2001) Testing-domain Dependent Software Reliability Growth Models and Their Comparisons of Goodness-of-Fit. International Journal of Reliability, Quality and Safety Engineering, 8, 205-218. http://dx.doi.org/10.1142/S0218539301000475
[10] Akaike, H. (1976) What Is the Information Criterion AIC? Suri Kagaku, 14, 5-11.

  
comments powered by Disqus

Copyright © 2018 by authors and Scientific Research Publishing Inc.

Creative Commons License

This work and the related PDF file are licensed under a Creative Commons Attribution 4.0 International License.