We will talk about who software architect is. Why we need software architect, What is definition of software architecture, the mindset and also how the software architect manage a particular software development.

1. Software
Architect
Introduction of Software Architect
Definition, Mindset, Process

2. “Good programmers know what to write. Great ones know what to rewrite and reuse.”
by Eric S. Raymond

3. - Principal Software Architect Telkom Indonesia
- Engineering Lead of Digital Product Engineering Chapter Digital Business & Technology
- Solution Architect at Online Single Submission System (oss.go.id)
- Head of Engineer at PeduliLindungi Application
- Software Architect Lead at Telkom Indonesia
- Professional Mentor at Purwadhika Digital Technology School
- Cloud Computing Instructor at Google Bangkit
- Software Engineer
- Professional Lecture
- Researcher
- Speaker
- Author
Rony Setyawan, S.T., M.Kom., CCP.,
CSAP.

4. “The craft of programming is the factoring of a set of requirements into a set of functions and data structures.”
by Douglas Crockford

5. What is Software Architect? Architect’s
Mindset
Architectural Process Q&A

6. Section One
What is Software Architect?
Someone who has responsibility to manage the software architecture of a
particular software system.
Software Architect
Set of structures needed to reason about the system, which comprise
software elements, relations among them, and properties of both
Software Architecture
- Enterprise Architect
- Solutions/Systems Architect
- Software/Technical Architect
- Data/Information Architect
- Infrastructure Architect
- Cloud Architect
- etc
Type of Software Architect

8. Section One
What is Software Architect?
Software Architect Skills
- Enabling quality attributes
- Defining constraints on implementation
- Improving cost and schedule estimates
- Supplying a transferable, reusable, and independently components
- Carrying early design decision and alternatives
- Reducing technical debt
- etc
Why we need Software Architect?

9. Section One
What is Software Architect?
Software Architect in Organizational Chart

10. Section One
What is Software Architect?
Software Architect in Organizational Chart

11. Section One
What is Software Architect?
Software Architect in Organizational Chart

12. Section One
What is Software Architect?
Software Architect in Organizational Chart

13. Section One
What is Software Architect?
Career Path Software Architect

14. Section One
What is Software Architect?
Career Path Software Architect

15. Section Two
Software Architect’s Mindset?
1
2
3
4
5
6
1.Learn & must familiar with
the inner parts of the business
4. Always touch to end users’
view
2. Understand Weaknesses,
Strength, Competition, Growth
Strategy
5.Talking to Subject Matter
Expert with proper language
3.Defining System’s Goals that
make impact and effect on the
organization / company
6. Requirements and
Exceptions are not defined
clearly

16. Section Two
Software Architect’s Mindset?
System’s Goals

17. Section Two
Software Architect’s Mindset?
End Users’ View

18. Section Two
Software Architect’s Mindset?
Right Language for Right Person

19. Section Two
Software Architect’s Mindset?
Right Language for Right Person

20. Section Two
Software Architect’s Mindset?
Right Language for Right Person

21. Section Three
Software Architectural Process?

22. Section Three
Software Architectural Process?

23. Section Three
Software Architectural Process?

24. Section Three
Software Architectural Process?

25. Section Three
Software Architectural Process?

26. Section Three
Software Architectural Process?

27. Section Three
Software Architectural Process?

28. Section Three
Software Architectural Process?

29. Section Three
Software Architectural Process?

30. Section Three
Software Architectural Process?

31. Section Three
Software Architectural Process?

32. Section Three
Software Architectural Process?

33. Section Three
Software Architectural Process?

34. Section Three
Software Architectural Process?

35. Section Three
Software Architectural Process?

36. Section Three
Software Architectural Process?

37. Section Three
Software Architectural Process?

38. Section Three
Software Architectural Process?

39. Any Question?

40. “There are two ways of constructing a software design; one way is to make it so simple that there are obviously
no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies.
The first method is far more difficult.”
by Tony Hoare

41. THANK
YOU
See You To Next Session