How are upgrades tested in a non-live environment before going live ?

S

supergrass207

New member
<<Q/How would a computerised system be upgraded, by adding new functionality ? Won't the changes likely muck up?
the existing system so the intent of enhancing the system is not achieved ? I realise there are reliable methods for enhancing a system, but how does one actually go about it ? It all seems a bit like deactivating a bomb - "cut this cable here" - there would need to be a very high level of confidence and trust - How do you achieve that ? Recruit trustworthy people ?

A/ by M O R P H E U S /Ugrades nearly always create compatibility problems. That's why, when possible, it's best to test the upgrades in a non-live environment before going live.>>
 
Hi,
Systems are almost always being upgraded or fixes are being introduced. Most system developers run two systems - the development (non-live) system and the live (production) system. The development system is used to test changes to systems before they get uploaded into a production system - this is what is known as a non-live environment. Once the changes pass the tests, they are introduced to the live (system that a user is using to be productive) system and users are asked to look for anomalies in the use of the system. The "bugs" are identified, they get corrected, they are re-introduced into the live system, etc. This continues throughout the life cycle of a production system.
 
Back
Top