Introducing formal requirements into industry

  • J. Hagelstein
  • F. Ponsaert
Part II Requirements And Design
Part of the Lecture Notes in Computer Science book series (LNCS, volume 490)


We draw some lessons from our attempt to introduce the formal requirements engineering language ERAE in an industrial context. We review the various experiments and comment on such issues as the typical deficiencies of current practices, misconceptions about the nature of requirements, our approach to technology transfer, the importance of methodological guidance, and the role of tools. One of the applications, a complete television set, is analysed in more detail.


Requirement Engineering Program Selection Requirement Engineer Industrial Partner Informal Requirement 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [1]
    L. Claeys, L. Loomans, F. Ponsaert, “ERAE Specification of D16 and D2B,” Philips CST report re89015, January 1989.Google Scholar
  2. [2]
    E. Dubois, J. Hagelstein, E. Lahou, F. Ponsaert, A. Rifaut, F. Williams, “The ERAE model: A Case Study,” in: T.W. Olle, H.G. Sol, A.A. Verrijn-Stuart (eds.), Information System Design Methodologies: Improving the Practice, North-Holland, 1986, pp. 87–105.Google Scholar
  3. [3]
    E. Dubois and J. Hagelstein, “Reasoning on Formal Requirements: a Lift Control System,” Proceedings of 4th International Workshop on Software Specification and Design, Monterey, California, 1987.Google Scholar
  4. [4]
    E. Dubois, J. Hagelstein, A. Rifaut, “Formal Requirements Engineering with ERAE,” Philips Journal of Research vol. 43 3/4, 1988.Google Scholar
  5. [5]
    A. Finkelstein and J. Hagelstein, “Formal Frameworks for Understanding Information System Requirements Engineering,” Proceedings of the IFIP WG 8.1 CRIS Review Workshop, Sesimbra (Portugal), 1989.Google Scholar
  6. [6]
    J. Hagelstein and E. Lahou, “A transit Node in ERAE,” METEOR report MET-199, September 1987.Google Scholar
  7. [7]
    J. Hagelstein, A. Rifaut, J. Vangeersdael and M. Vauclair, “The ERAE Language and Method,” Manuscript M 336, Philips Research Laboratory Belgium, 1990.Google Scholar
  8. [8]
    J. Hagelstein and A. Rifaut, “The ERAE Language Definition,” Manuscript M 337, Philips Research Laboratory Belgium, 1990.Google Scholar
  9. [9]
    E. Lahou and F. Ponsaert, “Case Study: Requirements for a Software Development and Maintenance Tool,” METEOR report MET-110, September 1986.Google Scholar
  10. [10]
    F. Ponsaert “TIP-TOP: An Experiment with ERAE,” METEOR report, June 1988.Google Scholar
  11. [11]
    E. Stephens and F. Williams, “A Case Study in Requirements Engineering. Studio Booking,” METEOR report MET-108, January 1986.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1991

Authors and Affiliations

  • J. Hagelstein
    • 1
  • F. Ponsaert
    • 2
  1. 1.Philips Research LaboratoryLouvain-la-NeuveBelgium
  2. 2.Philips Centre for Software TechnologyLouvain-la-NeuveBelgium

Personalised recommendations