Hi Katharina,
I understand that you want to know if there is a way to protect the referenced requirements that have already been unlocked.
However, in this case, there is no built-in mechanism to protect referenced requirements once they are unlocked.
You can, however, create your own bespoke protection mechanism using Simulink callbacks or customizations. Here are a few approaches to consider:
- Customization: You can construct a custom Simulink tool or add-on that implements protection rules for specified requirements' custom characteristics. This utility can provide a user interface for changing or accessing the properties while enforcing any needed security procedures.
- Callbacks: Simulink callbacks, such as 'requirement callbacks' and 'model callbacks', can be used to intercept attribute changes and implement protection rules. You can, for example, define a callback that checks the attribute value and rejects any changes that break the protection criteria.
- Model Reference Protection: If the referenced requirements are linked to a model reference, you can use model reference protection techniques to restrict access to and changes to the custom attributes.
If these methods prove difficult, one other approach could be to import the requirements once again, which may prove difficult depending on the number of requirement sets and the number of referenced requirements that need to be protected.
You may refer to the following documentation for information regarding importing requirement sets:
I hope this helps.
