This paper presents common weaknesses of requirements documents from commercial software projects that frequently cause problems in practice. Many documents contain extensive, unstructured or even superfluous descriptions of details. At the same time, they lack a thorough description of the aim of the software system or one of its features. Such documents are difficult to read and to work with ...