Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • I think your last paragraph sums it up real nice. Commented Oct 5, 2012 at 9:07
  • +1. I meant to vote it up at the time that I elaborated upon it. Apparently I forgot to do so. Commented Oct 7, 2012 at 3:54
  • Is a UI which is a bit too slow a bug? - could I call it Usability Bug? What about the fact that we forgot to tell the developers to add a basket to our web store? Could I call it bug in the requirements? Commented Feb 12, 2014 at 3:57
  • @Tarun you could definitely go that route. The word bug is very easily misunderstood though (usually along the lines of "programmer messed up"), so perhaps it's not the best terminology. Regarding the "UI too slow" issue, I was leaning towards a qualitative measure which is often not specified, yet implicit and expected by clients. In this case, it could almost be both a "usability bug" and a "requirements bug". Commented Feb 12, 2014 at 6:23