6.0. Notation
When identifying requirements, we must bring structure to the overall set of requirements the system must satisfy, which is one of the goals of a use case model. Our first order of discussion in this section is to understand the fundamental elements and diagrams within the UML that are most commonly used in establishing requirements.
6.0.1. Actor
As discussed in Chapter 3, actors are depicted as stick figures and represent an external entity that interacts with a system. Actors are always external to the system under development, which implies they mark the boundary conditions of our system. An actor should be given a name that makes sense within the context of the use case with which they interact. Because of this, actors typically ...
Get Java™ Design: Objects, UML, and Process 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.
