Information system p rojects often suffer from i ncomplete or inadequate requirements specifications. In our opinion, which is supported by practical experience, these problems result from the fact that the models usually applied for requirements analysis are to abstract as to be easily understood and validated by the business owners, i.e. the end users. In addition to that, validation is often hampered by the fact that traditional modeling approaches do not relate the particular model elements

more »

... to their corresponding requirements sources. We, therefore, propose an approach that uses a lean and thus more transparent requirements model, which is intermediate in the sense that it has to be mapped, after validation, to one of the traditional conceptual models. Clearly, introducing such an additional step into the information system development process induces increased effort which has to be reduced by appropriate tool support. This paper concentrates on specific aspects and tool support for extracting behavior models out of requirements texts.