The previous chapter focused on modeling the static (organizational) aspects of an OOP solution. It introduced and discussed the methodologies of the UML. It also looked at the purpose and structure of use case diagrams and class diagrams. This chapter continues the discussion of UML modeling techniques and focuses on modeling the dynamic (behavioral) aspects of an OOP solution. The focus in this chapter is on how the objects in the system must interact with each other and what activities must occur to implement the solution.
After reading this chapter, you should be familiar with the following:
The purpose of scenarios and how they extend the use case models.
How sequence diagrams ...