Software architecture introduction
Download as PPTX, PDF•1 like•446 views
The document is an introduction to software architecture by Freddy Munandar, covering various aspects such as the role of a software architect, the differences between software and enterprise architecture, and the importance of certification for architects. It discusses software architecture quality attributes, the goals of architecture, and trends impacting the field, along with certification details and salary insights for software architects in Indonesia. Lastly, it emphasizes the transition from developer to architect, highlighting the necessary skills and responsibilities in both roles.
Software architecture introduction
- 1. Software Architecture Introduction By Freddy Munandar 29 October 2016 Codigo
- 2. About Me I'm an active member of IASA Global - An Association for All IT Architects. I'm also Certified Microsoft MCPD for ASP.NET. Technology research is my favorite things especially in Software Development. I love transforming the research result by creating software that can make job or activity more faster to finish, more accurate and more fun. Ongoing open source project www.aspknife.net
- 3. Agenda • What is Software Architecture? • Who is a Software Architect? • Enterprise Architecture vs Software Architecture • Certification for Software Architect • Software Architect on Industries, are we need Software Architect? • Architecture vs Design • Software Architecture Patterns • Software Architecture Trend • From Developer to Architect
- 4. What is Software Architecture? • History • The comparison between software design and (civil) architecture was first drawn in the late 1960s • Software architecture as a concept has its origins in the research of Edsger Dijkstra in 1968 and David Parnas in the early 1970s • The term software architecture became prevalent only in the 1990s
- 5. Systems should be designed with consideration for the user, the system (the IT infrastructure), and the business goals
- 6. Software Architecture Quality Attributes IT Environment Human DynamicsBusiness Strategy Design
- 7. The Goals of Architecture • The primary goal of the architecture is to identify requirements that affect the structure of the application • Consider the following high level concerns when thinking about software architecture: • How will the users be using the application? • How will the application be deployed into production and managed? • What are the quality attribute requirements for the application, such as security, performance, concurrency, internationalization, and configuration? • How can the application be designed to be flexible and maintainable over time? • What are the architectural trends that might impact your application now or after it has been deployed?
- 8. Who is a Software Architect? “Gateway between stakeholder and developer team” “Not a must but could become technical dictator” “Obviously it’s technical lead”
- 9. More about Software Architect
- 10. Enterprise Architecture vs Software Architecture “Software Architecture is part of Enterprise Architecture (EA)” “Software Architecture can be called as Application Architecture”
- 12. “TOGAF Framework” Architecture Development Method
- 13. Certification for Software Architect • Comparing certification price • Open CA: Open Group Certified Architect • CITA: IASA's Certified IT Architect • EACOE Architect Certifications • Certified SOA Architect • CEA: FEAC's Certified Enterprise Architect • Benefit of certification • Recognition • Gives you confidence • Establishes you as a continuous learner
- 14. Open CA: Open Group Certified Architect • $1,250 certification fee; • $175 annual fee for certified participants, • $250 recertification every 3 years. • Same fees for all three levels; payable by credit card; fees are non- refundable
- 15. CITA: IASA's Certified IT Architect • CITA-F: training course $1,725 online or $2,525 onsite (exam included); exam only is $300 • CITA-A: two training courses at $500 (Business Technology Strategy) and $2,195 online or $2,925 onsite (Business Architecture) (exam included); exam only is $600 • CITA-S: $1,200 for registration and review ($600 retake cost within 12 months) • CITA-P: $2,000 for registration and review ($100 retake cost within 12 months) (Fees may vary by geography)
- 16. EACOE Architect Certifications • EACOE Enterprise Architect: Certification Workshop and Modeling costs $3,295 • EACOE Enterprise Architecture Development Review is free • Annual renewal during term of certification costs $100 • Continuation of certification is $500
- 17. Certified SOA Architect • Self-study cert kit bundle voucher: $1,196, $1,596 with exam vouchers • Individual self-study module: $299, $399 with exam vouchers • Most individual exams are $150, exam S90.09 is $175
- 18. CEA: FEAC's Certified Enterprise Architect • FEAC Commercial Black Belt Certified Enterprise Architect (CEA) Costs $11,000 ($10,000 for government employees), inclusive of classroom training and exams, both written and practicum; support for the practicum appears to be included in this fee
- 21. Software Architect on Industries • Are we need Software Architect?
- 22. 218 Software Architect in Indonesia
- 23. 11 Certified IASA CITA-F in Indonesia
- 24. 329 Certified TOGAF in Indonesia
- 25. Job Software Architect in Indonesia
- 26. Berdasarkan analisis Jobplanet terhadap informasi gaji dari 6.500 responden yang bekerja di bidang TI, Jobplanet menemukan beberapa profesi TI yang diganjar gaji rata-rata yang lebih tinggi, antara lain project coordinator, software architect, dan konsultan enterprise resource planning (ERP). Software Architect Salary in Indonesia
- 27. Architecture vs Design • All architecture is design, but not all design is architecture
- 28. Software Architecture Patterns • Architecture patterns help define the basic characteristics and behavior of an application • As an architect, you must always justify your architecture decisions, particularly when it comes to choosing a particular architecture pattern or approach. • Choosing the right architecture pattern is critical, because once an architecture is in place, it is very hard (and expensive) to change
- 31. From Developer to Architect Developer • More into coding and converned about best way to solve a particular problem • Usually no need to sell his way of working (which is often down to coding) • No involvement in strategic decisions • Tend to recommend a tool/language he is most familiar with • Goes for best technical solution • Less scope for delegation • Responsible for implementation • Heavily involved in coding • Finds a solution to a problem according to design • Soft skill less important • Often works in single project Architect • See big picture of the system before it is built • Need to convince (or sell) stakeholders about vision, ideas and recommendation • Often recommends and selects tools for strategic implementation • Evaluates and compares all available options and selects one which is best for business • Goes for best fit solution for the organization • More scope for delegation • Defines general layout of the system • Not heavily involved in coding • Finds the definition of actual problem and suggest design to solve it • Soft skill is more important • Often works in multiple projects across the organization
Editor's Notes
- #7: Quality Attributes: Design Qualities: Conceptual Integrity, Maintainability, Reusability Run-time Qualities: Availability, Interoperability, Manageability, Performance, Reliability, Scalability, Security System Qualities: Supportability, Testability User Qualities: Usability / User experiences
- #10: Ask the audience: Any software architect or tech lead or team lead here? Is the software architect job description explained here relevant to your job description?
- #11: Ask audience first Anybody already knows what is the different?
- #12: Common component of Enterprise Architecture
- #21: Suggest to take IASA Architect Core because its no vendor lock, fresh content following the latest IT trends, competitive exam price and membership price Ask audience: What do you think about the certification? How about certification benefit? Is certification matter?
- #27: Ask the audience: Are we need software architect?
- #30: Ask the audience: Anyone use Layered Architecture or Microservices Architecture?
- #32: Ask the audience: 1. How about the software architecture and software architect after you see this presentation? Interesting or not? Info the audience: This presentation is far away from detail of Software Architecture and Software Architect, need to continuous sharing and learning So on the next meetup we will deep dive one by one