Is it possible to link a requirement to a signal instead of a block , or do i have to use goto or input / output ports as block identifiers

I am using pre designed library components that are used many times in different models, I dont want to link a requirement in my model that uses the libary blocks to the library block ports, as they will be used in other models. I need a unique ideintifer for the signal in my main model the connects to the library port . I can't seem to link a requirement to a signal in my model , only blocks.

It could be done by adding goto blocks in my model any making links to these , but I would lose the visual indiaction of data flow of a signal and there are a lot of signals in the model.

Adding in and out ports could also be used and link requirements to these, but it make the model look more "busy" and adds extra unnecessary ports and possible extra effort for Test case coverage.

Ideally would like to link requirement to a named / labelled signal in my model

, and avoid unnecessary ports , gotos , whilst keeping a good visual indication of data flow, is this possible , or any other ideas please?