This site uses cookies. By continuing to browse the ConceptDraw site you are agreeing to our Use of Site Cookies.
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.
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,
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.
Bank ATM UML sequence diagram
Bank ATM UML sequence diagram, use case, subject, system boundary, association, actor,
This example of automated teller machine (ATM) UML sequence diagram was created on the base of figure 5 "Sequence diagram" on the webpage "Message Sequence Charts and their Ilk" from the website of the University of California Irvine (UCI) Donald Bren School of Information and Computer Sciences.
"A UML sequence diagram or SD is similar to an MSC but written with a different notation. Presumably the same semantic issues arise, but possibly not since UML semantics are not well-defined. An example is shown in Figure 5.
The timelines are dotted rather than solid, and the name of the component is inside a box at the head of each timeline. The narrow rectangles apparently show when a component is active (unsure precisely what "active" means). An X on a timeline indicates that the component ceases to exist in some sense (unsure precisely how this is meant also). In the example, the Bank timeline has an X simply as an example (presumably the Bank does continue to exist)."
[www.ics.uci.edu/ ~alspaugh/ cls/ shr/ msc.html]
This example of bank ATM sequence diagram 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.
Bank ATM UML sequence diagram
Bank ATM UML sequence diagram, lifeline, execution specification, destruction event, asynchronous call,

entity-relationship diagram, ER-diagram, database ERD Entity-Relationship Diagram (ERD)

entity-relationship diagram, ER-diagram, database ERD
Entity-Relationship Diagram (ERD) solution extends ConceptDraw PRO software with templates, samples and libraries of vector stencils from drawing the ER-diagrams by Chen's and crow’s foot notations.

Example of Organizational Chart

Example of Organizational Chart - Lots of organization chart examples created by ConceptDraw Organizational Chart Software. Include company organizational chart, hospital organizational chart, hotel Organizational chart, corporate organizational chart samples etc
How to draw an Organizational Chart
How to draw an Organizational Chart

Home area networks (HAN). Computer and Network Examples

A Home Area Networks (HAN) is a type of local area network that is used in an individual home. The home computers can be connected together by twisted pair or by a wireless network. HAN facilitates the communication and interoperability among digital devices at the home, allows to easier access to the entertainments and increase the productivity, organize the home security.
This example was created in ConceptDraw PRO using the Computer and Networks Area of ConceptDraw Solution Park and shows the home network diagram.

Credit Card Order Process Flowchart. Flowchart Examples

This sample was created in ConceptDraw PRO diagramming and vector drawing software using the Flowcharts solution from the What is a Diagram area of ConceptDraw Solution Park.
This sample shows the Flowchart of the Credit Card Order Process. On this diagram are used the flowchart symbols that represents the processes and documents. The flowchart symbols are connected with arrows.