Abstract
We describe an approach to embedding a formal method within UML use case modelling. Moreover, we extend use case modelling to allow for the explicit representation of safety concerns. Our motivation comes from interaction with systems and safety engineers who routinely rely upon use case modelling during the early stages of defining and analysing system behaviours. Our chosen formal method is Event-B, which is refinement based and consequently has enabled us to exploit natural abstractions found within use case modelling. By underpinning informal use case modelling with Event-B, we are able to provide greater precision and formal assurance when reasoning about concerns identified by safety engineers as well as the subsequent changes made at the level of use case modelling. To achieve this we have extended use case modelling to include the notion of an accident case. Our approach is currently being implemented, and we have an initial prototype.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Abrial, J.R.: Modeling in Event-B: System and Software Engineering. University Press, Cambridge (2010)
Booch, G., Rumbaugh, J., Jacobson, I.: Unified Modeling Language. Addison-Wesley (1997)
Arlow, J., Neustadt, I.: UML 2 and the Unified Process: Practical Object-Oriented Analysis and Design. Pearson Education (2005)
Abrial, J.R., Butler, M., Hallerstede, S., Hoang, T.S., Mehta, F., Voisin, L.: Rodin: An open toolset for modelling and reasoning in event-b. International Journal on Software Tools for Technology Transfer 12(6), 447–466 (2010)
Leveson, N.: Engineering a Safer World: Systems Thinking Applied to Safety. Mit Press (2011)
Ellison, R.J., Linger, R.C., Longstaff, T., Mead, N.R.: Survivable Network System Analysis: A Case Study. IEEE Software 16(4), 70–77 (1999)
McDermott, J., Fox, C.: Using abuse case models for security requirements analysis. In: (ACSAC 1999) Proceedings 15th Annual Computer Security Applications Conference, pp. 55–64. IEEE (1999)
Potts, C.: Using schematic scenarios to understand user needs. In: Proceedings of the 1st Conference on Designing Interactive Systems: Processes, Practices, Methods, and Techniques, pp. 247–256. ACM (1995)
Harel, D., Marelly, R.: Come, Let’s Play: Scenario-Based Programming using LSCs and the Play-Engine. Springer Science and Business Media, Vol. 1 (2003)
Russo Jr., A.G., de Sousa, T.: Starting B specifications from use cases. In: Abstract State Machines (ASM), Alloy, B and Z Conference (2010)
Whittle, J.: Precise Specification of Use Case Scenarios. In: Dwyer, M.B., Lopes, A. (eds.) FASE 2007. LNCS, vol. 4422, pp. 170–184. Springer, Heidelberg (2007)
Klimek, R., Szwed, P.: Formal Analysis of Use Case Diagrams. Computer Science, 115–131 (2010)
Jackson, M.: Problem Frames: Analysing and Structuring Software Development Problems. Addison-Wesley (2001)
Ponsard, C., Dieul, E.: From Requirements Models to Formal Specifications in B. ReMo2V (2006)
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2015 Springer International Publishing Switzerland
About this paper
Cite this paper
Murali, R., Ireland, A., Grov, G. (2015). A Rigorous Approach to Combining Use Case Modelling and Accident Scenarios. In: Havelund, K., Holzmann, G., Joshi, R. (eds) NASA Formal Methods. NFM 2015. Lecture Notes in Computer Science(), vol 9058. Springer, Cham. https://doi.org/10.1007/978-3-319-17524-9_19
Download citation
DOI: https://doi.org/10.1007/978-3-319-17524-9_19
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-17523-2
Online ISBN: 978-3-319-17524-9
eBook Packages: Computer ScienceComputer Science (R0)