Formal methods are becoming increasingly important in many areas of software development and should be incorporated in the teaching of software engineering. Requirement capture is, in our opinion, the hardest stage of development for students to learn and for lecturers to teach.This paper reports on our experience in teaching requirements engineering using formal methods, where we advocate a multiple methods approach in which students get to evaluate a large range of specification languages: students are more likely to learn the principles of good requirements engineering rather than become experts in one particular (formal) method.The need for formality is introduced step-by-step, where new concepts are identified by the students through the use of case studies. These concepts are then formalized in the most appropriate language or notation. Students are encouraged to question the need for formality. Each requirements engineering method is a compromise and the use of formal models needs to be placed within the context of the choices that a requirements engineer has to make.