Get Free Trial

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. Read more
UML activity diagram of purchase order processing
UML activity diagram of purchase order processing , send signal action, initial node, horizontal swimlanes, activity partition, activity group, fork node, join node, decision node, merge node, activity final node, activity edge, object flow edge, action, accept event action,
"In software engineering, an entity–relationship model (ER model) is a data model for describing a database in an abstract way.Chen's notation for entity–relationship modeling uses rectangles to represent entity sets, and diamonds to represent relationships appropriate for first-class objects: they can have attributes and relationships of their own. If an entity set participates in a relationship set, they are connected with a line.
Attributes are drawn as ovals and are connected with a line to exactly one entity or relationship set." [Entity–relationship model. Wikipedia]
This sample Chen's ER-diagram illustrates the structure of a typical MMORP game.
"Massively multiplayer online role-playing game (MMORPG) mixes the genres of role-playing video games and Massively multiplayer online games, possibly in the form of web browser-based games, in which a very large number of players interact with one another within a virtual world.
As in all RPGs, players assume the role of a character (often in a fantasy world or science-fiction world) and take control over many of that character's actions. MMORPGs are distinguished from single-player or small multi-player online RPGs by the number of players, and by the game's persistent world (usually hosted by the game's publisher), which continues to exist and evolve while the player is offline and away from the game." [Massively multiplayer online role-playing game. Wikipedia]
This ERD example was redrawn using the ConceptDraw PRO diagramming and vector drawing software from the Wikipedia file: ER Diagram MMORPG.png. [en.wikipedia.org/wiki/File:ER_Diagram_MMORPG.png]
This file is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license. [creativecommons.org/licenses/by-sa/3.0/deed.en]
This Chen's ERD example is included in the Entity-Relationship Diagram (ERD) solution from the Software Development area of ConceptDraw Solution Park. Read more
Chen's ERD
Chen's ERD, weak key attribute, weak entity, relationship, multivalue attribute, key attribute, identifying relationship, entity, derived attribute, attribute,