The Requirement module has different columns and each column has its own characteristics. However, if there is a column that is not available for your use case, you can create a custom column in the admin panel or you can request at support@valispace.com. Here we will discuss what each column fields are present

Column Fields

Characteristics

Identifier

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

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

Title

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

Text

The requirement text is added here in this fields

Rationale/comment

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

Specification

This field shows the name of the specification in which the requirement belongs. Its 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.

Images

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

Section

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

Parents

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

Children

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

Type

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. User can add other options fields. Refer Requirement Settings

Verified children

This field shows which children's are verified

State

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 Requirement 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, test. User can add additional verification methods based on their use case. Refer Requirement Settings

Components

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

Compliance

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

Compliance comment

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

Closeout reference

The supporting information which proves verification method. Refer Verifications within Valispace

Attachments

Attach any documents related to the requirments/verification document

Verified on

Latest date on which it is verified.

Verified by

Shows the users name who verified the requirement

Owner

Displays the owner of the requirment

Tags

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

Position

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

Created

Date on which the requirement is created

Updated

Date on which the requirement is update lasts.

Custom fields

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