No full-text available
To read the full-text of this research,
you can request a copy directly from the authors.
Hypothesis testing for module test in software development
Abstract
One of the most important issues in the software development is how to guarantee that the software satisfies the quality defined in the requirement specification. This paper proposes that the issue can be solved, first the number of test cases is statistically calculated from the failure density defined in the requirement specification, then the selected test cases are executed basing on the hypothesis testing. This paper also presents how our method can be used for debugging. When the number of the test cases is calculated, we applied the statistical behavior of the software quality to the integration testing. We, however, did not consider the ripple effect since it is unable to measure. In order to guarantee the quality of 4σ, and 5σ, we found that many more test cases are needed than is previously believed enough.
... Regression testing refers to the testing approach where a modified version of a component or application is tested, in order to ensure that existing features are still intact. This testing approach and other testing methods have been used by Beydeda [Beydeba and Gruhn 2002] and Yamaura [Yamaura and Onoma 2002]. ...
In the software engineering world, many modelling notations and languages have been developed to aid application development. The technologies, Java and Web services, play an increasingly important role in web applications. However, because of issues of complexity, it is difficult to build multi-threaded Java
applications and Web Service applications, and even more difficult to model. Furthermore, it is difficult to reconcile the directly-coded application with the model-based application.
Based on the formal modelling system, RDT, the new work here covers: (i) a translator, RDTtoJava, used to automatically convert an RDT model into an executable multi-threaded Java application; (ii) the framework for developing an RDT model into a Java synchronous distributed application that is supported by the JAX-RPC Web Services; and, (iii) the framework for developing an RDT model into a Java asynchronous distributed application that is supported by the JMS Web services.
Experience was gained by building distributed computing models and client/server models and generation of the application based on such models. This work is helpful for the software developers and software researchers in formal software development.
Issues such as test case revalidation, test execution, failure identification, fault identification, modification dependency, fault mitigation and test case dependency are essential for an industrial environment in applying regression testing. Most of these issues are easy to address if one is dealing with small programs, but in a large software house where multiple large programs are being developed and maintained, they suddenly become complicated and costly. Some of these issues are also related to general software testing, however, these problems become acute in regression testing because test cases are repeatedly exercised in case of regression testing.
This paper gives an overview of the software maintenance process of Hitachi Software Engineering (HSK) Co., Ltd in Japan-including its success and failure cases. It discusses HSK's software processes, issues, use of specific tools and techniques such as IMOZU diagrams, and approaches in solving problems. These include the requirement capturing process, reverse-engineering techniques, environmental changes, change management, and project management. By discussing actual project experiences, we point to certain lessons and their implications for research in software maintenance. We also present the latest re-engineering CASE tools, such as RE-ENGINEERING and SEWB3, used at HSK.
Describes assurance techniques for Year-2000 (Y2K) testing. The Y2K problem is an important issue in the computer industry today, and testing is still the main technique for quality assurance. There is a need to ensure that the software is reasonably safe from Y2K faults after testing. This paper uses a statistical model for ensuring this, and it explicitly models Y2K faults as well as the ripples induced by Y2K modifications. The paper then describes two processes that use the model in practice: a bottom-up process that can be used together with software development, and a top-down process that can be used when the project is almost completed. These processes can be easily embedded in an existing testing process with minimal changes and minimal extra effort
Good enough evaluation methods are reviewed, including low volume
statistical testing. High assurance software is viewed as requiring high
volume statistical testing, or analysis methods that prove that a
program has certain desired properties. The weaknesses of some previous
high assurance strategies are discussed, and a new approach called
pattern directed testing and analysis is described. In this approach,
design patterns are used to give high assurance for critical generic
properties, and enough assurance for problem dependent functionality
Software quality is a serious issue for developers and customers. At Hitachi Software, we have used our extensive experience to improve quality assurance and significantly decrease our fault rates
Assurance-based Y2K Testing. Private communication
- W T Tsai
- R Paul
- W Shao
- S Rayadurgam
- J Li
W. T. Tsai, R. Paul, W. Shao, S. Rayadurgam, and J. Li. Assurance-based Y2K Testing. Private communication, Soft-ware Engineering Laboratory, Department of Computer Science and Engineering, University of Minnesota, December 1999. Proceedings of the 26 th Annual International Computer Software and Applications Conference (COMPSAC'02) 0730-3157/02 $17.00 © 2002 IEEE