Note: The term generic scenario has been used in the early phases of the project, but is not used any more as the scope and purpose of these design artifacts turned out to be very fuzzy. See also the following similar terms Pedagogical and Professional Scenario and System Usage Scenario.

Generic Scenarios describe a recurring pattern of activity that is relevant across different settings. They were also a starting point for thinking the more concrete scenarios already when designing the KP-Lab project. In contrast to the pedagogical and professional scenarios they are not bound to a specific context and therefore more abstract in nature. Generic scenarios can be supplemented by a set of user stories as well as list of critical features, open issues, and related pedagogical and professional scenarios. The purpose of the generic scenarios is to create a shared understanding among technical and pedagogical partners in the initial phases of the project, to organize pedagogical and professional scenarios based on similarities, and to foster a discussion on core issues for the design teams. The generic scenarios were first written by some few partners and individuals, but they are revised and updated by the respective design teams. While some design teams use the generic scenarios as a shared artifact, other design teams focus on concrete pedagogical and professional scenarios or use mockups as the core artifact. Therefore the status of generic scenarios depends on the proceeding chosen by the design team.

An example of a generic scenario developed by DT3 on boundary crossing collaboration is available at:

Back to the Co-Evolutionary Design Glossary
  Page Info My Prefs Log in
This page (revision-3) last changed on 18:24 25-Mar-2017 by ChristophRichter.

Referenced by

JSPWiki v2.4.102