The reuse of software requirements may help requirement engineers to elicit, validate and document software requirements and, as a consequence, obtain software requirement specifications of better quality both in contents and syntax.

There are many approaches to reuse in software engineering. Among them, patterns hold a prominent position. "Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice" (Alexander, 1979). We are interested in the use of patterns for the requirements analysis stage, namely Software Requirement Patterns. The patterns applicability to this context is clear, since requirements that appear over and over in requirements books could be identified as the solution to particular problems in a given context (the classical context-problem-solution scenario of patterns).

The current state of the proposal consists of:

The research method used to build our requirements patterns catalogue and its underlying metamodel was based on the study of system requirement specifications from several call-for-tender real projects conducted by the SSI group (see Who We Are section in this site); experts’ knowledge, being these experts: IT consultants, facilitators and researchers; background on requirements engineering literature and especially on requirement patterns; and a first validation in two real projects.

This is not a finished work, and our ongoing work address: