In the first part of the book, we introduced the basic concepts of the object-oriented paradigm and their notations in UML. In the second part of the book, we will see how the knowledge accumulated so far will be used to model a particular problem and develop the corresponding software. We will go through the phases of analysis and design of a simple crop simulation model. The selected model is chosen to be simple on purpose; we would like to avoid getting lost in the details of the crop modeling. Instead, our focus is on the approach used to carry out the analysis and the design using the object-oriented paradigm and construct visual models using UML. The relative simplicity of the selected model does not question the integrity of the used methodology or the nature of the problems encountered and the provided solutions.

Chapter 8 deals with the process of analysis, design, and development of a crop simulation model referred to as the Kraalingen approach [Kra95]. First, a short description of the problem will be provided. Some of the equations used in this model will be presented to demonstrate the links that are needed between model elements such as Plant, Soil, and Weather. Then, the use case shows what the system can offer to users, without showing how these functionalities will be provided. After the use case model is developed, the use case realization is presented for each use case. The use case realization presents several type of diagrams developed to show the dynamic aspects of the system. The diagrams are the sequence and collaboration diagrams, known as interaction diagrams. They help developers to better understand the role and the behavior of each of the potential classes needed to develop the system.

A conceptual model for the Kraalingen approach is presented to show concepts and abstractions from the problem domain and their relationships. The conceptual model shows only one type of class, the classes that represent concepts of the problem. Other classes than the ones that represent concepts are needed; the behavior of these classes is needed to present the graphical user interface (GUI) and the dialog between the user and the system. Finally, the implementation in Java for interfaces and classes used in the system is provided.

0 0

Post a comment