Need of srs and frs sample docs
- Hi,im in need of frs and srs sample documents as i joined newly in the job.Plz can anyone help me?with regardsRenu
Answers
Hi,
There are many templates as well as sample FRS and SRS documents visible on the web. See examples below.
FRS: http://www.stemen.com/InstantCo-Func-Spec-Sample.pdf
SRS: http://mcis.jsu.edu/studio/SRSSample.doc
Here are a few suggestions for you:
1. If you do choose to read/ refer a specification document, it would be better to choose a document listing the requirements of a system similar to yours.
2. If you have to incorporate a part of the sample document in your own document, you may be required to take permission from the owner of that document. Check the web site in question and the sample document itself for such details.
3. Creating an FRS or SRS document may be (and usually is) an iterative process. One creates a part of the document, gets the relevant stakeholders to review it, addresses their concerns and produces another version. This cycle goes on until a definitive version is ready for use. Beyond this point, the changes to the document are either controlled OR the document stays constant and changes are introduced via Change Request documents.
4. Some of the main problems that have been observed in few SRS/ FRS documents include the following. Try to avoid them.
a. Missing requirements
b. Requirements conflicting with each other
c. Ambiguous/ vaguely worded requirements
d. Requirements that cannot be tested
Hope this helps!
Blog: Software Testing Space
- Marked As Answer byAlan PageMSFT, OwnerMonday, October 26, 2009 3:58 AM
All Replies
Hi,
There are many templates as well as sample FRS and SRS documents visible on the web. See examples below.
FRS: http://www.stemen.com/InstantCo-Func-Spec-Sample.pdf
SRS: http://mcis.jsu.edu/studio/SRSSample.doc
Here are a few suggestions for you:
1. If you do choose to read/ refer a specification document, it would be better to choose a document listing the requirements of a system similar to yours.
2. If you have to incorporate a part of the sample document in your own document, you may be required to take permission from the owner of that document. Check the web site in question and the sample document itself for such details.
3. Creating an FRS or SRS document may be (and usually is) an iterative process. One creates a part of the document, gets the relevant stakeholders to review it, addresses their concerns and produces another version. This cycle goes on until a definitive version is ready for use. Beyond this point, the changes to the document are either controlled OR the document stays constant and changes are introduced via Change Request documents.
4. Some of the main problems that have been observed in few SRS/ FRS documents include the following. Try to avoid them.
a. Missing requirements
b. Requirements conflicting with each other
c. Ambiguous/ vaguely worded requirements
d. Requirements that cannot be tested
Hope this helps!
Blog: Software Testing Space
- Marked As Answer byAlan PageMSFT, OwnerMonday, October 26, 2009 3:58 AM

