By writing better requirements

This link is to a series of blog posts on the V-model.  The V-model is a testing and validation framework for software development projects.

This article is useful for business analysts new to the software development world and highlights key quality gates in the development and implementation of software.  The articles focus on what a Business Analyst or Project Manager should know about the process.

The individual posts listed are

<font>Introduction</font>

<font>The value of testing</font>

<font>The V-Model and the development process</font>

<font>Verifying on the way into the development cycle</font>

<font>Testing and verifying on the way out of the development cycle</font>

<font>Extending the V-Model</font>

 

Deep analysis of the tasks that must happen in an iteration - development, analysis, testing, etc.  Focus on the problems with staggering them too much, and suggestions on how to properly organize the team around those tasks.

Article compares different approaches to testing the workflow of an application - specifically a web application.  Detailed analysis of the maintenance & skill level tradeoffs for each approach.  Also touches on Selenium and Watir approaches.

This paper gives a complete description of code coverage analysis (test coverage analysis), a software testing technique.

An article on testing strategy for non-functional requirements that stimulated a fantastic discussion about functional vs. non-functional requirements. Great points are made both to eliminate and to highlight the distinctions. The strategy for developing a test plan is good, and worth reading alone, but this article is fun in that it went in a completely different direction with a very well informed debate.

An excellent introduction to, overview of and fairly comprehensive discussion on continuous integrations. Here's an excerpt from the page: "Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly. This article is a quick overview of Continuous Integration summarizing the technique and its current usage."