Validating requirements: the evolutionary approach

Industrial practices in Requirements Engineering do not give the right place to formal methods. Two main reasons explain why such a failure arises. First of all formal methods have not promoted a dedicated SLC (Software Life Cycle) which should have been easily integrated within the upper phases of the traditional V-like or Waterfall-like model. A second reason is that formal methods have failed in scaling zip. In this paper we show how the requirements elicitation phase can take advantage of formal methods. We report the industrial and successful experience [2] undertaken by the STNA(1), a governmental office responsible for the French ATM (Air Traffic Management) system. We exhibit the evolutionary model which was applied to develop both a validated object-oriented model of a particular ATM subsystem, and a formal specification of some of its safety critical parts. We then show that the SRD (Software Requirements Document) is the key of the whole development. Its writing requires a strongly related cooperation of two different teams that are effective actors of the evolutionary model. We conclude the paper in exhibiting some recommendations.