In the United States alone, businesses will spend close to $440 billion to fix the problems caused by the Year 2000 (Y2K) dilemma. In 1999, most companies will be testing their solutions. Face it, there's not much time left to make sure that your company's Y2K software really works. And no business can afford to take that kind of risk. This book gives you a complete plan of attack for thoroughly testing all of your software solutions to the Y2K problem.

Recent rough estimates are that the U.S. Department of Defense (DoD) spends at least $38 billion a year on the research, development, testing, and evaluation of new defense systems; approximately 40 percent of that cost-at least $16 billion-is spent on software development and testing. There is widespread understanding within DoD that the effectiveness of software-intensive defense systems is often hampered by low-quality software as well as increased costs and late delivery of software components. Given the costs involved, even relatively incremental improvements to the software development process for defense systems could represent a large savings in funds. And given the importance of producing defense software that will carry out its intended function, relatively small improvements to the quality of defense software systems would be extremely important to identify. DoD software engineers and test and evaluation officials may not be fully aware of a range of available techniques, because of both the recent development of these techniques and their origination from an orientation somewhat removed from software engineering, i.e., from a statistical perspective. The panel's charge therefore was to convene a workshop to identify statistical software engineering techniques that could have applicability to DoD systems in development.

Managing Information Technology Resources in Organizations in the Next Millennium contains more than 200 unique perspectives on numerous timely issues of managing information technology in organizations around the world. This book, featuring the latest research and applied IT practices, is a valuable source in support of teaching and research agendas.

This updated and reorganized Fifth edition of Software Testing: A Craftsman's Approach applies the strong mathematics content of previous editions to a coherent treatment of software testing. Responding to instructor and student survey input of previous editions, the authors have streamlined chapters and examples. The Fifth Edition: Has a new chapter on feature interaction testing that explores the feature interaction problem and explains how to reduce tests Uses Java instead of pseudo-code for all examples including structured and object-oriented ones Presents model-based development and provides an explanation of how to conduct testing within model-based development environments Explains testing in waterfall, iterative, and agile software development projects 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, Fifth 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 is a valuable reference for software testers, developers, and engineers.

In architecting dependable systems, what is required to improve the overall system robustness is fault tolerance. Many methods have been proposed to this end, the solutions are usually considered late during the design and implementation phases of the software life-cycle (e.g., Java and Windows NT exception handling), thus reducing the effectiveness error and fault handling. Since the system design typically models only normal behaviour of the system while ignoring exceptional ones, the implementation of the system is unable to handle abnormal events. Consequently, the system may fail in unexpected ways due to faults.It has been argued that fault tolerance management during the entire life-cycle improves the overall system robustness and that different classes of threats need to be identified for and dealt with at each distinct phase of software development, depending on the abstraction level of the software system being modelled.This book builds on this trend and investigates how fault tolerance mechanisms can be applied when engineering a software system. In particular, it identifies the new problems arising in this area, introduces the new models to be applied at different abstraction levels, defines methodologies for model-driven engineering of such systems and outlines the new technologies and validation and verification environments supporting this.

This overview of software testing provides key concepts, case studies, and numerous techniques to ensure software is reliable and secure. Using a self-teaching format, the book covers important topics such as black, white, and gray box testing, video game testing, test point analysis, automation, and levels of testing. Includes end-of-chapter multiple-choice questions / answers to increase mastering of the topics. Features: • Includes case studies, case tools, and software lab experiments • Covers important topics such as black, white, and gray box testing, test management, automation, levels of testing, • Covers video game testing • Self-teaching method includes numerous exercises, projects, and case studies