This guide supplies innovative ideas concerning software quality control and the necessary theoretical and practical considerations of software testing needed by today's data processing practitioners. Features easy-to-understand discussions of software testing methods and contains example test plans designed for real world information systems.
Offers advice on designing and implementing a software test automation infrastructure, and identifies what current popular testing approaches can and cannot accomplish. Rejecting the automation life cycle model, the authors favor limited automation of unit, integration, and system testing. They also present a control synchronized data-driven framework to help jump-start an automation project. Examples are provided in the Rational suite test studio, and source code is available at a supporting web site. Annotation copyrighted by Book News, Inc., Portland, OR.
This updated and reorganized fourth edition of Software Testing: A Craftsman's Approach applies the strong mathematics content of previous editions to a coherent treatment of Model-Based Testing for both code-based (structural) and specification-based (functional) testing. These techniques are extended from the usual unit testing discussions to full coverage of less understood levels integration and system testing. The Fourth Edition: Emphasizes technical inspections and is supplemented by an appendix with a full package of documents required for a sample Use Case technical inspection Introduces an innovative approach that merges the Event-Driven Petri Nets from the earlier editions with the "Swim Lane" concept from the Unified Modeling Language (UML) that permits model-based testing for four levels of interaction among constituents in a System of Systems Introduces model-based development and provides an explanation of how to conduct testing within model-based development environments Presents a new section on methods for testing software in an Agile programming environment Explores test-driven development, reexamines all-pairs testing, and explains the four contexts of software testing Thoroughly revised and updated, Software Testing: A Craftsman’s Approach, Fourth Edition is sure to become a standard reference for those who need to stay up to date with evolving technologies in software testing. Carrying on the tradition of previous editions, it will continue to serve as a valuable reference for software testers, developers, and engineers.
Teaches readers how to test and analyze software to achieve an acceptable level of quality at an acceptable cost Readers will be able to minimize software failures, increase quality, and effectively manage costs Covers techniques that are suitable for near-term application, with sufficient technical background to indicate how and when to apply them Provides balanced coverage of software testing & analysis approaches By incorporating modern topics and strategies, this book will be the standard software-testing textbook
For more than 20 years, this has been the best selling guide to software engineering for students and industry professionals alike. This edition has been completely updated and contains hundreds of new references to software tools.
This Handbook provides critical, interdisciplinary contributions from leading international academics on the theory and methodology, practical applications, and broader context of Management Information Systems, as well as offering potential avenues for future research
C. Amting Directorate General Information Society, European Commission, Brussels th Under the 4 Framework of European Research, the European Systems and Soft ware Initiative (ESSI) was part ofthe ESPRIT Programme. This initiative funded more than 470 projects in the area ofsoftware and system process improvements. The majority of these projects were process improvement experiments carrying out and taking up new development processes, methods and technology within the software development process ofa company. In addition, nodes (centres ofexper tise), European networks (organisations managing local activities), training and dissemination actions complemented the process improvementexperiments. ESSI aimed at improving the software development capabilities of European enterprises. It focused on best practice and helped European companies to develop world class skills and associated technologies to build the increasingly complex and varied systems needed to compete in the marketplace. The dissemination activities were designed to build a forum, at European level, to exchange information and knowledge gained within process improvement ex periments. Their major objective was to spread the message and the results of experiments to awider audience, through a variety ofdifferent channels. The European Experience Exchange ~UR~X) project has been one ofthese dis semination activities within the European Systems and Software Initiative.~UR~)( has collected the results of practitioner reports from numerous workshops in Europe and presents, in this series of books, the results of Best Practice achieve ments in European Companies over the last few years.
"By incorporating systematic controls throughout the development process, the methods in Client-Server Software Testing on the Desktop and the Web can help any organization save time and money while building in quality for distributed systems."--BOOK JACKET.
Addressing various aspects of object-oriented software techniques with respect to their impact on testing, this text argues that the testing of object-oriented software is not restricted to a single phase of software development. The book concentrates heavily on the testing of classes and of components or sub-systems, and a major part is devoted to this subject. C++ is used throughout this book that is intended for software practitioners, managers, researchers, students, or anyone interested in object-oriented technology and its impacts throughout the software engineering life-cycle.
Software is one of the most important products in human history and is widely used by all industries and all countries. It is also one of the most expensive and labor-intensive products in human history. Software also has very poor quality that has caused many major disasters and wasted many millions of dollars. Software is also the target of frequent and increasingly serious cyber-attacks. Among the reasons for these software problems is a chronic lack of reliable quantified data. This reference provides quantified data from many countries and many industries based on about 26,000 projects developed using a variety of methodologies and team experience levels. The data has been gathered between 1970 and 2017, so interesting historical trends are available. Since current average software productivity and quality results are suboptimal, this book focuses on "best in class" results and shows not only quantified quality and productivity data from best-in-class organizations, but also the technology stacks used to achieve best-in-class results. The overall goal of this book is to encourage the adoption of best-in-class software metrics and best-in-class technology stacks. It does so by providing current data on average software schedules, effort, costs, and quality for several industries and countries. Because productivity and quality vary by technology and size, the book presents quantitative results for applications between 100 function points and 100,000 function points. It shows quality results using defect potential and DRE metrics because the number one cost driver for software is finding and fixing bugs. The book presents data on cost of quality for software projects and discusses technical debt, but that metric is not standardized. Finally, the book includes some data on three years of software maintenance and enhancements as well as some data on total cost of ownership.
