"Model checking is a technique for verifying finite state concurrent
systems
such as sequential circuit designs and communication protocols. It has a
number of advantages over traditional approaches that are based on
simulation, testing, and deductive reasoning. In particular, model
checking
is automatic and usually quite fast. "

The book by Edmund Clarke has been published at MIT Press.

I learn a good deal from almost every book that I read. Although I have
bought about 7 books on How to Program Visual Basic, and I still can't
write
a decent program. using that book or Microsoft Visual Basic language. And
I
reading some books which are stating, it is not really possible to write
anything without having an inspection team to test your work for you. No
one can really do the criticism of himself (as programmer), any justice.

A whole school of people in the data mining camp, do not trust their
appreciation of stored data either. They just consider everything that
happens to be in a coud, and then they write a botnet program or something
to work out the details. Anything they write as a proposal is "We don't
know anything".

That reminds me of that televicsion show where the characters write a
proposal for a television show about nothing. So we go in there and the
pruducer says, "Well what's your television show about?" And we say,
"Nothing, We dont have any idea!"

Ok then Ok there's salsa and hula girls in the beer tent. Watch your
purses.

"Crushed_Ice" <slipandslide at (no spam) yahoo.com> wrote in message
news:-_ednYFC1Oa8E-PXnZ2dnUVZ_oadnZ2d at (no spam) hbci.com...
"Model checking is a technique for verifying finite state concurrent
systems
such as sequential circuit designs and communication protocols. It has a
number of advantages over traditional approaches that are based on
simulation, testing, and deductive reasoning. In particular, model
checking
is automatic and usually quite fast. "

The book by Edmund Clarke has been published at MIT Press.

It's just software, not the monolith.
The answer is to refer to all of the design tips that you can find, before
creating the design model.

"Crushed_Ice" <slipandslide at (no spam) yahoo.com> wrote in message
news:isadnbLudpOpqB_XnZ2dnUVZ_gadnZ2d at (no spam) hbci.com...
I learn a good deal from almost every book that I read. Although I have
bought about 7 books on How to Program Visual Basic, and I still can't
write
a decent program. using that book or Microsoft Visual Basic language.
And
I
reading some books which are stating, it is not really possible to write
anything without having an inspection team to test your work for you.
No
one can really do the criticism of himself (as programmer), any justice.

A whole school of people in the data mining camp, do not trust their
appreciation of stored data either. They just consider everything that
happens to be in a coud, and then they write a botnet program or
something
to work out the details. Anything they write as a proposal is "We don't
know anything".

That reminds me of that televicsion show where the characters write a
proposal for a television show about nothing. So we go in there and the
pruducer says, "Well what's your television show about?" And we say,
"Nothing, We dont have any idea!"

Ok then Ok there's salsa and hula girls in the beer tent. Watch your
purses.

"Crushed_Ice" <slipandslide at (no spam) yahoo.com> wrote in message
news:-_ednYFC1Oa8E-PXnZ2dnUVZ_oadnZ2d at (no spam) hbci.com...
"Model checking is a technique for verifying finite state concurrent
systems
such as sequential circuit designs and communication protocols. It has
a
number of advantages over traditional approaches that are based on
simulation, testing, and deductive reasoning. In particular, model
checking
is automatic and usually quite fast. "

The book by Edmund Clarke has been published at MIT Press.