[ajug-members] design

[521]

that's too high-level/fancy for me as a hobbiest; i was asking for a much 
smaller project, say a math game or the like;

b

On Wed, 18 Feb 2009 09:55:23 -0500, Andrew Goode wrote 
> There are many ways to design your software/application.  I generally 
> prefer an adopted form of this: 
> 
> http://en.wikipedia.org/wiki/Domain-driven_design 
> 
> where you have "reference" objects that model your domain and "service" 
> objects that comprise the behavior of your domain, typically in the form 
> of manipulating or acting on the "reference" objects.  Services should 
> generally be exposed as interfaces (abstracting the implementations away 
> from their public API) whereas domain objects are more likely to be 
> exposed just as POJOs that may or may not be described by various 
> interfaces.  But remember that each object is *defined* by the business 
> domain your are developing towards. 
> 
> //-- a.goode 
> 
> -----Original Message----- 
> From: 521 [mailto:521 at ofig.org] 
> Sent: Monday, February 16, 2009 10:04 AM 
> To: ajug-members at ajug.org 
> Subject: [ajug-members] design 
> 
> by design, in java- or oop in general- is it best to have classes made 
> as follows... 
> 
>  -certain classes are designed to be the motors or engines of an 
> application 
>  -certain classes are designed to the the nouns/subjects of the 
> application 
>  -other classes, maybe, some other stuff, etc? 
> 
> barclay 
> 
> _______________________________________________ 
> ajug-members mailing list 
> ajug-members at ajug.org 
> http://www.ajug.org/mailman/listinfo/ajug-members 
> 
> _______________________________________________ 
> ajug-members mailing list 
> ajug-members at ajug.org 
> http://www.ajug.org/mailman/listinfo/ajug-members