UML Use Case Diagram. Design Elements

This example of bank ATM UML activity diagram was created on the base of UML use case diagram of automated teller machine from the course "Thinking in Java, 2nd edition, Revision 9" by Bruce Eckel published on the website of the Computer Science and Electrical Engineering Department of the University of Maryland, Baltimore (UMBC).
"If you are designing an auto-teller, for example, the use case for a particular aspect of the functionality of the system is able to describe what the auto-teller does in every possible situation. Each of these “situations” is referred to as a scenario, and a use case can be considered a collection of scenarios. You can think of a scenario as a question that starts with: “What does the system do if...?” For example, “What does the auto-teller do if a customer has just deposited a check within the last 24 hours, and there’s not enough in the account without the check having cleared to provide a desired withdrawal?”
Use case diagrams are intentionally simple to prevent you from getting bogged down in system implementation details prematurely...
Each stick person represents an “actor,” which is typically a human or some other kind of free agent. (These can even be other computer systems, as is the case with “ATM.”) The box represents the boundary of your system. The ellipses represent the use cases, which are descriptions of valuable work that can be performed with the system. The lines between the actors and the use cases represent the interactions.
It doesn’t matter how the system is actually implemented, as long as it looks like this to the user."
[csee.umbc.edu/ courses/ 331/ resources/ tij/ text/ TIJ213.gif]
This automated teller machine (ATM) UML use case diagram example was created using the ConceptDraw PRO diagramming and vector drawing software extended with the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.

"An example scenario is presented to demonstrate how a common issue tracking system would work:
(1) A customer service technician receives a telephone call, email, or other communication from a customer about a problem. Some applications provide built-in messaging system and automatic error reporting from exception handling blocks.
(2) The technician verifies that the problem is real, and not just perceived. The technician will also ensure that enough information about the problem is obtained from the customer. This information generally includes the environment of the customer, when and how the issue occurs, and all other relevant circumstances.
(3) The technician creates the issue in the system, entering all relevant data, as provided by the customer.
(4) As work is done on that issue, the system is updated with new data by the technician. Any attempt at fixing the problem should be noted in the issue system. Ticket status most likely will be changed from open to pending.
(5) After the issue has been fully addressed, it is marked as resolved in the issue tracking system.
If the problem is not fully resolved, the ticket will be reopened once the technician receives new information from the customer. A Run Book Automation process that implements best practices for these workflows and increases IT personnel effectiveness is becoming very common." [Issue tracking system. Wikipedia]
The UML use case diagram example "Ticket processing system" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.

"Banks offer many different channels to access their banking and other services:
(1) Automated Teller Machines.
(2) A branch is a retail location.
(3) Call center.
(4) Mail: most banks accept cheque deposits via mail and use mail to communicate to their customers, e.g. by sending out statements.
(5) Mobile banking is a method of using one's mobile phone to conduct banking transactions.
(6) Online banking is a term used for performing multiple transactions, payments etc. over the Internet.
(7) Relationship Managers, mostly for private banking or business banking, often visiting customers at their homes or businesses.
(8) Telephone banking is a service which allows its customers to conduct transactions over the telephone with automated attendant or when requested with telephone operator.
(9) Video banking is a term used for performing banking transactions or professional banking consultations via a remote video and audio connection. Video banking can be performed via purpose built banking transaction machines (similar to an Automated teller machine), or via a video conference enabled bank branch clarification.
(10) DSA is a Direct Selling Agent, who works for the bank based on a contract. Its main job is to increase the customer base for the bank." [Bank. Wikipedia]
The UML use case diagram example "Banking system" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.

The vector stencils library "UML use case diagrams" contains 25 symbols for the ConceptDraw PRO diagramming and vector drawing software.
"Use case diagrams are usually referred to as behavior diagrams used to describe a set of actions (use cases) that some system or systems (subject) should or can perform in collaboration with one or more external users of the system (actors). Each use case should provide some observable and valuable result to the actors or other stakeholders of the system. ...
Use case diagrams are in fact twofold - they are both behavior diagrams, because they describe behavior of the system, and they are also structure diagrams - as a special case of class diagrams where classifiers are restricted to be either actors or use cases related to each other with associations. ...
Use case is usually shown as an ellipse containing the name of the use case. ...
Name of the use case could also be placed below the ellipse. ...
If a subject (or system boundary) is displayed, the use case ellipse is visually located inside the system boundary rectangle. Note, that this does not necessarily mean that the subject classifier owns the contained use cases, but merely that the use case applies to that classifier. ...
A list of use case properties - operations and attributes - could be shown in a compartment within the use case oval below the use case name. ...
Use case with extension points may be listed in a compartment of the use case with the heading extension points. ...
A use case can also be shown using the standard rectangle notation for classifiers with an ellipse icon in the upper right-hand corner of the rectangle and with optional separate list compartments for its features. ...
Subject (sometimes called a system boundary) is presented by a rectangle with subject's name, associated keywords and stereotypes in the upper left corner. Use cases applicable to the subject are located inside the rectangle and actors - outside of the system boundary. ...
Standard UML notation for actor is "stick man" icon with the name of the actor above or below of the icon. Actor names should follow the capitalization and punctuation guidelines for classes. The names of abstract actors should be shown in italics. ...
Custom icons that convey the kind of actor may also be used to denote an actor, such as using a separate icon(s) for non-human actors. ...
An actor may also be shown as a class rectangle with the standard keyword «actor», having usual notation for class compartments ...
An actor can only have binary associations to use cases, components, and classes. ...
An association between an actor and a use case indicates that the actor and the use case somehow interact or communicate with each other.
Only binary associations are allowed between actors and use cases.
An actor could be associated to one or several use cases. ...
A use case may have one or several associated actors." [uml-diagrams.org/ use-case-diagrams.html]
The example "Design elements - UML use case diagrams" is included in the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.

"A catalog merchant (catalogue merchant in British and Canadian English) is a form of retailing. The typical merchant sells a wide variety of household and personal products, with many emphasizing jewelry. Unlike a self-serve retail store, most of the items are not displayed; customers select the products from printed catalogs in the store and fill out an order form. The order is brought to the sales counter, where a clerk retrieves the items from the warehouse area to a payment and checkout station. ...
The catalog merchant has generally lower prices than other retailers and lower overhead expenses due to the smaller size of store and lack of large showroom space.
There are a few key benefits to this approach. By operating as an in-store catalog sales center, it could be exempt from the "Resale price maintenance" policy of the manufacturers, which can force conventional retailers to charge a minimum sales price to prevent price-cutting competition; it also reduces the risk of merchandise theft, known in the industry as shrinkage.
From the consumer's point of view, there are potential advantages and disadvantages. The catalog showroom approach allows customers to shop without having to carry their purchases throughout the store as they shop. Possible downsides include that customers may be required to give their contact information when an order is placed, take the time to fill out order forms, and wait a period of time for their order to be available for purchase. This wait may be days long, one of the chief vulnerabilities of the catalog showroom approach." [Catalog merchant. Wikipedia]
The UML use case diagram example "System of goods selling via catalogues" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.