This Article 
 Bibliographic References 
 Add to: 
Supporting Scenario-Based Requirements Engineering
December 1998 (vol. 24 no. 12)
pp. 1072-1088

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.

[1] C.B. Achour and C. Rolland, "Introducing Genericity and Modularity of Textual Scenario Interpretation in the Context of Requirements Engineering," CREWS Technical Report, Centre de Recherche en Informatique, Universite de Paris 1, Paris, France, 1997.
[2] J.F. Allen, “Maintaining Knowledge about Temporal Intervals,” Comm. ACM, vol. 26, no. 11, pp. 832–843, 1983.
[3] R.W. Bailey, Human Performance Engineering. Prentice Hall, 1982.
[4] V.R. Basili and D.M. Weiss, "A Methodology for Collecting Valid Software Data," IEEE Trans. Software Eng., vol. 10, no. 3, pp. 728-738, 1984.
[5] B. Boehm and H. Hoh, Identifying Quality-Requirement Conflicts IEEE Software, pp. 25-36, Mar. 1996.
[6] C.M. Carroll, "The Scenario Perspective on System Development," J.M. Carroll, ed., Scenario-Based Design: Envisioning Work and Technology in System Development.New York: John Wiley&Sons, 1995.
[7] L. Chung, "Representing and Using Non-Functional Requirements: A Process-Oriented Approach," Technical Report, DKBS-TR-93-1, Univ. of Toronto, June 1993.
[8] P. Coad, D. North, and M. Mayfield, Object Models: Strategies, Patterns, and Applications. Yourdon Press, 1995.
[9] P. Coad and E. Yourdon, Object-Oriented Analysis, second ed., Yourdon Press, Englewood Cliffs, N.J., 1991.
[10] A. Cockburn, "Structuring Use Cases with Goals," 1995.
[11] J. Konclin and M. Bergen, “Gibis: A Hypertext Tool for Exploratory Policy Discussion,” ACM Trans. Office Information Systems, vol. 6, no. 4, pp. 303–331, Oct. 1988.
[12] A. Dardenne, A. van Lamsweerde, and S. Fickas, "Goal-Directed Requirements Acquisition," Science of Computer Programming, pp. 3-50, vol. 20, Apr. 1993.
[13] S.C. Dik, The Theory of Functional Grammar, Part I: The Structure of the Clause, Functional Grammar Series, vol. 9, Foris Publications, 1989.
[14] P. Dubois, E. Dubois, and J. Zeippen, "On the Use of a Formal Representation," Proc. Third Int'l Symp. Requirements Eng., IEEE CS Press, pp. 128-137, 1997.
[15] Dynamic Systems Development Method (DSDM) Version 3.0, DSDM Consortium, Tesseract Publishing, Sept. 1997.
[16] K.D. Eason, S.D. Harker, and C.W. Olphert, "Representing Social-Technical System Options in the Development of New Forms of Work Organization," European J. of Work and Organizational Psychology, vol. 5, no. 3, pp. 399-420, 1996.
[17] S.R. Faulk, "Software Requirements: A Tutorial," Software Engineering, M. Dorfman and R. H. Thayer, eds., pp. 82-103, 1996.
[18] M. Fowler, Analysis Patterns: Reusable Object Models. Addison-Wesley, 1997.
[19] E. Gamma et al., Design Patterns: Elements of Object-Oriented Software, Addison-Wesley, Reading, Mass., 1994.
[20] P. Gough et al., "Scenarios—An Industrial Case Study and Hypermedia Enhancements," Proc. Int'l Symp. Requirements Eng., IEEE CS Press, Los Alamitos, Calif., 1995, pp. 10-17.
[21] I. Graham, "Task Scripts, Use Cases and Scenarios in Object-Oriented Analysis," Object-Oriented Systems, vol. 3, pp. 123-142, 1996.
[22] R. Hauser and D. Clausing, "The House of Quality," Harvard Business Review, pp. 63-73, May-June 1988.
[23] P. Heymans and E. Dubois, "Some Thoughts about the Animation of Formal Specifications written in the ALBERT II Language," CREWS Technical Report, Computer Science Dept., Univ. of Namur, Belgium, 1997.
[24] E. Hollnagel, Human Reliability Analysis Context and Control. Academic Press, 1993.
[25] ISO 9241, Ergonomic requirements for office systems visual display terminals, Parts 10, 11, 16 International Standards, parts 1-9, 12-15, 17, draft standards; Int'l Standards Organization, Switzerland, available from National Standards Organization.
[26] M. Jackson, Software Requirements and Specifications, Addison-Wesley, Reading, Mass., 1995.
[27] M.A. Jackson, System Development. Prentice Hall, 1983.
[28] M. Jackson and P. Zave, "Domain Descriptions," Proc. RE'93—First Int'l IEEE Symp. Requirements Eng., pp. 56-64, Jan. 1993.
[29] I. Jacobson, M. Christerson, P. Jonsson, and G. Overgaard, Object-Oriented Software Eng.: A Use-Case Driven Approach. Addison-Wesley, 1992.
[30] M. Kyng, "Creating Contexts for Design," J.M. Carroll, ed., Scenario-Based Design: Envisioning Work and Technology in System Development.New York: John Wiley&Sons, pp. 85-107, 1995.
[31] W. Lam, J.A. McDermid, and A.J. Vickers, "Ten Steps Towards Systematic Requirements Reuse," Proc. Third IEEE Int'l Symp. Requirements Engineering, IEEE CS Press, pp. 6-13, 1997.
[32] A. van Lamsweerde and E. Leiter, "Integrating Obstacles in Goal-Driven Requirements Engineering," technical report, Dept. of Computer Science, Catholic Univ. of Louvain, 1997.
[33] A. van Lamsweerde, R. Darimont, and P. Massonet, "Goal-Directed Elaboration of Requirements for a Meeting Scheduler: Problems and Lessons Learned," Proc. RE'95—Second Int'l Symp. on Requirements Eng.,York, IEEE, 1995.
[34] N.A.M. Maiden and A.G. Sutcliffe, "Requirements Critiquing Using Domain Abstractions," Proc. IEEE Conf. Requirements Eng., IEEE CS Press, pp. 184-193, 1994.
[35] C. Mazza et al., Software Engineering Standards, Prentice Hall, Upper Saddle River, N.J., 1994.
[36] J. Nielsen, Usability Engineering, Academic Press, New York, 1993.
[37] D.A. Norman, The Psychology Of Everyday Things. Basic Books Inc., 1988.
[38] J.D. Palmer, "Traceability," Software Engineering, M. Dorfman and R.H. Thayer, eds., pp. 266-276, 1996.
[39] C. Potts, K. Takahashi, and A. Anton, "Inquiry-Based Requirements Analysis," IEEE Software, Mar. 1994, pp. 21-32.
[40] C. Potts, K. Takahashi, J. Smith, and K. Ora, "An Evaluation of Inquiry Based Requirements Analysis for an Internet Service," Proc. Second IEEE Symp. Requirements Eng., IEEE Computer Society, pp. 27-34, 1995.
[41] J. Rasmussen, A.M. Pejtersen, and L.P. Goodstein, Cognitive Systems Engineering, John Wiley&Sons, New York, 1994.
[42] J.T. Reason, Human Error. Cambridge Univ. Press, 1990.
[43] S. Roberston at the Atlantic Systems Guild, United Kingdom, personal communication.
[44] T. Royer, "Using Scenario-Based Designs to Review User Interface Changes and Enhancements," Proc. DIS95: Designing Interactive Systems,Ann Arbor, pp. 237-246, 1995.
[45] M.S. Sanders and E.J. McCormick, Human Factors Engineering and Design. McGraw-Hill, 1992.
[46] B. Shneiderman, Designing the User Interface: Strategies for Effective Human-Computer Interaction, 3rd Edition, Addison Wesley, Reading, Mass., 1998, to appear.
[47] A.G. Sutcliffe, Human Computer Interface Design. second edition, London: Macmillan, 1994.
[48] A.G. Sutcliffe, "Requirements Rationales: Integrating Approaches to Requirements Analysis," Proc. Designing Interactive Systems (DIS'95), pp. 33-42,New York: ACM Press, 1995.
[49] A.G. Sutcliffe and G. Rugg, "A Taxonomy of Error Types for Failure Analysis and Risk Assessment," Int'l J. Human Computer Interactions, to appear.
[50] A. Sutcliffe, "A Technique Combination Approach to Requirements Engineering," Proc. RE'97—Third Intl. Symp. Requirements Eng., pp. 65-74,Anapolis, IEEE, 1997.
[51] A.G. Sutcliffe and N.A.M. Maiden, "The Domain Theory for Requirements Engineering," IEEE Trans. Software Eng., vol. 24, no. 3, 1998, pp. 174–196.
[52] A.G. Sutcliffe and S. Minocha, "Scenario-Based Analysis of Non-Functional Requirements," Proc. Workshop 'Requirements Engineering for Software Quality' (REFSQ'98) at CAiSE' 98 Pisa, Italy, June 1998.
[53] A. Sutcliffe, Domain Analysis for Software Reuse J. Systems and Software, vol. 50, no. 3, pp. 175-199, 2000.
[54] E. Yu and J. Mylopoulos, "Towards Modelling Strategic Actor Relationships for Information Systems Development—with Examples from Business Process Reengineering," Proc. Fourth Workshop on Information Technology and Systems (WITS'94),Vancouver, B.C. Canada, Dec. 1994.

Index Terms:
Requirements engineering, use cases, scenarios, scenario generation, exception types, reuse, patterns.
Alistair G. Sutcliffe, Neil A.M. Maiden, Shailey Minocha, Darrel Manuel, "Supporting Scenario-Based Requirements Engineering," IEEE Transactions on Software Engineering, vol. 24, no. 12, pp. 1072-1088, Dec. 1998, doi:10.1109/32.738340
Usage of this product signifies your acceptance of the Terms of Use.