1. Building a SW Architecture Group Tomer Peretz Chief Software Architect

2. The Industries We Serve Bare PCB Production FPD Manufacturing Installations (# of systems) 11,500 1,700 Solar Power New Market 2 | Corporate Presentation Advanced Packaging & MEMS Installations (# of systems) 4,000 Initial Sales 2014 Advanced Packaging & MEMS

3. Orbotech in the Electronics Value Chain Today Flat Panel Displays (FPD) Printed Circuit Boards (PCB) 3 | Corporate Presentation Advanced Packaging & MEMS

4. Orbotech SW Discipline ~150 SW and ALG developers worldwide. Globally distributed development centers. Work in multidisciplinary environment.

5. Once up on a time … There is architecture. o Is it sustainable? o who is responsible for it? o Does it meets our needs? o Is it good?

6. Where to Start? Most of the people think an software architect is the person who does the UML staff. o Acknowledge the organization software needs o Find the pains and show the remedies o Make sure you understand what the role requires Find the right people Find the right methodology o There are several approaches on the software architect role. Adjust the methodology to the organization o Or the organization to the methodology. …

7. Do We Really Need an Architect? Do we really need an architecture? What is wrong with our current process? The SW discipline manager is the architect. Team leaders are the architects. We are using Agile, so there is no need for architects. Architecture is all about commonality. Architecture is like art, you can’t put it in a process. It is good only for new projects. Do we really need an architecture? What is wrong with our current process? The SW discipline manager is the architect. Team leaders are the architects. We are using Agile, so there is no need for architects. Architecture is all about commonality. Architecture is like art, you can’t put it in a process. It is good only for new projects.

8. We Really Need an Architect Who is responsible for the SW quality attributes Who is responsible for the SW architecture Who will make sure the architecture is documented and communicated Who is seeing the big picture How can we evaluate architectural tradeoffs Who can ensure implantation and design alignment

9. Architecture Methodology

10. Architecture Centric Engineering Business & Mission Goals Architecture System Implement & Evolve Design (QAW) Design (QAW) Implement (ADD) (Views)

11. Its All About Numbers

12. Adapting the Methodology Company global distribution Company culture Company domain Multi discipline company Dealing with existing products Management methodology CultureConstrainsMethodology

13. Different Perspective of the Architect Role

14. Who is a SW Architect

15. Hands On Architect “Painting is easy when you don’t know how, but very difficult when you do” Edgar Degas Starry Night, Vincent van Gogh

16. Architect and Authority As an architect you need to influence people you don’t have authority over.

17. Architecture and Organization Structure “Organizations which design systems... are constrained to produce designs which are copies of the communication structures of these organizations” M. Conway

18. How to Train you Architect

19. Architect Soft Skills Communication and negotiation skills Presentation skills Leadership skills Groups managements skills Influence abilities Organization politics

20. Inter Organization Abilities Understand the development process. Understand the business domain. Understand the customers. Understand the organization and the stakeholder.

21. Who Should be an Architect Hands on code vs. High level view Generalists vs. Specialists Technology oriented vs. Business oriented Technological skills vs. Leader skills Domain expertise vs. Experience in other domains

22. Nominating the Software Architects Some architects were already acting as architects without the title o While other was filling only part of the role Software architects are part of the Orbotech professional path A Chief software architect to lead the group and align the goals with management Currently all software architects are part time architects The software architects continue to report to their direct managers

23. SW Architect Positioning Make sure people sees the software architect as an important role. Make sure developers sees the software architect as the person that best understand the architecture. o Costs to change the architecture o Strengths and Weaknesses of the current architecture o Methodologies and pattern Make sure the architect have access to all the stakeholders. Make this position desirable.

24. The Power of the Group Joining forces Knowledge sharing Reference architecture Room for commonality Architectural Intrapreneurship

25. The Power of the Group Technical people from different products talking together. Reflecting our current status. o Understand other product lines needs and challenges o Understand other approach strength and weaknesses Split learning topics among different people in the group. o Give presentation to the group and to the SW teams Work together on methodologies. o Brainstorming and feedbacks

26. The Power of the Group Influence and give feedbacks to corporate wide processes and decisions. o Reflect the product lines SW pains and needs to the corporate. o Responsible for assimilating architecture based decision in the product lines. If possible, create reference architecture. o Good starting point for future projects o Allow better commonality between projects o Document architecture decisions with pros and cons

27. The Power of the Groups Give inputs to other task groups in the company Collaboration with other dedicated groups

28. Our Current Challenges Small wins VS. Big wins Continue to better define the role in Orbotech Continue positioning of architects in the company Create training program Deploy the architecture process over the entire development. How to evolve? Tests impact of the group over long time?

29. 29 | Corporate Presentation THANK YOU