Technical Specifications

[James Barrow]

As you read this, please ignore the squeaky sounds of me scratching my head.

To date, I have been providing the templates, and completing the documents,
for our software project.

The business requirements came and went, and all was good.

I translated those into functional requirements, and all was good.

Now that the Engineering department is ready to go, there's dissention
amongst the ranks regarding the Technical Specifications template.

Donn Le Vie wrote a great article and I fashioned my template using this as
a guideline:

http://www.techwr-l.com/techwhirl/magazine/writing/softwarerequirementspecs.
html

The developers didn't like it because it was too detailed.  Too detailed.
Like vague and ambiguous is the better way to go.

I'm looking at this but, in my opinion, it is at too high a level to explain
to developers what to build into the application:

http://www.computing.dcu.ie/~roconnor/modules/ca326/tmanual.html

If anyone has a tried-and-true template or method, I'd appreciate it.

Thanks,

Jim