Design and validation of computer protocols
Design and validation of computer protocols
Specification-based test oracles for reactive systems
ICSE '92 Proceedings of the 14th international conference on Software engineering
GPS-based geographic addressing, routing, and resource discovery
Communications of the ACM
Negative scenarios for implied scenario elicitation
Proceedings of the 10th ACM SIGSOFT symposium on Foundations of software engineering
Automated Software Engineering
Operational Profiles in Software-Reliability Engineering
IEEE Software
SCR*: A Toolset for Specifying and Analyzing Software Requirements
CAV '98 Proceedings of the 10th International Conference on Computer Aided Verification
Ad Hoc Wireless Networks: Architectures and Protocols
Ad Hoc Wireless Networks: Architectures and Protocols
Incremental elaboration of scenario-based specifications and behavior models using implied scenarios
ACM Transactions on Software Engineering and Methodology (TOSEM)
Validating Personal Requirements by Assisted Symbolic Behavior Browsing
Proceedings of the 19th IEEE international conference on Automated software engineering
Fundamental Nonmodularity in Electronic Mail
Automated Software Engineering
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Artificial neural networks as multi-networks automated test oracle
Automated Software Engineering
Requirements engineering tools: Capabilities, survey and assessment
Information and Software Technology
| Hi-index | 0.00 |
Formal scenarios have many uses in requirements engineering, validation, performance modeling, and test generation. Many tools and methodologies can handle scenarios when the number of steps (interleaved inputs and outputs of the target system) is reasonably small. However, scenario based techniques do not scale well with the number of steps, number of actors, and complexity of behaviors and system interactions to be specified in the scenario. First, it is impractically tedious and error-prone to specify thousands of input steps and corresponding expected outputs. Second, even if one can write down such large scale scenarios, confidence in their correctness is naturally low. Third, complex systems requiring large scale scenarios tend to require many such scenarios to adequately cover the behavior space. This paper describes the motivations for and problems of large scale scenarios, as well as the LSS method, which uses automated and semi-automated techniques in describing, maintaining, communicating, and using large scale scenarios in requirements engineering. The method is illustrated in two widely divergent application domains: military live training instrumentation and electronic mail servers. A case study demonstrates the practical and beneficial use of LSS in architectural modeling of a complex, real-world system design.