Add a comment

 

Re: Mapping software architecture to code

Frank, I think there is a misconception lurking in the dark. If your team is small enough that everybody can work on the same code base, the structuring can simple happen by putting stuff in the 'right' package. No extra interface, no extra separation. If and only if you application grows one would consider splitting it into separate projects / maven modules or whatever your tool names those thingies. A clean package structure will give you a head start on that.

Re: Mapping software architecture to code


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).