For the beginner architect, there are many options for doing pretty much anything. But for the Master architect, there are only a few. In this dense session Juval Lowy will explain his approach to large system analysis and design, using volatility to decompose a system into its comprising services. Juval will contrast it with the most common mistake done in architecture, using functionality to identify services. These are universal design principles, and Juval will use examples from software and non-software systems alike. You will also see how to overcome the real hurdles architects face pursuing volatility-based decomposing, simple and practical techniques for identifying areas of volatility, common telltale signs or "smells" when your design is still functional when using the Method, IDesign's approach for system architecture. You will see how to literally mechanize software system design, how to do it quickly and effectively.