Dependency Management?

[Jon Paynter]

Can controlTier do dependency management in a declarative way something like how Apache Maven handles dependencies at build time?

Im trying to see how controlTier can model our inter-process dependencies AND allow for ease of updates in the future.
Take the following case:
Web server talks to a back-end process.  The back end process makes calls to the DB, and posts messages on EMS queues.

When its time to do a db update, the DB, the back-end process and the webserver need to be shut down (in that order), and then started in the reverse order once the update is done. And then a simmilar procedure for EMS updates, and back-end process updates.

Now im sure its possible to construct controlTier services to handle the 4 components, and create start/stop scripts for each of them and have it work just fine.  But later on when more web servers and back-end processes are added into the mix, all the existing scripts must be updated to handle the new servers and processes.

Is there a way to model dependencies between controlTier services?
And model them in such a way that if I change the relationships, I dont have to re-write all my stop/start scripts?

Take the case of adding a cache server between the back-end process and the DB.  I dont want to have to re-code the start scripts for the webserver to take into account the new cache server.

Is any of this possible with controlTier?
If so - how?