Scribd
Upload
19 views17 pages

Installation 20241126 195541 0000

Uploaded by

Hazel Mae Martin Casarino
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
19 views17 pages

Installation 20241126 195541 0000

Uploaded by

Hazel Mae Martin Casarino
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

INSTALLATION

Ishie Laus & Camille Gaurino


Installation is the transition from the old system
to the improved or new system. This also refers to
the conversion of an outdated system to a more
modern one. At this point, all users must stop
relying on the existing system and start relying on
the new system. Direct, parallel, singlelocation
and staggered installation are the four methods
available. The scope and complexity of the
organisations and the system will determine
which approaches are used.
www.reallygreatsite.com
DIRECT INSTALLATION
A sudden cut-over installation is another term for direct
installation. Direct installation entails turning off the old system
and turning on the new one Figure 4-3. The old system will be
shut down at this hour on this date, and the new system will take
over. This strategy carries a high risk because there might still be
significant issues that aren't discovered until the system has
been in use. Users will directly be affected by errors caused by
the new system, and how they perform their duties will depend
on it. If the system cannot be used on that date, there may be a
delay while the errors are fixed
www.reallygreatsite.com
This strategy can be required, for instance, if the
system cannot be implemented before a corporate
policy takes effect on a certain date. Making sure that
the system works well is crucial if the firm intends to
employ this strategy because it will make it less
hazardous. Even though it's a risky approach, it might
lower the installation costs.

www.reallygreatsite.com
www.reallygreatsite.com
PARALLEL INSTALLATION
As shown in Figure 4-4, a parallel installation occurs when both the
old and new systems are running concurrently up until the
management decides the old system can be turned off. This
strategy is referred to as a riskless strategy because all significant
issues are resolved before the old system is shut off. Direct
installation is the reverse of this strategy. Despite being risk-free, it
came at a considerable expense because the company needed to
run two systems concurrently. Running two identical systems
simultaneously can be quite expensive, both in terms of maintaining
them and paying the salaries of the employees. Users can
occasionally become perplexed because
www.reallygreatsite.com
of having to deal with two
systems.
www.reallygreatsite.com
SINGLE LOCATION INSTALLATION
Site or pilot installation are both terms for a single location. This strategy
involves the organisation testing out a new system at a single location
before deciding how the completesystem should be implemented across
the organisation, as shown in Figure 4-5. Direct installation or parallel
installation are both options for a single-site installation.

Compared to direct and parallel installation, it is a moderate strategy.


One department or one branch office might be referred to as a single
location. The system will be installed at the other place as soon as the
first location approves it. Since all the significant issues at the initial test
location have been resolved, the installation at another site can be done
directly at this point. www.reallygreatsite.com
PHASE INSTALLATION
Like single-location installation, phase installation (Fig. 4.6) differs in
that the new system is installed in functional components. A new
system is implemented incrementally, module by module. Up until the
installation of the entire system, various modules from the new and
old systems are utilised in tandem. Phased installation, like single-
location installation, aims to reduce installation-related risk.

A phased installation is comparable to rolling out the system in a


series of releases. As a result, phased installation necessitates
meticulous version control, repeated conversion at each phase, and a
lengthy time of change. Users may become frustrated and perplexed
www.reallygreatsite.com
as a result.
www.reallygreatsite.com
Verification testing
Alpha testing is often referred to as verification testing. This testing
operates the system with simulated data in a simulated environment.
It involves looking for mistakes and omissions in the design standards
and end users that were stated in the earlier testing phase.

Validation testing
Beta testing is another name for validation testing. This testing uses
actual data to run the system in a real-world setting. This testing
included several tests for system performance, peak workload
processing performance, and the human engineering test.

• Test methods and processes


www.reallygreatsite.com
• testing for backup and recovery
DOCUMENTING THE SYSTEM
Each system development requires a different set of
documentation. System documentation and user documentation
are the two fundamental categories of documentation.

SYSTEM DOCUMENTATION
System design specifications, internal workings, and
functionality are all thoroughly documented in the system
documentation. For the maintenance person who will be in
charge of the system's operation in the future, system
documentation is developed.
www.reallygreatsite.com
There are two types of system documentation: internal
and external.

• Internal paperwork: Internal documentation is either created


at compile time or is included in the software source code.

• External references: Data flow and entity-relationship


diagrams are two examples of structured diagramming
approaches that are used in external documentation, which is a
type of system documentation. Although it doesn't cover the
code itself, it can give the system documentation's main users
helpful information.
www.reallygreatsite.com
USERS DOCUMENTATION
As previously said, user documentation is meant for system users, whereas
system documentation is meant for programmers who maintain the systems.
Written and visual information on the system, including what it does, how it
works,and how to use it, make up user documentation. Different kinds of user
documentation include:

i. reference manual: contains a comprehensive list of system commands and


functions
ii. fast reference guide: short, to-the-point explanations of the most important
information about using a system.
iii. User's manual: This resource tells users how to use a computer system to
carry out tasks.

www.reallygreatsite.com
TRAINING
It's vital to teach users the new system, even though the documentation is
designed to support them throughout the life of the system. The team
typically uses the written materials created to aid them during training
sessions. The users of the system must be trained and given documentation
that will help them navigate the new system as part of the conversion from
the old to the new.

Although one-on-one instruction is an option, group instruction is preferred.


Group instruction can shorten the duration and cost of the training while
also encouraging group participation and system feedback. During the
training session, there are a few things to keep in mind. An introduction to
the system should be covered in the training session's curriculum, and
www.reallygreatsite.com
system manual.
thynk
unlimited

THANK YOU!

10

You might also like