Re: writing functional specs?

["Lurker writer" <lurker_writer -at- hotmail -dot- com>]

I think the conversation has drifted off target. The original post was about 
writing functional specs (aka requirements specs, not design. If you're 
interviewing SMEs about a "design," you aren't talking about 
functional/requirements specs...you'd better be interviewing customers.

Your description about how you work with an engineer(s) who "proposes a 
design" (assuming you're talking about design specs) sounds more like an SOP 
for any document. Specs are different animals. The design spec is a daughter 
document of the functional/requirement spec, and should be reviewed against 
the criteria in that document that the internal/external customer has signed 
off to. Ideally, those folks you have reviewing the design spec were also 
involved in the development of the functional/requirements spec, as well as 
those responsible for implementing the design.

If you really want to have fun with specs, try getting on the team that 
develops the functional/requirements spec and stay with them through the 
design spec/document, architectural spec, statement of work or product 
implementation plan...