Validating non-functional requirements only at the end of the project can lead to significant rework in the architecture and software, making necessary changes difficult and costly.

If you're not testing these non-functionals in the development process, it might be harder to make the changes that need to be done when you test these criteria at the end of the project. Your architecture choices typically influence the system's performance, scalability and reliability.

Ensure you incorporate the validation of non-functionals as early as possible in your development process. This will identify potential issues early, allowing for timely adjustments and ensuring the final product meets all necessary criteria. In this session, Tom will show the audience how to leverage the possibilities in Azure to verify your non-functionals using real-world examples.