In the implementation phase, the previously designed application solution is technically realized through configuration of software products.
A rebuild of software is usually by programming, ie the individual functions, objects classes, etc. are coded in a programming language using an integrated development environment.
The software is tested in two ways, firstly
technically, that is a correct implementation of the design specification and program errors, and on the other;
content, ie completeness with respect to the functional specification and suitability for the intended purpose
The test procedure is usually carried out in collaboration with the end users of the client.
Sometimes even whole parts have to be completely re-implemented, thus reprogrammed.
Since errors in complex applications can not be completely ruled out, a renewed complete test of the whole system should be done after fault clearance.
The finished software, accompanied by any required standard software products, hardware, etc, is then partly filled during the installation on the computer systems of the customer or the operator and made operational.
An essential part of the project is the introduction of support, particularly in the form of training or instruction of end users, power users and administrators.
There are many different training concepts. A larger number of users are often trained as multipliers . Multipliers are users who in turn train other users.
This procedure is also called Train the Trainers. Increasingly, user training takes place over the Internet with appropriate training applications.
After the commissioning of a software solution, a continuous follow-up is necessary and customary.
This includes both support for the user, eg, via the hotline during normal operation as well as enhancements to the software, if necessary.
A distinction is made between a first- level support and a second-level support. The first- level support (including Helpdesk) is the first point of contact for all incoming support issues and will answer all problem reports.
It handles only serious problems to the second- level support for standard software, eg at the product manufacturer , on.
The continuous adaptation of the software to changing requirements or environmental conditions , eg type of new versions of standard software is referred to as ” software maintenance “.
Major changes are processed on their own maintenance projects , minor adjustments frequently, than maintenance tasks with simpler process rules.
The management of the subsequent introduction of changes into a running system called change management.