This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Making Use of Scenarios for Validating Analysis and Design
December 1998 (vol. 24 no. 12)
pp. 1182-1196

Abstract—Scenarios can help remedy the most serious obstacle in the design process that is a chronic lack of knowledge of the application domain. Moreover, scenarios can be employed in analysis and design to serve both illustrating the context of an envisaged usage (user's perspective) and demonstrating the design proposal in terms of the intended usage (analyst's perspective). In contrasting both perspectives by means of a dialectic process a synthesis can be achieved that incorporates a shared understanding. Validation is a process to achieve such an understanding. The semantic structure of types of scenarios is investigated thus illustrating how a context of use analysis according to ISO 9241-11 can be exploited for validation purposes. The role of scenarios in usability engineering is contrasted with traditional concepts of systems analysis as an attempt to narrow the bridge between software engineering and usability engineering.

[1] D.M. Berry and B. Lawrence, "Requirements Engineering," IEEE Software, pp. 26-29, Mar./Apr. 1998.
[2] W. Bischofsberger and G. Pomberger, Prototyping-Oriented Software Development. Concepts and Tools.Berlin: Springer, 1992.
[3] G. Bjerknes, P. Ehn, and M. Kyng, eds., "Computers and Democracy—a Scandinavian Challenge,"United Kingdom: Gower, Adlershot, 1987.
[4] B. Boar, Application Prototyping: A Requirements Definition Strategy for the 80th.New York: John Wiley&Sons, 1983.
[5] B.W. Boehm, "Verifying and Validating Software Requirements and Design Specifications," IEEE Software, vol. 1, pp. 75-88, 1984.
[6] F.P. Brooks Jr., "No Silver Bullet—Essence and Accident in Software Engineering," The Mythical Man-Month: Essays on Software Engineering, second edition. pp. 179-203.Reading, Mass.: Addison-Wesley, 1995.
[7] J.M. Carroll and M.B. Rosson, "Getting Around the Task-Artifact Cycle: How to Make Claims and Design by Scenario," ACM Trans. of Information Systems, vol. 10, pp. 181-212, 1992.
[8] J.M. Carroll, "Making Use a Design Representation," Comm. ACM, vol. 37/12, pp. 29-35, 1994.
[9] J.M. Carroll, ed., Scenario-Based Design: Envisioning Work and Technology in System Development.New York: John Wiley, 1995.
[10] J.M. Carroll, M.B. Rosson, and M.K. Singley, "The Collaboration Thread: A Formative Evaluation of Object-Oriented Education," C. Cook and J. Spohrer, eds., Empirical Studies of Programmers. Proc. Fifth Workshop, pp. 26-41.Norwood, N.J.: Ablex, 1993.
[11] B. Dahlbom and L. Mathiassen, Computers in Context.Oxford: NCC Blackwell, 1995.
[12] D. Dörner, Problemlösen als Informationsverarbeitung.Stuttgart: Kohlhammer, 1979. in German
[13] W. Dzida, "On Controllability," C. Floyd, H. Züllighoven, R. Budde, and R. Keil-Slawik, eds., Software Development and Reality Construction.Berlin: Springer, pp. 325-335, 1992.
[14] A. Finkelstein, J. Kramer, B. Nuseibeh, L. Finkelstein, and M. Goedicke, "Viewpoints: A Framework for Integrating Multiple Perspectives in System Development," Int'l J. Software Eng. and Knowledge Eng., vol. 2, no. 1, pp. 31-57, 1992.
[15] C. Floyd, "A Systematic Look at Prototyping," Budde, Kuhlen-kamp, Matthiassen, und Züllighoven, eds., Approaches to Prototyping, pp. 1-8.Berlin: Springer, 1984.
[16] C. Floyd, "Autooperationale Form und situiertes Handeln," C. Hubig (Hrsg.): Cognitio humana—Dynamik des Wissens und der Werte. XVII Deutscher Kongreßfür Philosophie, Akademie Verlag, pp. 237-252, 1996. in German
[17] C. Floyd, H. Züllighoven, R. Budde, and R. Keil-Slawik, eds., Software Development and Reality Construction.Berlin: Springer, 1992.
[18] J.D. Gannon, "Verification and Validation," A.B. Tucker, ed., The Computer Science and Engineering Handbook, ch. 109. Boca Raton: CRC Press, 1997.
[19] J. Goguen, "Requirements Engineering Reconciliation of Technical and Social Issues," technical report, Centre for Requirements and Foundations, Oxford Univ. Computing Laboratory, Cambridge, United Kingdom, 1992.
[20] J. Goguen, "Formality and Informality in Requirements Engineering," Proc. IEEE Int'l Conf. Requirements Eng.,Los Alamitos, Calif.: IEEE CS Press, 1996.
[21] J. Greenbaum and M. Kyng, eds., Design at Work: Cooperative Design of Computer Systems.Hillsdale, N.J.: Lawrence Erlbaum, 1991.
[22] P. Hsia, A. Davis, and D. Kung, "Status Report: Requirements Engineering," IEEE Software, pp. 75-79, Nov. 1993.
[23] IEEE Std. 610.12-1990, Standard Glossary of Software Engineering Terminology, IEEE Press, Piscataway, N.J., 1990.
[24] ISO 9001, Quality Systems, Model for Quality Assurance in Design/Development, Production, Installation and Servicing, 1994.
[25] ISO 9241-10, Ergonomic Requirements for Office Work with Visual Display Terminals (VDTs)—Dialogue Principles, 1995.
[26] ISO 9241-11, Ergonomic Requirements for Office Work with Visual Display Terminals (VDTs)—Guidance on Usability, 1998.
[27] I. Jacobson, Object-Oriented Software Engineering, Addison-Wesley/ACM Press, New York, 1991.
[28] 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.
[29] J. Leite and P.A. Freeman, "Requirements Validation Through Viewpoint Resolution," IEEE Trans. Software Eng., vol. 17, no. 12, pp. 1,253-1,269, 1991.
[30] P. Loucopoulos and V. Karakostas, System Requirements Engineering, first edition. London: McGraw-Hill, 1995.
[31] R.L. Mack, "Discussion: Scenarios as Engines of Design," J.M. Carroll, ed., Scenario-Based Design. Envisioning Work and Technology in System Development.New York: John Wiley&Sons, pp. 361-386, 1995.
[32] I.I. Mitroff and T.R. Featheringham, "On Systematic Problem Solving and the Error of the Third Kind," Behavioral Sciences, vol. 10, no. 6, pp. 383-393, 1974.
[33] B.A. Myers, "User-Interface Tools: Introduction and Survey," IEEE Software, pp. 15-23, Jan. 1989.
[34] J. Nielsen, Usability Engineering, Academic Press, New York, 1993.
[35] D. Norman, "Some Observations on Mental Models," D. Gentner and A.L. Stevens, eds., Mental Models.London: Erlbaum, 1983.
[36] C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyte, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, E. Dubois, and P. Heymans, "A Proposal for a Scenario Classification Framework," Requirements Engineering J., vol. 3, no.1, 1998.
[37] D.T. Ross, "Structured Analysis (SA): A Language for Communicating Ideas," IEEE Trans. Software Eng., vol. 3, no 1, pp. 16-34, 1977.
[38] M.B. Rosson and J.M. Carroll, "Narrowing the Specification-Implementation Gap in Scenario-Based Design," J.M. Carroll, ed., Scenario-Based Design: Envisioning Work and Technology in System Development.New York: John Wiley&Sons, pp. 247-278, 1995.
[39] M. Scriven, "The Methodology of Evaluation," R.W. Tyler, R.M Gagné, and M. Scriven, eds., Perspectives of Curriculum Evaluation. AERA Monograph Series on Curriculum Evaluation, no. 1, Chicago: Rand McNally, pp. 39-83, 1967.
[40] J. Siddiqi, "Challenging Universal Truth of Requirements Engineering," IEEE Software, pp. 18-19, Mar. 1994.
[41] W. Stein, "Objektorientierte Analysemethoden—ein Vergleich," Informatik Spektrum, vol. 16, pp. 317-332, 1993. in German
[42] D. Teichrow and E.A. Hershey, "PSL/PSA: A Computer Aided Technique for Structured Documentation and Analysis of Information Processing Systems," IEEE Trans. Software Eng., vol. 3, no. 1, pp. 41-48, 1977.
[43] D.R. Wallace and R.U. Fujii, "Software Verification and Validation: An Overview," IEEE Software, pp. 10-17, May 1989.
[44] K. Weidenhaupt, K. Pohl, M. Jarke, and P. Haumer, "Scenarios in System Development: Current Practice," IEEE Software, pp. 34-45, Mar./Apr. 1998.
[45] T. Winograd and C.F. Flores, Understanding Computers and Cognition: A New Foundation for Design, Ablex, Norwood, N.J., 1986.

Index Terms:
Requirements construction, validation, scenario types, dialectic process, work context, prototyping.
Citation:
Wolfgang Dzida, Regine Freitag, "Making Use of Scenarios for Validating Analysis and Design," IEEE Transactions on Software Engineering, vol. 24, no. 12, pp. 1182-1196, Dec. 1998, doi:10.1109/32.738346
Usage of this product signifies your acceptance of the Terms of Use.