'site easy to use' was just one example of the untestable items that routinely appear in functional specifications.
This is a contractual document therefore there must be no room for ambiguity and the spec must be usable as the basis for a fixed price quotation. So any usability research has to be done before the spec is raised and the results incorporated into the spec.
So a serious site should have a multi-stage contract with results from each stage being built into the budget for the next..
Prototyping can be tremendously useful in the specification stage and a rapid build system can be worth its weight in gold even if you are going to hand craft the final result.
Common Mistakes: Functional Specification for Web Development, nbuerki, 26 Jul 09:34 Issue:
What are pitfalls that companies should avoid when specifying Web applications for internal or external development?
Response:
Ineffective functional specification ...
Common Mistakes: Functional Specification for Web Development, Loz, 27 Jul 10:47 In Italian we would say 'sante parole'... meaning saintly words.
In my experience point 3 is particularly crucial and generally underestimated. If, like me, you're working with ...
Common Mistakes: Functional Specification for Web Development, textor, 27 Jul 15:29 In the IT industry the standard criterion for a functional specification is 'can you write a test plan from it?.You should be able to sit down with the functional spec, write a ...
Common Mistakes: Functional Specification for Web Development, Paul Evans, 27 Jul 15:39 I'd agree with everything Nicolas says here: But I'd suggest that it goes further back. It is important that a series of measurable success criteria are built into any website. It ...
Common Mistakes: Functional Specification for Web Development, textor, 27 Jul 16:14 'site easy to use' was just one example of the untestable items that routinely appear in functional specifications.
This is a contractual document therefore there must be no ...