| || |
How best to read a functional design document?
I am looking for an article or your expertise on how best to read a functional design document to prepare to create your test plan and test cases?
When you read a document for a new application being created that details what it should do and how it will interact with other systems. What keywords do you look for?
What things do you look for beyond **If this is the input, this should be the output that tells you as a tester, we should build a Test Case for this?
I know this can be a broad subject so perhaps keeping it to the realm of functional and usability testing would be helpful?
Re: How best to read a functional design document?
To further narrow this, do you have a fragment of one you can post? As you said this is very broad. On top of that the meaning/content of functional design document may vary greatly by organization.