Purchase order processing UML activity diagram

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.

"Metadata is "data about data". The term is ambiguous, as it is used for two fundamentally different concepts (types). Structural metadata is about the design and specification of data structures and is more properly called "data about the containers of data"; descriptive metadata, on the other hand, is about individual instances of application data, the data content.
Metadata are traditionally found in the card catalogs of libraries. As information has become increasingly digital, metadata are also used to describe digital data using metadata standards specific to a particular discipline. By describing the contents and context of data files, the quality of the original data/ files is greatly increased. For example, a webpage may include metadata specifying what language it is written in, what tools were used to create it, and where to go for more on the subject, allowing browsers to automatically improve the experience of users." [Metadata. Wikipedia]
The UML class diagram example "Metadata information model" 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 bank account UML package diagram was redesigned from the Wikimedia Commons file: Package diagram1.jpg.
[commons.wikimedia.org/ wiki/ File:Package_ diagram1.jpg]
This file is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license. [creativecommons.org/ licenses/ by-sa/ 3.0/ deed.en]
"A very important concept in object-oriented design, inheritance, refers to the ability of one class (child class) to inherit the identical functionality of another class (super class), and then add new functionality of its own. (In a very non-technical sense, imagine that I inherited my mother's general musical abilities, but in my family I'm the only one who plays electric guitar.) To model inheritance on a class diagram, a solid line is drawn from the child class (the class inheriting the behavior) with a closed, unfilled arrowhead (or triangle) pointing to the super class. Consider types of bank accounts: Figure 4 shows how both CheckingAccount and SavingsAccount classes inherit from the BankAccount class.
Figure 4: Inheritance is indicated by a solid line with a closed, unfilled arrowhead pointing at the super class." [ibm.com/ developerworks/ rational/ library/ content/ RationalEdge/ sep04/ bell/ index.html]
This bank account UML package 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.

This sequence diagram example was redesigned from the Wikimedia Commons file: Builder design pattern sequence1.png.
"The UML sequence diagram which illustrates the Builder design pattern."
[commons.wikimedia.org/ wiki/ File:Builder_ design_ pattern_ sequence1.png]
"The builder pattern is an object creation software design pattern. Unlike the abstract factory pattern and the factory method pattern whose intention is to enable polymorphism, the intention of the builder pattern is to find a solution to the telescoping constructor anti-pattern. ... The intent of the Builder design pattern is to separate the construction of a complex object from its representation. By doing so the same construction process can create different representations." [Builder pattern. Wikipedia]
The SysML sequence diagram example "Builder design pattern sequence" was drawn using the ConceptDraw PRO diagramming and vector drawing software extended with the SysML solution from the Software Development area of ConceptDraw Solution Park.