This document contains questions for systematically planning and preparing software testing. -------------------------------------------------------------------------------- Have you planned for an overall testing schedule and the personnel required, and associated training requirements? Have the test team members been given assignments?...   Read Article.

Summary: This checklist is intended to help with the creation of good test cases....   Read Article.

My personal experience of trying to introduce an Inspection programme at a UK software house. First presented at STAR East in Orlando, May 1998....   Read Article.

This paper focuses on the defect analysis aspect of the process improvement task and describes how it was deployed quickly and economically....   Read Article.

Getting process improvement "just right" is difficult. Go too far in the definition of processes, and it really does get too hot, with the heat coming from the people trying to use the processes. On the other hand process definitions that are too short to contain anything of value will leave users in the cold, and then there will be no improvement in...   Read Article.

Admit it: When you're faced with a lengthy checklist for testing, you're tempted to skip steps. Some of the items aren't really necessary, are they? They might be so obvious that there's no need to include them in the list. In this week's column, Elisabeth Hendrickson offers some advice on constructing useful checklists that are brief but complete....   Read Article.

Errors in requirements specifications translate into poor designs, code that does the wrong thing, and unhappy customers. Requirements documentation should be inspected early and often. Anything you can do to prevent requirements errors from propagating downstream will save you time and money. Karl Wiegers shows you how....   Read Article.

Inspections are hard to do for small and immature organizations. This paper shows a way to introduce author reader cycles without going all the way to extreme programming practices....   Read Article.

Inspections are hard to do for small and immature organizations. This paper shows a way to introduce author reader cycles without going all the way to extreme programming practices....   Read Article.

Reviews can be effectively integrated in your workshops, helping participants to create higher quality deliverables. Integrating reviews in your requirements workshops also helps participants to more fully explore how requirements relate to each other. This brief document provides you with a list of steps to employ before, during, and after a collaborative...   Read Article.

The succession of the Capability Maturity Model for Software (SW-CMM) and the System Engineering Capability Maturity Model (EIA/IS 731) by the Capability Maturity Model-Integrated (CMMI) will expose many organizations that currently use either the SW-CMM or the SE-CMM to the challenge of an effective and efficient transition from the old models to the...   Read Article.

This document identifies guidelines that review high-integrity software requirements documents in nuclear power plants. The topic areas are conformance with the SRP, accuracy, functionality, reliability, robustness, maintainability, security, timing, and human-computer interaction. A checklist for the requirements and their ordering for a Software Requirements...   Read Article.

This document identifies guidelines that review high-integrity software requirements documents in nuclear power plants. The topic areas are conformance with the SRP, accuracy, functionality, reliability, robustness, maintainability, security, timing, and human-computer interaction. A checklist for the requirements and their ordering for a Software Requirements...   Read Article.

Driving usability improvement in a company with over 100 different remotely-located software development organizations, each using independent development processes, presents specific Software Quality challenges. This paper describes the usability acceptance testing and usability risk assessment approaches that one organization instituted within this...   Read Article.

This article gives an overview of testing teams, including the common issues they encounter. It also discusses changes that can be implemented to have an effective and efficient testing team....   Read Article.

Every problem-solving activity in an organization requires some learning. Both the stakeholders and the facilitators of the organization need to learn as they go through change. This paper describes our fist experiences with facilitating process improvement and problem solving by focusing on congruence, building trust experiences with facilitating process...   Read Article.

A brief overview to reviews, inspections, and walkthroughs--an essential technique to increase quality and enhance team collaboration....   Read Article.

This paper describes twenty techniques for testing E-Business applications. These techniques were introduced in the companion paper, “Risk-Based E-Business Testing, Part 1, Risks and Test Strategy." The techniques are described under five categories: Static Testing, Test Browsing, Functional Testing, Non-Functional Testing, and Large-Scale Integration...   Read Article.

The biggest obstacle in the software industry is lack of time to do the job well. Negotiation can buy valuable time and help management avoid blunders. This paper is about estimating and negotiating test schedules....   Read Article.

This paper aims to emphasize the importance of efficient and thorough review of test cases. A methodical approach to test case review suggesting that the reviews are done for each phase of testing is presented. Areas to focus on during the review have been identified and explained. This paper also contains a comprehensive checklist for test cases review...   Read Article.