Software Quality Testing Research Articles

Research on Application of Software and Information Technology for Implementation of Test Management System in Bank

The banking information construction in China has made great progress with the rapid development of science and technology. The various systems is on-line continuously for the expansion of banking. While the in-depth development of banking systems is in various types and the scale and complexity of software projects is increasing, the quality of software testing become a constraint to improve the quality of each system bottleneck gradually. As an important aspect of a quality assurance software testing, the test management system is being pay attention gradually. The application software on banking for test management system is first described in this article, and than the research and implementation of test management system is described in detail.

Design and Implementation of the Software Testing Management System Based on Django

As the complexity and reliability requirements of software projects increase constantly, software testing is becoming more and more prominent and important in software engineering. Testing management system is the basis of constructing software testing management system. It regulates software testing processes, and ensures the entire testing process is under control. Based on the Django framework, this paper design and implement a test management system based on B/S architecture. It can operate as a common platform for software testing management, and reduce the cost and cycle of software testing, guarantee the quality and efficiency of software testing.

New Perspectives on Software Quality [Guest editors' introduction

This special issue, owing to its fundamental software quality focus, comprises a collection of diverse articles that address the challenges and directions for software quality research. The Web extra at http://youtu.be/T7V4RSr1KEE is an audio interview in which Davide Falessi speaks with guest editors Annie Kuntzmann-Combelles, Michael Felderer, and Ruth Breu about methods for improving software quality management, testing, and security on intelligent and interconnected devices.

A New Dynamic Model for Software Testing Quality

Research and study of Software Quality has Traditionally Focused on the Overall Product Quality Rather than on the sub-phase’s milestones. There are many attempts over software testing as a standalone development phase which introduced in the literature; these efforts lacked the dynamic nature which has a diverse effect on the maintenance phase. This study will present the current software testing models; their challenges and at the end it will present our new dynamic model for applying quality assurance requirements over the sub-phases of the testing model. Quality properties may include as performance, efficiency, reliability, etc., new model will present for Improving the effectiveness and efficiency of the testing process through applying the quality requirements, designing high quality products, producing software with high Cost optimization, satisfying the product stakeholders.

Enhancing Software Quality by an SPL Testing based Software Testing

Software testing is a process of providing information that a software application or program meets the business and technical requirements that guided its design and development; and works as expected. Regardless of the environment (i.e. Structured or Object Oriented), software testing can also identifies important defects, flaws, or errors in the application code that must be fixed. Quality control involves the maintenance of quality in a product, particularly by comparing the performance of a product with a set of specifications. This paper introduces some basic knowledge regarding to software testing. The paper provides some new model that could improve quality of software testing as a mean to increase the overall quality of the product.

An efficient software testing method by decision table verification

A typical software testing is performed by making and running test cases that consist of input pattern and expected output pattern. Because exhaustive testing requires billions of test cases and many labours, we can only perform hundreds of them in practice. As for a software logic testing, selecting test cases from many candidates to achieve enough programme path coverage is important, and specific software testing skills are required for it. In our study, we propose a knowledge creation method of software logic extracted automatically from programme source code. In our method, all possible programme paths are extracted from source code, then converted into a decision table, which is easy-readable table format for software testing engineer. The logic verification can be performed exhaustively in a short time by comparing the decision table with a specification of software. Our method would contribute to improve both efficiency and quality of software testing.

AN OVERVIEW OF CLOUD TESTING AS A SERVICE

Testing is an important process for software quality assurance. A cloud infrastructure creates significant new opportunities for software quality assurance and testing. Making the test infrastructure that directly represents the production cloud infrastructure is too expensive – in terms of hardware, software licenses and testing professionals. To deal with this challenge the paper gives an overview of various cloud testing strategies and also introduces ‘Testing as a Service’, using Cloud computing.

Framework for Extensible Application Testing

In recent years large corporations as well as smaller commercial enterprises have begun to devote increased attention to software testing and software quality. This paper introduces a novel tool—the Framework for Extensible Application Testing (FEAT), implemented by the author and applicable for automatic generation and execution of test cases. The paper discusses system requirements, design, architecture and modes of operation. It also contains a detailed comparison of the FEAT framework with existing test environments, focusing in particular on the STAF/STAX framework. The final section is devoted to experimental research into the applicability and efficiency of the presented tools in various projects and configurations, as reflected by quality metrics.

Taguchi methods in software quality testing

Quality optimisation methods offer a structured way of improving software development as early as in the product design phase. This work introduces the Taguchi method in software design optimisation. The basics of the method are reviewed along with a proposed methodology for design of experiments (DOE). A case study is drawn from a real software development project in the area of industrial simulations. One critical quality characteristic in simulations software is the software performance. A key performance metric, the code total execution time, is selected to monitor experimentally performance variation. Taguchi's DOE is employed to provide a practical relationship between code structure factors and factor interactions and the performance metric. The run-time performance evaluation of two alternate versions of multiple loop-nesting are analysed by Taguchi's signal-to-noise ratio (SNR) concept. The purpose of the paper was to insinuate the usefulness of these statistical tools in assessing software quality metrics based on a scientific approach. It is demonstrated that performance optimisation enhances execution time by a factor of three with respect to the expected value.

A Framework for Improved Regression Testing Based Upon CTest and CDash

The existing CMake and CTest environment provides an excellent platform for execution and submission of software quality tests. However, there is little support or aid for regression type tests provided to lessen the burden of writing tests and verifying the results. We propose an additional facility to compare measurements generated by a software quality test to a based-line result. Our approach enables the ability to use multiple images as measurements, along with integer, floating point and string values for regression tests. We describe a new testing class framework which provides the functionality of reading, writing, comparing and differentiating named measurements.

A Unified Modeling Framework Incorporating Change-Point for Measuring Reliability Growth daring Software Testing

Reliability of software often depends considerably on the quality of software testing. By assessing reliability we can also judge the quality of testing. Alternately, reliability estimation can be used to decide whether enough testing has been done. Hence, besides characterizing an important quality property of the product being delivered, reliability estimation has a direct role in project management-the reliability models being used by the project manager to decide when to stop testing Jalote [12]. A plethora of software reliability growth models (SRGM) have been developed during the last three decades. Various software development environment and assumptions have been incorporated during the development of these models. From our studies, many existing SRGM can be unified under a more general formulation. In fact, model unification is an insightful investigation for the study of general models without making many assumptions. In the literature various software reliability models have been proposed incorporating change-point concept. To the best of our knowledge these models have been developed separately. In this paper we propose a general framework for deriving several software reliability growth models with change-point concept based on non-homogeneous Poisson process (NHPP). Some existing change-point models along with three new models have been derived from the proposed general framework. The models derived have been validated and verified using real data sets. Estimated Parameters and comparison criteria results have also been presented.

DEVELOPMENT OF FUZZY SOFTWARE OPERATIONAL PROFILE

Software operational profile (SOP) has found its extensive use in applications such as estimation of software reliability, allocation of testing resources, evaluation of software quality attributes, performance analysis and testing of software. However, benefits of the SOP can only be reaped if it is developed during early stages of software life cycle and updated for changes in operational structure with the progress in development of software process. In the early stages of software life cycle usage data is available only in linguistic form. This linguistic data may be obtained from previous release of software usage data, marketing surveys, experts or user's opinion or from combinations of these. Moreover, due to limited data resources and large efforts required to convert the gathered data into point estimates, reluctance is observed towards the development of SOP in spite of its numerous benefits. This paper proposes a fuzzy software operational profile (FSOP) approach, which takes input data in the form of linguistic variables from experts and assigns occurrence possibilities to the input parameters. Linguistic data collected from the experts are processed to obtain the resultant fuzzy operational profile. Further, the resultant profile is defuzzified and normalized to estimate occurrence probability of operations. The proposed method has been applied to various software systems and results obtained are compared with existing practice. Besides simplicity, FSOP can easily be altered for changes in operational architecture and frequencies simply by changing the location and value of the affected linguistic variable.

Validating Theories for Brittle Damage

Validating simulated predictions of internal damage within armor ceramics is preferable to simply assessing a model’s ability to predict penetration depth, especially if one hopes to perform subsequent “second strike” analyses. We present the results of a study in which crack networks are seeded by using a statistically perturbed strength, the median of which is inherited from a deterministic “smeared damage” model, with adjustments to reflect experimentally established size effects. This minor alteration of an otherwise conventional damage model noticeably mitigates mesh dependencies and, at virtually no computational cost, produces far more realistic cracking patterns that are well suited for validation against X-ray computed tomography (XCT) images of internal damage patterns. For Brazilian, spall, and indentation tests, simulations share qualitative features with externally visible damage. However, the need for more stringent quantitative validation, software quality testing, and subsurface XCT validation, is emphasized.

생체인식 소프트웨어의 품질 평가모듈에 관한 연구

최근 생체인식 분야는 IT 분야의 보안기술과 함께 빠르게 진전되어 왔다. 현재 생체인식의 중요성이 인식되면서 국내외 생체인식 소프트웨어 시장이 급격히 증가하고 있는 추세이다 이에 따라 생체인식 소프트웨어의 고신뢰성과 고품질 소프트웨어의 요구가 증대되고 있다. 생체인식 소프트웨어의 품질인증을 위해서는 평가항목 및 평가기준이 마련되어 있어야 한다 본 논문에서는 생체인식 소프트웨어의 품질요구와 시험에 관한 표준인 ISO/IEC 12119, 소프트웨어 제품평가를 위한 표준인 91뽀, 평가모듈의 구성을 위한 국제 표준인 ISO/IEC 14598-6을 기반으로 하여 생체인식 소프트웨어 시험을 위한 평가모듈을 개발하였다. 본 논문에서 제시하는 품질 평가모듈은 생체인식 소프트웨어 제품의 구성요소(제품설명서, 사용자문서, 프로그램과 데이터)를 대상으로 하고 있으므로 ISO/IEC 9126-3과 같은 소프트웨어 개발과정에서 적용 가능한 표준과 병행함으로써 소프트웨어의 품질 향상을 기대할 수 있다. The latest biometric field have marched fast with security technology of IT. As importance of present biometrics is realized, internal and external biometrics software market is trend that is soaring. Accordingly, high reliability of biometric software and request of high quality software are enlarged. Evaluation items and criteria must be established for biometric software quality assurance. In this paper, we development the evaluation module for biometric software test based on ISO/IEC 12119 that is the standard about software quality requirement and test, and ISO/IEC 9126 that is standard about evaluation of software product, and ISO/IEC 14598-6 that is the standard about construction of the evaluation module. Constituents of biometric software products(product descriptor, user document program and data) is subject to the quality evaluation module that we developed in this paper, we can expect improvement in the quality of software by using with a standard such as ISO/IEC 9126-3 that can be used in software development process.

Software testing and preventive quality assurance for metrology

Software controlled measuring systems can be approved with the help of different kinds of conformity assessment techniques based either on the final product, the product design or corresponding development and production processes. To validate the software as an integral part of the measuring system, different approaches of software quality assurance have to be applied for different conformity assessment procedures. There are two essential categories of software quality assurance, both of which supplement each other. On the one hand side, analytical methods of software testing, static analysis, and code inspection are used in the scope of conformity assessments of final or intermediate products. On the other hand, preventive audits of software development processes are applied to evaluate and improve appropriate software processes and to consequently support process related conformity assessment procedures. Depending on the validation objectives, validation methods, audit areas, and the appropriate requirements have to be selected and refined. A major problem of validation efforts, namely the process of defining and refining testable requirements, can be solved with the help of international software standards. In Germany, the accredited software testing laboratory at PTB supports software quality in metrology.

Bringing maturity to test [software quality testing

Test is an often forgotten process when organisations aim to improve their software quality practices. The Test Maturity Model is one way of bringing order to the process of making sure software does what it is meant to. The TMM addresses static and dynamic testing. The TMM structure consists of a set of maturity goals. These identify testing improvement goals that must be addressed and satisfied to achieve maturity at that level.

Software Testing and Continuous Quality Improvement. Second Edition. By William E. Lewis. Technical Contributor: Gunasekaran Veerapillai. Published by Auerbach Publications, 2005. Auerbach is an imprint of CRC Press LLC, Boca Raton, Florida, U.S.A. ISBN: 0-8493-2524-2, pp 534.

Software Testing and Continuous Quality Improvement. Second Edition. By William E. Lewis. Technical Contributor: Gunasekaran Veerapillai. Published by Auerbach Publications, 2005. Auerbach is an imprint of CRC Press LLC, Boca Raton, Florida, U.S.A. ISBN: 0-8493-2524-2, pp 534.

Comparative Assessment of Software Quality Classification Techniques: An Empirical Case Study

Software metrics-based quality classification models predict a software module as either fault-prone (fp) or not fault-prone (nfp). Timely application of such models can assist in directing quality improvement efforts to modules that are likely to be fp during operations, thereby cost-effectively utilizing the software quality testing and enhancement resources. Since several classification techniques are available, a relative comparative study of some commonly used classification techniques can be useful to practitioners. We present a comprehensive evaluation of the relative performances of seven classification techniques and/or tools. These include logistic regression, case-based reasoning, classification and regression trees (CART), tree-based classification with S-PLUS, and the Sprint-Sliq, C4.5, and Treedisc algorithms. The use of expected cost of misclassification (ECM), is introduced as a singular unified measure to compare the performances of different software quality classification models. A function of the costs of the Type I (a nfp module misclassified as fp) and Type II (a fp module misclassified as nfp) misclassifications, ECM is computed for different cost ratios. Evaluating software quality classification models in the presence of varying cost ratios is important, because the usefulness of a model is dependent on the system-specific costs of misclassifications. Moreover, models should be compared and preferred for cost ratios that fall within the range of interest for the given system and project domain. Software metrics were collected from four successive releases of a large legacy telecommunications system. A two-way ANOVA randomized-complete block design modeling approach is used, in which the system release is treated as a block, while the modeling method is treated as a factor. It is observed that predictive performances of the models is significantly different across the system releases, implying that in the software engineering domain prediction models are influenced by the characteristics of the data and the system being modeled. Multiple-pairwise comparisons are performed to evaluate the relative performances of the seven models for the cost ratios of interest to the case study. In addition, the performance of the seven classification techniques is also compared with a classification based on lines of code. The comparative approach presented in this paper can also be applied to other software systems.

A survey of software testing practices in alberta

Software organizations have typically de-emphasized the importance of software testing. In this paper, the results of a regional survey of software testing and software quality assurance techniques are described. Researchers conducted the study during the summer and fall of 2002 by surveying software organizations in the Province of Alberta. Results indicate that Alberta-based organizations tend to test less than their counterparts in the United States. The results also indicate that Alberta software organizations tend to train fewer personnel on testing-related topics. This practice has the potential for a two-fold impact: first, the ability to detect trends that lead to reduced quality and to identify the root causes of reductions in product quality may suffer from the lack of testing. This consequence is serious enough to warrant consideration, since overall quality may suffer from the reduced ability to detect and eliminate process or product defects. Second, the organization may have a more difficult time adopting methodologies such as extreme programming. This is significant because other industry studies have concluded that many software organizations have tried or will in the next few years try some form of agile method. Newer approaches to software development like extreme programming increase the extent to which teams rely on testing skills. Organizations should consider their testing skill level as a key indication of their readiness for adopting software development techniques such as test-driven development, extreme programming, agile modelling, or other agile methods.

Test Data Selection and Quality Estimation Based on the Concept of Essential Branches for Path Testing

A new coverage measure is proposed for efficient and effective software testing. The conventional coverage measure for branch testing has such defects as overestimation of software quality and redundant test data selection because all branches are treated equally. These problems can be avoided by paying attention to only those branches essential for path testing. That is, if one branch is executed whenever another particular branch is executed, the former branch is nonessential for path testing. This is because a path covering the latter branch also covers the former branch. Branches other than such nonessential branches will be referred to as essential branches.