Pau Lo
asked on
change control 3rd party apps
How does (or perhaps should) change control work for applications your users use which arent owned/hosted by yourselves. Say for example a key application which is a web based app hosted on someone elses infrastructure. When they announce they are due to move to a new release and upgrade their system - how should that tie in with your internal change control systems? As the end of the day your end users could still be affected.
I know one element of change control is user acceptance testing - which again I find hard to see how and when you get the opportunity to do so when the system is external.
I know one element of change control is user acceptance testing - which again I find hard to see how and when you get the opportunity to do so when the system is external.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
i will also add in the case for any changes, there is always the agreement whereby if there is direct contact the provider or the main supplier whom you signed off with, they must still in no circumstances, in breach or not able o fulfill the service level of proper testing and releases - you own internal user testing is transparent to them and they would be more of answering to you so you have to manage it. If the service need to go proper test lab, they have to do so as the contract is based on "cleared" product on signing and changes may indirect be non compliant..