When exception handling is required for a software system, the defining the requirements of the desired behavior in the presence of exceptional conditions is generally defined as an add-on to the core requirements. This is necessary because by definition, requirements define desired behavior, and exceptions are undesired, abnormal situations. Consequently, by using separate mechanisms to define:normal" processing and "exceptional" processing, the requirements statements do not provide a unified way of analyzing behavior, potentially allowing undesired effects during execution. This paper proposes a new approach, based on usage modeling, to unifying the specification of normal behavior and exceptional behavior into one model. Keywords: exception handling, usage models, state machines, requirements specification. © 2006 Springer-Verlag Berlin/Heidelberg.
CITATION STYLE
Bail, W. (2006). An approach to defining requirements for exceptions. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 4119 LNCS, pp. 243–254). https://doi.org/10.1007/11818502_13
Mendeley helps you to discover research relevant for your work.