Requirements engineering is a central part of software projects. It is assumed that two third of all errors in software projects are caused by forgotten requirements or mutual misunderstandings in the requirement gathering process. Due to the inherent structure of project planning and the project management process, it is very unlikely that this problem will be solved unless the process itself is changed or we develop tools that possess some intelligence to facilitate the assessment of requirements. In this paper a position for the latter approach is formulated. It is argued that it is feasible to establish a domain ontology based on meta information and explanations that are represented as scripts. It is shown that this ontology has to be constructed in a dynamic way to reflect the dynamics of the requirements engineering process. Finally, it is sketched how use cases and test cases can be derived from this ontology. 1 The Difficulty of Creating Novel Things in Time and Budget A proje...