In a dynamic business model we also represent the life-cycle relationships among these entities, showing which entity is responsible for which life cycle activity.

Realise that in the above model (as shown by ‘generative arrows):
• Corporate Management mandates some change in the identity, concept and requirements of the
• Manufacturing Division,
• Product Design Division identifies, develops the concept of and designs the Product, and the
• Manufacturing Division implements (builds/manufactures) the Product.
The question is: which entity is responsible for the rest of the life cycle activities of the Manufacturing Division (the area of life cycle activities shown in dotted lines)?
The answer is: there is a need for an entity that carries out the change (and performs the life cycle activities in question) -- a Change Project (called 'Project to Improve Mfg Division' below) is this missing entity.
So, a change project is another entity in your dynamic business model diagram.
