Re: Template open/save behavior

Hi John,

I'm not going to continue this ad infinitum because you and I have already
had this discussion ad infinitum. But I have to respond to just a few
points :-).

On 2/11/06 5:05 PM, in article C014D4FD.2DF7C%john@xxxxxxxxxxx, "John McGhie
[MVP - Word and Word Macintosh]" <john@xxxxxxxxxxx> wrote:

Let me be clear on this :-) *I* do not argue this, the "Software Industry"
argues this. You're not arguing with "me", you're arguing with the
International Standards Organization and Carnegie Mellon University :-)

What I am espousing is not *my* opinion, it's the software industry's
current best practice.

Can you point me to where this is written? And when you say "software
industry", are you talking about some unilateral organization? I wasn't
aware that such a thing existed. Are you saying that every software company
accepts "your" definition of these terms? And if the ISO defines "bug" as
you have stated, but the majority of people understand it otherwise, how is
their definition useful?

The term "Bug" is simply slang for "Defect". The software industry has now
discovered that all the really expensive problems happen in places OTHER
than at the coder's workstation.

As I've said before, the term "bug" is a commonly accepted term for a type
of flaw (or defect) which was not intended by the designer of the software.
The fact that *some* software manufacturers/designers choose to redefine the
term so that it includes what are commonly referred to as "design flaws" ­
and thus equate the term "bug" with "flaw" or "defect" ­ does not make the
*commonly accepted* meaning any less commonly accepted.

If we were all to accept "your" definition (a bug is a defect is a flaw is a
bug), then we would need *new* terms to distinguish between a defect that
was by design and a defect that was not intended. Since we already have
those terms ("design flaw" and "bug"), why create new ones? And what terms
would *you* use to distinguish between the two?

Respectfully (but in total disagreement on the basis of usefulness in
communication and discourse ­ and regardless of the ISO or Carnegie Mellon
University :-),

Beth


.

Relevant Pages

  • Re: Template open/save behavior
    ... ISO standards or Carnegie Mellon University publications "bug" is defined as ... unintentional flaws and design flaws (or, if you prefer, Design, Coding and ... is interchangeable with "defect" does not make it so. ...
    (microsoft.public.mac.office.word)
  • Re: Template open/save behavior
    ... "defect". ... Does it do what the CUSTOMER really wanted? ... specifications it is, if the customer didn't want it that way, it's a bug. ... days to be a design bug or a specification bug or an analysis bug. ...
    (microsoft.public.mac.office.word)
  • Re: Template open/save behavior
    ... A defect, if encountered during execution, may cause a failure ... Does it do what the CUSTOMER really wanted? ... specifications it is, if the customer didn't want it that way, it's a bug. ... days to be a design bug or a specification bug or an analysis bug. ...
    (microsoft.public.mac.office.word)
  • Re: Template open/save behavior
    ... A defect, if encountered during execution, may cause a failure ... Does it do what the CUSTOMER really wanted? ... specifications it is, if the customer didn't want it that way, it's a bug. ... days to be a design bug or a specification bug or an analysis bug. ...
    (microsoft.public.mac.office.word)
  • Re: Why does that surprise anyone?
    ... But if a design defect puts users at risk, ... Windows and MacOS are all equally complex and made out of the ... Linux desktop in about an hour. ...
    (microsoft.public.windowsxp.general)