Final Class Diagram For The Kraalingen Approach

Figure 8-27 shows the final class diagram for the Kraalingen approach. For readability reasons, attributes and operations are not presented in the class diagram. Interfaces are used where change or substitutability is expected. For example, the communication point between SimulationForm and SimulationController is represented by the interface ISimulationController. Therefore, any simulation class/component that implements ISimulationController can be used. In the same way, the communication point between SimulationController and entity classes is represented by three interfaces; IPlant, ISoil for communicating with Plant and Soil, and IWeather for communicating with Weather.

Figure 8-27 shows the final class diagram for the Kraalingen approach. For readability reasons, attributes and operations are not presented in the class diagram. Interfaces are used where change or substitutability is expected. For example, the communication point between SimulationForm and SimulationController is represented by the interface ISimulationController. Therefore, any simulation class/component that implements ISimulationController can be used. In the same way, the communication point between SimulationController and entity classes is represented by three interfaces; IPlant, ISoil for communicating with Plant and Soil, and IWeather for communicating with Weather.

0 0

Post a comment