DIS '97 Proceedings of the 2nd conference on Designing interactive systems: processes, practices, methods, and techniques
Lessons learned during requirements acquisition for COTS systems
Communications of the ACM
Supporting Scenario-Based Requirements Engineering
IEEE Transactions on Software Engineering
Inferring Declarative Requirements Specifications from Operational Scenarios
IEEE Transactions on Software Engineering
Requirements engineering in the year 00: a research perspective
Proceedings of the 22nd international conference on Software engineering
Viewing use cases as active objects
ACM SIGSOFT Software Engineering Notes
Experience with SCRAM, a SCenario Requirements Analysis Method
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
A Case Study of Decomposing Functional Requirements Using Scenarios
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
CREWS-SAVRE: Systematic Scenario Generation and Use
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Streams, structures, spaces, scenarios, societies (5s): A formal model for digital libraries
ACM Transactions on Information Systems (TOIS)
Evaluation of software usability using scenarios organized by abstraction structure
Proceedings of the 14th European conference on Cognitive ergonomics: invent! explore!
| Hi-index | 0.02 |
An approach to requirements engineering based on a combination of early prototyping, scenario-based analysis and design rationale is described. Requirements are elicited by presenting users with a prototype-simulation of a prospective design, combined with rationale based techniques for structuring probe questions. Design of analysis sessions and a walkthrough method for requirements elicitation are reported in three layers for linking questions to artefact/scenario demonstrations, follow-up questioning for user-system dependencies and handling user-analyst discourse. An empirical study of the requirements analysis approach is reported. The study used a ship board emergency application. The technique combination approach proved very effective in eliciting requirements but differences in analyst style were an important variable. Recommendations are made for designing and managing requirements capture sessions using scenario-based approaches.