UML use case diagram - System of goods selling via catalogues

"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.

This purchase order processing UML activity diagram was created on the base of activity diagram from the software architecture documentation wiki of the Software Engineering Institute (SEI) of Carnegie Mellon University (CMU).
[wiki.sei.cmu.edu/ sad/ index.php/ Image:PurchaseOrderActivityDiagram.png]
"A purchase order (PO) is a commercial document and first official offer issued by a buyer to a seller, indicating types, quantities, and agreed prices for products or services. Acceptance of a purchase order by a seller forms a contract between the buyer and seller, so no contract exists until the purchase order is accepted. It is used to control the purchasing of products and services from external suppliers.
Creating a purchase order is typically the first step of the purchase to pay process in an ERP system." [Purchase order. Wikipedia]
This purchase order processing UML activity 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.

"Communication diagram (called collaboration diagram in UML 1.x) is a kind of UML interaction diagram which shows interactions between objects and/ or parts (represented as lifelines) using sequenced messages in a free-form arrangement.
Communication diagram corresponds (i.e. could be converted to/ from or replaced by) to a simple sequence diagram without structuring mechanisms such as interaction uses and combined fragments. It is also assumed that message overtaking (i.e., the order of the receptions are different from the order of sending of a given set of messages) will not take place or is irrelevant." [uml-diagrams.org/ communication-diagrams.html]
The template "UML communication diagram" for the ConceptDraw PRO diagramming and vector drawing software is included in the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.
www.conceptdraw.com/ solution-park/ software-uml

This IDEF3 diagram example was redesigned from the Wikimedia Commons file: 2-02 Example of a Transition Schematic.jpg.
[commons.wikimedia.org/ wiki/ File:2-02_ Example_ of_ a_ Transition_ Schematic.jpg]
"The schematic in Figure 2-2 represents an Object Schematic for the Order Material scenario derived from the business owner’s description. This example happens to illustrate a Transition Schematic since it characterizes the nature and structure of object state transitions for occurrences of the Order Material scenario. A key document in this process is the Purchase Request form. This form is eventually transformed into a Purchase Order (PO) via the Order Material process. A circle containing the name of an object represents an object of a certain kind (e.g., Purchase Request, Account Manager, Project). These labeled circles are known as kind symbols. A certain kind of object being in a certain state is represented by a circle with a label that captures both the kind itself and a corresponding state, thereby representing the type (or class) of objects that are in that state (within a given process). ... One of the first steps to develop an Object Schematic is to identify the possible states in which the object can exist. Though a real-world object often evolves through a continuum of states, an Object Schematic focuses on those distinguished states of particular interest to the domain expert. The transition arcs (arrows with triangular, filled-in heads) connecting the circles symbolize a state transition, the activity of changing from one state to another. The conditions that establish when an object is in a given state, how it exists a state, how it can transition between states, and how it can enter a new state are recorded on a special form. The banded boxes linked to the arrows (called referents) are aids to describe the relationships between objects states and UOBs, scenarios, or other Transition Schematics that participate in a scenario occurrence. ... The transition junctions containing an “X” (for exclusive or) indicate the choice of exactly one path among several possible paths in an occurrence." [IDEF3 Process Description Capture Method Report AL-TR-1995-XXXX. idef.com/ pdf/ Idef3_ fn.pdf]
The diagram "Transition schematic - IDEF3 diagram example" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the solution "IDEF Business Process Diagrams" from the area "Business Processes" of ConceptDraw Solution Park.

"Communication diagram (called collaboration diagram in UML 1.x) is a kind of UML interaction diagram which shows interactions between objects and/ or parts (represented as lifelines) using sequenced messages in a free-form arrangement.
Communication diagram corresponds (i.e. could be converted to/ from or replaced by) to a simple sequence diagram without structuring mechanisms such as interaction uses and combined fragments. It is also assumed that message overtaking (i.e., the order of the receptions are different from the order of sending of a given set of messages) will not take place or is irrelevant." [uml-diagrams.org/ communication-diagrams.html]
The template "UML communication diagram" for the ConceptDraw PRO diagramming and vector drawing software is included in the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.
www.conceptdraw.com/ solution-park/ software-uml

The vector stencils library "UML communication diagrams" contains 23 symbols for the ConceptDraw PRO diagramming and vector drawing software.
"... communication diagrams use the free-form arrangement of objects and links as used in Object diagrams. In order to maintain the ordering of messages in such a free-form diagram, messages are labeled with a chronological number and placed near the link the message is sent over. Reading a communication diagram involves starting at message 1.0, and following the messages from object to object." [Communication diagram. Wikipedia]
The example "Design elements - UML communication diagrams" is included in the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.