System Development Methods

CT046-3-2

System Deployment
 Topic & Structure of the lesson

 System deployment and its activities.

 System change-over methods with its advantages and
disadvantages.
 System maintenance
 Post-implementation evaluation and the final report to
management

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 2

 Learning Outcomes

At the end of the module, you should be able to:

1. Describe system deployment and its activities.
2. Explain system change-over methods with their
advantages and disadvantages.
3. Define the four types of system maintenance
4. Explain post-implementation evaluation and the final
report to management

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 3

 Key Terms you must be able to use

If you have mastered this topic, you should be able to use the
following terms correctly in your assignments and exam:

 System deployment and its activities.

 System change-over methods with its advantages and
disadvantages.
 System maintenance
 Post-implementation evaluation and the final report to
management

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 4

 System deployment and its activities

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 5

 System Deployment

 Activities that make a software system available for use.

 The system is ready to be delivered to owner / customer.

 The system fully tested and fully functional.

 Production site / pre-deployment test
 To conduct ‘Post-deployment’ test (on-site testing)

 Owner / customer are informed about the deployment

(product release / launching).

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 6

 System Deployment Activities

 Determining Deployment Options

 Where will the system / software be delivered?
 Packaging Software / Systems
 What and how the components will be delivered to the users?
 Deployment Scheduling
 Inform stakeholders of deployment event, who and when?
 System change-over strategies
 How the old system will be replaced with new one?
 Integrating System Components
 Installing equipment / connecting servers, etc.
 Post-Deployment (On-Site) Testing
 Provide Training to users
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 7
 Determining Deployment Options
(Where will the system be delivered?)

 Upload to Web Server / Web Host

– Website / web applications
– Software patches / plug-ins, etc.
 Upload to Web Store
– Mobile applications, games
 Create digital medium - DVD
– Off-shelf applications
– Console games
 Install in customer’s local servers
– Customized Business Systems / applications
– Security Systems
– Database
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 8
 Packaging Software / Systems
(Operations to prepare a system for assembly and
transfer to the customer site)

 Converting / securing source codes

 Preparing SETUP or INSTALL files
 Compress files
 Burn to installation disks
 OR prepare to upload to server
 Prepare User Manual
 Prepare Technical Manual

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 9

 Deployment Scheduling
(Inform stakeholders of deployment event)

 For cloud-based system

– Plan to backup old system files in cloud
– Plan upload / update new system to cloud (date, duration)
– Plan ‘fallback’ time

 For local system installation at user’s place

– Identify all stakeholders involved in deployment
– Inform relevant users of installation date and time
– Ask to backup all ‘old’ files
– Standby system support personnel
– Instruct local servers to be ‘off-line for maintenance’
– Plan ‘Fall-Back’ time
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 10
 System Change-over Methods
(How the old system will be replaced with new?)

 System changeover is the process of putting the new

information system online and retiring the old system.
Changeover can be rapid or slow, depending on the
method.
 The four changeover methods are direct cutover, parallel
operation, pilot operation, and phased operation
(discussed in the next section).

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 11

 Integrating System Components
(Installing equipment / connecting servers, etc)

 Connecting sub systems to main systems

 Connecting database
 Connecting new system to other local system (legacy
systems)
 Installing security components
– Firewall
– User profiles (administrator access)

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 12

 Post Deployment (On-Site) Test

 Running test to spot new problems after deployment

 Develop Test
– Functional Tests
– Non-functional Tests
– Connections Tests
– Security Tests
 User Test
– User Acceptance Test

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 13

 User Training

 Applicable for large / complicated systems. Need to identify the users

who will be using the system and train them.
 Without training, user error rates will be high.
 Training considerations
 Frequency and duration of system use
 Need to understand system’s business context
 Existing computer skills and proficiency
 Number of users
 Training Administrators
 Content Management
 Maintenance of the system
 Training End-Users
 Common User functions
 Training Technical Support
 Fixing common problems
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 14
 Administrators
