Data Conversion Plan: Strategies, Preparations, And Specifications

Through the brief study of this assignment, it can be clearly stated that:

1. Who are liable for interacting assignment data

2. What are the communication needs regarding every assignment stakeholders

3. What origins the assignment distributes for interaction

4. How some susceptible or secret data is interacted and who should permit this

5. How transformation in interaction or the communication method are administered 

Ideally, the sole purpose of having a data conversion plan is to ensure that flaws are eliminated in the process of migration thus ensuring that the resulting data in the migration process is adequately validated in line with the intended task (Gordon, 2013). Even more, a well-defined methodology is important in preparation and execution of a successful data migration process. Security and privacy considerations are also paramount due to the sensitivity of some of the information (Gordon, 2013). This data conversion plan describes the strategies, preparations and the specifications for the process of migrating existing data to the testing platform at Brewton Enterprises. Included, is the overall approach, assumptions, and the processes that will be used in the migration. Further, the process of extracting, transforming, and loading the varied data sources is outlined; data migration tools and how quality assurance and control will be ensured. The intended audience at Brewton Enterprises Data Conversion Plan is the assignment administrators.

The following limitations must be put into consideration prior to data migration of the existing data to the testing platform. The hardware and software environment, the end-user environment, availability of resources, the order in which is to be processed by the test platform, protocol requirements, the volume requirements that entails the database size, the amount of data to be migrated and the time needed for the completion of migration and lastly, the security requirements.

The following are important before the data migration or conversion process. Firstly, there are prerequisites to data migration such as verification that the setup on the source system matches that on the test platform and verification that the hardware and software on both sets of systems are on the same patch level. Secondly, a backup strategy should be put in place that offers an option for data restoration in the event of a storage or server failure (Mogann, 2017). Lastly, a restore process to enable a reversal of the process of migration if need be. This could be necessary for the event an error is detected during the process (Mogann, 2017). 

During data migration or conversion process, there are three landmark procedures that will be undertaken: extraction, transformation/ cleansing, and data loading. During extraction, relevant data is copied from the source application database. This data remains untampered with. During this stage, the data is enriched with data not previously contained in the source but important in the in the platform. The following extraction is transformation or cleansing during which fine-granular filtering is a test conducted to establish the kind of data needed by the target application. Contained in the transformation program are the data mappings mediating the two destinations involved in the migration or conversion. The last step of the conversion/ migration process is the data loading. During this phase, data is loaded into the database of the test platform. Some systems allow for data to be written directly into the database of the testing platform.

Constraints

This lists the conversion activities to be undertaken in accordance with the data conversion plan. The tasks are listed in chronological order with the time frame indicated. Further, key personnel- management testers, developers, and end-users- for the relevant tasks are listed including the dependencies and the milestone. (table)

Quality assurance refers to the process of profiling data in order to ascertain inconsistencies if any, amongst other anomalies. Also, data cleansing procedures are conducted here to enhance the quality of data (Loshin, 2017). Quality control, on the other hand, entails the regulation of data usage to known quality measures. This process follows the process of data quality assurance. Established from the above are; how severe data inconsistency might be, the incompleteness of data, accuracy, data precision and missing or unknown pieces of data (Loshin, 2017).

Success in user testing is hugely determined by setting up the right test environment (Khanduja, 2017). There are various key areas that are required to facilitate the above mentioned. To begin with, the hardware includes test setup PC that will comprise of removable media storage devices, Display stations, Printers and scanners; Communication controllers, hubs, routers and modems, Power distribution unit and the database server (Lee, 2017). Further, the software and network configurations are needed in the test environment applications, such as the office package, drawings … Also, the environmental data that entails the standard test data sets. Moreover, a read-only copy of the source database and a clean copy of the target database. Lastly, the maintenance tools or processes that encompass a couple of point contact for the maintenance of the test environment, an agreement regarding the readiness and the quality of the test environment and knowledge of all the members involved in the test environment maintenance (Lee, 2017).

