Tuesday, June 02, 2009

Marvin the martian


I was accused at Apachecon EU a year or two ago by Steve of relying on "architect tools" i.e. visio, powerpoint etc., instead of programmer tools, (like what? emacs!) For which he proposed a test framework here.

Well today I was discussing some of the finer points of separation of concerns with the guys and had cause to exhume (and re-label for php) a diagram I drew a couple of years ago for a former employer to illustrate the layering in our java systems to an interested, but unenlightened group of Oracle developers.

It would be a good test case for Steve's framework, because it has to be a particular shape, no matter what information it has to convey.

I could plead that I drew it first then recognised the shape, but I won't bother because life's too short.

Colleague Ed suggested it should be recorded for posterity so here is the original Java version...


Comments:

SteveL said...

nice!

Danny Angus said...

cheers!

Dave said...

interesting...
you could have shown the php one though...
and you relying too much on architect tools?
I recall you growling 'model-based-development' any time i so much as thought OMG...!
(or UML)

Danny Angus said...

the php one was a hack! Its basically the same, but PHP Doctrine replaces hibernate, mysqli replaces jdbc, smarty replaces tapestry, and the spring/ ejb & servlet bit is replaced by generic "business logic" and "MVC controller". Its no patch on the original ;-)

Newbie said...

Great representation of software architecture. This is definitely a model that will come in handy.

blog comments powered by Disqus

I know nothing, I'm not a fortune teller, and you'd be insane to think that I am. This disclaimer was cribbed from an email footer I once received. It is so ridiculous I had to have it for myself.

Statements in this blog that are not purely historical are forward-looking statements including, without limitation, statements regarding my expectations, objectives, anticipations, plans, hopes, beliefs, intentions or strategies regarding the future. Factors that could cause actual results to differ materially from the forward looking statements include risks and uncertainties such as any unforeseen event or any unforeseen system failures, and other risks. It is important to note that actual outcomes could differ materially from those in such forward-looking statements.

Danny Angus Copyright © 2006-2013 (OMG that's seven years of this nonsense)