Plan
by
Benedikt Liegener
—
last modified
Apr 30, 2012 09:17
—
filed under:
KnowledgeModel
Definitions
| Term: Plan |
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) |
Plans represent activities usually with timing and resources,carried out by some actor to satisfy goals or to satisfice soft-goals. [Tropos] {SYN: Task}, [Wikipedia]. | ||||
Competencies
-
UniDue: Requirements Engineering; http://paluno.uni-due.de/en/adaptive-software-services/#c22302; Klaus Pohl, Andreas Gehlert
- POLIMI: Web service orchestration and QoS optimization; http://home.dei.polimi.it/pernici/ws-research.html;
Barbara Pernici, Danilo Ardagna
- Tilburg: Project Management; http://www.tilburguniversity.nl/eriss/research/; Oktay Turetken
References
- [Tropos]: http://troposproject.org/
- [Wikipedia] Plan: http://en.wikipedia.org/wiki/Plan
