Validation/Testing/UAT

Managing Data Defects in the Software Development Process

For the purpose of this discussion, let me define data defects in a software development process as defects caused when improper data setup manifests itself as “application errors.” I ran into this situation recently when I was asked to define requirements to fix a couple of defects that had been …

Read More

Don’t Forget About the Testers

“Karl – how’s testing going on Project Zeta?”“Not too good, Michael. I can’t figure out which features have been implemented, it looks like several key requirements have changed but I don’t know what the new details are, and I have a whole slew of untestable requirements.”“Some of those ‘the system …

Read More

The Value of Peer Reviews

You’re near the end of a long requirements phase, you’ve been working 60+ hours a week, and the project manager is pressuring you to deliver a final deliverable. So you do a quick spell check and proof read, and then toss it over for final review to business, development, test, …

Read More

Software Requirements: Validation vs. Verification, Part 2

In my last post, I explained the difference between validation and verification. In this post, I’ll further explain validation and provide some best practices. To ensure that software requirements validation goes smoothly, the following questions should be posed: Are all requirements necessary and sufficient? Do lower level detailed software requirements …

Read More

Software Requirements: Validation vs. Verification

In software development, validation and verification are key elements to a successful project, but often the terms are mis-understood. Per the CMMI guidelines, validation is used to demonstrate that the product will meet it’s intended use, and verification demonstrates that the product matches the specified software requirements. Validation ensures that …

Read More

Requirements Review: Team Effort – Early and Often

How often should I be reviewing my requirements with members of my project team? By requirements I mean everything from high-level business needs (e.g. stakeholder requests, business requirements, vision and problem statements) to the most granular requirements (aka shall statements, functional and supplementary requirements and the like). My answer (with …

Read More

User Acceptance Testing Is Hardly Testing

A good project team relies on many kinds of testing to help ensure a high-quality release. Developers use unit and integration tests to verify functionality of their individual modules. Quality assurance personnel use performance and reliability testing to verify service levels of the system as a whole. While each of …

Read More

Making sure your spec is reviewed.

Do you ever get the uneasy feeling that no one is reading your software requirements specification? The reality is that the development team is probably busy on the last release and that the business stakeholders are busy doing their jobs in the business. What is a lonely Product Manager to …

Read More