Knowledge Sharing on Deployment Models and Best Practices for Siebel

Hi,

I am currently working with a Siebel development team and would like to hear from others in the community how their deployment models look like as we are reviewing our current deployment model and are looking for a deployment model that allows us to be flexible and managed several releases but still provides containment for different test phases.

As it looks today we have 3 environments in the deployment chain:

Environment A - Development  (DEV)

Environment B - Test (Functional/Regression)

Environment C - Quality Assurance (QA) and Production

Environment C is sharing the same Siebel instance and server hardware which I find unusual coming from a more traditional development background as I would expect more separation of the QA and Production environment, but please feel free to comment on this aspect as much as you like as I would like to understand whether this is a typical setup for Siebel deliveries. I also believe the current deployment model also limits the way we can run performance and load testing.