Here are a couple of notes I just sent someone on how to get started writing a requirements specification. They may be a little vague, but I hope they show my intent, or perhaps my frame of mind, when writing a specification.

Fred,

Here are two notes on my mental approach for writing a requirements specification:

1) On easier requirements specifications, I approach these like I am writing them for someone I don't currently know. They are sold as "Al will write these, but then any competent development firm can implement the design". So, if you think of them that way, you need to include information at a detailed level, so someone you don't currently know could actually have a chance of implementing your design.

2) In design areas where I can't think of what to do, I try to start writing that portion of the real application. When I hit spots where I don't know what to do, I realize that I need to do some more design and investigative work. There's nothing like trying to create the actual application to show what you're missing.

I hope that helps,
Al