Do we have any mechanism in uvm data classes(i.e. any class extended from uvm_transaction) through which we don't allow users to change any attribute of the class object(typically configuration object).
I am developing a verification component which has a configuration class and I need to ensure that users are not changing any attributes accidently, if they really need to change anything they should follow a specific protocol so that verification component work as expected all the time.
The behaviour of the feature would be something like this:
create configuration ob