Does your existing application always have parts that need to be rewritten? Is your application impossible to test? Does it feel like you are constantly writing the same code repeatedly? Volatility and tight coupling are likely part of your problem.

In this session, we will discuss techniques to detect and isolate volatility in your software architecture (and requirements). By isolating volatility in your architecture, teams will be able to better decouple components, test the system and offer protection from changing requirements. We will also discuss how to apply these techniques to existing legacy applications and when designing new applications and/or services. In addition, the session will cover some guidelines and warning signs that you are over-designing/engineering your solution.

Whether you are new to being a software/solutions architect or have 20 years of experience, this session is sure to spark hot debate and engaging conversations. This session “may” touch on some controversial architectural concepts/ideas; we encourage you to be interactive and vocal!