Review of case studies

This chapter presents a review of case studies regarding the application of unified modeling language (UML). In the majority of modeling activities it is important to consider a balance of things and behaviors. The model being developed needs to be able to demonstrate support for dynamic processes, either related to a business model or a software/hardware model. There must be a system structure that supports this dynamic behavior, so both static and dynamic model elements need to be considered somewhere along the way. In some case beginning with an element of class modeling seems appropriate, being supplemented by the CRC technique or interaction diagrams to test out the model to see if it supports key dynamic behaviors. At other times starting with a dynamic modeling approach might help to determine key classes. If a use case diagram has just a single actor and a single use case it can still be helpful. For a start it makes the overall requirement and system interfaces crystal clear. Statecharts tend to imply a lower level of dynamic modeling, moving toward code and implementation.