We're close to the same... >Change Request via module-specific superuser. >Write up a proposal that includes description of problem, what the mod will do to fix the problem, and any ongoing maintenance that will be required as a result of the mod. Sign off from the requestor, requestor's department manager, and IT manager. >Do the mod. Programmer signs off that it's finished. >IT manager delivers change to pilot, signs off. >Superuser tests in pilot, signs off. >IT manager delivers change to live, signs off.
Amazing that the process to get a mod in place sometimes takes lots longer than the mod itself....week or two ago, I just needed to change the length of a field...uugghhh! But that's the part where we've felt the most pain. Most of the other points we had to meet were minor changes. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, August 05, 2004 12:24 PM To: [EMAIL PROTECTED] Subject: Re: [U2] [OT] Sarbanes-Oxley Same here. We have established a fairly extensive Change Control Tracking system with approval tracking at every stage. Change Request -> Approval Modification -> Approval Testing -> Approval Move to production -> Approval Final -> Approval Vance Alspach J & L Industrial Supply I was just wondering what lengths other departments/companies are doing to satisfy the requirements imposed by the Sarbanes-Oxley act? How much of an impact is it on your operations? Gordon J. Glorfield Sr. Applications Developer MAMSI (A UnitedHealth Company) 301-360-8839 [demime 1.01d removed an attachment of type image/gif which had a name of graycol.gif] ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
