A first attempt to combine SysML requirements diagrams and B

  • Régine Laleau
  • Farida Semmak
  • Abderrahman Matoussi
  • Dorian Petit
  • Ahmed Hammad
  • Bruno Tatibouet
Original Paper

Abstract

This article describes a work-in-progress in the framework of a research project aiming at combining requirements engineering methods with formal methods. The main idea is to extend the SysML language with concepts of existing requirements engineering methods. In this article we present extensions to SysML with concepts from the goal model of the KAOS method and we give rules to derive a formal B specification from this goal model. The approach is then illustrated on a case study.

Keywords

Requirements engineering SysML KAOS goal model B method 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Abrial JR (1996) The B-Book: assigning programs to meanings. Cambridge University Press, CambridgeMATHGoogle Scholar
  2. 2.
    Anton AI (1996) Goal based requirements analysis. In: Proceedings of international conference on requirements engineering (ICRE96), pp 136–144Google Scholar
  3. 3.
    Aziz B, Arenas A, Bicarregui J, Ponsard C, Massonet P (2009) From goal-oriented requirements to are Event-B specifications. In: First Nasa formal method symposium (NFM 2009), Moffett Field, California, USAGoogle Scholar
  4. 4.
    Badeau F, Amelot A (2005) Using B as a high level programming language in an industrial project: Roissy val. In: Proceedings of ZB’05. LNCS, vol 3455. Springer, Berlin, pp 334–354Google Scholar
  5. 5.
    Behm P, Benoit P, Faivre A, Meynadier JM (1999) METEOR : a successful application of B in a large project. In: Proceedings of FM ’99. LNCS, vol 1708. Springer, Berlin, pp 369–387Google Scholar
  6. 6.
    Chung L, Nixon B, Yu E, Mylopoulos J (2000) Non-functional requirements in software engineering. Kluwer Academic, BostonMATHGoogle Scholar
  7. 7.
    Darimont R, van Lamsweerde A (1996) Formal refinement patterns for goal-driven requirements elaboration. In: Proceedings of SIGSOFT ’96. San Francisco, USA, pp 179–190Google Scholar
  8. 8.
    Friedenthal S, Moore A, Steiner R (2008) A practical guide to SysML. Morgan Kaufmann OMG Press, San FranciscoGoogle Scholar
  9. 9.
    Goknil A, Kurtev I, van den Berg K (2008) A metamodeling approach for reasoning about requirements. In: Proceedings of ECMDA-FA. LNCS, vol 5095. Springer, Berlin, pp 310–325Google Scholar
  10. 10.
    Hassan R, Bohner S, El-Kassas S, Eltoweissy M (2008) Goal-oriented, B-based formal derivation of security design specifications from security requirements. In: Proceedings of ARES 2008, Barcelona, Spain. IEEE Computer Society, USA, pp 1443–1450Google Scholar
  11. 11.
    van Lamsweerde A (2009) Requirements engineering: from system goals to UML models to software specifications. Wiley, New YorkGoogle Scholar
  12. 12.
    Maiden N, Sutcliffe A (1993) Exploiting reusable specifications through analogy. Commun ACM 35(4): 55–64CrossRefGoogle Scholar
  13. 13.
    Mammar A, Laleau R (2006) A formal approach based on UML and B for the specification and development of database applications. Autom Softw Eng 13(4): 497–528CrossRefGoogle Scholar
  14. 14.
    Matoussi A, Laleau R, Petit D (2009) Bridging the gap between KAOS requirements models and B specifications. In: Technical Report TR-LACL-2009-5, LACL, University of Paris-Est (Paris 12), http://lacl.univ-paris12.fr/Rapports/TR/TR-LACL-2009-5.pdf
  15. 15.
    Mylopoulos J, Chung L, Yu E (1999) From object-oriented to goal-oriented requirements analysis. Commun ACM 42(1): 31–37CrossRefGoogle Scholar
  16. 16.
    Nakagawa H, Taguchi K, Honiden S (2007) Formal specification generator for KAOS: model transformation approach to generate formal specifications from KAOS requirements models. In: Proceedings of automated software engineering (ASE 2007). IEEE/ACM, Atlanta, USA, pp 531–532Google Scholar
  17. 17.
  18. 18.
    Ponsard C, Dieul E (2006) From requirements models to formal specifications in B. In: Proceedings of REMO2V’2006, 241 CEUR-WS.org, LuxembourgGoogle Scholar
  19. 19.
    Potts C, Takahashi K, Anton AI (1994) Inquiry-based requirements analysis. IEEE Softw 11(2): 21–32CrossRefGoogle Scholar
  20. 20.
    Rolland C, Souveyet C, Ben Achour C (1998) Guiding goal modeling using scenarios. IEEE Trans Sofw Eng 24(12): 1055–1071CrossRefGoogle Scholar
  21. 21.
    Snook C, Butler B (2006) UML-B: formal modelling and design aided by UML. ACM Trans Softw Eng Methodol 15(1): 92–122CrossRefGoogle Scholar
  22. 22.
    Spivey JM (1988) Understanding Z. Cambridge University Press, CambridgeMATHGoogle Scholar
  23. 23.
    Sutcliffe A, Maiden N (1998) The domain theory for requirements engineering. IEEE Trans Sofw Eng 24(3): 174–196CrossRefGoogle Scholar
  24. 24.
    TACOS Project. ANR-06-SETIN-017, http://tacos.loria.fr
  25. 25.
    TACOS Project, deliverable 1.1 (2008) Model for the Land Transport Domain, http://tacos.loria.fr/drupal/?q=node/57

Copyright information

© Springer-Verlag London Limited 2009

Authors and Affiliations

  • Régine Laleau
    • 1
  • Farida Semmak
    • 1
  • Abderrahman Matoussi
    • 1
  • Dorian Petit
    • 2
  • Ahmed Hammad
    • 3
  • Bruno Tatibouet
    • 3
  1. 1.LACLUniversité Paris-Est, IUT FontainebleauFontainebleauFrance
  2. 2.LAMIH, Université Lille Nord de France, UVHCValenciennesFrance
  3. 3.LIFC, Université de Franche ComtéBesançonFrance

Personalised recommendations