Search

Software testing is the critical component of the software development life cycle. Cost of software testing would affect the cost benefit trade-off of a development organization. Any reduction in the cost of software testing would help to deliver the product to the customer at less cost. The existing research is to find the ways to reduce the testing cost. In this paper, an approach to test case design which reduces software testing cost in black box environment has been proposed. This type of approach has not been used earlier. The proposed approach reduces the total number of test cases in black box environment. This reduced test case set covers total functionality and ensures the quality of the product. The proposed approach is applied on four case studies and found that the reduction in testing cost is ranging between 27 and 36 percent. Hence, by using the proposed approach the software testing cost can be reduced considerably. [ABSTRACT FROM AUTHOR]

This article explores the critical factors and issues that impede the performance of software reliability modeling science. The literature review indicates that software reliability models have not delivered the desirable deliverables that they are intended to realize. The current work suggests that the reasons for such performance incompetence of the software reliability modeling are attributed to eight major causes. Based upon the findings of the current study, a simple framework is proposed to provide guidelines to developing software organizations in order to improve the performance of software reliability modeling concept. [ABSTRACT FROM AUTHOR]

This article analysis non-technical aspects of software quality perception and proposes further research activities for this subject. Cognitive science, psychology, micro economics and other human-oriented sciences do analyze human behavior, cognition and decision processes. On the other hand engineering disciplines, including software engineering, propose many formal and technical approaches for product quality description. Linkage between technical and subjective quality has been subject of research in areas related to food and agricultural applications and in this article we propose analysis of professional product perception which beyond doubt is a software product. This new research is called Software quality psychology. [ABSTRACT FROM AUTHOR]

Growing Web Service usage, design and composition methods require precise and reliable information about Web Services quality. Such quality description has to be compatible with universal software quality models, so designers will be able to gather and decompose quality requirements addressing them to different IT solution components, including used Web Services. This article proposes Web Services Quality Model based on ISO/IEC Software product Quality Requirements and Evaluation (SQuaRE) model. Model consists of three perspectives Internal Web Service Quality, External Web Service Quality and Web Service Quality in Use. Prior to model definitions the authors present extended search on quality related issues in literature regarding Web Services and software in general. Authors refer to general need for measuring and publication of Web Service Quality measures considering limited trust and temporal character of measures. This article does not include technical solutions, but focuses on quality model showing its relevance to business needs. [ABSTRACT FROM AUTHOR]

This paper proposes a fuzzy Analytic Hierarchy Process model for evaluating the software quality of vendors. The criteria of software quality adopt the international norm ISO/IEC9126-1:2001 which includes of six criteria. The fuzzy AHP model applies the modified fuzzy Logarithmic Least Squares Method (LLSM) in this software criteria models. The proposed model can help the developers and testers to evaluate the vendors' software applications and select the best alternative under uncertain environment. [ABSTRACT FROM AUTHOR]

For users, a software product frequently corresponds to a black box that must effectively support their business processes. Consequently, what a stakeholder seeks is a software product that possesses both required functionality and required quality. Young, immature companies usually can only afford developing functionalities, while mature organizations can develop quality, as well. In this sense, the level of quality observed in a software product is an indicator of the level of maturity of its developer. One may even say that because functionalities are always in a product and quality only sometimes, quality is a more restrictive indicator. Having this in mind, in this chapter we present software quality engineering from both implementation and managerial perspectives, discuss aspects of functionality-quality conflict in the economic and business dimensions, and finally give a few practical observations and recommendations that might find merit in the real, software development lifecycle. [ABSTRACT FROM AUTHOR]

