Abstract
High quality requirements definition needs knowledge regarding how to elicit, represent, verify and validate requirements specification. Although experienced requirements engineers possess such knowledge, it is usually neither explicitly represented nor shared. In this paper, we propose a method for eliciting and representing requirements definition knowledge. We have analyzed requirements specification of successful system development projects and interviewed experienced engineers, extracted and specified four kinds of knowledge: a requirements specification meta model, requirements specification templates, and requirements definition verification rules for product and process.
