Scribd
Upload
78 views7 pages

System Build, Implementation and Maintenance: Change Management

This document discusses system build, implementation, and maintenance from a managerial perspective. It defines system build as the creation of software through programming, testing, documentation, and training. System implementation involves transitioning from the old system to the new one, including replacing infrastructure and training staff. Maintenance deals with reviewing projects and resolving issues. The key questions addressed are how to test systems, migrate data, manage changeovers between old and new systems, and manage transitions to new processes.

Uploaded by

koaslosa
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
78 views7 pages

System Build, Implementation and Maintenance: Change Management

This document discusses system build, implementation, and maintenance from a managerial perspective. It defines system build as the creation of software through programming, testing, documentation, and training. System implementation involves transitioning from the old system to the new one, including replacing infrastructure and training staff. Maintenance deals with reviewing projects and resolving issues. The key questions addressed are how to test systems, migrate data, manage changeovers between old and new systems, and manage transitions to new processes.

Uploaded by

koaslosa
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/ 7

Lecture 13

System build, implementation


and maintenance: change
management
Learning objectives

• After this lecture, you will be able to:


– state the purpose of the build phase, and its difference
from changeover and implementation;
– specify the different types of testing required for a
system;
– select the best alternatives for changing from an old
system to a new system;
– recognise the importance of managing software, IS and
organisational change associated with the introduction
of a new BIS.
Management issues

• From a managerial perspective, this chapter


addresses the following questions:
– How should the system be tested?
– How should data be migrated from the old system
to the new system?
– How should the changeover between old and new
systems be managed?
– How can the change to a process-oriented system
be managed?
System build and implementation

• System build: The creation of software by programmers


involving programming, building release versions of the
software and testing by programmers and end-users. Writing
of documentation and training may also occur at this stage.
• System implementation: Involves the transition or changeover
from the old system to the new and the preparation for this
such as making sure the hardware and network infrastructure
for a new system are in place; testing of the system and also
human issues of how best to educate and train staff who will be
using or will be affected by the new system.
• Maintenance: Deals with reviewing the IS project and acting
on problems with the system.
• Change management: The period of migration from existing
systems to a new system.
System Development

• System development, includes programming and


testing, is the main activity that occurs at the
system build phase.
• Software consists of program code written by
programmers that is compiled or built into files
known as ‘executables’ from different modules,
each with a particular function.
• There are a number of system development tools
available to programmers and business users to
help in writing software; 3GLs, 4GLs, Visual
Development, CASE.
Software quality

• The quality of software is dependent on two key


factors:
– the number of errors or bugs in the software;
– the suitability of the software to its intended
purpose, i.e. does it have the features identified by
users which are in the requirements specification?
– how well it operates in its environment
Examples of source of introducing errors

Table 12.1 Table comparing the source of errors in three different software projects

You might also like