Cartridge kissmda-cartridges-simple-java: add Stereotype "Boundary" to create DTO (Data Transfer Object) or VO (Value Object)

crowdcode-de / KissMDA

Keep It Simple Stupid, MDA!

33 stars 8 forks source link

Cartridge kissmda-cartridges-simple-java: add Stereotype "Boundary" to create DTO (Data Transfer Object) or VO (Value Object) #24

Open lofidewanto opened 11 years ago

lofidewanto commented 11 years ago

We need to be able to create DTO with stereotype "Transport Object".

lofidewanto commented 10 years ago

Or we just use stereotype "Value"

idueppe commented 10 years ago

Isn't a DTO a UML boundary object? Look at this page http://www.cs.sjsu.edu/~pearce/modules/lectures/ooa/analysis/ecb.htm.

lofidewanto commented 10 years ago

Yes correct. DTO == TO == Value Object == Value == Boundary Object. I thought it is good to have these elements in our UML language:

Entity, Service, Value

idueppe commented 10 years ago

I don't think so that a Value object is equal to a Dto. See http://www.adam-bien.com/roller/abien/entry/value_object_vs_data_transfer.

lofidewanto commented 10 years ago

Ahhh.... sometimes I think that those JEE design patterns are typical of "over engineering" in our enterprise software development. Also the whole specifications with JEE. My analogy: do we need a specification for Android OS so that every vendor can implement "other" Android OS? Nope! So who needs those JEE servers from IBM, Oracle, JBoss, etc.? You only need ONE JEE server just like ONE Android OS. You can still do your own Android OS just like Linux because it's Open Source but you don't need such over specifications like JEE... I think I need to blog this ;-)

lofidewanto commented 10 years ago

OK, @idueppe you are right. We should make "boundary". Here is a good example: http://goo.gl/kpiOEK