Articles

Please enter an article title, author, or keyword
Seven Deadly Sins of Software Reviews

This article describes seven common ways that technical reviews go wrong. Symptoms of the problem and suggestions for getting the review back on track also are presented.

Karl E. Wiegers
From Software Quality Control to Quality Assurance

A two-stage approach to transforming quality control to quality assurance: Quality Assessment (Stage 1) provides objective quantitative evaluation of quality while identifying and fixing software defects early in the development cycle, before they get to the customer and even before testing; Quality Assurance (Stage 2) helps prevent defects from entering the code base by enforcing coding standards during, and by preventing new defects from occurring during times of change through accurate impact analysis.

TechWell Contributor's picture TechWell Contributor
E-Business Testing: Test Techniques and Tools

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 Testing. A chapter on Post-Deployment Monitoring is appended.

Paul Gerrard's picture Paul Gerrard
Measurement Maturity at CMM Level 3

This slide presentation discusses CMM Level 2 and 3. It describes characteristics of a mature measurement program at Level 3 and discusses measurement requirements from an assessor's perspective. The presentation provides examples and offers ideas on good and bad practices/programs. Measurement requirements are embedded throughout the model.

Beth Layman
When Helping Doesn't Help

The term "codependency" was coined to describe an unhealthy coping pattern--one that focuses much on compensating for another party's shortcomings or weaknesses. This week's column asks the question, "Are you involved in codependent relationships with your software developers and project managers?" If so, you may be causing long-term harm in your effort to "do the right thing" for the project at hand.

Lee Copeland's picture Lee Copeland
Project Post Mortem is Not the Time for Criticism

Those who talk about software development process seldom forget to mention the importance of a project post mortem. All books on process management that I have read and all company Web sites that I have visited have something to read about project post mortems. And my concern here is, do we realize the importance just because everyone else is talking about it or are we committed to use it because the concept sounds relevant? And if we are committed, then how do we take the best out of it?

TechWell Contributor's picture TechWell Contributor
Strategies to Maximize the Value of Your Updates

Updates are costly and disruptive. Plan to make certain that your updates are successful.

TechWell Contributor's picture TechWell Contributor
A Problematic Truth

"No Fred, we're not considering you for that promotion. You're too valuable where you are." How many of us have heard those words, or said them at least once to our staff? Sometimes, we use the "too valuable" phrase to avoid discussing problems with a staff member, problems you can bring out in the open and manage.

Johanna Rothman's picture Johanna Rothman
A Child's-Eye View of Software Testing

You've had to explain and justify your job to Management, to Human Resources, and to everyone at your high school reunion. But now comes the ultimate test: Your child's assignment for the next show-and-tell is to describe what her mom or dad does for a living. You scramble for an easy way to explain—maybe for the first time—what you do at the office, but your software testing reference books just don't have enough pictures of cute animals to really do the trick. This book might be just what you're looking for.

Alyn Wambeke
What Is Exploratory Testing?

Exploratory software testing is a powerful and fun approach to testing. In some situations, it can be orders of magnitude more productive than scripted testing. I haven't found a tester yet who didn't, at least unconsciously, perform exploratory testing at one time or another. Yet few of us study this approach, and it doesn't get much respect in our field. It's high time we stop the denial, and publicly recognize the exploratory approach for what it is: scientific thinking in real time. Friends, that's a good thing.

James Bach's picture James Bach

Pages

Upcoming Events

Sep 22
Oct 13
Apr 27