1.4. Scenarios
The object model gives us a static picture of our system. That is, we depict classes and associations that are unchanging. However, systems are not static, and objects change as their data members change values. We can explore the dynamic behavior of a system through a technique known as scenarios: walking through a portion of our system, taking different paths.
For example, suppose we are modeling a digital answering machine that records, plays back, and erases messages. Here is a portion of our system, shown in Figure 1.14 . Base class Message has placeholder functions record(), erase() and playback(). Classes Out_Going_Message and In_Coming_Message both derive from Message. Class Machine controls an Out_Going_Message and many ...
Get Navigating C++ and Object-Oriented Design now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
