Resumen
The article focuses on scenarios for modeling. Scenarios have become key artifacts in systems engineering but their management is poorly understood. 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, 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. Software engineering employs scenarios as intermediate design artifacts in an expanded goal-driven change process. 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