SimulationForm initial data for soil and plant, selecting a weather station name from a pull down list, etc. Additional behavior such as the one used for validating the input data, can be part of class definition. As the input data are entered using the boundary class, their validation should be part of class's behavior too.
Figure 8-11. One boundary class controls the dialog between an actor and a use case.
It is not necessary at this point of the analysis to go into deep details over how the user interface will be designed and how many items will it contain. These details will be provided later, during the implementation phase. For the moment it is important only to define in a general manner the behavior of the boundary class. As boundary classes are used to model user interfaces, they are platform dependent. As an example, if the implementation environment changes from Windows to UNIX, then the boundary classes will change too. Usually, the lifecycle of a boundary class follows the lifecycle of the corresponding use case. When the use case terminates, there is no more need for the object created from the boundary class.
Was this article helpful?