Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


The completion & Handover Process

No description

E Duffy

on 15 September 2016

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of The completion & Handover Process

Customer /User Acceptance
The completion & Handover Process
Completion & Handover
The final stage of installing and upgrading software is the completion and handover stage.

At this stage you will perform the final tasks to be completed after installation (eg, registering the product) and then hand the product over to the customer.
P6 - Explain the importance of the user acceptance policy
Configuration to meet Customer /User Needs
Handover to the Customer /User
Backing Out
- Mrs Duffy
The Handover
The handover process occurs when the fully functioning computer system is returned to the customer.
If the client does not accept that the work completed meets the requirements then they will not accept the handover until any issues have been resolved.
It is therefore important that the installation is fully completed to the agreed user requirements before the handover is attempted.
As the customer has the right to refuse to pay you if the installation doesn't meet the agreed requirements it is important that you have configured the software to meet their needs completely.
The task of configuring the software is not complicated but it must be completed and the software tested to ensure it works as expected and required.
Formal handover to the customer involves more than handing over the computer with the software installed. It also requires handing over:
installation details
technical manuals
user guidance documentation
contact details for technical and user support
any other materials that were used in the installation that belong to the customer
All of this information is extremely important to the customer so that they can make effective use of the software installation.
Once you have completed the formal handover the customer will need to formally accept the installation or upgrade as having been completed satisfactorily.
Before they do this they may subject it to
user acceptance testing
. At this point the customer will normally sign a release form that confirms the installation has been accepted as complete.
If the customer does not accept the installation has been completed satisfactorily you may need to spend more time working on it. This is why clearly defined requirements with the customer are so important. If there is a dispute over whether the job has been completed you will have a document that proves you have completed the installation to meet the requirements that were agreed.
If the installation has not been successful then it is likely that you will be expected to back out of the installation. This involves uninstalling the new software, reinstalling the previously installed software, recovering any lost data files and reconfiguring your system settings.
This process will be greatly simplified if you took a backup of the system before you started the installation process, especially a
full image backup
. This would enable you to restore all software applications and system settings from that one backup.
Contractual Implications
Data Integrity
Product Registration
Once an installation is completed you should register the new software with the software vendor. There are a wide range of benefits of doing this (even though it is not mandatory)
You should do this for every piece of software that you install.
You are usually asked to register via a simple electronic form. This information is then sent to the software vendor over the internet.

Benefits of registering
software for the Vendor...

Registration will also prove to the vendor that your installation is using a legal license.
The vendor could include you in a bug reporting scheme to help them to improve the reliability of the software.
Tells them about the type of people or businesses that are using their software
Tells them what the software is being used for
Provides them with your contact details
Tells them how you discovered the software
Benefits of registering software for the User...
Because there are so many advantages of registering software for the vendor, it is important that they try to encourage users to provide this information. They need to encourage users to register their software. They do this in a number of ways...
Benefits of registering software for the User...

you will receive user support and software updates (this is useful as software is often released with many bugs still present - the updates will fix this)
you will be kept informed of future releases and upgrades
they will give you a replacement license key if you lose yours
you may receive discounts on future purchases
Whenever you install a new piece software you will need to agree to enter into a EULA (End User License Agreement).
This is a legal agreement that defines how you can use the software. If you buy software off the shelf, you will usually have a standard single user license (one that lets only you use the software)
Dongles are used by software vendors to protect their software from unlicensed use. The dongle itself is a small piece of hardware that must be connected to the computer every time you run the software. If the dongle is not attached, the software may only run in a limited format or not at all. Dongles are used because they are difficult to replicate and therefore add another layer of security.
Whenever you are performing a software installation there is always a chance of causing damage to the data that is stored on the computer system. This is why measures must be put in place to ensure the integrity of data is retained.
Other kinds of licenses...
OEM (original equipment manufacturer) License - this is for software that is purchased by a hardware supplier and comes with your computer system
Site License - this is an unrestricted license and means you can install the software as many times as you need to within your organisation
Other kinds of licenses...
Open Source License - this type of license not only gives you access to the software, it also allows you to view, modify and share changes to the actual source code.
Freeware License - This is for software that is completely free to use, although sometimes there will be an optional payment.
When you agree to an EULA (end user license agreement) you agree to a number of contractual implications.
You must ensure that you are not in breech of any of the terms of your contract or you will be breaking the law. A major part of most licensing agreements is the limited liability of the vendor if their software causes damage to your computer system. This means that you will not be able to claim if the software damages your system.
There may also be agreements to prohibit users from reverse engineering the software as well as limiting the number of times the software can be installed.

People rarely read the entire EULA when installing software but within an organisation it is important to fully understand what you are agreeing to.
System Recovery Point
This is also known as a snapshot. It is a backup of your system at a specific point in time to which you can roll back if a problem with your computer system arise.
These can be created manually or automatically and are usually made before major changes are made to a computer system, such as new software being installed. By creating these recovery points it is very easy to recover from any damage to data integrity.
Copy of Registry Data
The registry data stores configuration settings and options that you have set on your operating system, software applications and hardware. Damage to registry data can cause applications, hardware and the entire computer system to become completely inoperable. Due to how serious this can be, you should always have a backup of your registry data.
Copy of Registry Data
All operating systems will have an application that will allow you to browse the registry data and take a copy of it - for example, Windows operating systems have an application called regedit.
However, there is also a variety of third party software applications that will perform these actions.
Copy of User Data
User data refers to the files created by the user while using the software applications. This could be:
Word processed documents
web pages
game save files
It is important to keep all of this data secure as it could contain important information such as customer details, payroll data or financial information.
Copy of User Data
Copy of User Data
It is quite easy to manually copy the user data on your hard disk to another location, but you must ensure that ALL files are copied so that none are lost.
There are a huge number of programs designed to automate this process such as the backup and restore program of the Windows Operating System.
Copy of User Data
There are huge amounts of user data that are stored by businesses that are absolutely essential to the running of the business. It is extremely important to keep a copy of this data, which can be used in the event of damage to the data that is currently stored on the system.
Prior image of Hard Drive
Creating a full image of the hard drive the best way to ensure you will be able to recover all data on you computer system should there be damage to the data. Restoring from the image is a time consuming task and as such it is usually used as a last choice, should your system recovery points and other backups not resolve the issues that arise.

There are a variety of software applications available for creating a hard disk image, eg Norton Ghost or Acronis True Image.
Full transcript