Q

Plant

Figure 8-14. Icon representations for an entity class

Because entity classes are an internal part of the system, actors cannot communicate with them directly. For similar reasons, boundary classes should not communicate directly with them unless the context of the corresponding use case is simple. Entity classes are provided with behavior that is used to solve the problem. Their main responsibility is to store and manage information in the system.

In the Kraalingen approach, as shown in the conceptual model, classes that hold the data and the behavior needed in the simulation process are Soil, Plant, and Weather. Figure 8-15 shows the entity classes for the Start Simulation use case.

Weather

Figure 8-15. Entity classes for the Start Simulation use case.

Weather

Figure 8-15. Entity classes for the Start Simulation use case.

0 0

Post a comment