Kandráč JánAbstract. Especially in the early days of IT departments of smaller companies happens, that their documentation is underestimated. Documentation management is failing and time is showing that the situation is critical. The problem is in slow and low quality output, or other problems that poor management may arise. There can be found several solutions for such problems, but these solutions are often not based on reversing the bad situation, but on its prevention. Usually it is a description of the prevention against bad documentation or changing management which is necessary because of failure to comply project. How to heal the documentation which is really bad? Or how is it possible to grasp it at any stage and lead it into a success?Kostolanský JurajAbstract. Technical documentation, user's guide, source code comments. These documents are considered an essential part of a software product. However, writers often spent much less energy to create them than they deserve. Although good documentation implies more satisfied customers, saved significant time and money, it is still considered as a necessary evil more than as a way to simplify own work and to improve the quality of the final product. In this essay I focus on the need for documenting software from multiple perspectives, I think about the concept of quality in the context of documenting and I describe the basic mistakes made by the documentation writers.
|