Skip to content
Tyner Blain logo

Tyner Blain

Software product success.

  • Main
  • Profile
  • Tyner Blain
  • Subscribe
Requirements / Software requirements specification / Testing

How To Deal With Untestable Requirements – Rewrite Them

Posted on: November 30, 2005May 29, 2006

The premise behind the rule that requirements must be testable is driven by the goal of avoiding ambiguous language in your requirements. Statements like “the application must have a clean user interface” or “search response times must be fast” are also untestable, but more because of language than anything else.

Categories

Archives

Who Should Read Tyner Blain?

These articles are written primarily for product managers. Everyone trying to create great products can find something of use here. Hopefully these articles help you with thinking, doing, and learning.

Welcome aboard!

Recent Posts

  • Reaching Consensus on How
  • The Secret of Diminishing Returns
  • When Clocks Aren’t Reliable
  • Coherence, Outcomes, and Dictation
  • Problems in the Solution
Niche Blog WordPress Theme by Fahim Murshed