If you want to create links to reference requirements between one and another. When creating your requirements, you will want to reference that requirement to another existing requirement. We’ll see how to create dependencies depending on your structure in this documentation.
You can also take a look at the tutorial for more information:
...
How to create a dependency?
Using tables
When you write your requirements in tables, whether in Horizontal, or Vertical, you will simply have to add the /requirement yogi link macro to your requirement line.
The name of the relationship is the one you put in the column header.
In the first example below: FN-01 references BR-01 and DIS-REQ-001 with the relationship Refines.
Horizontal Tables | Vertical Tables |
|---|
...
Paragraphs
Linear Docs
...
 |  |
.png?version=1&modificationDate=1740498707354&cacheVersion=1&api=v2&width=363) | .png?version=1&modificationDate=1740498724796&cacheVersion=1&api=v2&width=363) |
Using paragraphs
When you write requirements is using paragraphs, we will index the paragraph where the requirement is defined in. And the dependencies work the same way as above:
Write your requirement definition and put a
/requirement yogi linkmacro in the same paragraph for us to index it as a dependency.By default, the name of the relationship will be
Dependencybut you can customize it with the RY Configuration macro and Paragraph Configuration (see docs).In the example below,
TECHNICAL REQUIREMENT 001referencesLIDAR 001, with the relationshipDependency.
 |  |
Using Linear Docs
When you write requirements outside of tables, and need a better customization than the paragraphs, we have a feature called Linear Documents.
💡Linear documents create requirement keys for each heading, we index the heading text as the description, and everything that is written in that section will be the property @Content of the requirement. If you are not familiar with linear docs, we recommend to read the documentation and test the feature: Linear documents: Manage requirements outside of tables .
There are two ways to create dependencies using Linear Documents:
Automatic dependencies: Linear docs index dependencies using the heading hierarchy. H1 titles reference H2 titles, which also reference H3 titles, etc.
In the example below, you can see the heading
4.1.1references headings4.1.1.2and4.1.1.1, and is referenced by heading4.1.
 |  |
Usual way: Using the
/requirement yogi linkmacro anywhere in your paragraphs, and we’ll index it as a dependency of the last heading.In the example below, you can see the Heading
1.2referencesMSFC-STF-3716with the link macro.
 |  |
Using the parent requirement configuration
How to trace dependencies?
Search syntax
Traceability Matrix
Dependency graph
Most asked questions
How do I know the direction and hierarchy?
...
cleanup tasks