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:

• http://www.stickyminds.com/sitewide.asp?ObjectId=6552&Function=DETAILBROWSE&ObjectType=ART

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