Hi,
Once the functional guys collect the business requirements from the clients, for whatever development requirements identified they prepare a functional specification.
It contains who the business process owners are, the developers, the functional guys involved, the proj manager names, version of the specification. Then what is the task, a pseudo logic for it, then how the desired result should be like and on what parameters the results are validated. Also the client needs approve the functional document thus prepared.
Apart from these basic details there are some more details in a funcitonal specification document. Now based on the functional spec, the technical guys prepare a technical specification which contains further explanation of how that particular is gonna be executed and how the logic is going to be validated, a code walk through. After the technical specification is okayed by the functional guy, they go throught with the actual development work. After it is done the fucntional guy tests it and asks for the clinet to check if it is as per his requirement.
If some more modifications or minor changes are required, then the same specification can be used with a different version number. Like if they beginned it with ' 1 ' , this time it will be 1.1 for a minor change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.