...
We recommend you to write your requirements in tables, this way you’ll be able to assign properties and dependencies to your requirements, and have a clear traceability and readability of your specifications. You can use horizontal tables, and also vertical tables.
The idea is to add structure to your writing keeping a fluid readability.
We noticed that writing requirement should be The best way to write requirements is to be as transparent as possible for your users.
Writing requirements should be easyWriting requirements should be human friendly, the main focus of users must be the product to specify, and still allow you to be flexible over what you want to write. For you to keep a structured and clear readability of your requirements, we figured tables were the best way. Indeed, using rows for the listing of your requirements, and columns for categorization helps you and your users to access generated reports and look through all your specifications.
...
most keyboard symbols
Paragraph symbol
blank spaces
Language characters like arabarabic, german, or japanese.
However, do not use % , / or \.
...
For the numbering, we recommend to put an extra 0 depending on the number of requirements you plan to have. This will simply help us to keep the order in the search and traceability, making sure number 10 will be put correctly in order after the number 909.
Best Practice 3: Ways to add your first requirement
...