Better Software Articles

Please enter an article title, author, or keyword
Test Design: Developing Test Cases from Use Cases

A use case is a sequence of actions performed by a system, which combined together produce a result of value to a system user. Use cases describe the "process flows" through a system based on its actual likely use, so the test cases derived from use cases are most useful in uncovering defects in the process flows during real-world use of the system. Here is an example of how a use case is used to derive and prioritize test cases.

Ross Collard's picture Ross Collard
Application Integration

Building an integrated suite of applications can be complicated, especially when several groups are working on the project in different locations. Here are some risks, as well as recommendations for allowing planning, development, and testing artifacts to be shared between disparate groups.

Sam Guckenheimer's picture Sam Guckenheimer
Untangling Communication

Software development involves sharing critical ideas in a hectic, high-pressure environment. If you want your team to excel in its software projects, it's important to understand the communication circuitry at work in your everyday interactions. Here's a look at the components of the communication process, and five common errors to avoid.

Dale Emery's picture Dale Emery
Lo-Fi GUI Design

This article takes you from “what happens before Lo-Fi Design” (understand the user) to storyboarding (with post-it notes), through final implementation. Other steps include window design (get out the scissors) and simulated execution. This thorough, step-by-step explanation of design method is supplemented with graphics and a usability sidebar.

Luke Hohmann's picture Luke Hohmann
Building Productivity Through Measurement

Collecting and analyzing some simple measures on your application development project will provide a set of building blocks that can be used to manage your projects. This data will improve your success rate and reduce project development risk. Here are some simple measures that can improve your development efforts.

Randy Numbers's picture Randy Numbers
Requirements When the Field Isn't Green

Most advice on requirements gathering is targeted for brand-new "green-field" projects. What about evolving projects? Here's a seven-point strategy for those of us working on maintenance, updates, and legacy documentation.

Karl E. Wiegers's picture Karl E. Wiegers
Calculating the Value of Testing

From an executive's perspective, software testing is not a capital investment in the physical plant, an acquisition, or another readily accepted business expense. A Quality Assurance Manager describes how to present testing as a business-process investment.

James Bullock's picture James Bullock
Bringing Your Test Data to Life

Tracking test results is one of the fundamental tasks that your software testing organization must perform to be successful. Explore how a customized database can enhance that process.

Len DiMaggio's picture Len DiMaggio
Estimating Time, Effort, and Cost

Correctly judging project needs and scope is a challenging task. Here are some techniques and tools for accurately predicting project deliverables.

David Garmus's picture David Garmus
Extreme Testing

Rapid application development means you have to accept that the things you build will need to change. Approach development in a way that makes it easy to transform yesterday’s code into what you need tomorrow. This article explains how testing works in the world of Extreme Programming.

Ronald E. Jeffries's picture Ronald E. Jeffries

Pages

Upcoming Events

Apr 03
Apr 24
Apr 24
May 07