[EXCELLENT PRESENTATION SNIPPED]
>
>
> It's not sufficient to detail all that one is able to determine. You
> must detail all that is required, and as a functional specification.
> If the bits that are being loaded are indeed tables for some finite
> state machine, then you can't specify the bits, but you can describe
> the machine and detail what transitions need to be made and why.
>
> --Cliff
> ctm@ardi.com
>
It may be sufficient, in a functional specification, to treat an object
as a "black-box". For instance, I may wish to communicate with a terminal
using RS-232C. I may not be familiar with the standard. I could, therefore,
detail the true/false pulses with their time intervals necessary to send
a particular character, without any knowledge whatsover of what the character
was nor the baud-rate. Such a specification might detail the procedure
necessary to "reset the terminal", without any idea that I had actually sent
a ^Z to the terminal.
Cheers,
Dick Johnson
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Richard B. Johnson
Project Engineer
Analogic Corporation
Voice : (508) 977-3000 ext. 3754
Fax : (508) 532-6097
Modem : (508) 977-6870
Ftp : ftp@boneserver.analogic.com
Email : rjohnson@analogic.com, johnson@analogic.com
Penguin : Linux version 2.1.16 on an i586 machine (66.15 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-