Role of an Architect in Software Engineering by Silpa Akkina
Introduction Special talent. Architects create architectures. Sound sense of business and technical strategy.
Definition Technical leadership based upon experience and knowledge. “A good Architect is the principle keeper of the user’s vision of the end product” Norman Simenson
Need of an Architect in Software Engineering To design and build a software product Leads the architecture team, developer community and the organization. Apex of the software engineering process. Effective communication.
Characteristics of an Architect Technically competent Business strategy Organizational politics Consulting Leadership
Characteristics of an Architect - Continued Technically competent In-depth understanding. Understand what technical issues are key to success. Development methods and modeling techniques
Business strategy Organization’s business strategy and rationale Competition (products, strategies and processes) Company’s business practices Characteristics of an Architect - Continued
Organizational politics Who are the key players. What they want. Consulting Elicitation techniques. Consulting frameworks. Characteristics of an Architect - continued
Leadership Self confident. Decision making.
Roles &Responsibilities Communicator Strategist Leader Coherent, Intuitive and Creative Risk assessment and Management
Traps and Pitfalls of an Architect Improper reporting structure Lack of authority Globalization Team composition
Additional Skills and Qualities Experience Excellent oral, written and personal communication skills Up to date technical skills Innovative and have a vision Mentor
Conclusion Deep understanding about technology and business factors. Greatest challenge – communication skills. Lead the project with minimum confusion and fuss.
References Large-Scale Software Architecture, A practical guide using UML by Garland and Richard Anthony Resources for Software Architect- Web Resources