Re: Template open/save behavior

It's not a bug...;-)

--
Paul Berkowitz
MVP MacOffice
Entourage FAQ Page: <http://www.entourage.mvps.org/faq/index.html>
AppleScripts for Entourage: <http://macscripter.net/scriptbuilders/>

Please "Reply To Newsgroup" to reply to this message. Emails will be
ignored.

PLEASE always state which version of Microsoft Office you are using -
**2004**, X or 2001. It's often impossible to answer your questions
otherwise.


From: Beth Rosengard <bethrosengard@xxxxxxxxxxxxx>
Newsgroups: microsoft.public.mac.office.word
Date: Sat, 18 Feb 2006 12:32:45 -0800
Conversation: Template open/save behavior
Subject: Re: Template open/save behavior

Hi John,

I said I wasn't going to get into this debate again and, of course, I did
:-). However, I'm done now. Nothing I say will change your opinion and
vice versa. And, besides, CyberTaz just summed it all up in his post and
did so quite definitively.

Sorry, John, the only logic in your definitions is one based on a personal
agenda and it's not an agenda I buy into :-). You may now have the last
word ...

Cheers,

Beth


On 2/16/06 10:33 PM, in article C01BB956.2E743%john@xxxxxxxxxxx, "John
McGhie [MVP - Word and Word Macintosh]" <john@xxxxxxxxxxx> wrote:

The one most commonly cited internationally is:
http://www.istqb.org/fileadmin/media/glossary-1.0.pdf

Wow! Now that is really interesting. All this time I have been arguing
over
the meaning of the term "bug" and taking your word for the meaning of the
term
"defect". But according to the source you've quoted, the meaning of
"defect"
is synonymous with what you have called "Coding Defect" and I have called
"bug"!

Ummm... No, it very specifically did NOT say that :-)

Let me back up a minute and explain (for anyone else still reading this :-)
how I came to that conclusion. On the page referenced above, the entry for
"bug" says "See defect." The entry for "defect" says:

A flaw in a component or system that can cause the component or system to
fail to perform its required function, e.g. an incorrect statement or data
definition. A defect, if encountered during execution, may cause a
failure
of the component or system.

It said "A flaw in a component or system that can cause the component or
system to fail to perform its required function..."

It did NOT say "A _coding_ defect...". This distinction is utterly critical
to software quality management. A Defect is anything the customer didn't
want (even including a schedule or budget overrun). The *cause* of the
defect gets worked out later in the process.

Does it do what the CUSTOMER really wanted? If yes, it's good. No matter
how weird the software's behaviour, if that's the way the customer wants it,
it is good.

If not, it's a Defect/Bug. No matter how reliable, stable, or conforming to
specifications it is, if the customer didn't want it that way, it's a bug.

If it's a bug, then we can sit down and work out how it got that way. We
might at that stage discover it's a coding bug, but it's more likely these
days to be a design bug or a specification bug or an analysis bug. It often
IS a "systemic failure", where the "system" in question is the system by
which we manage the software development process.

The required function is, of course, determined by the software
designer/manufacturer. It's *his* software.

Well, that's the opposite of what the majority of the industry believes. If
I paid for it, it's *my* software. I'm the customer, the
designer/manufacturer are working for me. I say what I want, not them.

In the case of "shrink-wrap" software (i.e. Off-the-shelf, ready to install
software) such as Microsoft Office, nothing changes. If it doesn't do what
the purchaser wants, it's defective/faulty/flawed/buggy.

Since the sad reality of life is that no-one could afford to make or buy
software that didn't have at least SOME bugs in it, every manufacturer heads
for their lawyers to write an End User Licensing Agreement that basically
says "It is like it is, and by installing it, you indicate that you agree
that you wanted it just like that." Doesn't alter the state of the
software; it just gives us the option of either not buying it; or not
complaining about it. But it's still buggy :-)

Now it may be that the *user* would like to see a different result and
believes that the designer has incorrectly understood the required function.
From the user's standpoint, the software has a design flaw (or defect), but
not a bug.

Yep. That's a bug. One of (I think it's 29) different causes of a defect,
but it's still a bug.

I think that the International Software Testing Qualification Board" needs
to
update its glossary and redefine "bug" or redefine "defect", because as the
Glossary now reads, a bug is exactly what I have contended all along.

You be sure to write and tell 'em :-)

I ain't weepin' :-). "Bug" absolutely HAS had that meaning within the
industry and your source proves it.

Oh. Well, you be sure to alert the ISO and the IEEE to this new discovery.
I suspect it will come as something of a shock to all of us working in the
industry, after all those years of trying to make what the customer wanted;
but there you go :-)


.

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
    ... I'm not going to continue this ad infinitum because you and I have already ... 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. ... was by design and a defect that was not intended. ...
    (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: Template open/save behavior
    ... This page does not contain a definition of the term "bug". ... ISO standards or Carnegie Mellon University publications "bug" is defined as ... those standards is an official glossary of industry terms and definitions. ... of flaw (or defect) which was not intended by the designer of the software. ...
    (microsoft.public.mac.office.word)