- Architect also implements
Each architect should also implement. This is very important, because as a architect you make decisions about performance, scalability and similar stuff. Without any technical backround these issues are very hard to design/answer.
- Senior Developer = Software Architect
It is important the a software architect has experience in software development.
- Manages makes the final decision
One man of the management must make the final decision. The software architect prepares the material which are used for the decision
- Ivory-Twoer Architect:
The purchase to the reality lost
- One Man Show:
The software architect makes everything alone
- Single point of decision:
The software architect must decide everything, e.g. implementation details.
- Design by Committee:
On the other side, it makes no sense to make all decisions in the team which ends in a never ending discussion. A good mixture is the answer.
- Architecture by implication:
Architecture is not documented.
- Architecture without review:
- Meta architecture:
Software architect remains too abstract
- Customers are idiots:
The Software architect is not a God!!
- No Refactoring:
The management does not give time for refactoring