create new tag
, view all tags
A DesignBug occurs when a progam does exactly what was intended, however the intention is flawed, producing results which are not wanted.

It's corrallory is the CodeBug, in which the program fails to do what was intended, or does something in addition to what was intended.

You can use these WikiBadges when submitting a BugReport if you want to fine tune what kind of bug it is (DesignBugs often get rejected, because the program is doing nothing "wrong").

-- MattWilkie - 10 Oct 2004

Surely this is a SpecificationBug?

I thought of calling it that, but design is easier to say and type, and in this circumstance the meaning is nearly equivalent -- in my opinion. It wouldn't bother me much if it were renamed to SpecificationBug. -- MW

Anyway.. there is some good material on here:

We would do well to layout a method so that everyone has a common set of guidelines.

-- MartinCleaver - 11 Oct 2004

DesignBug is right, I think. I may design a car to have three wheels; the specification "it will have 3 wheels" correctly expresses the DesignIntent. However, it is an inherently flawed design, as anyone who has driven a Reliant Robin around a roundabout in a high wind will tell you. A SpecificationBug would be the result if the specification did not express the DesignIntent, and said instead "it will have 2 wheels". By Matt's definition above, I would call that a CodeBug.

-- CrawfordCurrie - 11 Oct 2004

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r4 - 2004-10-11 - CrawfordCurrie
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.