My First Architecture Deliverable

The first artifact that I come out is the Application Architecture Document. This is high level, architect to architect communication.

Senior developer will understand this document. It is a single starting point for all other technical requirement for the software.

Yes, it's high level. I will tell, it is high level and serve as the starting point for the rest of the detail designs. By looking at the high level class diagram. You will automatically know what to be derived in detail design or even coding. That's the achievement of this artifact.

I am still junior to this... let take a look of my scratch.. below. Hope to expose more artifact, however there is confidentiality need to be protected. It really look like a board design.

What it take to be Software Architect

After sometime being Solution Architect with Avanade (Microsoft Arm of Accenture). I start looking for more tips on how to be better solution architect.


One key point which is Architect is to save money. In current economy, we really have no luxury to over commit. Technical leadership become very important in this.


Sometime, young developer might be over passionate to what he/she is developing. Architect is the one who put a stop and give a wise technical decision in term of cost. Only an experience architect will able to give cheaper solution and target to the right customer. Know what the customer really want. Don't give a BMW for a retired mother.


It is quite a challenge for me to put a stop to the passionate developers. They are really keen. Easily get offended if this is not communicated well. Per half some stand up meeting. Open for discussion. Reader please help.


With some googling, i found these information.


Why We Need Architects