Using Requirement patterns glossary

On this page

You can use the specific condition patterns in Requirement texts if you want to extract Constraint from Requirement automatically.

Enabling/disabling the Requirement patterns underlining in Requirement text

Before using this feature, make sure the Underline Patterns in Requirement Text option is enabled.

To enable/disable Requirement patterns underlining

1. From the main menu, click Options > Project.
2. In the Project Options dialog, under the General group, click Requirements and select the Underline Patterns in Requirement Text option.

3. Set its value to true to underline the Requirement text that matches the defined pattern, or false - to disable it.

   The default value of the Underline Patterns in Requirement Text option is true.

   

Defining custom condition patterns

If you can't find an appropriate condition pattern from the predefined glossary table, you can define a custom glossary. For this, you have to create a new Glossary Table with the <<requirementTerms>> stereotype applied.

To create a new glossary table with the stereotype <<requirementTerms>>

1. From the main toolbar, click the Create Diagram button.
2. Double-click the glossary table icon.
3. Open the Specification window of the newly created Glossary table.
4. Change the Applied Stereotype property value to <<requirementTerms>>.
5. Click Close.
   The new glossary table with the stereotype <<requirementTerms>> is created. You can now define your own condition patterns by adding them in the Glossary Table.

Opening the predefined requirements glossary table

You can use condition patterns from the already created glossary table. If you want to check the most frequently used patterns, open the predefined glossary table.

To open the predefined glossary table

1. In the Model Browser, click  and select Show Auxiliary Resources.
2. Expand MD Customization for Requirements Package > requirement verification Package.
3. Double-click the requirement verification to open the table (see the figure below).

The glossary table with the stored frequently used condition patterns opens (see the following figure).

Related pages

• Creating requirements
• Importing text-based requirements
• Requirements decomposition
• Requirements numbering
• Requirements gap and coverage analysis
• Tracing requirement changes in Teamwork Cloud
• Requirements verification
• Generating requirement document
• Requirement coverage analysis