"Testing and DeploymentFunctionality Testing ChecklistChecklist Description:The purpose of this checklist is to ensure that all stakeholder requirements are met, and that alldesign specifications are within budgetary and technical constraints.Project Name: Review Date: Lancaster Community College – Student Database ImplementationReviewer: Signature: General Design Comments Does the overall design of the system meet your needs as an end user?Is the user interface efficiently designed and easy to understand?Are all of the features necessary for your job tasks present and working?Are there features that should be included that have not been? Adoptability Comments Are there any concerns you can see in eliminating the old system? Will you require additional training in order to complete your job tasks with the new system? Will the implementation impact your job tasks in a negative way?Does the system make it clear where to go for assistance?Does the system allow you to access it from all of the necessary locations?Are there any features present that should be removed? Performance Reliability Comments Based on the published performance results, are you satisfied with the new system?Functionality Testing Checklist Do the performance expectations of the system meet your daily job task needs and your expectations?Productivity Impact Comments Will the new system enhance your productivity or efficiency in work?Are there any considerations that were missed in changing from the old system to the new? Are there any unforeseen burdens placed on your position due to the new system?Are technical and help documents readily available to you? TestersFirst, to test the database for errors, bugs, malfunctions and fix them. Then customersatisfaction, changes that need to be made. Make sure the database does it said it would do forthe school.Security. Single-Sign On authentication with active directory and the web server. Database daily operation procedures (data entry – add students, search for them, add classes tostudents, see other financial aid documentation, see all application statuses, etc.)The databaseadministrator / developer, the tester, which would be an end-user (stakeholder, student testaccount, faculty and staff test accounts).Deployment ScheduleAfter testing, the new system will be implemented in a single school department at atime, ending finally with the full deployment to outside users including students. Thedeployment will occur over the period of 1 week for each department. Once implemented in adepartment, the deployment team will remain physically on-site in order to support the newusers. After full deployment is realized the support team will then remain on-site for an additional 2 weeks for support, and be available through remote communications for a period of1 year.It will be deployed in phases to certain school departments first, so the system can be inproduction for some period of time before it gets rolled out to all the school departments. Thiswill depend on the school readiness, hours of operation and critical timing.Downtime and Data MigrationAs there is currently not a system in place, there will be no downtime for the currentsystem. Data Migration will occur for each department in the week following the rollout in theirdepartment with full migration to be completed over the following 6 months.Rollback PlanThere should and will be a rollback plan.This will be on in the case where the complete database fails to do what it was designedto do.Users will be trained and little by little system will be deployed to the whole school.It will start off on a per-department bases, get tested out and end-users get accustomed to the dataentry, search, reports and all the functions the database has to offer for them.The database will always have a daily and instantaneous backup every time data isentered into the database system.In the case where the database fails, there will be an option fora temporary rollover to fix any issues, then immediately go back to using the database normally."