Printer Friendly


Scenarios have become key artifacts in systems engineering but their management is poorly understood.

Management science, software engineering, and human-computer interaction research have traditionally followed a model-based approach, which involves: formally reconstructing the concepts and rationale behind the current system; specifying the desired change at the conceptual level; and implementing the changed concepts to reach the new system while taking the legacy context into account.

With the deeper immersion of IT usage and impact in everyday life, formal models often prove clumsy to develop and difficult to understand. Even when an initial shared understanding exists, the preceding procedure describes but one step in a continuous change process that is hard to trace without strong linkage to reality.

A scenario describes a possible set of events that might reasonably take place. Its purpose is to stimulate and document thinking about current problems, possible occurrences, assumptions relating to these occurrences, action opportunities, and risks. Thus, scenarios must be linked to change goals. Results from cognitive psychology [1] indicate that scenarios offer a middle-ground abstraction between models and reality, providing a universally understood medium for participatory design, and facilitating reuse of design knowledge:

* Scenarios focus design efforts on use first and foremost. What people can do with the old/new system, and the consequences for themselves and for their organizations, is described and analyzed prior to detailing the system functions and features that enable this use.

* Scenarios suspend commitment but support concrete progress. They vividly explain why a system is needed by showing what it is used for, but they also facilitate an analysis of design alternatives for how it is used.

* Scenarios provide a task-oriented design decomposition that can be used from many perspectives, including usability trade-offs, iterative development, and manageable software design object models.

Consistent with these observations, software engineering employs scenarios as intermediate design artifacts in an expanded goal-driven change process, as shown in Figure 1 [3]. This implies four typical views for the classification of scenario-based approaches [4]:

* What part of the work activity is captured in a scenario (content view)?

* How is it represented in the development environment (form view)?

* For what usage in the design process is it captured (purpose view)?

* How is it developed and evolved (life-cycle view)?


In the European CREWS project, this framework was used to compare research and practice in scenario management [5]. While researchers, focusing on the form view, investigate scenarios as formal mediators between detailed traces and class-level specifications, practitioners rarely use formal scenario representations but complain about a lack of guidance in authoring text scenarios.

From the content perspective, scenarios can address an organizational work context, they can represent the internal interplay of components within the current or future system, or--the most frequent case--they can focus on the interaction between the system and its environment. Interaction, in turn, can be studied in an inbound direction (what constraints does the environment place on the system?) or in an outbound direction (what impact has the system on its environment?).

Scenario purpose and impact showed much more variation than expected from the research literature. While researchers discuss the application of scenarios for making abstract models understandable, to reach partial agreement and consistency, practitioners also use scenarios for task decomposition in complex projects, as a linkage between development phases, and as design aids and boundary conditions for object models.

Consequently, the life cycle of scenarios is also much more involved than is addressed by current research. The framework shown in Figure 1 covers a broad variety of possible methodologies. Many software companies follow an informal development cycle that contains general goals and future scenarios, but no models. At the other extreme, formal scenario techniques in strategic management often abstract reality to the values of a few key variables and strategic events. In between, Rational's Unified Modeling Language (UML) has adapted Jacobsen's approach [2], which groups a collection of interaction scenarios (expressed as message trace diagrams or collaboration diagrams) into a use-case for manageability. However, this definition of scenarios is clearly too narrow. For example, practitioners also employ use-cases for managing internal scenarios of technical systems such as in telecommunications.

Many large projects consider scenario selection, structuring, and evolution to be key issues. Multiple views on scenarios (developer, user, and manager views of the same scenario) and the traceability of scenarios across project phases (interplay between scenarios and prototypes, elaboration of scenarios into test cases) still await solid solutions. Finally, methodological advice--when to embed what kind of scenario technique into traditional methods, based on sound cost-benefit analysis of scenario usage--is one of the most crucial topics to be addressed when the vision of scenario-integrated methodologies such as those promoted by UML is to become a reality.


[1.] Carroll, J.M., Ed. Scenario-based Design: Envisioning Work and Technology in System Development. Wiley, NY, 1995.

[2.] Jacobsen, I. The use-case construct in object-oriented design. In Carroll, J.M., Ed. Scenario-based Design: Envisioning Work and Technology in System Development. Wiley, NY, 1995.

[3.] Jarke, M., Bui, X.T., Carroll, J. Scenario management--An interdisciplinary perspective. Requirements Engineering J. 3, 3 (1998).

[4.] Rolland, C., Ben Achour, C., Cauvet, C., Ralyte, J., Sutcliffe, A., Maiden, M., Jarke, M., Haumer, P., Pohl, K., Dubois, E., Heymans, P. A proposal for a scenario classification framework. Requirements Engineering Journal 3, 1 (1998), 23-47.

[5.] Weidenhaupt, K., Pohl, K., Jarke, M., Haumer, P. Scenario usage in software development: Current practice. IEEE Software (Mar. 1998), 34-45.

This work was supported in part by the European Commission via ESPRIT Long Term Research project 21.903 (CREWS).

Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee.

MATTHIAS JARKE (jarke@informatik. is a professor of Information Systems and the chairman of the Computer Science Department at RWTH Aachen in Germany.
COPYRIGHT 1999 Association for Computing Machinery, Inc.
No portion of this article can be reproduced without the express written permission from the copyright holder.
Copyright 1999 Gale, Cengage Learning. All rights reserved.

Article Details
Printer friendly Cite/link Email Feedback
Title Annotation:Industry Trend or Event
Publication:Communications of the ACM
Date:Jan 1, 1999
Previous Article:CONNECTING the DESIGN of SOFTWARE to the DESIGN of WORK.

Terms of use | Privacy policy | Copyright © 2019 Farlex, Inc. | Feedback | For webmasters