I'd also add that a Revision History is essential, because this will be a
living document, and it will be necessary to track changes.
RE: Agile lite specs vs. full massive specs, I'd be interested in any
discussion on the usability of spec documents from a technical communication
standpoint (and h
Functional spec is a summary of the functional analysis I make. It
contains all possible features description, the screen flow for all
interactions (regular flows, errors, alternative flows).
I use UML diagrams to describe features in use cases and show how the
process looks like. Wireframes or s
I write specs for music applications. I try to keep the pictures
pretty sketchy, unless when pixel-perfection is required.
We have a basic anatomy of the specs, which looks like this:
Title page
Executive Summary - the elevator pitch of the feature
Goals and Non-goals - what user goals we try t
Do you need the functional spec? I know it is a common thing, and is
often demanded by QA, but what do you get in return?
If the the goal is to allow developers to start coding then the first
draft of the User Manual could be just as helpful. Complemented with a
test spec these 2 documents could p
I find that I like to use rendered comps with final visuals in my
functional specs. And I often put the visual specs in the appendix.
That way test/QA can use this document as a resource. It depends what
your design resources and skills are.
. . . . . . . . . . . . . . . . . . . . . . . . . .
In my opinion, the purpose of a functional spec is to describe the
applications functionality and user interface/experience. The spec
should enable developers to begin coding the application. Note that I
dont view a functional spec as a design or technical document.
Heres an outline that I