The personnel in the test environment include the management testers, developers, and end-users

There are various methods and the respective procedures that are used to conduct testing. Performance testing is a non-functional testing type that determines how fast some aspect of a system performs under a certain load of work amongst other purposes such as demonstrations that a system meets some particular performance criteria (Rouse, 2017). Further, the performance testing establishes the part of the system or workload that leads to poor system performance. The process sometimes involves quantitative tests such as measurement of the response time or the speed (millions of instructions per second) of the system. It is one of the most critical parts of the process of system development (Rouse, 2017).

Data conversion/ migration preparation

The procedure for performance testing is as follows. First, identify the test environment. This includes the software hardware and the network configurations. This allows for efficiency in the test design and identification of potential challenges beforehand. Second, identify the performance acceptance criterion that entails the response time, throughput, and goals and constraints related to resource utilization. The third step involves planning and designing tests putting into consideration key scenarios and determination of variability. The fourth step entails configuring the test environment in preparation to execute each strategy in accordance with the availability of components and features. Fifth, the test is implemented by developing a performance test that takes into consideration the best practice of the test design. Sixth, the test is executed, monitoring it as it runs. 

Load testing involves the application of ordinary stress to a system to ascertain whether its performance can, under normal conditions, be replicated (Menasce, 2002). Basically, the test is meant to ensure that a certain function of the system as a whole has the capability of comfortably handling what it is designed to handle. According to the Microsoft guide on testing web applications load testing is described as a procedure that allows a developing team to establish the measure of the response time, throughput rates and the levels of resource utilization in addition to identifying the breaking point of an application under the assumption that the breaking point is experienced below the peak load condition. Conducted, are the test validation, test data, and collection of results. Last, the results are analyzed (individually and as a team), report prepared and a retest conducted (Menasce, 2002).

It is important to note that load testing follows a similar process to performance testing i.e., identification of the test environment, identification of the performance acceptance criteria, planning and designing the tests, configuration of the test environment, followed by implementation of the test by developing a load test and finally the test is monitored as it runs. 

References

Khanduja, J. (2017). What is a Testing environment for software testing? - Quality Assurance and Project Management. Quality Assurance and Project Management. Retrieved 29 May 2017, from https://itknowledgeexchange.techtarget.com/quality-assurance/what-is-a-testing-environment-for-software-testing/

Mcgann, J. (2017). Data Migration Strategies: Retiring Non-Production Backup Platforms | Data Center Knowledge. Data Center Knowledge. Retrieved 29 May 2017, from https://www.datacenterknowledge.com/archives/2015/03/11/data-migration-strategies-retiring-non-production-backup-platforms/

Loshin, D. (2017). Five steps to an improved data 5 assurance plan. SearchDataManagement. Retrieved 29 May 2017, from https://searchdatamanagement.techtarget.com/tip/Five-steps-to-an-improved-data-quality-assurance-plan

Menascé, D. A. (2002). Load testing of websites. IEEE Internet Computing, 6(4), 70-74.

Rouse, M. (2017). What is performance testing? - Definition from WhatIs.com. SearchSoftwareQuality. Retrieved 29 May 2017, from https://searchsoftwarequality.techtarget.com/definition/performance-testing

Gordon, D. (2013). Developing a Data Conversion Plan - The Practicing IT Project Manager. The Practicing IT Project Manager. Retrieved 29 May 2017, from https://blog.practicingitpm.com/2013/07/20/developing-a-data-conversion-plan/

Paygude, P., &Devale, P. R. (2013). Automated data validation testing tool for data migration quality assurance. Int J Mod Eng Res, 3, 599-603.

Lee, J. (2017). Scenario: Configuring a Test Environment for Web Deployment. Docs.microsoft.com. Retrieved 29 May 2017, from https://docs.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/scenario-configuring-a-test-environment-for-web-deployment