Model-Driven Requirements Engineering: Synchronising Models in an Air Traffic Management Case Study

  • Neil A. M. Maiden
  • Sara V. Jones
  • Sharon Manning
  • John Greenwood
  • L. Renou
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3084)


Different modelling techniques from different disciplines are needed to model complex socio-technical systems and their requirements. This paper describes the application of RESCUE, a process that integrates 4 modelling techniques to model and analyse stakeholder requirements for DMAN, a system for scheduling and managing the departure of aircraft from major European airports. It describes how human activity, use case and i* modelling were applied and integrated using synchronisation checks to model requirements on DMAN. Synchronisation checks applied at predefined stages in RESCUE revealed omissions and potential inconsistencies in the models and stakeholder requirements that, in turn, led to improvements to the models and resulting specification. The paper ends with implications for requirements model integration, and describes future work to extend and apply RESCUE.


Case Model Context Model Case Description Requirement Engineer Case Diagram 
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.


  1. Cockburn, A.: Writing Effective Use Cases. Addison-Wesley, Pearson Education (2000)Google Scholar
  2. De Landtsheer, R., Letier, E., van Laamsweerde, A.: Deriving Tabular Event-Based Specifications from Goal-Oriented Requirements Models. In: Proceedings 11th IEEE International Conference on Requirements Engineering, pp. 200–210. IEEE Computer Society Press, Los Alamitos (2003)Google Scholar
  3. Hall, J., Jackson, M., Laney, R., Nuseibeh, B., Rapanotti, L.: Relating Software Requirements and Architectures using Problem Frames. In: Proceedings 10th International Joint Conference on Requirements Engineering, pp. 137–144. IEEE Computer Society Press, Los Alamitos (2002)CrossRefGoogle Scholar
  4. ICAO, Human Factors in CNS/ATM systems. The development of human-centred automation and advanced technology in future aviation systems’ ICAO Circular 249- AN/149 (1994)Google Scholar
  5. Jacobson, I., Booch, G., Rumbaugh, J.: The Unified Software Development Process. Addison-Wesley, Reading (2000)Google Scholar
  6. Leveson, N., de Villepin, M., Srinivasan, J., Daouk, M., Neogi, N., Bachelder, E., Bellingham, J., Pilon, N., Flynn, G.: A Safety and Human-Centred Approach to Developing New Air Traffic Management Tools. In: Proceedings Fourth USA/Europe Air Traffic Management R&D Seminar (2001)Google Scholar
  7. Liu, L., Yu, E., Mylopoulos, J.: Security and Privacy Requirements Analysis within a Social Setting. In: Proceedings 11th IEEE International Conference on Requirements Engineering, pp. 151–161. IEEE Computer Society Press, Los Alamitos (2003)Google Scholar
  8. Liu, L., Yu, E.: From Requirements to Architectural Design – Using Goals and Scenarios. In: Proceedings first STRAW workshop, pp. 22–30 (2001)Google Scholar
  9. Maiden, N., Gizikis, A.: Where Do Requirements Come From? IEEE Software 18(4), 10–12 (2001)CrossRefGoogle Scholar
  10. Maiden, N.A.M., Jones, S.V., Flynn, M.: Innovative Requirements Engineering Applied to ATM. In: Proceedings, A.T.M. (ed.) Proceedings ATM (Air Traffic Management), Budapest, June 23-27 (2003)Google Scholar
  11. Mavin, A., Maiden, N.A.M.: Determining Socio-Technical Systems Requirements: Experiences with Generating and Walking Through Scenarios. In: Proceedings 11th International Conference on Requirements Engineering, pp. 213–222. IEEE Computer Society Press, Los Alamitos (2003)Google Scholar
  12. Nentwich, C., Emmerich, W., Finkelstein, A.C.W.: Flexible Consistency Checking. ACM Transactions on Software Engineering and Methodology 12(1), 28–63 (2003)CrossRefGoogle Scholar
  13. Nuseibeh, B., Kramer, J., Finkelstein, A.C.W.: Viewpoints: Meaningful Relationships are Difficult. In: Proceedings 25th IEEE International Conference on Software Engineering, pp. 676–681. IEEE Computer Society Press, Los Alamitos (2003)CrossRefGoogle Scholar
  14. Praxis, 2001, REVEAL: A Keystone of Modern Systems Engineering’, White Paper Reference S.P0544.19.1, Praxis Critical Systems Limited (July 2001)Google Scholar
  15. Robertson, S., Robertson, J.: Mastering the Requirements Process. Addison-Wesley, Reading (1999)Google Scholar
  16. Rumbaugh, J., Jacobson, I., Booch, G.: The Unified Modelling Language Reference Manual. Addison-Wesley, Reading (1998)Google Scholar
  17. Santander, V., Castro, J.: Deriving Use Cases from Organisational Modeling. In: Proceedings IEEE Joint International Conference on Requirements Engineering (RE 2002), pp. 32–39. IEEE Computer Society Press, Los Alamitos (2002)CrossRefGoogle Scholar
  18. Sutcliffe, A.G., Maiden, N.A.M., Minocha, S., Manuel, D.: Supporting Scenario-Based Requirements Engineering. IEEE Transactions on Software Engineering 24(12), 1072–1088 (1998)CrossRefGoogle Scholar
  19. Vicente, K.: Cognitive work analysis. Lawrence Erlbaum Associates, Mahwah (1999)Google Scholar
  20. Viller, S., Sommerville, I.: Social Analysis in the Requirements Engineering Process: from Ethnography to Method. In: Proceedings 4th IEEE International Symposium on Requirements Engineering, pp. 6–13. IEEE Computer Society Press, Los Alamitos (1999)Google Scholar
  21. Yu, E., Mylopoulos, J.M.: Understanding Why in Software Process Modelling, Analysis and Design. In: Proceedings, 16th International Conference on Software Engineering, pp. 159–168. IEEE Computer Society Press, Los Alamitos (1994)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • Neil A. M. Maiden
    • 1
  • Sara V. Jones
    • 1
  • Sharon Manning
    • 1
  • John Greenwood
    • 2
  • L. Renou
    • 3
  1. 1.Centre for Human-Computer Interaction DesignCity UniversityLondon
  2. 2.National Air Traffic ServicesLondonUK
  3. 3.Sofreavia/CENAParisFrance

Personalised recommendations