Those who work in the IT sector will – one day or another – be faced with the topic of IT documentation. A chore that nobody likes to tackle. Many do not know how to address it and what they have to pay attention to. First, it is important to consider some basic questions: What is the documentation needed for? Who is it intended for? Why must it be created at all? These questions are legitimate as IT documentation serves different purposes such as:<\/p>\n
– define what is needed for a project (requirements catalog)<\/p>\n
– capture the structure of an IT network so that errors can be eliminated quickly (emergency manual)<\/p>\n
– explain the operation of an IT network (operating manual)<\/p>\n
When the purpose of the IT documentation is clear, the next thing is to consider the target group. It may include:<\/p>\n
IT documentation often lacks a (clear) structure. So, it is not surprising that reading hundreds of pages turns out to be a drag. This is why IT documentation needs to be subdivided into logical units. Depending on the requirements, these can be quite different, but these five parts can be considered as standard:<\/p>\n
The content, i.e. the documents to be comprised, is predetermined in many companies by standards or templates. If this is not the case, a Google search for samples may be helpful. In any case, illustrate your network information by adding pictures and diagrams. Visualizations make it easier to grasp correlations. However, make sure that the graphics and diagrams correspond to the text and are duly explained. To relieve yourself from tedious manual work, better use a suitable software program.<\/p>\n