HI all, A few thoughts - first I often call "What a product should do" Business requirements - not functional requirements.
Also I recently worked on a project where I helped craft the business requirements by working with users and I created a UI specification but the developers kept complaining that there was no "functional specification" This was not a web product but a thick-client app - with an interface but also with many business rules that I didn't have the knowledge to document - I just said something like "system applies limits to data entry - here is how a limit appears to the user" but I didn't say anything about how those limits were applied through the workflow management tool. The developers I worked with expected that to be in a doc too - but I knew it wasn't me that wrote that kind of a doc - they called it a functional spec.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://gamma.ixda.org/discuss?post=21651 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://gamma.ixda.org/unsubscribe List Guidelines ............ http://gamma.ixda.org/guidelines List Help .................. http://gamma.ixda.org/help
