Value Chain
by
Benedikt Liegener
—
last modified
Jul 26, 2011 09:57
—
filed under:
KnowledgeModel
Definitions
| Term: Value Chain |
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) |
An approach to designing service-based systems based on their role and added value in the actual process of rendering a product or a service. This typically involves making distinction between the core and the supporting processes. | An approach to correlating requirements and opportunities for changes in the evolving product/service value chains, with changes in the underlying business processes and/or activities, and vice-versa. | Correlation between the notion of (added) value within a business value chain and quality metrics for components of a service-oriented application. | A Value Chain is the largest possible process in an organization. The value chain is decomposed into a set of core business processes and support processes necessary to produce a service, product or product line. These core business processes are subdivided into activities. |
| Service Composition and
Coordination (KM-SC) |
|||||
| Service Infrastructure (KM-SI) |
|||||
| Generic (domain independent) |
|||||
Competencies
- TBD
Scenarios
TBD
References
- TBD













