Inherit TAG from Usecases to Operations to use it in the code template C

[omis]

Hello, I would like to keep track about how an operation (C interface) is traced(or any other kind of connection) by a UseCase ( operation -> UseCase) when generating the C source code. Actually, I can see that the Usecase’s tag are inherit by the whole class containing the operations, but I need to associate it directly to the operations to track it in our C code. Is it possibile to have this kind of behavior?

Thanks,
Best regards

[qwerty]

Well, yes and no. You can create a connector to an element feature with the context menu (Link to element feature IIRC). But that's a) no UML standard but an EA feature and b) will be a lot of work to maintain. So I would not really suggest to use it.

q.

[omis]

Thanks for your quick reply.

I tried your first solution but I was not able to replicate the behavior needed (maybe I'm missing something).

It is asked by our quality team to keep track about which usecase require the particular interface in our C code (obviously using the C code template generator).
Do you have any other idea about how we can achieve this feature?
We would like to have, for each C interface implemented, a reference to the UseCase linked.
Thanks a lot for your help.

[qwerty]

If you (what makes more sense) only link the interface to a UC then just draw a <<trace>> relation (or IIRC there is a <<implements>>). That will give you enough traceability. You could add descriptive context in each operation as to how it is related to a requirement.

q.

[omis]

Ok, understood.

Thank you so much for your help.

My best regards.

[omis]

Hello,

I m sorry to come back to this topic.
Basically we are able to connect the class operations to the requirements like you said before (using Link to element feature) but we are still trying to figure out how to print this information in our C source code.
Do you know how to do it with the code template generator?

Thanks
Best regards

[qwerty]

Definitely not. I stay away of this as far as possible. If I ever want to produce code from the model I do that via the API and a programming language that suits me.

q.