9.7. Naming System Events and Operations
System events (and their associated system operations) should be expressed at the level of intent rather than in terms of the physical input medium or interface widget level.
It also improves clarity to start the name of a system event with a verb (add..., enter…, end…, make…), as in Figure 9.4, since it emphasizes the command orientation of these events.
Figure 9.4. Choose event and operation names at an abstract level.
Thus “enterItem” is better than “scan” (that is, laser scan) because it captures the intent of the operation while remaining abstract and noncommittal with respect to design choices about ...
Get Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process, Second Edition 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.
