Your architecture starts to be sub-optimal if...
- 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.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)