Standard software
As standard software are software understood systems that cover a clearly defined scope and can be purchased as ready-made products. In contrast to this, individual software is specifically developed for use by a customer or company. Occasionally, a distinction is still made between standard application software and standard system software ; In the area of system software , however, the use of standard software is so common that this term is rarely used and this distinction is usually dispensed with.
Classification of standard software
In the area of application software , standard software can be subdivided into the areas of function-related or cross-functional standard software and industry software .
Function- related or cross-functional standard software is industry-neutral ( horizontal market ) and tailored to a specific area of application, which in many cases is strictly regulated, for example by legal requirements. The transition between function- related and cross-functional software is fluid, typical examples of function- related standard software are accounting software, CAD or production planning and control systems (PPS). Cross-functional standard software, on the other hand, can be used in several functional areas of the company, for example for office packages or ERP systems ( Enterprise Resource Planning ). The latter are also referred to as integrated systems, as they represent a bundling of several function-related modules. The use of integrated systems has the advantage of avoiding redundant data storage.
Also because the area of function-related or cross-functional standard software is now dominated by a few providers in almost all areas, industry software is offered in particular by smaller providers. This software is tailored to the special requirements and conditions of the companies in a branch ( vertical market ).
Introduction of standard software
→ Main article: Software introduction
The introduction of standard software can be carried out in a similar way to the introduction of individual software. In the case of large standard software systems in particular, the introduction not only includes installing and training users, but also configuring the software. The configuration of standard software is called customizing . The introduction of standard software is a large project that usually requires the use of external consultants .
There are roughly two basic strategies for introducing standard software:
- The “ big bang ” is the complete changeover at a clearly defined point in time, usually at times when the unavailability of a system is largely uncritical. To minimize risk, this type of software implementation requires extensive planning and preparation (data migration to be carried out during the changeover period, training courses, planning of a fallback in the event of problems).
- The opposite strategy is an iterative introduction of a new system in several, smaller steps, which, however, is rather unusual when introducing standard software, but rather is used when introducing individual software . Depending on the field of application of the software, the iterative introduction is to be considered sensible, since the effort of customizing can otherwise increase considerably with complex software systems.
- In the case of business-critical software, there is often a phase in which the old and new software systems are used in parallel in order to still be able to act in the event of migration problems.
Advantages and disadvantages of standard software compared to individual software
Basically, it depends on the specific case whether the use of standard or individual software is cheaper. The main advantage of using standard software is usually the lower costs, which, however, is often put into perspective due to the necessary adjustments ( configuration ) to existing system components. Due to the adaptability of many standard software products, the main argument for the use of individual software, namely the possibility of tailoring it to individual circumstances, is a little weakened.
Furthermore, the following advantages for the use of standard software are often mentioned:
- The involvement of specialists in certain fields (e.g. mathematicians, designers, communication experts, etc.) or the perfecting of certain details (e.g. database optimization, usability, look & feel, help and documentation) is more worthwhile for manufacturers of standard software their products recoup the costs for this via the sales volume.
- A high degree of distribution of standard software brings with it a high degree of distribution of operating know-how.
In many cases it is not possible, or only possible with disproportionately high effort, to use standard software. In particular, if there are very special requirements with regard to the existing infrastructure ( e.g. because many complex interfaces to external systems have to be taken into account) or very special and complex business processes have to be mapped, the implementation of individual software is essential.