Few column fields in the requirement module have their own drop down menu to select the relevant option to the requirement. These option can be created and managed by the admins based on their use cases. The few drop down that are 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 the admin can modify the column fields. The gif below illustrates on how to access the project settings which contains the requirement settings.
The default verification methods that are available when the deployment is created are analysis, Inspection, Review, Rules and Test. Note that each verification method has it own closeout references. A close out reference in Valispace means the references which will verify or prove the verification method. The current closeout references avaliable in Valispace are
Adding an analysis document from the analyses module
Attaching doucments/models as references to the verification method
As the name says, its manually changing the status of the verification method
Using the boolean comparison to compare the current design property with the requirement 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 own verification method with their closeout references.
For example, lets 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 close out reference as shown in the gif below
States in Valispace denotes the state at which the requirement text are 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 have the access to add new states other than the default ones.
In case if any of the user changes 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 final state and there is a modification due to the change in the stakeholder needs, and the user modifies. If the transition state is set up for the state “Final” is “Draft” and whenever the requirement text is edited, the state of requirement automatically changes.
Note: If the transition state is not visible in the “Requirement state “ settings, click on the columns on the right side and tick on the transition column
System Engineer often uses the type to classify/group their requirements based on the common features. To integrate this feature, types was introduced in the valispace. Few types which are set as default are functional, System and performance. User have the possibility to add other types based on their use cases. To add new types, click on the”+” and add the state and create.