Presentation is loading. Please wait.

Presentation is loading. Please wait.

Role of an Architect in Software Engineering by Silpa Akkina.

Similar presentations


Presentation on theme: "Role of an Architect in Software Engineering by Silpa Akkina."— Presentation transcript:

1 Role of an Architect in Software Engineering by Silpa Akkina

2 Introduction  Special talent.  Architects create architectures.  Sound sense of business and technical strategy.

3 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

4 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.

5 Characteristics of an Architect  Technically competent  Business strategy  Organizational politics  Consulting  Leadership

6 Characteristics of an Architect - Continued  Technically competent  In-depth understanding.  Understand what technical issues are key to success.  Development methods and modeling techniques

7  Business strategy  Organization’s business strategy and rationale  Competition (products, strategies and processes)  Company’s business practices Characteristics of an Architect - Continued

8  Organizational politics  Who are the key players.  What they want.  Consulting  Elicitation techniques.  Consulting frameworks. Characteristics of an Architect - continued

9  Leadership  Self confident.  Decision making.

10 Roles &Responsibilities  Communicator  Strategist  Leader  Coherent, Intuitive and Creative  Risk assessment and Management

11 Traps and Pitfalls of an Architect  Improper reporting structure  Lack of authority  Globalization  Team composition

12 Additional Skills and Qualities  Experience  Excellent oral, written and personal communication skills  Up to date technical skills  Innovative and have a vision  Mentor

13 Conclusion  Deep understanding about technology and business factors.  Greatest challenge – communication skills.  Lead the project with minimum confusion and fuss.

14 References  Large-Scale Software Architecture, A practical guide using UML by Garland and Richard Anthony  Resources for Software Architect- http://www.bredemeyer.com/papers.htm  Web Resources http://www.softwarearchitect.biz


Download ppt "Role of an Architect in Software Engineering by Silpa Akkina."

Similar presentations


Ads by Google