When working on eclipse, I discovered the necessity to represents things like plugins or components which are not directly handled in Famix.

It is important if we want to be able to deal with real world cases.

May be we should consider introducing them as Moose Entities?

Or may be not: I used Moose-Groups (of class because one package can be spread over different plugins) and it is not that bad.
the main issue, in my case, was that classes don't know to what group they have been assigned...
So computing dependencies could be very lengthy.
I solved that by creating a dictionary on the side, but maybe we should think on a better solution.

And then of course integrate this with all the tools...