Hello again!
Just wanted to add that derived tables are executed sequentially - the source table is executed first, and afterwards the derived table. You will find a useful diagram in this thread: Understanding derived table execution sequence.
In the case you have a complex workflow with many tables and sequence actions, you can also split whole groups of tables into modules. So you run certain actions, and afterwards you call a certain module, that contains all the sequence of actions that need to take place afterwards. It's a way to simplify execution order management when there's many tables to take care of. More information on modules: Calling modules/projects (subroutines).