- Big systems are hard to get right. Thinking about “architecture stuff” up front is necessary for success.
- Architecture is the bearer of quality, but reasoning about architecture is actually reasoning about the potential of a system.
- Performance and flexibility really do trade off against each other.
- Reprioritizing architectural qualities is extremely risky.
- Don’t forget “saleability” and “marketecture.” They can help you sell a system to upper management before it is built, even if they offend a “pure” architecture sensibility.
- Autonomy of organizations and systems is paramount, and this autonomy happens to be the foundational principle of service-oriented architecture.
- If you don’t know where you’re going, you’re not going to get there—regardless of how good your map is.
- Technology doesn’t matter. What does matter are people, the process, and the consistency of practice.
- Architecture validation is critical but hard to institutionalize—even in a process-oriented organization.
- The deepest problems in IT are still communication and understanding.
- Don’t let “pragmatism” become a disguise for shortsightedness.
Reference:Lessons Learned about Software Architecture @ SEI
Quote:
“Architecture is not a set of PowerPoint slides, It’s the bridge between the business goals and the way a system operates.” Michael Gagliardi
