How to create a simple Domain Model. Tutorial

[Wivel]

Hi

I have written this little tutorial on how to develop a simple domain model using Enterprise Architect. The model is developed so it be used to generate a JPA model using the TigerTeam TRIMM tool.

You can find it here: http://www.tigerteam.dk/tutorial-getting-started-with-trimm-jpa/create-a-simple-domain-model-using-enterprise-architect/

Henrik

[AndyJ]

Hi Henrik,

I would probably display the "association" between OfferType and ExpirationType <<enumeration>> in a different way. I'm not sure about having an association between attributes and enumerations.

In my case, I'd add an attribute called "Expiration" to the class "OfferType" and then type that attribute as ExpirationType.

Then that attribute would appear as Expiration:ExpirationType in the OfferType class.

Andy

[Wivel]

Hi Andy

Glad that you have read your blogpost and I hope that you have found it useful.

Yes, you are right and both ways of doing it is correct, both from a modeling standpoint and when modeling for use with our TRIMM generator.

The added benefit from using an Attribute is that you can control the position of the Enumeration within the generated Entity. When you use a link/association to the Enumeration the order is based on the timestamp of the association, which is not always the most usable way of sequencing information

I have to ask. Are you planning on doing any code generation from your domain models or are you using it for documentation purposes only?

Henrik

[AndyJ]

As a general rule, we do not generate code from the domain models.

Our domain models represent the user experience rather than the software behind the scenes.

Andy