How do you write requirements with Requirement Yogi?

There are a couple of key points that can help to write and structure your requirements:

• The tables

• The key patterns

• The Requirement Types

Best Practice 1: Put your requirements in Tables

Users should be able to focus on their product, and writing quality requirements, and not so much on the tool they are using and the structure it must follow. The best compromise we found to help you accomplish that, and not lose sight of your data is: Tables.

1. 1 Row = 1 requirement

2. 1 Column = 1 data type, also called properties.

3. This will allow us to read and interpret your data, to give you:

   1. Structured requirements

   2. Quality reporting

   3. Easy Navigation and lecture

Best practice 2: Define your key patterns

If you want to identify and organize the types of requirements you are creating. If you want to be able to use a quick search, filter your requirements based on the key, then defining unique key patterns is important. Once they are created, it will also ease the flow of creation as we’ll be able to autosuggest the next requirements.

• For example, business requirements, functional requirements and technical requirements: PRODUCT-BR-001, PRODUCT-FN-001 , PRODUCT-TECH-001.

We recommend to keep your requirement keys concise, but you are rather free in terms of format. You can use:

• most keyboard symbols

• Paragraph symbol

• blank spaces

• Language characters like arabic, 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 09.

Best Practice 3: Ways to add requirements

There are more than one way to create new requirements.

• I am writing my requirements one by one, as I create my specifications

  • Use the /req shortcut to add our macros. You’ll be able to write your requirement key and insert it.

• Inserting the requirement macro individually takes me too much time, I want to generate my requirements

  • Use the Transformation wizard in your table and select the rule ‘Generate keys’. Find out more in the documentation.

• I already have my requirement keys written in text, how can I transform the requirements?

  • Same as the point above, use the Transformation wizard and choose the rule ‘Transform text in keys’.

  • 💡 You can also do the same with requirement links, and transform mentions of existing requirement definitions. Read the docs.

• I want to ease the writing for my users, and create templates

  • Using the requirement types, you can create templates of pages that will help to facilitate the writing process of your users, making sure the requirements have the correct properties. See more in the next Best Practice.

Best Practice 4: Organize your requirements per type

If you’re looking for a way to combine all the best practices above so you can have more clarity and structure over your requirements, be able create requirements efficiently with templates, and check the compliance of those requirements, then Requirement Types are your answer.

• Create your requirement type and choose the key pattern, replacing the numbering by %.

• Assign the properties and external properties desired, and make them required to trigger a validation.

• Save your requirement type.

• Create a page from this requirement type, and see your requirement type.

This template will generate the first requirements with the correct key, create your requirement table with the correct properties, and the rest is now up to you!