Skip to main content
Skip table of contents

Requirements Fields

The Requirements Module has different columns for every Requirement Field, each with its own characteristics. However, if there is a field that is not available for your use case, you can create a custom column in the admin panel or also you can request it at Figure Default Requirement Fields (2) illustrates one way to set the visibility for each of these columns via the “Columns” side pane (1).


Default Requirement Fields

Users can also set which columns are visible through the header pop-up panel (3) as see in Figure Header Pop-Up Panel, by clicking on the three dash line which appears when hovering the mouse over any of the columns headers (1), and clicking on the columns tab (3).


Header Pop-Up Panel

Column Fields



The identifier is the mandatory field which is usually a unique name to the requirements. For example BAT-001, the BAT represents the battery subsystem and 001 represents the first requirement of the subsystem.


ID is different from the identifier in Valispace. ID are automatically created by Valispace when a requirement is created. It is used in the Backend and also in the Rest API.


As the name suggests, it is a title or a short description of the requirement.


The requirement text is added here in this field. You can use the dollar sign to reference Valis, Components and other Requirements directly in this field.


In this field, the user can input the additional comments or the logical reasons behind the requirement.


This field shows the name of the specification to which the requirement belongs. It’s a drop-down menu and if the user wants to move from one specification to another, he can select the specification and it automatically moves.


In case your requirement has additional information in the form of an image, the user can add it here.


Similar to specification, this field shows the name of the section in which the requirement belongs. It’s a drop-down menu and if the user wants to move from one section to another, the user can select the section and Valispace automatically rearranges the requirement.

Path to Section

If a requirement is placed within a sub-section, its full path will be displayed here with each section level being separated by a “\” character. This field can be used in an imported file to create the sections structure and properly place the requirements in it on creation.


If the requirement has parent’s requirements, it shows the list of requirements which are a parent. Clicking on them leads to parent requirement information.


If the requirement has children’s requirements, it shows the list of requirements. Clicking on them leads to children’s requirements information.


It is a user-defined field. The type relates to what kind of requirement it is. For example, the default ones we have are functional, performance and system. Users can add other options fields. Refer to Requirements Settings.

Verified children

This field shows which children are verified.


This field shows the state of the requirement identifier and the text. The current default ones are final, draft and in review. You can set the transition settings in the state. So, whenever the requirement text or identifier is edited, the state is automatically changed. Refer to Requirements Settings.

Verification status

Here you can find if the requirement is verified or not.

Verification methods

The method by which you are verifying the requirements. Currently, we have Analysis, Inspection, Review, Rules, and Tests. Users can add additional verification methods based on their use case. Refer to Requirements Settings.


In Valispace, each requirement is related to a component and the verification is done for each component. The verification method is editable only when the component is referred to as a requirement.


Add the nature of compliance with the requirement. Default ones are compliant, partially compliant and non-compliant.

Compliance comment

If you have any comments related to the compliance, they can be added here.

Closeout reference

The supporting information that proves the verification method. Refer to Verifications within Valispace.


Attach any documents related to the requirements/verification document.

Verified on

Latest date on which it was verified.

Verified by

Shows the user’s name who verified the requirement.


Displays the owner of the requirement.


If the user wants to group based on special needs e.g. to be reviewed, the user can add tags to each requirement.


Currently, you cannot have a custom arrangement of requirements as it is alphabetically. So, to have a workaround, a position was introduced. Give a number to each number according to your order and sort the column to have the custom order.


Date on which the requirement was created.


Date on which the requirement was last updated.

Custom fields

In case the user needs a field that does not cover his use case, the user can create custom fields which can be a rich text field or a drop-down menu. If you would like to have a custom menu, refer to the admin settings.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.