K
koes0030
Hi all,
I am working on helping my company better define their software change control process. Currently, we have a standard process that is used for planned releases, and a "hot fix" that is used for more urgent releases... currently, the only difference between the two processes is the ability to use an abridged testing plan for the hot fixes... a review board meets to determine and document which tests must be done, which ones don't, etc... for some simple fixes, not much testing is needed. Today we were discussing the potential need for an immediate/critical fix... in the event that the service goes down, or a really nasty bug(maybe potential for risk to patient safety) is found, our engineers would like the ability to deploy a fix ASAP, prior to getting all of the documentation in place, performing all the validation/verification testing, etc.
In our regulated world, I'm not seeing how we can make this work... how could it ever be OK to push software to production (release a device) prior to testing it to make sure it is safe and works properly? Then again, I'm new to the software device realm, so I'm wondering if anybody has any insight on this matter. Is this totally impossible?
I am working on helping my company better define their software change control process. Currently, we have a standard process that is used for planned releases, and a "hot fix" that is used for more urgent releases... currently, the only difference between the two processes is the ability to use an abridged testing plan for the hot fixes... a review board meets to determine and document which tests must be done, which ones don't, etc... for some simple fixes, not much testing is needed. Today we were discussing the potential need for an immediate/critical fix... in the event that the service goes down, or a really nasty bug(maybe potential for risk to patient safety) is found, our engineers would like the ability to deploy a fix ASAP, prior to getting all of the documentation in place, performing all the validation/verification testing, etc.
In our regulated world, I'm not seeing how we can make this work... how could it ever be OK to push software to production (release a device) prior to testing it to make sure it is safe and works properly? Then again, I'm new to the software device realm, so I'm wondering if anybody has any insight on this matter. Is this totally impossible?