Markov analysis of software specifications
ACM Transactions on Software Engineering and Methodology (TOSEM)
Requirements Specification for Process-Control Systems
IEEE Transactions on Software Engineering
Managing Conflicts in Goal-Driven Requirements Engineering
IEEE Transactions on Software Engineering
Fault Detectability Analysis for Requirements Validation of Fault Tolerant Systems
HASE '99 The 4th IEEE International Symposium on High-Assurance Systems Engineering
Improving the use case driven approach to requirements engineering
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Formal specification of real-time dependable systems
ICECCS '95 Proceedings of the 1st International Conference on Engineering of Complex Computer Systems
Quantifying the reliability of software: statistical testing based on a usage model
ISESS '95 Proceedings of the 2nd IEEE Software Engineering Standards Symposium
Reconciling System Requirements and Runtime Behavior
IWSSD '98 Proceedings of the 9th international workshop on Software specification and design
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Automatic Generation of Markov Chain Usage Models from Real-Time Software UML Models
QSIC '04 Proceedings of the Quality Software, Fourth International Conference
Using Markov Chain Usage Models to Test Complex Systems
HICSS '05 Proceedings of the Proceedings of the 38th Annual Hawaii International Conference on System Sciences - Volume 09
The Usage Model: A Structure for Richly Describing Product Usage during Design and Development
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Performability modeling of exceptions-aware systems in multiformalism tools
ASMTA'11 Proceedings of the 18th international conference on Analytical and stochastic modeling techniques and applications
| Hi-index | 0.00 |
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.