Scenario
by
Benedikt Liegener
—
last modified
Jul 13, 2011 16:28
—
filed under:
KnowledgeModel
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) |
Typically a Scenario 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. |
||||
Competencies
-
UniDue: Requirements Engineering; http://www.sse.uni-due.de/wms/en/index.php?go=110; Klaus Pohl, Andreas Gehlert
- CITY: User-centred requirements engineering; http://hcid.soi.city.ac.uk/research/index.html; Neil Maiden, Kos Zachos
Scenarios
TBD
References
- TBD
