01.01.2015 Views

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

54<br />

Saturday Morning<br />

In Use Case diagrams, people, systems, and devices are all referred to as actors. The icons<br />

to model them may vary, but the concept remains the same. An actor is a role that an external<br />

entity plays in relation to the system. <strong>To</strong> reiterate, an actor is a role, not necessarily a<br />

particular person or a specific system. Figure 5-5 shows some actor icons.<br />

Venue Manager<br />

<br />

HR System<br />

<br />

Satellite Feed<br />

person example system example device example<br />

Figure 5-5 Actor icons for the Use Case diagram<br />

For example, an actor may be the role of a stock clerk placing products into inventory.<br />

Later that day the same person might work receiving products from a delivery truck. The<br />

same person played two roles. Likewise, many people can function in the same role. For<br />

example, warehouses have many stock clerks.<br />

Using roles helps keep you focused on how the system is being used rather than on the<br />

current organization of the company into job titles and responsibilities. The things that<br />

people do must be separated from their current job titles for the system to be able to cope<br />

with the changes that are inevitable in any system.<br />

How do you identify actors Listen to descriptions of the system. Listen for the roles<br />

people perform when using the system. When multiple people perform the same function,<br />

try to name the role they all share when performing the particular function.<br />

Tip<br />

Throughout the modeling effort, the vocabulary of the user will reveal most<br />

of the key elements of the model. Watch for how parts of speech translate<br />

into model elements; actors typically show up as the subject in sentences<br />

describing how people use the systems.<br />

Use Cases<br />

Use Cases define the required features of the system. Without these features, the system<br />

cannot be used successfully.<br />

Each Use Case is named using a verb phrase that expresses a goal the system must<br />

accomplish, for example, deposit money, withdraw money, and adjust account (see Figure<br />

5-6). Although each Use Case implies a supporting process, the focus is on the goal, not<br />

the process.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!