Effective Architecting: Best Practices for Software Architects
6 likes1,083 views
The document discusses best practices for software architects, including applying design patterns and principles to address technical debt. It provides examples of patterns used in compilers, such as the interpreter and visitor patterns for representing grammar and generating code. It also discusses expanding influence through activities like public speaking, writing, and community involvement. Key terms mentioned include SOLID principles, design smells, technical debt, and influence.
Effective Architecting: Best Practices for Software Architects
- 1. Effective Architecting Best Practices & Guidelines for Software Architects
- 2. Case Study: Patterns and Styles in Compilers
- 3. Overarching Style Lexical Analyzer Parser (Syntax & Semantic Analysis) Optimizer Code generator Pipe-and-filter style
- 6. Generating code Source: “Design Patterns: Elements of Reusable Object-Oriented Software”, Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides, Addison-Wesley,1994 Visitor pattern
- 8. Apply relevant patterns and styles for effective architecting
- 9. “Cities grow, cities evolve, cities have parts that simply die while other parts flourish; each city has to be renewed in order to meet the needs of its populace… Software-intensive systems are like that. They grow, they evolve, sometimes they wither away, and sometimes they flourish…” Grady Booch in the foreword for “Refactoring for Software Design Smells: Managing Technical Debt”, Girish Suryanarayana, Ganesh Samarthyam, Tushar Sharma, Morgan Kaufmann/Elsevier, 2014.
- 10. CodeCity tool
- 12. Code Query Language (NDepend, Architect, …)
- 13. Look at the world differently for creative design solutions
- 14. Who coined the term “code smell”? Hint: He also originated the terms TDD and XP
- 15. Kent Beck
- 16. Who coined the acronym “SOLID”? (as in SOLID principles) Hint: He is the author of the book “Working effectively with legacy code”
- 17. Michael Feathers S Single Responsibility Principle Every object should have a single responsibility and that should be encapsulated by the class O Open Closed Principle Software should be open for extension, but closed for modification L Liskov’s Substitution Principle Any subclass should always be usable instead of its parent class I Interface Segregation Principle Many client specific interfaces are better than one general purpose interface D Dependency Inversion Principle Abstractions should not depend upon details. Details should depend upon abstractions
- 18. Who coined the term “technical debt”? Hint: He is the creator of “wiki”
- 28. "This is a good book about ‘Design Smells’ – actually a great book – nicely organized - clearly written with plenty of examples and a fair sprinkling of anecdotes." - Will Tracz (Principal Research Scientist & Fellow, Lockheed Martin) (review in ACM SIGSOFT Software Engineering Notes)
- 29. Believe in your ideas: how small or “insignificant” it may appear to be!
- 30. Steve Jobs is viewed as an excellent speaker, business person, and leader. But not much as an architect. He is an excellent architect. Why?
- 32. In the movie Steve Jobs, he gives an example of a music composer. The composer directs the people and focuses on the orchestra. That is the case with a software architect as well.
- 34. As an architect, be a problem solver & technology leader
- 35. What is the key to grow big and succeed?
- 37. Other organizations Your organization Gradually expand your circle of influence Your departmentYour team The world
- 38. Some ways to expand your circle of influence Give talks (conference, workshop…) Write articles, books, white papers, … Organize meet-ups, training programs, … Contribute to process, quality, and cost- saving initiatives
- 39. Meetups • Software Architecture: http://www.meetup.com/SoftwareArchitectsBangalore/ • Container Developers: http://www.meetup.com/Container-Developers-Meetup-Bangalore/ • Software Craftsmanship: http://www.meetup.com/Software-Craftsmanship-Bangalore-Meetup/ • Core Java: http://www.meetup.com/Core-Java-Meetup-Bangalore/ • Technical Writers: http://www.meetup.com/Technical-Writers-Meetup-Bangalore/ • JavaScript: http://www.meetup.com/JavaScript-Meetup-Bangalore/
- 40. Influence is leadership - expand your influence!
- 41. Register here: https://www.townscript.com/e/designpattern SOLID Principles and Design Patterns Bootcamp Location: Bangalore 11 JUN 2016: 10:00AM - 6:00 PM
- 42. email sgganesh@gmail.com website www.designsmells.com twitter @GSamarthyam linkedin bit.ly/sgganesh slideshare slideshare.net/sgganesh