Training Management Information System (TIMS) Implementation Plan

This article discusses the implementation plan for Training Management Information System (TIMS) including installation process, testing plan, data conversion plan, changeover method, and post-implementation review.

Running Head: INFORMATION SYSTEM DEVELOPMENT
Information System Development
Name of the Student
Name of the University

1INFORMATION SYSTEM DEVELOPMENT
1. Training Management Information System (TIMS) Implementation Plan
a. Installation Process
Installation of the Training Information Management System (TIMS) will require
upgradation of the existing hardware. After hardware installation is complete, a cloud
subscription is required to store and manage all training related data that will be gathered in the
system (Jan et al., 2016). Finally, the TIMS software will be installed in the system and
connected directly to the cloud database.
TIMS will be used to enhance the working skills of the employees who in turn will
increase the business productivity of the organization. A realistic timeline for the project is
shown as follows.
Task Name Duration Start Finish
Installation of TIMS 78 days Mon 11/26/18 Wed 3/13/19
Planning of TIMS Implementation 18 days Mon 11/26/18 Wed 12/19/18
Identify issues with current system 5 days Mon 11/26/18 Fri 11/30/18
Propose implementation of TIMS 1 day Mon 12/3/18 Mon 12/3/18
Determine the required features
for the TIMS
2 days Tue 12/4/18 Wed 12/5/18
Receive approval to proceed 0 days Wed 12/5/18 Wed 12/5/18

2INFORMATION SYSTEM DEVELOPMENT
Hire Team for Project
Implementation
10 days Thu 12/6/18 Wed 12/19/18
Recruit Development Team 4 days Thu 12/6/18 Tue 12/11/18
Discuss the requirements of the
project
4 days Wed 12/12/18 Mon 12/17/18
Allocate the budget 2 days Tue 12/18/18 Wed 12/19/18
Provide green light to proceed 0 days Wed 12/19/18 Wed 12/19/18
Installation and Implementation
Plan
32 days Thu 12/20/18 Fri 2/1/19
Analyze the requirements of the
organization
2 days Thu 12/20/18 Fri 12/21/18
Purchase computer parts as
necessary
5 days Mon 12/24/18 Fri 12/28/18
Purchase updated hardware
peripherals as required
3 days Mon 12/31/18 Wed 1/2/19
Assemble the computers 10 days Thu 1/3/19 Wed 1/16/19
Test the running and functioning
of the computers
2 days Thu 1/17/19 Fri 1/18/19
Purchase necessary software 2 days Mon 1/21/19 Tue 1/22/19

3INFORMATION SYSTEM DEVELOPMENT
Subscribe to Cloud Computing
service
1 day Wed 1/23/19 Wed 1/23/19
Install the software in the
computer systems
1 day Thu 1/24/19 Thu 1/24/19
Install firewalls in the systems 3 days Fri 1/25/19 Tue 1/29/19
Install anti-virus software in the
systems
1 day Wed 1/30/19 Wed 1/30/19
Check the features and working of
the installed software
2 days Thu 1/31/19 Fri 2/1/19
Testing 19 days Mon 2/4/19 Thu 2/28/19
Unit Testing 5 days Mon 2/4/19 Fri 2/8/19
Integration Testing 5 days Mon 2/11/19 Fri 2/15/19
System Testing 5 days Mon 2/18/19 Fri 2/22/19
Finalization of the System 4 days Mon 2/25/19 Thu 2/28/19
System Handover 0 days Thu 2/28/19 Thu 2/28/19
Post Project Review 9 days Fri 3/1/19 Wed 3/13/19
Gathering facts for review 3 days Fri 3/1/19 Tue 3/5/19

4INFORMATION SYSTEM DEVELOPMENT
Review of the project 4 days Wed 3/6/19 Mon 3/11/19
Finalization of payments 2 days Tue 3/12/19 Wed 3/13/19
Stakeholder Signoff 0 days Wed 3/13/19 Wed 3/13/19
b. Testing Plan
i. Unit Tests
The unit test process is the first step for the TIMS software testing. This testing will be
conducted through White Box Testing process for analyzing the internal structure of the TIMS
and will include the following steps (Barr et al., 2015).
 Preparation of Unit Test Plan
 Development of Unit Test Cases / Scripts
 Performing the Unit Test Using the Test Cases
ii. Integration Tests
In these tests, the individual units or components identified above will be combined and
tested in form of a group rather than separate units. The integration tests will be conducted to
determine whether there are any errors or problems in the interface. Integration tests are to be
done in two main steps – component integration testing and system integration testing. The first
step mainly involves testing of the system components in groups and the second step involves
testing of the system as a whole.

5INFORMATION SYSTEM DEVELOPMENT
iii. System Tests
The final step of testing is the system test in which the entirely integrated software is
tested as whole (Barr et al., 2015). Similar to the unit testing, system tests also involve
preparation of test plan and test cases but in this case, instead of units, the entire system is tested
as unit. The project can be handed over once the system tests are completed and all the errors and
issues have been solved.
c. Data Conversion Plan for TIMS
In order to implement the TIMS, data conversion is also required so that the existing data
can be integrated within the next system. Most of the current data are stored in the form of paper
documents while some basic data are stored in the existing computer in MS Word format. During
migration, all the offline and online data will be entered into the computer and saved in pdf
formats in the cloud storage space available for the TIMS.
d. Changeover Method for TIMS
There are several changeover methods that are mainly been selected based on the
operational requirements of the organization. For this particular case, the most suitable
changeover method will be parallel running i.e. the existing processes will continue while the
TIMS will be implemented (Jan et al., 2016). Once the implementation is complete, the
processes can be migrated into TIMS.
e. Post Implementation Review
i. Fact Gathering Methods for the Review
For the purpose of the review, fact gathering is required to verify whether all the
requirements have been met. In this case, a suitable fact gathering method can be personal

6INFORMATION SYSTEM DEVELOPMENT
interview in which, the developers will be interviewed to understand what they have performed
in this process (Jan et al., 2016). Validation of project progress report is another reliable method
for gathering facts regarding the project during the review process.
ii. Topics to be Addressed
During the review process, a number of topics need to be addressed before sign off is
done. These topics are as follows.
Milestones – It is to be determined whether all the milestones of the project have been
successfully reached. Often, project team members skip milestones to complete the project
within time and budget.
Deliverables – It is to be reviewed whether all the deliverables have been met in the
project (Barr et al., 2015). All deliverables are necessary parts of the project and even one
exclusion can cause major problems for the company.
Time Frame – It is required to be reviewed whether the specified time frame has been
fulfilled in the project. Exceeding the time limit can cause financial losses for the organization.
Budget – It is to be checked whether the budget of the project has exceeded the estimated
value or not.
iii. When Review Will Occur
The review will occur when all the software tests are complete and the TIMS is handed
over to the management team. Without this review, the project cannot be closed and residual
payments will not be processed.

7INFORMATION SYSTEM DEVELOPMENT
iv. Who Will Participate in the Review
The members of the management team of the organization will participate in the review
with the assist of the existing IT manager of the company.

8INFORMATION SYSTEM DEVELOPMENT
References
Barr, E. T., Harman, M., McMinn, P., Shahbaz, M., & Yoo, S. (2015). The oracle problem in
software testing: A survey. IEEE transactions on software engineering, 41(5), 507-525.
Jan, S. R., Shah, S. T. U., Johar, Z. U., Shah, Y., & Khan, F. (2016). An Innovative Approach to
Investigate Various Software Testing Techniques and Strategies. International Journal of
Scientific Research in Science, Engineering and Technology (IJSRSET), Print ISSN,
2395-1990.