The five expertise of a software architect
Download as PPTX, PDF6 likes6,621 views
The document discusses the five areas of expertise of a software architect: 1. Technology - Having strong technical skills including writing code, understanding technologies, and solving difficult problems. 2. Technical communication - Effectively communicating technical concepts to both technical and non-technical audiences. 3. Human communication - Having strong empathy, influencing, and communication skills to work with various teams. 4. Domain knowledge - Understanding the business domain including customers, competitors, and market factors. 5. Architectural methods - Applying design principles, patterns, and processes to software architecture.
The five expertise of a software architect
- 1. The Five Expertise of a Software Architect Lior Bar-On, Senior Development Architect, SAP Dec. 2014
- 2. Who is this guy?! Working in SAP 11+ years in the software industry 7+ years as an Architect Done a lot of different stuff… A Blogger (“ (”בלוג ארכיטקטורת תוכנה
- 3. Prelude What is the Architect’s Role? What is an Architect? What are the Architect’s responsibilities? What is Software Architecture? What do we do? What are the Architect’s Interfaces?
- 4. Tim Brown (CEO @IDEO) - Shaped Person
- 5. Dineli Mather (Head of IS Dept. @Deakin University) - Shaped Person Marketers and IT architects are talking about the need for Pi-shaped skills.
- 6. In this Talk: - Shaped Person
- 7. Five Expertise of a Software Architect
- 8. I. Technology • Write code • Know the Technology • Understand the Technology • Solve difficult problems • Be familiar with many technologies
- 9. II. Technical Communication • Simplify, • Not dumbing • Main vs. Secondary • Adapt to the audience • Creating metaphors and stories
- 10. An Architect as a “Glue” dev team A dev team B “Development Architect” Product Product A dev team Product B dev team “Integration Architect” Solution Management IT / CIO / SIs / Contractors Business / LOB / “IT” or “Enterprise Architect” IT / CIO / SIs / Contractors “Solution Architect” Own Development Group
- 11. III. Human Communication • Empathy • Motivate / Influence • Recognize and Accept differences • Build an Architecture that fits the implementers
- 12. IV. Domain Knowledge • Customers • Competitors • Market “Rules” • “Where is the money?”
- 13. V. “Classical” Architectural Methods • SOLID / GRASP • Thinking in Quality Attributes • ATAM • Separation of Views • Patterns
- 14. Does having the 5 Expertise is a “must”?
- 15. Questions? Lior Bar-On baronlior@gmail.com http://www.softwarearchiblog.com/ ( )בלוג ארכיטקטורת תוכנה
Editor's Notes
- #9: בסוף העולם בו המוצרים שלנו מתקיימים – הוא עולם הקוד לכן חשוב להבין אותו More “don’t know” over “no clue” Be comfortable with more than one approach / technology stacks
- #12: Chess metaphor Understand the forces Build an architecture others can execute אפשר לומר שיכולת הארכיטקט להשפיע מורכבת מ: יכולות טכניות x יכולות אנושיות.
- #13: F-16 “faster engine” story
- #14: Most recognized with the “Architect Role” – but least frequently needed.
- #15: No. 2 or more.