Textual Requirement Artifacts
A textual requirement artifact is a documented property or capability that a product must possess to provide value to a stakeholder. In this case, the requirement is documented in a textual (as opposed to visual) form. Textual requirements are beneficial for capturing requirements rapidly.
Once captured, textual requirements are often used as the basis for visualizing requirements using other types of artifacts such as use cases and UI mockups.
You can enhance your textual requirements by taking advantage of rich text formatting. You can also attach files to your textual requirements, and trace your textual requirements to other artifacts.
To support your existing business processes and standards, project administrators can customize the set of requirement types, and create other custom properties as needed.
Textual Requirement Artifact Properties
By default, a textual requirement artifact contains the following system properties:
Property | Description |
Name | Indicates the name of the textual requirement |
Type | Indicates the type of artifact |
Id | Provides a unique identifier for the textual requirement. The Id cannot be modified. |
Description | Provides the description of the textual requirement |
Your instance administrator can configure standard properties for each standard artifact type. Textual requirements also have their own relationships, discussions, files, and history.
