e3value user manual, first release

Chapter 4
Dependency Elements

Actors and value activities have one or more value interfaces through which they perform economic transactions with the outside world. There are internal dependencies among the interfaces of each actor that must be included in a business model of a value network.

For example, to provide a luxury rail transport service, a railway company has to acquire food somewhere to serve during the trip. The value activity Luxury rail transporting thus has two value interfaces, one for providing the luxury rail transport service and the other to acquire food. The first interface depends on the second. These dependencies are represented in an e3value model by means of dependency elements.

Dependency elements do not represent the time ordering of transactions nor the operational activities of actors. Dependency elements represent the value-adding logic of an actor by relating the value interfaces of an actor to each other, to customer needs, and to boundary elements that indicate the scope of the model.

 4.1 Customer needs
 4.2 Boundary elements
 4.3 Dependency paths
 4.4 And-dependencies
 4.5 Or-dependencies
 4.6 Dependency graphs