Actor

• Actor icon (Stick-man);
• Actor name (label for the icon);
• Actor documentation: text (optional);
• External user with stereotyped class <<actor>> whose specific role is to use one or more use case in a system;
• Communication relationships with the use cases in the system;
• Identifying actors help determine use cases in the requirement Analysis phase of the Software Development Process.
• The same physical object may play different roles and become different actors that use different use cases (e.g., the same person may be the Customer actor who orders goods and Salesman actor who processes sales)