Modern Software Engineering relies on battle-tested Software Architectures and Architecting Techniques to deliver not only a product successfully but to allow that product to be maintainable throughout its lifespan. One such technique is that of Trade-Off Analysis where you look at all the possible Software Architectures that could solve your problem and you choose ‘the least worst one’ (a term coined by Neal Ford & Mark Richards). The execution of Trade-Off Analysis can be the deciding factor in whether your software system flourishes and is a joy to work with or is laying the foundation for future Developer horror stories.

In this talk, we’ll discuss Modern Trade-Off Analysis for Software Architectures. How to look at different architectures and choose which to utilize based on the importance of their benefits to the project and how significant their weaknesses would be. But we will not learn these techniques by looking at successful software projects, the systems they created and what Trade-Off Analysis they potentially made…

Let’s learn Modern Trade-Off Analysis through the eyes of a Street Fighter player, who does this same analysis every game, but only has an average of 100 seconds to do it in.