Comparing representations with relational and EER models
Communications of the ACM
Graphs and tables: a four-factor experiment
Communications of the ACM
Diagrams and design tools in context
ACM SIGDOC Asterisk Journal of Computer Documentation
Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
Replicating the CREWS Use Case Authoring Guidelines Experiment
Empirical Software Engineering
Guiding Use Case Authoring: Results of an Empirical Study
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
UML Bible
Deriving Safety Requirements Using Scenarios
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Eliciting security requirements with misuse cases
Requirements Engineering
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)
Clarity for Stakeholders: Empirical Evaluation of ScenarioML, Use Cases, and Sequence Diagrams
CERE '07 Proceedings of the 2007 Fifth International Workshop on Comparative Evaluation in Requirements Engineering
Safety Hazard Identification by Misuse Cases: Experimental Comparison of Text and Diagrams
MoDELS '08 Proceedings of the 11th international conference on Model Driven Engineering Languages and Systems
Misuse Cases: Use Cases with Hostile Intent
IEEE Software
A Safety Inspection Management System for Mine Equipment Based on UML
ICSPS '09 Proceedings of the 2009 International Conference on Signal Processing Systems
A comparison of two approaches to safety analysis based on use cases
ER'07 Proceedings of the 26th international conference on Conceptual modeling
Templates in domain modeling - a survey
The evolution of conceptual modeling
Supporting failure mode and effect analysis: a case study with failure sequence diagrams
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
Using SMCD to reduce inconsistencies in misuse case models: A subject-based empirical evaluation
Journal of Systems and Software
Hi-index | 0.00 |
Safety is of growing importance for information systems due to increased integration with embedded systems. Discovering potential hazards as early as possible in the development is key to avoid costly redesign later. This implies that hazards should be identified based on the requirements, and it is then useful to compare various specification techniques to find out the strengths and weaknesses of each with respect to finding and documenting hazards. This paper reports on two experiments in hazards identification - one experiment based on textual use cases and one based on systems sequence diagrams. The comparison of the experimental results reveal that use cases are better for identifying hazards related to the operation of the system while system sequence diagrams are better for the identification of hazards related to the system itself. The combination of these two techniques is therefore likely to uncover more hazards than one technique alone.