The DOI matches its Crossref record; 35 of the 35 references it cites were found in a registry or an index.
Supporting scenario-based requirements engineering
Abstract
Scenarios have been advocated as a means of improving requirements engineering yet few methods or tools exist to support scenario based RE. The paper reports a method and software assistant tool for scenario based RE that integrates with use case approaches to object oriented development. The method and operation of the tool are illustrated with a financial system case study. Scenarios are used to represent paths of possible behavior through a use case, and these are investigated to elaborate requirements. The method commences by acquisition and modeling of a use case. The use case is then compared with a library of abstract models that represent different application classes. Each model is associated with a set of generic requirements for its class, hence, by identifying the class(es) to which the use case belongs, generic requirements can be reused. Scenario paths are automatically generated from use cases, then exception types are applied to normal event sequences to suggest possible abnormal events resulting from human error. Generic requirements are also attached to exceptions to suggest possible ways of dealing with human error and other types of system failure. Scenarios are validated by rule based frames which detect problematic event patterns. The tool suggests appropriate generic requirements to deal with the problems encountered. The paper concludes with a review of related work and a discussion of the prospects for scenario based RE methods and tools.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
(1994) · Cited by 21,711
(1993) · Cited by 9,879
Maintaining knowledge about temporal intervals
Allen, J. F. (1983) · Communications of the ACM · doi:10.1145/182.358434 · Cited by 7,593 · cited 1×
“A use case is a collection of actions with rules that govern how actions are linked together , drawn from Allen's temporal semantics [2] and the calculus of the ALBERT II specification language [14].”
(1993) · Elsevier eBooks · doi:10.1016/c2009-0-21512-1 · Cited by 5,504
Reason, J. (1990) · doi:10.1017/cbo9781139062367 · Cited by 5,108
The Psychology of Everyday Things
Massaro, D. W., & Norman, D. A. (1990) · The American Journal of Psychology · doi:10.2307/1423268 · Cited by 3,466
Object Oriented Software Engineering: A Use Case Driven Approach
Jacobson, I. (1992) · CERN Document Server (European Organization for Nuclear Research) · Cited by 2,914
Designing the user interface strategies for effective human-computer interaction
Shneiderman, B. (1987) · ACM SIGBIO Newsletter · doi:10.1145/25065.950626 · Cited by 2,798
Hauser, J. R. (1988) · Harvard business review · Cited by 2,266
Goal-directed requirements acquisition
Dardenne, A., van Lamsweerde, A., & Fickas, S. (1993) · Science of Computer Programming · doi:10.1016/0167-6423(93)90021-g · Cited by 1,976
Human factors in engineering and design
Asfour, S. S. (1988) · International Journal of Industrial Ergonomics · doi:10.1016/0169-8141(88)90028-5 · Cited by 1,807
(2007) · Software Solutions for Engineers and Scientists · doi:10.1201/9781420043037.ch29 · Cited by 1,631
Cognitive Systems Engineering: An Integrative Living Laboratory Framework
(2017) · CRC Press eBooks · doi:10.4324/9781315155401 · Cited by 1,193
A Methodology for Collecting Valid Software Engineering Data
Basili, V. R., & Weiss, D. M. (1984) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1984.5010301 · Cited by 1,149
Verstraete, J. (2000) · Language · doi:10.2307/417432 · Cited by 1,145
gIBIS: a hypertext tool for exploratory policy discussion
Conklin, J., & Begeman, M. L. (1988) · ACM Transactions on Information Systems · doi:10.1145/58566.59297 · Cited by 1,088
Analysis patterns: reusable objects models
Fowler, M. (1996) · Addison-Wesley Longman Publishing Co., Inc. eBooks · Cited by 1,062
Representing and using nonfunctional requirements: a process-oriented approach
Mylopoulos, J., Chung, L., & Nixon, B. (1992) · IEEE Transactions on Software Engineering · doi:10.1109/32.142871 · Cited by 1,018
(1995) · Choice Reviews Online · doi:10.5860/choice.32-2769 · Cited by 993
Human Reliability Analysis: Context and Control
Hollnagel, E. (1994) · Medical Entomology and Zoology · Cited by 733
Software requirements & specifications: a lexicon of practice, principles and prejudices
Jackson, M. (1995) · ACM Press/Addison-Wesley Publishing Co. eBooks · Cited by 575
Inquiry-based requirements analysis
Potts, C., Takahashi, K., & Anton, A. I. (1994) · IEEE Software · doi:10.1109/52.268952 · Cited by 522
Identifying quality-requirement conflicts
BOEHM, B. W., & In, H. P. (1996) · IEEE Software · doi:10.1109/52.506460 · Cited by 295
Structuring Use Cases with Goals
Cockburn, A. (2000) · Cited by 282
Object Models: Strategies, Patterns, and Applications
Coad, P., North, D. M., & Mayfield, M. (1995) · CERN Document Server (European Organization for Nuclear Research) · Cited by 266
Nielsen, J. (1987) · ACM SIGCHI Bulletin · doi:10.1145/25281.1044310 · Cited by 141
Ten steps towards systematic requirements reuse
Lam, W., McDermid, J. A., & Vickers, A. J. (1997) · Requirements Engineering · doi:10.1007/bf02813029 · Cited by 110
The domain theory for requirements engineering
Sutcliffe, A., & Maiden, N. (1998) · IEEE Transactions on Software Engineering · doi:10.1109/32.667878 · Cited by 108
Self-citationIntegrating Obstacles in Goal-Driven Requirements Engineering
van Lamsweerde, A., Letier, E., & (belgium, B. L.-L.-N. (1998) · Cited by 104
A Taxonomy of Error Types for Failure Analysis and Risk Assessment
Sutcliffe, A., & Rugg, G. (1998) · International Journal of Human-Computer Interaction · doi:10.1207/s15327590ijhc1004_5 · Cited by 48
Self-citationTask scripts, use cases and scenarios in object oriented analysis.
Graham, I. M. (1996) · Cited by 42
Representing socio-technical systems options in the development of new forms of work organization
Eason, K., Harker, S., & Olphert, W. (1996) · European Journal of Work and Organizational Psychology · doi:10.1080/13594329608414867 · Cited by 42
Requirements critiquing using domain abstractions
Maiden, N., & Sutcliffe, A. (2002) · doi:10.1109/icre.1994.292386 · Cited by 39
Self-citationDomain analysis for software reuse
Sutcliffe, A. (2000) · Journal of Systems and Software · doi:10.1016/s0164-1212(99)00096-5 · Cited by 8
Self-citationThe psychology of everyday things
(1988) · Choice Reviews Online · doi:10.5860/choice.26-1204 · Cited by 4
Cited by
Handling obstacles in goal-oriented requirements engineering
van Lamsweerde, A., & Letier, E. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.879820 · Cited by 648
Streams, structures, spaces, scenarios, societies (5s): A formal model for digital libraries
Gonçalves, M. A., Fox, E. A., Watson, L. T., & Kipp, N. A. (2004) · ACM Transactions on Information Systems · doi:10.1145/984321.984325 · Cited by 325
Metadata
- Authors
- Sutcliffe, A. G., Maiden, N. A. M., Minocha, S., & Manuel, D.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 1998
- Volume
- 24
- Issue
- 12
- Pages
- 1072-1088
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2113223747
- Cited by
- 337
- References
- 35
- FWCI
- 34.47
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.