CROAM - objective analysis

In my study for the 'perfect' project analysis tool, I developed a new analysis model , I'll call CROAM from now (Core Recursive Objective Analysis Model).
With this model, one should be able to analyze almost anything. The whole new idea of this model is the fact that it's a recursive model, it gets recursed by refining the objectives.
This model can be used to map business processes, create project plans, ...

I' ll explain this model with an imaginary company called 'Xmastree', a company that sells Christmas trees.

The graph for each objective in this model looks like this :

Example objectives:

1.  The CEO wants the management  to increase the profit, and let the accounting division inform him (the manager) about it.
   1. The Management wants the Marketing Division to Increase Customer sales, and lets a survey company inform them (the management)
      1. The Marketing division wants the regional television to publish a documentary about ecologic awareness within the company , and lets the regional television inform the customers.
      2. The Marketing division wants the national newspaper to publish a marketing campaign, and lets the newspaper inform the customers.
      3. The Marketing division wants The Marketing division  to do a mailing to it's high potentials, and lets the Marketing division inform the customers
   2. The Management wants the HRM Division to Streamline personnel costs, and lets the accounting division inform them (the management)
      1. The Hrm division wants the accounting division to report all logistic costs by division and lets the accounting division inform them(the hrm division)
      2. The Hrm division wants The Hrm division to apply logistic hrm savings and lets The Hrm division inform the management.
   3. The Management asks the ICT Division to Optimize communication costs, and lets the accounting division inform them (the management)
   4. The Accounting division wants the accounting division to report profit gains, and lets the accounting division inform the CEO

This gives an easy to define analysis method. Each step mentioned in the example above, contains a Requester, a negotiator, an objective, a deliverer and an acceptor.

The following step is to define when a certain objective can be put in a certain state. 

As an example, objective 1.2.2 should be put in a Refused state when objective 1.2.1 receives a Decline or Refused state. Objective 1.2.2 should be put in a Request state when objective 1.2.1 receives an Accept state

Using this simple technique one should be able to describe all  business processes of a company in a simple way.

The next step for me will be creating a program that implements work flows using this kind of analysis as a proof of concept. The final idea is to implement this in CUDI (my universal database framework).