Personal tools
You are here: Home Knowledge Model REPOSITORY of Terms S Scenario

Scenario

by Benedikt Liegener last modified Apr 25, 2012 13:35
— filed under:

Definitions

Term:
Scenario
Domain: Cross-cutting issues
Engineering and Design
(KM-ED)
Adaptation and Monitoring
(KM-AM)
Quality Definition, Negotiation and Assurance
(KM-QA)
Generic
(domain independent)
D
o
m
a
i
n
:
L
a
y
e
r
s

Business Process Management
(KM-BPM)




Service Composition and Coordination
(KM-SC)




Service Infrastructure
(KM-SI)




Generic
(domain independent)
A scenario typically contains a set of activities that are related to its context. Such a scenario describes a concrete example, which either satisfies or denies a set of goals for which the scenario is a specialisation.

Scenario is a valuable means for providing context to the elicitation of user requirements. They allow the software engineer to provide a framework for questions about user tasks by permitting "what if" and "how is this done" questions to be asked. The most common type of scenario is the use case. Scenario notations such as use cases and diagrams are common in modeling software [SWEBOK].


Scenario is a synoptical collage of an event or series of actions and events [Wikipedia].

 

Competencies

 

Scenarios

 

References


Document Actions
  • Send this
  • Print this
  • Bookmarks

The Plone® CMS — Open Source Content Management System is © 2000-2017 by the Plone Foundation et al.