End Users and Technical
Support

can be less formal

Hands-on training as operators may be
for specific business experienced and
processes able to use new
system quickly

Jobs include starting

Prepare practice
and stopping the
exercises, Q&A
system, backup and
sessions, one-on-
recovery, setting up
one tutorials
users

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 15

 Other Activities of System Deployment

 License Activation
– EULA (End User License Agreement)
– Corporate License

 Connecting new system to backup machines

– Connecting to Disaster Recovery centre (DR)

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 16

 System change-over methods with its
advantages and disadvantages.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 17

 System Change-over Methods

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 18

 System Change-over Methods
(continued)

Direct Cutover
 The direct cutover approach causes the changeover from the
old system to the new system to occur immediately when the
new system becomes operational.
 The primary advantage of direct deployment is its simplicity.
Because the old and new systems aren’t operated in parallel,
there are fewer logistical issues to manage, and fewer
resources required.
 The primary disadvantage of direct deployment is its risk.
Because older systems aren’t operated in parallel, there is no
backup in the event that the new system fails.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 19

 System Change-over Methods
(continued)

Parallel Operation
 The parallel operation changeover method requires that both
the old and the new information systems operate fully for a
specified period.
 Data is input into both systems, and the output generated by
the new system is compared with the equivalent output from
the old system.
 When users, management, and the IT group are satisfied that
the new system operates correctly, the old system is
terminated.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 20

 System Change-over Methods
(continued)

 The main advantage of parallel operation is lower risk. If the

new system does not work correctly, the company can use
the old system as a backup until appropriate changes are
made.
 The main disadvantage this the costly changeover method.
Because both the old and the new systems are in full
operation, the company pays for both systems during the
parallel period. Users must work in both systems and the
company might need temporary employees to handle the
extra workload. In addition, running both systems might
place a burden on the operating environment and cause
processing delays.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 21

 System Change-over Methods
(continued)

Pilot Operation
 The pilot operation changeover method involves implementing the
new system at a selected location of the company.
 A new sales reporting system, for instance, might be implemented
in only one branch office, or a new payroll system might be installed
in only one department. In these examples, the group that uses the
new system first is called the pilot site.
 During pilot operation, the old system continues to operate for the
entire organization, including the pilot site. After the system proves
successful at the pilot site, it is implemented in the rest of the
organization, usually using the direct cutover method.
 Therefore, the pilot operation is a combination of parallel operation
and direct cutover methods.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 22

 System Change-over Methods
(continued)

 The main advantage is that restricting the implementation to a pilot

site reduces the risk of system failure, compared with a direct
cutover method. Besides, operating both systems for only the pilot
site is less expensive than a parallel operation for the entire
company.
 The main disadvantage is the department or selected location
taking part in the pilot can lose data if the new system fails.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 23

 System Change-over Methods
(continued)

Phased Operation
 The phased operation changeover method allows you to
implement the new system in stages, or modules.
 For example, instead of implementing a new manufacturing
system all at once, you first might install the materials
management subsystem, then the production control
subsystem, then the job cost subsystem, and so on.
 With phased operation, you give a part of the system to all
users, while pilot operation provides the entire system, but to
only some users

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 24

 System Change-over Methods
(continued)

 The main advantage is reduced risk because the failure of a

single phase is less problematic than the failure of an entire
system.
 The main disadvantage is increased complexity. Dividing the
deployment into phases creates more activities and
milestones, thus making the entire process more complex.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 25

 System maintenance

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 26

 System Maintenance

 The process of modifying a system or component

after delivery to correct faults, improve
performance or other attributes, or adapt to a
changing environment.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 27

 Types of System Maintenance

Corrective Maintenance
 Corrective maintenance diagnoses and corrects errors in
an operational system. To avoid introducing new
problems, all maintenance work requires careful analysis
before making changes.
 Example of tasks:
 Diagnose and fix logic errors
 Replace defective network cabling
 Restore proper configuration settings
 Debug program code
 Update drivers
 Install software patch
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 28
 Types of System Maintenance
