Use Case Scenarios as Verification Conditions: Event-B/Flow Approach

  • Alexei Iliasov
Part of the Lecture Notes in Computer Science book series (LNCS, volume 6968)

Abstract

Model-oriented formalisms rely on a combination of safety constraints and satisfaction of refinement obligations to demonstrate model correctness. We argue that for a significant class of models a substantial part of the desired model behaviour would not be covered by such correctness conditions, meaning that a formal development potentially ends with a correct model inadequate for its purpose. In this paper we present a method for augmenting Event-B specifications with additional proof obligations expressed in a visual, diagrammatic way. A case study illustrates how the method may be used to strengthen a model by translating use case scenarios from requirement documents into formal statements over a modelled system.

Keywords

Case Scenario Proof Obligation Requirement Document Operation Lookup Automate Prover 
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.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Abrial, J.-R.: Modelling in Event-B. Cambridge University Press, Cambridge (2010)CrossRefMATHGoogle Scholar
  2. 2.
    Abrial, J.-R., Mussat, L.: Introducing Dynamic Constraints in B. In: Bert, D. (ed.) B 1998. LNCS, vol. 1393, pp. 83–128. Springer, Heidelberg (1998)CrossRefGoogle Scholar
  3. 3.
    Event-B.org. Event-B model repository (2011), http://deploy-eprints.ecs.soton.ac.uk/view/type/rodin=5Farchive.html
  4. 4.
    Fischer, C., Wehrheim, H.: Model-Checking CSP-OZ Specifications with FDR. In: Araki, A., Galloway, A., Taguchi, K. (eds.) IFM 1999: Proceedings of the 1st International Conference on Integrated Formal Methods, London, UK, pp. 315–334. Springer, Heidelberg (1999)Google Scholar
  5. 5.
    Hurlbut, R.R.: A survey of approaches for describing and formalizing use cases. Technical report, Expertech, Ltd. (1997)Google Scholar
  6. 6.
    Butler, M., Leuschel, M.: Combining CSP and B for Specification and Property Verification, pp. 221–236 (2005)Google Scholar
  7. 7.
    Mendoza-Grado, V.M.: Formal Verification of Use Cases. In: Requirements Engineering: Use Cases and More (1995)Google Scholar
  8. 8.
    Flow Models of stack and NFS. Event B/Flow specification (2011), http://iliasov.org/usecase/nfs.zip
  9. 9.
    Plugin, F.: Event-B wiki page (2011), http://wiki.event-b.org/index.php/Flows
  10. 10.
  11. 11.
    Treharne, H., Schneider, S., Bramble, M.: Composing Specifications Using Communication. In: Bert, D., Bowen, J.P., King, S. (eds.) ZB 2003. LNCS, vol. 2651, pp. 58–78. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  12. 12.
    NFSv4 web page. Network File System Version 4 (2011), http://datatracker.ietf.org/wg/nfsv4/
  13. 13.
    Woodcock, J., Cavalcanti, A.: The Semantics of Circus. In: Bert, D., Bowen, J.P., Henson, M.C., Robinson, K. (eds.) B 2002 and ZB 2002. LNCS, vol. 2272, pp. 184–203. Springer, Heidelberg (2002)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Alexei Iliasov
    • 1
  1. 1.Newcastle UniversityUK

Personalised recommendations