Your architecture starts to be sub-optimal if...

Submitted by adam bien on Tue, 2008/12/02 - 7:38am

Ads by DZone

There are lot of experts involved, but no one is really excited.
You are talking for more than a day about concepts and architectures without a single Proof Of Concept or even discussion of code.
You are just selling the features without explaining the consequences.
You start with a multi-layer architecture without highlighting the "added value" of each layer and its individual responsibilities.
You are searching for the "silver bullet" architecture, with which all known and, even, future requirements can be fulfilled.
You are trying to identify hotspots and shortcomings in advance with ...UML.
There is no clear vision defined; there is no clear relationship between the vision and the resulting architecture.
The is no secondary strategy... you have only one "master plan".
You are thinking in pictures, not in code. You believe that pictures are more valuable than code.
The architect/s believe they can be smarter / have more experience than the whole development team.

From http://www.adam-bien.com/roller/abien

Your rating:

Average: 2 (2 votes)

Login or register to post comments
5134 reads
Printer-friendly version

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Comments

juancarlos.molina replied on Tue, 2008/12/02 - 3:40pm

great checklist

hundal replied on Wed, 2008/12/03 - 2:43pm

Will I be rude if I said that you've just summarised the "architects" at where I work ? :)

Silvio Bierman replied on Wed, 2008/12/03 - 5:33pm in response to: hundal

Any architect who is not one of the actual programmers of the system being "architected" should be fired immediately, along with the executive who hired him.

proflux replied on Thu, 2008/12/04 - 11:31am

It sounds like you had a fallout with your architecture team and decided to create this bitch-list to vent (sorry, number 10 really gave it away.) I hope you feel better soon.

Liam Knox replied on Fri, 2008/12/05 - 5:11am

I agree, just sounds like a bitch list with no real substance and stated context.

A complete waste of time for the writer and reader a like. Why dont you just say Ha 'Ocams Razor' , its a lot shorter and as useful.

Geertjan Wielenga replied on Fri, 2008/12/05 - 7:08am

Doesn't seem like a waste of time to me at all. But sorry you felt that way.

Liam Knox replied on Fri, 2008/12/05 - 7:35pm in response to: geertjan

Ok take any one on the statements tell me how to evaluate its worth in the context of developing a system? What metrics do you use, what is each statements worth?

for example 'There are lot of experts involved, but no one is really excited.'

What do you do ask all developer in the firm if they are really excited , no , ok well can the project. Pointless statement

'The architect/s believe they can be smarter / have more experience than the whole development team.'

Sorry Rob and Jurgeun you clearly have no ideas in application development compared to the millions of developers brainwashed on the EJB lie, you will have to can Spring and stick building inefficient monolithic applications. Pointless statement

You are trying to identify hotspots and shortcomings in advance with ...UML

If you are trying to do that anyway you seem to of taken a completely wrong career path that you

'You are thinking in pictures, not in code. You believe that pictures are more valuable than code.'

Absolutely worthless statement without any context. An architecture diagram would be worth more than some artibtary lines of code. A class and Java Doc may be worth more than a UML diagram to some. All needs context.