Few column fields in the Requirements Module have their drop-down menu to select the relevant option to the requirement. These options can be created and managed by the admins based on their use cases. The few drop-downs customizable by the admins are:
Custom drop-down field
To access the settings menu for the above column fields, the user has to navigate to the user name and click on the settings. Upon clicking the “Settings” option, the admin will have the project settings where they can modify the column fields. The gif below illustrates how to access the project settings which contains the requirement settings.
The default verification methods available when the deployment is created are Analysis, Inspection, Review, Rules, and Test. Note that each verification method has its closeout references. A closeout reference in Valispace means the references which will verify or prove the verification method. The current closeout references available in Valispace are:
Adding an analysis document from the Analyses Module.
Attaching documents/models as references to the verification method.
As the name says, it manually changes the status of the verification method.
Using the boolean comparison to compare the current design property with the requirement’s property.
Adding the test procedure and doing automatic verification whenever the test runs are performed.
Here’s what the default verification methods with their default closeout references are shown in the verification methods settings. The user can change the closeout references to the default ones and also create their verification method with their closeout references.
For example, let's say the user would like to add a new verification method “Script” with the closeout reference “Upload”. Within the verification method settings, on the right side corner click on “+” and add the name, abbreviation and the closeout reference as shown in the gif below:
States in Valispace denote the state at which the requirement text is present. The default requirement states we have in the settings are Draft, In Review and Final. The user can manually set the state to each requirement. Here, the user has the access to add new states other than the default ones.
In case any of the users change the requirement text, the user can set the transition state or change the state manually in the Requirements Module.
For example, when a requirement text is in the final state and there is a modification to be done due to the change in the stakeholder needs, the user modifies the requirement text. If the transition state set up for the state “Final” is “Draft”, whenever the requirement text is edited the state of the requirement will automatically change.
Note: if the transition state is not visible in the “Requirement state“ settings, click on the columns on the right side and tick the transition column.
System Engineers often use types to classify/group requirements based on their common features. To integrate this feature, the “Types” were introduced in Valispace. The types set as default are Functional, System and Performance. Users can add other types based on their use cases. To add new types, click on the ”+”, add their states and create them.