Applicable Components
The “Applicable components” column was enabled in the “Requirements module in the significant release Version 2.2. This feature now links the requirements with the components, replacing the old way through the Verification methods. The first section will explore how it differs from the old to the current ways.
Old Way
In the Valispace requirement verification workflow, requirements must always be linked to one or more components for verification. The usual process involves the user specifying the "Verification Method" for the requirement and assigning a "component" to the verification method. The requirement and component connections are created once the user assigns the component to the verification method.
![image-20240603-123516.png](../__attachments/2455568399/image-20240603-123516.png?inst-v=06dc8543-c86b-474b-8373-a5305e368ba8)
Adding components to requirements through the Verification methods
Subsequently, this requirement becomes visible within the "Requirements" section of the component.
![image-20240603-081411.png](../__attachments/2455568399/image-20240603-081411.png?inst-v=06dc8543-c86b-474b-8373-a5305e368ba8)
The Requirements within the “Requirements” section of the component don't show up anymore if the component is added to the VM. The user needs to add them using the new method illustrated below.
However, if you would like to migrate the components of the VMs/requirements, please contact us at support@valispace.com. We can migrate the components from VMs to the “Applicable Component” attribute through a script.
New way
The previous method of component-requirement link has been changed by implementing “ Applicable Components.” Under the new process, Requirements can be directly paired with components without needing a specific VM (Refer Image and video Setting Applicable Components).
The user can assign the components to the requirements within the requirements module’s table view(1) in the attribute column “Applicable Component” (2), as in Figure Setting Applicable Components.
![image-20240415-160210.png](../__attachments/2455568399/image-20240415-160210.png?inst-v=06dc8543-c86b-474b-8373-a5305e368ba8)
Setting Applicable Components
The “Applicable Components” columns are only visible and shown in the “Quick-load tables”. If you are using the old tables, the attribute is missing. To use the quick load tables, Use the toggle to turn it on. Refer to the image Applicable Column attribute in Quick load tables
![image-20240603-110158.png](../__attachments/2455568399/image-20240603-110158.png?inst-v=06dc8543-c86b-474b-8373-a5305e368ba8)
Applicable Column attribute in Quick load tables
Applicable Components can be set from the current Project or you can also search for Components in other Projects within the same Workspace.
Setting Applicable Components
By setting Applicable Components, you can relate your design goals (Requirements) to your system architecture and design intent (Components). As seen in the Video Setting Applicable Components, you can not only directly navigate to a Requirement’s Applicable Component from the Requirement’s table, but from that component’s Requirements tab, you can also view all Requirements for which that Component is an Applicable Component of.
![image-20240415-171151.png](../__attachments/2455568399/image-20240415-171151.png?inst-v=06dc8543-c86b-474b-8373-a5305e368ba8)
A Component’s Application to Requirements
In Figure A, Component’s Application to Requirements, you can see how this particular component would reflect a connection to multiple Requirements as an Applicable Component.
Setting up a “Default Component” to a specification/section, does not automatically add the component to the “Applicable Components”.