ICTSAS503 - Database Migration Case Study: XYZ Company Implementation

This case study report describes the data migration process undertaken by XYZ Company, focusing on the transition from a file.txt database to a new Java database. The report details the notification process to team members, the scheduled testing of the new database, and the implementation plan. It highlights the expected improvements in functionality, reliability, and data integrity with the new database, ensuring compliance with organizational standards. The report also covers the urgency of the migration due to existing database issues and outlines the feedback meeting scheduled to discuss the implementation process with stakeholders. The conclusion emphasizes the suitability of the new database for the company's needs.

XYZ COMPANY DATA
MIGATION

Introduction
This is a report that describes the migration process of database from file.txt to new java
database. The process of data migration involves different processes (Dunn and Kelbie ,2009). This
report describes this processes from notifying members to attend the scheduled meeting to test
the database up to how the new database will be implemented.
Notification to members
Dear members,
This is notify you of data migration process that will take place in the company. The company
has decided to move its data from the old data table into a new table that is well designed to meet
the company present data storage requirements. This was decided after a long discussion
between the management team and IT experts. The IT experts explained to the management how
the database that we are using currently is more dangerous when it comes to security issues. Data
will be migrated from file.txt database to java database table that is more secure. The test of data
transfer will be carried out on 20TH OF SEP 2018 from 08:00hrs in the morning to 1300hrs. You
are currently invited to attend the meeting in the board room. Your participation will be highly
appreciated.
Expected results of the process
The newly implemented database has more functionalities than the previous one which at some
point it had some errors .This errors made the database not to meet the users’ requirements. The
new data table to be implemented has the following features which makes it more suitable and
efficient to be used by customers in the company. This features are more reliable and they are
expected to meet the user requirements .The following are some of the expected results of the
newly implemented database.
 Each item row and column field in the newly implemented database will not be left blank
in case any data updated or inserted in the database. All fields will be field with data.
 Each column will be uniquely identified from the database since it contains unique data
of a specific item.
 The data type of each column will be similar such that there is no confusion if any user
wants to view the database any time.

 Each row in the table will be uniquely identified by a particular key of certain length as
specified in the user requirements. This key can be called the primary key in this case the
primary keys will be found in ItemNo column. Each key will have length of 11 digits and
of datatype integer.
 Other columns like ItemName will have a specified a maximum number of 30 characters.
 Each column will have its on data that is uniquely defined in the column unlike the
previous database that data was separated by stroke e.g. Fantastic Furniture/Sofa.
 The table will named using the company name so that it can be easily identified with
anybody that will come across it whether in online sources or printed copies.
Organization and industry standards
The database templates complies with the organization standards. The organization requires all
fields in the new table to be filled with data .This requirements are fulfilled in the new table since
each cell in the table is filled with the required data. Each column has a specific value has
required by the organization. The table is labeled with the organization data to be easily
identifies that it belongs to the company when one come across it from anywhere.
Urgent and non-urgent results
The migration of database to new database is more urgent due to the problems that the company
has been phasing on updating data to the database. Participation as team on testing the new
database will be highly appreciated and this will make the database to be unique. Naming of the
database using our company’s is required as soon as possible this will increase the popularity of
the company.
Feedback meeting
The feedback meeting will be held on will be held on 30th of sep 2018. The aim of this meeting
is to discuss with stakeholders the implementation process of the new database. This will involve
presenting to the stakeholders report on the new database to be implemented in the company.
Your participation will be highly appreciated.

Conclusion
The implementation of the new database is good option for the company .The new database has
suitable characteristics that are suitable for the company.

References
Dunn, S. and Kelbie, P., International Computers Ltd, 2009. Database management system. U.S. Patent
5,668,991.
Granebring, A., 2010. Database Migration Structure: an Innovation Process Perspective (Doctoral
dissertation, Ekonomihögskolan).