Please enable JavaScript.
Coggle requires JavaScript to display documents.
Implementation and Changeover (Implementation Plan (Author, Sign-offs,…
Implementation and Changeover
Waterfall
Maintenance is the final stage after testing
Extended 'V' Model
Not explicitly shown, follows the completion of testing
Incremental
Maintenance is the final stage of each increment
Iterative
Release is implemented at the end of each iteration
Agile
Implementation or deployment is a part of the repeated Agile Lifecyle
Spiral
Each prototype is implemented to gather feedback and progress the development with a final implementation
Planning
Needs to start as early as possible
Considerations
Data set up
Software
Checks
Timings
Duration
Documentation
New Skills
Changeover
Project Manager is generally responsible
Data Creation / Conversion
Data an organisation already has needs to be safely transferred to new system
Analyst must assess the technical feasibility of converting data in correct format for new system
To determine whether a direct file conversion is possible a data mapping exercise is needed
Data Mapping
Documents the relationship of the fields in the current system to those in the new system
Compare field type, length and structure
Some automatic conversion of format may be possible
Having mapped the data the next step is to plan, text and undertake data conversion
Data Conversion
Planning when to do the conversion and step is essential
Static data can be loaded early and dynamic data can only be loaded last minute
Archived data may be converted in advance
Automated test comparators may be used when testing the conversion programs tto check whether one file is the same as another
The time taken for live data conversion must be estimated from the number of records to be converted and the time taken by programs
Migration of Software
New or changed software will need to be moved from test to live environment
Failure to migrate the correct modules and versions could result in system failure
Installation of Hardware and Infrastructure
Needs to be considered as part of the implementation to handle increased volume of data, user and transactions and agreed processing times
Upgrades or replacement need to be managed, actioned and tested
Supporting Documentation
Consider both users of the new system and operational and technical staff responsible for its support and maintenance
On-line help
Printed user guides
Operational manuals
Technical documents
Training
Users and operation will need to be trained in the new system
Key steps
Identifying competencies
Define training strategy
Deliver training
Assess training effectiveness
Systems Implementation
Direct Changeover or 'Big Bang'
New system straight into operation
Immediate switch
Strengths
Clean break
Less expensive
Weaknesses
High risk
Parallel Run
Old and new systems operated side by side
When confident new system working OK old system switched off
Strengths
Less ris
Compare data between systems
Weaknesses
Expensive
Pilot Implementation
In one or more sites or a subset of users
Make corrections / adjustments before fully deployed
Strengths
Less risk
System stabilised and 'tuned' by operational use
Weaknesses
Area chosen may not be typical of organisation as whole
Phased Implementation
Functionality deployed in stages or increments
Gain confidence in new functionality before extra features added
Strengths
Higher priority functionality delivered first
Risk is reduced
Easier to fall back if problems
Weaknesses
Expensive
Lose interest after initial implementation
Implementation Plan
Author
Sign-offs
Revision History
Purpose
System Overview
Stakeholders and Points of Contact
Implementation Schedule
Entry Criteria
Exit Criteria