Goodbye, My Good Friend.

Bob Noel wrote:
In article ,
Matt Whiting wrote:


Only if the software engineers made mistakes. If they wrote the
software correctly against the requirements, then there would be nothing
to test. Then again, that assumes that the buyer knew what they wanted
and wrote the requirements accordingly. :-)


of course there is still something to test.

Don't confuse testing to detect an error with testing to show the customer
that the system is operating correctly.


That should be a demonstration, not a test.
Unfortunately, since all software systems are still delivered with
defects, it does constitute a test. :-)

Matt

In article ,
Matt Whiting wrote:

Don't confuse testing to detect an error with testing to show the customer
that the system is operating correctly.

That should be a demonstration, not a test.
Unfortunately, since all software systems are still delivered with
defects, it does constitute a test. :-)

Try demonstrating the correct operation of the TCAS II algorithms. :-/

--
Bob Noel
no one likes an educated mule

Bob Noel wrote:

In article ,
Matt Whiting wrote:


Don't confuse testing to detect an error with testing to show the customer
that the system is operating correctly.

That should be a demonstration, not a test.
Unfortunately, since all software systems are still delivered with
defects, it does constitute a test. :-)


Try demonstrating the correct operation of the TCAS II algorithms. :-/


Shouldn't be much harder then testing them exhaustively. ;-)

Matt

If they wrote the software correctly against the requirements, then there would be nothing to test.

How do you convince the customer that the software is written correctly
against the requirements? Especially given the experience most of us
have with software?

Jose
--
Quantum Mechanics is like this: God =does= play dice with the universe,
except there's no God, and there's no dice. And maybe there's no universe.
for Email, make the obvious change in the address.

Jose wrote:

If they wrote the software correctly against the requirements, then
there would be nothing to test.


How do you convince the customer that the software is written correctly
against the requirements? Especially given the experience most of us
have with software?

You can't, I was being facetious. Since the OP writes software, I knew
he'd understand.

However, he also understands that only a very, very naive customer
believes that the tests you show them ensures that the software is
written correctly against the requirements.

Software development is still progressing, albeit glacially, but we have
a long ways to go. As long as the s/w community insists on using
substandard tools such as C++ and such, things will progress slowly.


Matt

On Mon, 15 Aug 2005 01:00:38 GMT, Matt Whiting
wrote:

Don't care if you don't make mistakes.
You still need to verify the correction
operation of the system.


Well put.

Mike Weller

"the correction operation of the system" is "well put?" Herein lies the
problem.

Matt

That was my point. I hate smileys.

Mike Weller

On Mon, 15 Aug 2005 10:38:09 GMT, Matt Whiting
wrote:

snip here and there,

You can't, I was being facetious. Since the OP writes software, I knew
he'd understand.

However, he also understands that only a very, very naive customer
believes that the tests you show them ensures that the software is
written correctly against the requirements.

Software development is still progressing, albeit glacially, but we have
a long ways to go. As long as the s/w community insists on using
substandard tools such as C++ and such, things will progress slowly.


Matt

Now you've really really got my interest.

Substandard?

What is standard? I really do want to improve on C++, but I haven't
seen anything better.

Please don't say Ada.

Mike Weller

"Mike Weller" wrote in message
news:1124124085.7f7946b83a82b2e392e47822e8419de4@o nlynews...
Software development is still progressing, albeit glacially, but we have
a long ways to go. As long as the s/w community insists on using
substandard tools such as C++ and such, things will progress slowly.


Matt

Now you've really really got my interest.

Substandard?

What is standard? I really do want to improve on C++, but I haven't
seen anything better.

(getting sucked into an off-topic thread...)

I think he's talking about the fact that development tools still allow
programmers to do stupid things. For example, Java and C# add a layer of
protection, making it more difficult for programmers to screw things up.
They are still procedural languages, and it may be that programming really
needs a whole paradigm shift to some other sort of programming. Charles
Simonyi was pushing something he was calling "intentional programming" a
while back...so far, nothing real has come of that, but the general thought
that getting a little further from the underlying Turing machine may reduce
mistakes is still valid, IMHO.

That said, most of the problems with programming stem from how careless
people are while doing it. As a programmer myself, I am well aware of the
difference between well-written code and poorly-written code. Most code is
poorly-written, IMHO. This is true through all phases of implementation,
from the original design and architecture, through the actual coding, and
finally with respect to testing, both on the part of the programmer as well
as on the quality assurance folks, should they actually exist.

For the most part, engineering in other technical areas tries to take into
account human error. Structures are built with some margin of extra
strength, machinery attempts to include designs that help prevent the user
from killing themselves, etc. Programming, on the other hand, still pretty
much lets the programmer do whatever dumb thing they want. Protected memory
operating systems (ie, pretty much every operating system in common use
today) do help prevent one bad programmer from messing up someone else's
stuff. But even there, a given application is not protected from itself,
and certain components of the operating system can still bring the whole
mess down (audio and video drivers being a common culprit).

At some point, perhaps programming WILL develop better tools, and maybe even
more stringent standards of quality. I saw an ultrasound machine at the
hospital crash the other day; during a routine exam, this wasn't a problem,
but what if it had been being used during some kind of invasive procedure
(ultrasound-guided fine-needle aspirate, for example). And no, the
ultrasound machine wasn't running Windows (or any other off-the-shelf
operating system). The more pervasive computers become, the more important
it will be to hold programmers to higher standards.

Until then, they are going to keep making the same stupid mistakes every
other careless human being does on a daily basis. And there are a LOT of
careless human beings.

Please note, the above is a broad oversimplification of the issues at hand.
This is the sort of thing that a professional committee could spend a year
talking about and still not come up with a good answer. Pretty hard to sum
up in a single Usenet post, even a long one.

Pete

Mike Weller wrote:
On Mon, 15 Aug 2005 10:38:09 GMT, Matt Whiting
wrote:

snip here and there,


You can't, I was being facetious. Since the OP writes software, I knew
he'd understand.

However, he also understands that only a very, very naive customer
believes that the tests you show them ensures that the software is
written correctly against the requirements.

Software development is still progressing, albeit glacially, but we have
a long ways to go. As long as the s/w community insists on using
substandard tools such as C++ and such, things will progress slowly.


Matt


Now you've really really got my interest.

Substandard?

What is standard? I really do want to improve on C++, but I haven't
seen anything better.

Please don't say Ada.

Ada is better from a reliability and correctness perspective. So is
Java. However, I think that longer term model-based development tools
show the greatest promise.

Matt

Matt Whiting wrote:
Ada is better from a reliability and correctness perspective. So is
Java.

I disagree... You can write crap code in ANY language... I've worked on
Ada and Java projects... Although I have more confidence in Ada than
Java, neither are what I would call "confidence inspiring"... Although
C++ has some nice features, I prefer to stick with straight 'C' from a
portability standpoint... With a statically linked executable, I can
have a pretty good feeling that my executable is going to run the same
each time it is executed... With DLLs and such, this is not possible,
so I avoid them... Unfortunately, sometimes it's difficult to
completely avoide them when you're forced to program for Windoze
platforms...

However, I think that longer term model-based development tools
show the greatest promise.

And, exactly WHAT have you been inhaling?

rant-mode
The problem that I see these days is that the 'developers' no longer
have to design an entire system... MS has ushered in the age of
fill-in-the-blank programming... These 'developers' draw their user
interface dialogs and how they relate to each other and then all they
have to do is fill in the pieces of code for the various callback
functions...
/rant-mode