Presents an overview of software verification and validation (V#x0026;V), including the software V#x0026;V techniques that can be applied to evaluate and test the software in each life-cycle activity. Identification of software V#x0026;V as a technical discipline of systems engineering; Relationship of V#x0026;V to the software life-cycle process; Description of standards and guidelines for planning and managing software V#x0026;V.

Focuses on the testing of graphical user interfaces (GUI) in software design. Suggestion that GUI have become increasingly easy to design using contemporary tool sets, and they make software easy to use for all types of users; Problems in testing GUI system; Factors influencing why a GUI testing strategy must be systematic and scalable.

Discusses how software organizations choose to invest in quality and testing. Suggestion that testing is a risk management exercise that helps the organization reduce the likelihood of bearing unanticipated future; Importance of considering the desired test process when selecting the development model; Information on software defects found by test design techniques.

Discusses issues that are most applicable to tool support for test execution automation, the most popular type of test automation. Identification of test automation as an automated execution of test cases including automated verification of the test results; Types of tool that support testing activities; Suggestion that the main role of a testing tool is usually to support, not replace, a person's efforts.

Describes the quality control heritage of software quality assurance applied in practices with industrial quality control in the U.S. Application of statistical quality control in the manufacturing processes; Changes in the formal programs directed to hardware design and development; Details on the various aspects of software development and its management.

Describes the nature and operation of the Personal Software Process (PSP). Production of quality software systems; Basis in the design of PSP; Citations of the steps in the PSP process planning.

The article reports that software testing refers to methods in which a piece of finished software is run on actual data. Analysis refers to methods in which software or other development products are examined for necessary or sufficient correctness. This article does not consider the more formal kinds of analytical methods, in which the goal is to prove correctness and for which a set of formal system specifications is necessary, but it includes descriptions of the less formal methods associated with and normally included in discussions of testing.

This article focuses on automatic test software. To test a program, a number of inputs are applied and the program response is observed. If the response is different from what was expected, the program has at least one defect. Testing can have one of two separate objectives. During debugging, the aim is to increase the reliability as fast as possible, by finding faults as quickly as possible. On the other band, during certification, the objective is to assess the reliability; thus the fault-finding rate should be representative of actual operation. Software testing tools can be expensive. The cost to license a tool can be just a fraction of the overall cost. The testers need to understand the tools and become familiar with them. The use of the tools needs to be incorporated in the process.

Quality of Software developed in any Software Development Life Cycle (SDLC) is related to quality of the "Process" applied. Chaos in software development process depends on many factors. Watts Humphrey developed the Personal Software Process (PSP) [1][2] and Team Software Process (TSP) [3] to improve the software process that in turn improve the quality of software products. The PSP provides software engineers with a methodology for consistently and efficiently developing high-quality products. PSP has been shown to substantially improve the Software Engineering ability of an individual at various levels. Motivated by PSP, this paper proposes a new metric "Initial Maturity Gap (IMG)" to measure the understanding of an individual about Software development life cycle (SDLC). This measure is used to take necessary action so that all the professionals who are going to be involved in a project have uniform mindset, which will reduce the chaos in SDLC. This metric can be used in different phases of SDLC as well as the personal process improvement approaches like PSP. We can reduce the Chaos in software processes by reducing the value of IMG. [ABSTRACT FROM AUTHOR]

Provides information on the white-box testing, a test methods that rely on the internal structure of the software. Use of the white-box approach to generate test cases; Requirements of a simple and complex white-box approach; Effectiveness of white-box testing.

Provides information on test case generator, an automated software tool that creates test cases. Suggestion that creating test cases is the most essential activity in software testing; Key to understanding specification- based test case generation; Demand for automated test case generators.

Presents an article that discusses about the ways to determined the software assurance in the industry. Examination on the quality and reliability of the software; Difference between the indirect and direct software assurance techniques; Details of the combination of both qualitative and quantitative approaches and its impact on software quality testing.

The article provides an overview of Michael S. Deutsch career history. He is a widely known for his work in software quality methods and as an author of several textbooks on software. He has acquired over 23 years of experience in software engineering at Hughes Aircraft Co. He has served on the editorial board of "IEEE Transactions on Software Engineering."