A typical feature of software documentation is the variety of topics and target groups. This is best explained using the following example: take for instance an IT company that is offering software to control production processes. What does the documentation need to cover?
Firstly, there are the users of the software. In our example, users cannot only use the software to control processes, but also – and most importantly – design the process logic, meaning we already have two very different user groups: system operators and project developers.
In addition, software administrators make up a third target group, and because this software can also be programmed via an API, there exists a fourth group of software developers.
Each of these target groups completes various different tasks with the help of the software. Each target group has its own information requirements, which must be considered in the documentation as a whole.