Turns out it is even easier than that! Nothing to develop. When I finally decided that the domain object diagram was settled enough and we were needing the class diagram to generate from, I started reading up on transformation and poking about. In the process, I did a right click on the package in the Domain Model, check Transform Current Package, selected Java, since that is what we will be implementing in, and off it went. I suppose that, if I cared in the current round about keeping the Class diagram as PIM, I would have to add that, but for a specific language context, it is already there.
My one question about this process is that under Domain Objects, I have 5 packages defined for the sake of helping mostly to organize the documentation -- Base, Primary, Supporting, Type, and Association. I generated each of these one at a time. I created corresponding packages under Base Classes prior to the transformation, intending those to the the targets. But, what I got instead of my Primary Classes under Primary Classes, for example, was that under the target Primary Class there was Java Model/Domain Objects/Primary Classes. IT was easy enough to drag the lowest level up to the intended target, but is there a way that one should be doing this to make it come out more tidily?
