ITM 305 Chapter Notes -Systems Development Life Cycle, Formal System, Application Software

46 views7 pages
Chapter 13 Installation and Operations
1
Installation and operations
This chapter examines the actives needed to install the information system and successfully convert the
organization to using it.
Introduction
Managing the change to a new system whether it is computerized or not is one of the most
difficult tasks in any organization.
One of the earliest models for managing organizational change was developed by Kurt Lewin.
Lewin argued that change is a three step process: unfreeze, move, and refreeze.
Frist, the project team must unfreeze the existing habits and norms so that change is possible.
Most of the systems development life cycle SDLC to this point has laid the groundwork for
unfreezing
Users are aware of the new system being developed, some have participated in an analysis of
the current system, and some have helped design the new system
These activities have helped to unfreeze the current habits and norms.
The Second step is to help the organization move the new system via a migration plan.
The migration plan has two major elements. One is technical, which include how the new
system will be installed and how data is the as=is system will be moved into the to-be system.
The second component is organizational, which include helping users understand the change
and motivating them to adopt it.
The third step is to refreeze the new system as the habitual way of performing the work
processes ensuring that the new system successfully becoming the standard way of performing
the business function it supports.
Conversion
Conversion is the technical process by which the new system replaces the old system
The migration plan specifies what activities will be performed when and by whom and include
both technical aspects and organizational aspects
Conversion refers to the technical aspects of the migration plan
There are three major steps
The first step in the conversion plan is to buy and install any needed hardware
Nothing can stop a conversion plan in its tracks as easily as the failure of a vendor to deliver
needed equipment.
The second step is to install the software
The third step is to convert the data from the as is system to the to be system
Conversion can be thought of along three dimensions: the systole by which the conversion is
done, what locations or work groups are converted at what time, and what modules of the
system are converted at what time.
Unlock document

This preview shows pages 1-2 of the document.
Unlock all 7 pages and 3 million more documents.

Already have an account? Log in
Chapter 13 Installation and Operations
2
Direct conversion
With direct conversion, the new system is instantly replaces the old system.
The new system is turned on and the old system is immediately turned off.
Direct conversion is the simplest and most straightforward.
However, it is the most risky, because any problems with the new system that have escaped
detection during testing may seriously disrupt the organization
Parallel conversion
With parallel conversion the new system is operated side by side with the old system; both
systems are used simultaneously.
After some time period of parallel operation and intense comparison between the two systems,
the old system is turned off and the organization continues using the new system.
This approach is more likely to catch any major bugs in the new system and prevent the
organization from suffering major problems.
The problem with this approach is the added expense of operating two systems that perform
the same function.
Conversion location
There are at least 3 fundamentally different approaches to selecting the way in which different
organization locations are converted: pilot conversion, phased conversion, and simultaneous
conversion
Pilot conversion
One or more locations or units/work groups within a location are selected to be converted first
as part of a pilot test.
The locations participating in the pilot test are converted.
The advantage of providing an addition level of testing before the system is widely deployed
thought the organization, so that any problems with the system affect only the pilot locations
Require more time before the system installed at all organizational locations.
Also, it means that different organizational units are using different versions of the system and
business processes, which may make it difficult for them to exchange data.
Phased conversion
The system is installed sequentially at different locations.
A first set of locations are converted, then a second set, then a third set, and so on till all
locations are converted
Sometimes there is a deliberate delay between the different sets, so that any problems with the
system are detected before too much of the organization is affected.
Unlock document

This preview shows pages 1-2 of the document.
Unlock all 7 pages and 3 million more documents.

Already have an account? Log in

Get OneClass Notes+

Unlimited access to class notes and textbook notes.

YearlyBest Value
75% OFF
$8 USD/m
Monthly
$30 USD/m
You will be charged $96 USD upfront and auto renewed at the end of each cycle. You may cancel anytime under Payment Settings. For more information, see our Terms and Privacy.
Payments are encrypted using 256-bit SSL. Powered by Stripe.