Value Chain

by Benedikt Liegener — last modified Apr 25, 2012 14:28

— filed under: KnowledgeModel

Definitions

Term: Value Chain		Domain: Cross-cutting issues
Term: Value Chain		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)				A value chain is a chain of activities for a firm operating in a specific industry. The business unit is the appropriate level for construction of a value chain, not the divisional level or corporate level. Products pass through all activities of the chain in order, and at each activity the product gains some value. The chain of activities gives the products more added value than the sum of the independent activities' values [Wikipedia].