This site uses cookies. By continuing to browse the ConceptDraw site you are agreeing to our Use of Site Cookies.
"Causes in the diagram are often categorized, such as to the 6 M's ...
The 6 Ms (used in manufacturing industry):
(1) Machine (technology);
(2) Method (process);
(3) Material (Includes Raw Material, Consumables and Information.);
(4) Man Power (physical work)/ Mind Power (brain work): Kaizens, Suggestions;
(5) Measurement (Inspection);
(6) Milieu/ Mother Nature (Environment).
The original 6Ms used by the Toyota Production System have been expanded by some to include the following and are referred to as the 8Ms. However, this is not globally recognized. It has been suggested to return to the roots of the tools and to keep the teaching simple while recognizing the original intent; most programs do not address the 8Ms.
(7) Management/ Money Power;
(8) Maintenance." [Ishikawa diagram. Wikipedia]
This 8Ms Ishikawa diagram (manufacturing cause and effect diagram) template is included in the Fishbone Diagram solution from the Management area of ConceptDraw Solution Park.
8Ms Ishikawa diagram
8Ms Ishikawa diagram, effect, cause, category,
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.
Bank account UML package diagram
Bank account UML package diagram, uml 2.5 class, package, generalization,