Exception handling and object-oriented programming: towards a synthesis
OOPSLA/ECOOP '90 Proceedings of the European conference on object-oriented programming on Object-oriented programming systems, languages, and applications
Safeware: system safety and computers
Safeware: system safety and computers
The B-book: assigning programs to meanings
The B-book: assigning programs to meanings
The unified software development process
The unified software development process
Handling Obstacles in Goal-Oriented Requirements Engineering
IEEE Transactions on Software Engineering - special section on current trends in exception handling—part II
Exception handling: issues and a proposed notation
Communications of the ACM
Design of dependable computing systems
Design of dependable computing systems
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process
Writing Effective Use Cases
Dependability: Basic Concepts and Terminology
Dependability: Basic Concepts and Terminology
AToM3: A Tool for Multi-formalism and Meta-modelling
FASE '02 Proceedings of the 5th International Conference on Fundamental Approaches to Software Engineering
The Object Constraint Language: Getting Your Models Ready for MDA
The Object Constraint Language: Getting Your Models Ready for MDA
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Eliciting security requirements with misuse cases
Requirements Engineering
Exception handling in the development of dependable component-based systems
Software—Practice & Experience - Research Articles
Use Case-Based Modeling and Analysis of Failsafe Fault-Tolerance
RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
Better Exception-Handling in Block-Structured Systems
IEEE Software
Misuse Cases: Use Cases with Hostile Intent
IEEE Software
Addressing degraded service outcomes and exceptional modes of operation in behavioural models
Proceedings of the 2008 RISE/EFTS Joint International Workshop on Software Engineering for Resilient Systems
UML'99 Proceedings of the 2nd international conference on The unified modeling language: beyond the standard
Model-Driven assessment of use cases for dependable systems
MoDELS'06 Proceedings of the 9th international conference on Model Driven Engineering Languages and Systems
Exception-Aware requirements elicitation with use cases
Advanced Topics in Exception Handling Techniques
A survey of software development approaches addressing dependability
FIDJI'04 Proceedings of the 4th international conference on Scientific Engineering of Distributed Java Applications
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
Addressing degraded service outcomes and exceptional modes of operation in behavioural models
Proceedings of the 2008 RISE/EFTS Joint International Workshop on Software Engineering for Resilient Systems
Crisis management systems: a case study for aspect-oriented modeling
Transactions on aspect-oriented software development VII
Workflow design using fragment composition: crisis management system design through ADORE
Transactions on aspect-oriented software development VII
Crisis management systems: a case study for aspect-oriented modeling
Transactions on aspect-oriented software development VII
Idealized fault-tolerant components in requirements engineering
SERENE'11 Proceedings of the Third international conference on Software engineering for resilient systems
Dependability modeling and analysis of software systems specified with UML
ACM Computing Surveys (CSUR)
Hi-index | 0.00 |
Discovering and documenting potential abnormal situations and irregular user behavior that can interrupt normal system interaction is of tremendous importance in the context of dependable systems development. Exceptions that are not identified during requirements elicitation might eventually lead to an incomplete system specification during analysis, and ultimately to an implementation that lacks certain functionality, or even behaves in an unreliable way. This paper presents a requirements engineering process, DREP, that systematically guides the developer to consider reliability and safety concerns of reactive systems. After the discovery of normal system behavior by means of use cases, the developer is lead to explore exceptional situations arising in the environment that change the context in which the system operates and service-related exceptional situations that threaten to fail user goals. The process requires the developer to specify means that detect such situations, and to define the recovery measures that attempt to put the system in a reliable and safe state. The process is iterative, and refinements are carried out, if necessary, to achieve desired quality levels. To conclude the requirements phase, an extended use case diagram summarizes the normal interactions, exceptions, handlers and their relationships. The proposed process is demonstrated with the 407 Express Toll Route System case study.