Dear All,

Here I want to share few techniques and guidelines to write clear cut requirements

that I draw out from my experience...

• Think before you start writing about a requirement even you are clear to it.
• Formulate a plan to arrange/sequence requirements before documentation.
• For wiriting requirement use KISS (Keep it simple & short) methodology.
• Don't use unessential jargons and vocabulary.
• Document your requirement in consistent manner, don't use ambigous words.
• Try to avoid the uses of "Should, Could, perhaps, approx, nearly", etc in your sentences because this will make your reuirement a vague one.
• For sentence grammar use active voice and direct narration.
• Tag your requirements with specifier, so that each requirement is uniquely identified.
• Use a standard requirement template for documentation.
• Maintain a separate document for requirement tracealibility and dependency matrix to trace out requirements for future analysis.

Hope this helps!

Regards,

Kumar Rohit

Hi Adrian,

Yes, I have a Sample template wherein I use to show, the dependency b/w requirements

and relation between use cases and requirements using requirement identifier.

Regards,

Kumar Rohit.

Hi All!

I am uploading the sample templates for requirement management.

 It is a extract of a small "Point of Sale" solution on which I had worked.

Please go through the contents of attachment & let me know if it helps you.

Regards,

Kumar Rohit

Associate Business Analyst.