(continued)

Adaptive Maintenance
 Adaptive maintenance adds enhancements to an operational system
and makes the system easier to use.
 An enhancement is a new feature or capability, usually arises from
business environment changes such as new products or services, new
manufacturing technology, or support for a new Web-based
operation.
 Example of tasks:
 Add online capability
 Create new reports
 Add a new data entry field to the input screen
 Install links to the Website
 Create employee portal

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 29

 Types of System Maintenance
(continued)

 Minor adaptive maintenance is similar to routine corrective

maintenance. A user submits a systems request that is evaluated and
prioritized by the systems review committee. A maintenance team
then analyzes, designs, tests, and implements the enhancement.
 A major adaptive maintenance project is like a small-scale project
because the development procedure is similar.
 Adaptive maintenance can be more difficult than new systems
development because the enhancements must work within the
constraints of an existing system.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 30

 Types of System Maintenance
(continued)

Perfective Maintenance
 Perfective maintenance involves changing an operational
system to make it more efficient, reliable, or maintainable.
 Requests for corrective and adaptive maintenance normally
come from users, while the IT department usually initiates
perfective maintenance.
 Example of tasks:
 Install additional memory
 Write macros to handle repetitive tasks
 Compress system files
 Optimize user desktop settings
 Develop library for code reuse
 Install more powerful network server

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 31

 Types of System Maintenance
(continued)

Preventive Maintenance
 To avoid problems, preventive maintenance requires analysis of
areas where the trouble is likely to occur. Like perfective
maintenance, the IT department normally initiates preventive
maintenance.
 Preventive maintenance often results in increased user
satisfaction and decreased downtime.
 Example of tasks:
 Install new antivirus software
 Develop a standard backup schedule
 Implement regular defragmentation process
 Analyze problem report for patterns
 Tighten all cable connections

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 32

 Post-implementation evaluation and the final
report to management

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 33

 Post-implementation Evaluation

 A post-implementation evaluation assesses the overall quality of the

information system, should examine all aspects of the development effort
and the product.
 A typical evaluation includes feedback for the following areas:
 Accuracy, completeness, and timeliness of information system output
 User satisfaction
 System reliability, maintainability, system controls and security measures
 Hardware efficiency and platform performance
 Effectiveness of database implementation
 Performance of the IT team
 Completeness and quality of documentation
 Quality and effectiveness of training
 Accuracy of cost-benefit estimates and development schedules
 You can use the same requirement gathering techniques in a post-
implementation evaluation (interview, survey, etc.).
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 34
 The Final Report to Management

 At the end of each system development, you submit a

report to management.
 Your report should include the following:
 Final versions of all system documentation
 Planned modifications and enhancements to the system that have
been identified
 Recap of all systems development costs and schedules
 Comparison of actual costs and schedules to the original estimates
 Post-implementation evaluation, if it has been performed
 The final report to management marks the end of systems
development work.

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 35

 Slide 6 (of 25)

Summary

 System deployment aimed to make a system available for use, and the system
fully tested and fully functional.
 Activities during the system deployment include determining deployment
options, packaging systems, deployment Scheduling, system change-over
strategies, integrating system components, conducting post-deployment testing,
and providing training to users.
 The four system-change-over strategies include direct cutover, parallel
operation, pilot operation, and phased operation.
 Most corrective maintenance is initiated by end-users who use the system daily.
Whereby adaptive, preventive, and perfective maintenance is mostly initiated
by IT staff.
 A post-implementation evaluation assesses the overall quality of the
information system. At the end of each system development, a final report
needs to be submitted to management that includes overall system
documentation, planned modifications and enhancements, and a recap of all
costs and schedules.
CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 36
 Question & Answer

CT046-3-2 – SYSTEM DEVELOPMENT METHODS Slide 37