An Empirical Evaluation about Using Models to Improve Preliminary Safety Analysis
Resumo
Context: Safety analysis is an activity of fundamental importance in the development of safety-critical systems (SCS) to ensure that hazardous situations are properly found and mitigated. Such analysis is usually performed after a system requirements specification is available. Therefore, it is then worthwhile to investigate specification techniques to detect their strengths and weaknesses with respect to finding and documenting hazards early in the development process. Objective: In this paper, we investigate similarities and differences in the results of a preliminary safety analysis from requirements specified using Textual Use Cases (TUC) and Business Process Modeling Notation (BPMN). Method: We adopted a controlled experiment as research method using computer engineering students as subjects. Results: The subjects of BPMN group found more accidents, hazards as well as more causes of hazards. Moreover, they have a higher preference for the template used for safety analysis documentation. Conclusions: The use of BPMN to represent the interactions among actors in a system probably lead to the discovery of more accidents and hazards, but more experiments are necessary to test this hypothesis since the results are not statistically significant.
Referências
Wohlin, Claes et al. Experimentation in software engineering. Springer Science & Business Media, 2012.
Stålhane T, Sindre G. An experimental comparison of system diagrams and textual use cases for the identification of safety hazards. In: International Journal of Information System Modeling and Design (IJISMD), 5 (1), 2014, pp. 1-24.
Leveson, N. Engineering a Safer World: Systems Thinking Applied to Safety. Mit Press, 2011.
H. Kaindl, R. Popp, D. Raneburger. Towards reuse in safety risk analysis based on product line requirements. In: 23rd International Requirements Engineering Conference (RE), 2015, pp. 241-246.
Stålhane T, Sindre G, Du Bousquet L. Comparing safety analysis based on sequence diagrams and textual use cases. In: Advanced Information Systems Engineering, 2010, pp. 165-179.
Alspaugh TA, Sim SE, Winbladh K, Leila MH, Ziv H, Richardson DJ. Clarity for stakeholders: Empirical evaluation of scenarioml, use cases, and sequence diagrams. In: International Workshop on Comparative Evaluation in Requirements Engineering, 2007, pp. 1-10.
Svahnberg M, Aurum A, Wohlin C (2008) Using students as subjects - an empirical evaluation. In: Proceedings of International Symposium on Empirical Software Engineering and Measurement, 2008, pp 288–290.
Larkin, J.H. and H.A. Simon, Why a diagram is (sometimes) worth ten thousand words. Cognitive Science, 1987, pp. 65-99.
Vilela, Jéssyka; Castro, Jaelson; Pimentel, João. A systematic process for obtaining the behavior of context-sensitive systems. Journal of Software Engineering Research and Development, v. 4, n. 1, p. 2, 2016.
Moody D. The “physics” of notations: toward a scientific basis for constructing visual notations in software engineering. In: IEEE Transactions on Software Engineering. 2009 Nov; 35 (6), pp. 756-79.
