This page will be an overview on what was our experience in iterating through the CDM-s steps.

We've been given a ready to use set of models with already defined objective.
The main question is “How does the initial allocation of carbon quotas and the rules governing their trade influence the distribution and total release of carbon?”.
In the second step we needed to answer to the following questions:

• What is the data: The data is the whole behavior of the simulation. We are interested in statistics and all the numbers.
• Where is the data: Those numbers and statistic values are held within the messages. Listening to all of them with a module is enough to have all the information we need to answer to the main topic.
• How is it shared: The data is shared through the network and with messages with the use of the Blackboard system architecture.
• How is it processed/changed: The data is processed inside all the modules. All of them have tasks to do meanwhile they are exchanging messages with the other modules. The system will evolve itself just using its modules and their simple functions.

This accomplish the first two steps of the CDM-s in which we should define objectives and questions to answer to during and at the end of the simulation.

In step 3 we had to define:

• Modules: this was given in the beginning with the specification of objective and the roughly defined modules.
• Blackboards: our blackboard architecture is implemented with a single WhiteBoard (naming by Psyclone framework) that is our Market. This is the most rational decision since in a double auction market the first functionality is to run a market accepting all the requests by the industries.
• Unit tests: we used a unit test in the beginning to troubleshoot the initial weird behavior that we were getting from the first implementation. This was really helpful for having a robust skeleton of the system before starting improving the rest of the functionality.
  

Step 4: the fun starts here..
This was one of the hardest step to go through because all the debugging, troubleshooting and important decision were made in this step after experiencing all the possible behaviors of the system.