In this article, Demetrius Madrigal and Bryan McClain explains why you should not take user feedback or requests for design changes at face value.
The Dangers of Design by User
Articles
Knowledge
Reviewing Requirements for Testability
Modern software development approaches like Agile and Scrum support a strong collaboration between all member of the software development team, software testers and business analysts included. Even if you don’t use a method like Behavior-Driven Development (BDD) or Specification by Example, checking the fact that you will be able to actually test your requirements is […]
Read More
Articles
Knowledge
Understanding System Analysis Models
This article is an extract of the “Complete Systems Analysis” written by James and Suzanne Robertson. It explains the basics of analysis models and emphasize that the important thing to remember is that modeling tools are complementary. Each shows one aspect of the system. Together, they make a complete working model of the system.
Read More
Blogs
Knowledge
Find Missing Requirements
This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.
Read More
One thought on “The Dangers of Design by User”
Comments are closed.