Dbm/500 Week 4 Business Plan
Database Implementation Plan for Riordan Manufacturing
University of Phoenix
DBM/500
Nov 10, 2007
Database Implementation Plan for Riordan Manufacturing Riordan Manufacturing has asked our firm, LTB and Associates, to develop a web-based plan to be used as a Business-to-Business web site in order to purchase materials from their vendors. We have examined Riordan’s products and business systems, interviewed Riordan’s employees, and have determined the best course of action to implement the plan. Riordan Manufacturing is a plastics manufacturer based in several locations across the world. With three plants based in the continental US, which are located in Albany, Georgia; Pontiac Michigan; and in San Jose, California, …show more content…
Change Management The backbone to any administration plan is change management. Maintenance, database backups, upgrades, and other events must be carefully tested, planned, and executed to minimize potential consequences including data corruption and downtime, and changes must be closely tracked to preserve the integrity of the database, maintain a log of changes for troubleshooting potential issues, and ensure proper testing and compliance controls are met. The database team will use Microsoft’s Visual Source Safe (VSS) as the main tool for version control. Patches, fix scripts, and any other code that applies to the databases will be stored in VSS and proper code check in and check out procedures will be followed to ensure the proper code changes are migrated to the database. Only database administrators will have the ability to migrate changes to the databases. Developers can check out and modify code, but cannot implement any changes in the …show more content…
A network of IT and business “approvers” will be established for each business area (for example: accounting, procurement, sales, etc.) and will be responsible for signing off on changes that affect their particular areas. There will be at least one main approver and one backup approver that are subject matter experts for their respective business areas so that all areas utilizing the database will have a representative. Approvers will be the preferred testers, but other users may test changes as long as the approvers review the test results prior to signing off on the test. Signoff for changes will be obtained via email using a template that details the change to be made, a tracking number for the change, and the location in VSS where the change is stored, so that the database administrators will be able to pull the change directly from VSS for implementation. Database administrators will not proceed with migration of a change until all appropriate approvers have responded in the
University of Phoenix
DBM/500
Nov 10, 2007
Database Implementation Plan for Riordan Manufacturing Riordan Manufacturing has asked our firm, LTB and Associates, to develop a web-based plan to be used as a Business-to-Business web site in order to purchase materials from their vendors. We have examined Riordan’s products and business systems, interviewed Riordan’s employees, and have determined the best course of action to implement the plan. Riordan Manufacturing is a plastics manufacturer based in several locations across the world. With three plants based in the continental US, which are located in Albany, Georgia; Pontiac Michigan; and in San Jose, California, …show more content…
Change Management The backbone to any administration plan is change management. Maintenance, database backups, upgrades, and other events must be carefully tested, planned, and executed to minimize potential consequences including data corruption and downtime, and changes must be closely tracked to preserve the integrity of the database, maintain a log of changes for troubleshooting potential issues, and ensure proper testing and compliance controls are met. The database team will use Microsoft’s Visual Source Safe (VSS) as the main tool for version control. Patches, fix scripts, and any other code that applies to the databases will be stored in VSS and proper code check in and check out procedures will be followed to ensure the proper code changes are migrated to the database. Only database administrators will have the ability to migrate changes to the databases. Developers can check out and modify code, but cannot implement any changes in the …show more content…
A network of IT and business “approvers” will be established for each business area (for example: accounting, procurement, sales, etc.) and will be responsible for signing off on changes that affect their particular areas. There will be at least one main approver and one backup approver that are subject matter experts for their respective business areas so that all areas utilizing the database will have a representative. Approvers will be the preferred testers, but other users may test changes as long as the approvers review the test results prior to signing off on the test. Signoff for changes will be obtained via email using a template that details the change to be made, a tracking number for the change, and the location in VSS where the change is stored, so that the database administrators will be able to pull the change directly from VSS for implementation. Database administrators will not proceed with migration of a change until all appropriate approvers have responded in the