the five expertise of a software architect
TRANSCRIPT
The Five Expertise
of a Software ArchitectLior Bar-On, Senior Development Architect, SAP Dec. 2014
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 (“בלוג ארכיטקטורת תוכנה”)
Prelude
What is an Architect?
What is the Architect’s Role?
What is Software Architecture?
What are the Architect’s responsibilities?
What do we do?
What are the Architect’s Interfaces?
Tim Brown (CEO @IDEO)
- Shaped Person
Dineli Mather (Head of IS Dept. @Deakin University)
- Shaped Person
Marketers and IT architects are talking about the need for Pi-shaped skills.
In this Talk:
- Shaped Person
Five Expertise of a Software Architect
I. Technology
• Write code
• Know the Technology
• Understand the Technology
• Solve difficult problems
• Be familiar with many technologies
II. Technical Communication
• Simplify,
• Not dumbing
• Main vs. Secondary
• Adapt to the audience
• Creating metaphors and stories
An Architect as a “Glue”
dev
team A
dev
team B
Product
“Development
Architect”
Product
A
dev
team
Product
B
dev
team
Solution Management
“Integration
Architect”
IT / CIO /
SIs /
Contractors
Business /
LOB /
“IT” or
“Enterprise
Architect”
IT / CIO /
SIs /
Contractors
“Solution
Architect”
Own
Development
Group
III. Human Communication
• Empathy
• Motivate / Influence
• Recognize and Accept differences
• Build an Architecture that fits the
implementers
IV. Domain Knowledge
• Customers
• Competitors
• Market “Rules”
• “Where is the money?”
V. “Classical” Architectural Methods
• SOLID / GRASP
• Thinking in Quality Attributes
• ATAM
• Separation of Views
• Patterns
Does having the 5 Expertise is a “must”?
