Problem
Your Change Request should include the following sections. This means each section in your change request has the following information. This change request form covers how the business and the technology will change. This is not a change request for a project. A project would be setup based on this change request.
A. Change Request - Initial Request. For this section assume the request is made by the sales team. They notice that their inventory collection has gotten really big and accessing it is extremely slow. They want to double the table size and double the performance for accessing. This is a high priority request to improve worker productivity.
B. Change Request Analysis. Provide a detailed technical explanation of what needs to be changed and why. Determine why the performance is an issue based on your understanding of how MongoDB works.
C. Database Current State. Provide screen shots of all current database settings that will be changed per this change request.
a. Specify which settings will be changed. Use one shell method for the database, one shell method for the collection, and one shell method for the collection size. Provide screen shots of using these methods and what the results of these methods show.
D. Change Procedure. Specify the high-level steps required to implement the change. DO NOT go deep into MongoDB coding.
a. Specify the shell methods and how to best use them to support your high-level procedure. Provide the results of each shell method.
E. Roll Back Procedure. Specify the high-level steps required to reverse the change.
a. Specify the shell methods and how to best use them to support your high-level procedure. Different versions of MongoDB may not have a rollback method. If the version of MongoDB you downloaded doesn't have that method you will need to provide a script that undoes the change by recreating the database environment.
F. Change Request Completed. Provide screen shots of the database's new settings, emphasizing only those settings that changed.