I tend to observe interesting trend, appearing one and then here and there - people overuse the words "architect" and "architecture" when they speak about software: every diagram is "an architecture blueprint" every design document is "an architecture overview" every analyst who creates a high-level design document is a "solution architect" It looks like every word that starts with "arch-" makes the entity named more serious and professional ;) Noblesse oblige ;> So, what does make an architect? When can someone call him an architect? What’s the difference between a design and system architecture, between a developer and an architect?…