Study About UML Diagram

• UML Diagram List
  UML Class Diagram, UML Component (Structure) Diagram, UML Deployment Diagram
• Most Common UML Notation
  Study about Notes and Stereotypes
• UML Vocabulary List
• Apa Itu UML Diagram
  Mempelajari tipe-tipe diagram UML, Class Diagram, Package Diagram, Object Diagram, Component Diagram, Composite Structure Diagram, Deployment Diagram, Activity Diagram, Sequence Diagram, Use Case Diagram, State Diagram / Statechart Diagram / State Machine Diagram, Communication Diagram / Collaboration Diagram, Interaction Overview Diagram, Timing Diagram, dan manfaat UML Diagram.

Use Case Diagram:

• Use Case Diagram ( uml )
  System, Use Case, Actors
• Use Case Diagram 2 ( UML )
  Use case, Actor, Extension, Stereotypes
• Use Case Diagram Notation 1 ( UML )
• Tabel Identifikasi Use Case Dalam AsciiDoctor
• Tabel Identifikasi Aktor Use Case Dalam Markdown

Class Diagram and Object Diagram:

Class Diagram ( UML )

Class Diagram ( UML ) 2

Object Diagram ( UML )

Other Structure Diagrams:

Component Diagram ( UML )

Deployment Diagram ( UML )

Behavioral Diagrams:

Activity Diagram ( UML )

Activity Diagram ( UML ) 2

State Diagram ( UML )

View Of State Chart Diagram  ( UML )

Interaction Diagram:

Sequence Diagram ( UML )

Sequence Diagram ( UML ) 2

PlantUML:

• PlantUML Local Installation
• Check PlantUML Installation
• Format File Extension For PlantUML
• Hello World In PlantUML
• ERD In PlantUML
• PlantUML Sequence Diagram Message Arrow 1
• PlantUML Code About CMS
• Salt Plant UML For ComboBox 1
• Table Creole PlantUML About Microsoft Excel Arithmetic Operator
• Flowchart JS Symbols List
• Simple Ecommerce Website Navigation Diagram In Plant UML

Business Process

• A Kind Of Process Model In Technology
• Typical Operating Events In Business Process

unified modeling language, uml chart, software engineer, software developer,

Related Post

• Microsoft Visio Diagram And Chart List
• DDL, DQL, DML, DCL and TCL Commands
• Top Database Comment Syntax 1
• Two Dimensional Shape

Most Common UML Notation

Notes

• Notes allow you to enter additional comments that are not captured in your diagrams. You can write anything you want in a note to explain your diagram, similar to a comment in code. 
• Notes are pictured with the folded rectangle notation.

Stereotypes

• Stereotypes signify a special use or intent and can be applied to almost any element of UML notation.
• Stereotypes modify the meaning of an element and describe the element's role within your model.
• A stereotype sometimes has an associated icon, such as stick-figure actor symbol.
• The stereotype is shown using guillemots at either end of the stereotype name, as in «stereotype_name». However, because guillemots require an extended character set, you can substitute them for angle brackets, as in <<stereotype_name>>.
• There is no limit to the number of stereotypes with which an element can be associated; sometimes you may end up specifying more than one stereotype.
• The UML specification defines a set of "standard" or predefined stereotypes. Some of the more useful standard stereotypes include:
• utility: Represents a class that provides utility services through static methods, just as Java's Math class.
• service: A stateless, functional component that computes a value; could be used to represent a web service.
• subsystem: A large component that is actually a subordinate system of a larger system.

<< back to  Study About UML Diagram

Unified Modelling Language ( UML ), uml modelling, uml diagram, uml chart, program design, software design, application design

Related Post

• UML Diagram List
• UML Vocabulary List
• Class Diagram ( UML )
• Class Diagram ( UML ) 2
• Component Diagram ( UML )
• Deployment Diagram ( UML )
• Object Diagram ( UML )
• Use Case Diagram ( UML )
• Use Case Diagram ( UML ) 2
• Use Case Diagram Notation 1 ( UML )
• Activity Diagram ( UML )
• State Diagram ( UML )
• State Diagram ( UML ) 2
• Sequence Diagram ( UML )
• Collaboration Diagram ( UML )
• DDL, DQL, DML, DCL and TCL Commands
• ER-Model Of A Database
• Post about UML

UML Diagram List

UML Diagram Hierarchy:

• Structure Diagrams:
• Class Diagram
• Component (Structure) Diagram
• Deployment Diagram
• Object Diagram
• Package Diagram
• Profile Diagram
• Composite Structure Diagram
• Behavioral Diagrams:
• Use Case Diagram
• Activity Diagram
• State Machine Diagram
• Interaction Diagram:
• Sequence Diagram,  
• Communication Diagram
• Interaction Overview Diagram:
• Timing Diagram

to learn more about Use Case Diagram (UML) click 

• Use Case Diagram ( uml )

• Use Case Diagram Notation 1 ( UML )

to learn more about Sequence Diagram (UML) click 

• Sequence Diagram ( UML ) 

• Sequence Diagram ( UML ) 2

Bibliography:

https://www.ibm.com/

https://www.visual-paradigm.com/

https://www.researchgate.net/

https://www.uu.se/ ( university )

Unified Modelling Language ( UML ), uml modelling, uml diagram, uml chart, program design, software design, application design

Related Post:

• State Diagram ( UML )
• Object Diagram ( UML )
• Component Diagram ( UML )
• Object Diagram ( UML )
• Activity Diagram ( UML )
• Deployment Diagram ( UML )
• Class Diagram ( UML )
• Collaboration Diagram ( UML )
• Post about UML
• Flowchart Symbol List
• DDL, DQL, DML, DCL and TCL Commands
• Top Database Comment Syntax 1

Apa Itu UML Diagram

Apa itu Diagram UML?

UML  (Unified Modelling Language) adalah cara memvisualisasikan software program menggunakan kumpulan diagram. Notasi ini telah berkembang untuk digunakan pada desain object oriented, tetapi sejak itu telah diperluas untuk mencakup berbagai macam proyek software engineering. Saat ini, UML diterima oleh Object Management Group (OMG) sebagai standar untuk pemodelan pengembangan software.

Tipe-Tipe Diagram UML

Standar UML saat ini menyerukan 13 jenis diagram yang berbeda:

class diagram, activity diagram, object diagram, use case diagram, sequence diagram, package diagram, state diagram, component diagram, communication diagram, composite structure diagram, interaction overview diagram, timing diagram, and deployment diagram.

Diagram ini diorganisasikan menjadi dua kelompok berbeda: Structural Diagram dan Behavioral Diagram.

• Structural UML diagrams
• Class diagram
• Package diagram
• Object diagram
• Component diagram
• Composite structure diagram
• Deployment diagram
• Behavioral UML diagrams
• Activity diagram
• Sequence diagram
• Use case diagram
• State diagram
• Communication diagram
• Interaction overview diagram
• Timing diagram.

Class Diagram

• Class Diagram adalah tulang punggung hampir setiap metode object oriented, termasuk UML.
• Class Diagram menggambarkan static structure suatu sistem.
• Class diagram atau diagram kelas merupakan suatu diagram yang digunakan untuk menampilkan kelas-kelas berupa paket-paket (packets) untuk memenuhi salah satu kebutuhan paket yang akan digunakan nantinya.
• Namun, pada Class diagram desain modelnya dibagi menjadi 2 bagian.
• Class diagram yang pertama merupakan penjabaran dari domain model yang merupakan abstraksi dari basis data.
• Class diagram yang kedua merupakan bagian dari modul program, contohnya metode pemrograman MVC pattern (Model View Controller), dimana terdapat boundary presentation class sebagai class interface, class control sebagai tempat ditemukannya algoritma, dan class entity sebagai tabel dalam basis data dan query program.

Package Diagram

• Package Diagram bagian dari class diagram, tetapi pengembang terkadang memperlakukannya sebagai teknik terpisah.
• Package Diagram hadir sebagai solusi untuk memudahkan organisasi dan pemetaan elemen-elemen dalam sistem tersebut.
• Package Diagram mengatur elemen-elemen suatu sistem ke dalam kelompok-kelompok terkait  dalam unit yang lebih kecil untuk meminimalkan ketergantungan antar package.

Object Diagram

• Object Diagram digunakan untuk menggambarkan sebagian atau seluruh static structure diagram ( UML  structural diagram ) dari suatu sistem pada waktu tertentu. Object Diagram dapat digunakan untuk menguji kelengkapan dan keakuratan class diagram.
• Object Diagram menggambarkan hubungan dan struktur objek pada waktu tertentu, contoh selama eksekusi.
• Object Diagram ini dapat memudahkan tim memahami perilaku dan interaksi objek yang terlibat, baik selama pengembangan maupun analisis masalah.
• Object Diagram biasanya digunakan untuk mengidentifikasi informasi mengenai elemen model tertentu untuk menunjukkan contoh spesifik dari pengklasifikasikan yang diperlukan.

Component diagram

• Component Diagram menjelaskan organisasi software component fisik, termasuk source code, run-time (biner)  code, interface yang tersedia, port dengan hubungan di antaranya dan file yang dapat dieksekusi.
• Component Diagram ini biasa digunakan dalam pengembangan perangkat lunak untuk menggambarkan struktur ( UML structural diagram ) dan hubungan antar komponen dalam sistem agar lebih mudah dianalisis.
• Component Diagram membantu dalam visualisasi, spesifikasi, dan dokumentasi sistem berbasis komponen juga membangun sistem yang dapat dieksekusi melalui forward engineering dan reverse engineering.

Composite Structure Diagram

• Composite Structure Diagrammerupakan bagian dari structural Unified Modeling Language (UML) diagram untuk menunjukkan bagian dalam kelas atau komponen.
• Composite Structure Diagram ini berguna untuk memvisualisasikan interaksi antara objek dan elemen internal dari suatu kelas, terutama ketika elemen tersebut memiliki peran yang berbeda dalam komunikasi.
• Composite Structure Diagram dapat mendokumentasikan dan memvisualisasikan hubungan internal yang tidak terlihat pada diagram kelas, dengan menggunakan elemen, seperti objek, port, dan konektor untuk menunjukkan komunikasi antar objek.

Deployment Diagram

• Deployment Diagram menggambarkan sumber daya fisik dalam suatu sistem, termasuk node, component, dan koneksi.
• Deployment diagram menjadi salah satu jenis UML diagram yang memainkan peran penting dalam mendeskripsikan bagaimana komponen software saling berinteraksi dengan komponen lainnya.
• Deployment diagram adalah diagram yang berfungsi untuk menggambarkan penempatan (deployment) komponen software dalam perangkat keras.

Activity Diagram

• Activity Diagram menggambarkan sifat dinamis suatu sistem dengan memodelkan aliran control dari satu activity ke activity lainnya.
• Suatu activity mewakili suatu operasi atau proses pada beberapa class dalam sistem yang mengakibatkan perubahan pada state sistem. Biasanya, aktivitas dari activity diagram digunakan untuk memodelkan workflow atau proses bisnis dan operasi internal.
• Seperti layaknya runtutan proses berjalannya suatu sistem dan digambarkan secara vertikal.
• Activity diagram adalah salah satu contoh diagram dari behavioral UML dalam pengembangan dari Use Case.

Sequence Diagram

• Sequence Diagram menggambarkan interaction antar class atau objek dalam hal pertukaran message dari time ke time atau berdasarkan urutan waktu.
• Sequence dapat menggambarkan urutan atau tahapan yang harus dilakukan untuk dapat menghasilkan sesuatu, seperti yang tertera pada Use Case diagram.

Use Case Diagram

• Use Case Diagram adalah satu jenis dari diagram UML (Unified Modelling Language).
• Use Case Diagram memodelkan fungsionalitas suatu sistem menggunakan actor dan use case.
• Use Case Diagram menggambarkan hubungan interaksi antara sistem dan aktor/pengguna.

State Diagram / Statechart Diagram / State Machine Diagram

• Statechart Diagram, yang sekarang dikenal sebagai State Machine Diagram dan State Diagram, menggambarkan behavior dinamis suatu sistem dalam menanggapi rangsangan external. State Diagram terutama berguna dalam pemodelan objek reaktif yang statenya dipicu oleh event tertentu.
• Statemachine yaitu salah satu jenis diagram pada UML yang berfungsi untuk menggambarkan transisi serta perubahan pada suatu objek pada sistem.

Communication Diagram / Collaboration Diagram

• Communication Diagram memodelkan interaction antara object secara sequence.
• Communication Diagram menggambarkan static structure dan behavior dinamis suatu sistem. Dalam banyak hal, Communication Diagram adalah versi sederhana dari collaboration diagram yang diperkenalkan dalam UML 2.0.
• Communication Diagram memodelkan kolaborasi antara object-object atau peranan yang mengirimkan fungsionalitas dari use cases dan operasi-operasinya.
• Mekanisme Model Communication Diagram dalam architectural design dari suatu system.

Interaction Overview Diagram

• Interaction Overview Diagram merupakan kombinasi activity diagram dan sequence diagram. 
• Interaction Overview Diagram memodelkan serangkaian actiondan memungkinkan Anda mendekonstruksi interaction yang lebih kompleks menjadi kejadian yang dapat dikelola. Anda harus menggunakan notasi yang sama pada Interaction Overview Diagram seperti yang Anda lihat pada activity diagram.
• Interaction Overview Diagram dapat memungkinkan analisis interaksi antar objek atau elemen , mengidentifikasi masalah potensial, dan memiliki fungsi sebagai alat komunikasi untuk pemangku kepentingan (stakeholder) non-teknis.

Timing Diagram

• Timing Diagram adalah jenis diagram UML behavior atau interaction yang berfokus pada proses yang terjadi selama periode time tertentu.
• Timing Diagram adalah contoh khusus dari sequence diagram, kecuali time ditunjukkan meningkat dari kiri ke kanan, bukan dari atas ke bawah.

Manfaat UML Diagram

Berikut adalah beberapa manfaat membuat UML diagram:

1. Membantu Pengambilan Keputusan: Dengan membuat UML diagram, tim pengembang dan perancang software dapat menentukan jenis infrastruktur fisik mengenai apa yang dibutuhkan, seperti apakah sistem harus di-hosting di cloud, server fisik, atau di keduanya.
2. Memudahkan Pengembangan Dan Pemeliharaan: UML diagram juga dapat memudahkan dalam memahami bagaimana komponen dalam software saling berinteraksi, sehingga pengembang dapat lebih mudah memecahkan masalah saat sistem berkembang.
3. Meminimalisir Resiko Kesalahan: Dengan penggambaran visual yang tepat, tim pengembang dapat menghindari kesalahan dalam penempatan komponen produk atau kesalahan konfigurasi yang dapat menyebabkan downtime.
4. Memudahkan Pemahaman Fungsi Komponen Atau Elemen: Tiap-tiap komponen dalam diagram memiliki tugas tertentu dalam sistem, pada aspek ini UML diagram dapat membantu memperjelas tanggung jawab masing-masing komponen sehingga lebih mudah memahami peran mereka dalam sistem secara menyeluruh.
5. Dapat memberikan bahasa pemodelan visual atau gambar kepada para pengguna dari berbagai macam pemrograman maupun proses umum rekayasa.
6. Menyatukan informasi-informasi terbaik yang ada dalam pemodelan.
7. Memberikan suatu gambaran model atau sebagai bahasa pemodelan visual yang ekspresif dalam pengembangan sistem.
8. Tidak hanya menggambarkan model sistem software saja, namun dapat memodelkan sistem lain, seperti sistem berorientasi objek.
9. Mempermudah pengguna untuk membaca suatu sistem.
10. Berguna sebagai blueprint, jelas ini nantinya menjelaskan informasi yang lebih detail dalam perancangan berupa coding suatu program.
11. Panduan Implementasi: UML diagram dapat membantu pengembang saat membangun dan menguji suatu sistem, serta memberikan pedoman dalam representasi sistem pada kode. 
12. Dukungan Pengujian Integrasi: Memiliki fasilitas pengujian integrasi dengan memvisualisasikan hubungan antar-objek dalam sistem dan memastikan sebuah komponen dapat bekerja secara efektif.
13. Validasi Kode: Pengembangan dapat menggunakan diagram ini untuk memastikan sebuah konsistensi antara kode dan sebuah desain. 
14. Ilustrasi Skenario: Diagram objek dapat menggambarkan sebuah skenario atau kasus penggunaan, serta memvisualkan perilaku sistem dalam berbagai keadaan.
15. Mengelola Kompleksitas: Dengan membagi sistem besar menjadi unit yang lebih kecil, analisis dan desain bisa lebih disederhanakan.
16. Komunikasi yang Lebih Efektif: UML Diagram ini mempermudah tim untuk memahami komponen mana saja yang terkait dan bagaimana relasi antar paket berlangsung.

< back to Study About UML Diagram

technical interview, coding qna, most technology question and answer, concept, managerial theory

Bibliography

https://www.conceptdraw.com/

https://www.dicoding.com/

https://www.lawencon.com/

https://www.smartdraw.com/

https://www.sjsu.edu/ ( university )

https://www.visual-paradigm.com/

UML Vocabulary List

These are UML ( Unified Modelling Language ) Vocabulary List:

• Basic Components:
• Structure
• Use Case
• Class
• Active Class
• Interface
• Component
• Collaboration
• Node
• Component
• Interaction Diagram
• State Machine Diagram
• Group
• Model Geographic Boundaries ( Activity Partition )
• Worker Responsibilities ( Swim Lanes )
• Complex Transactions ( State Chart / State Chart Machine Diagram )
• Package
• Model
• Sub system
• Framework
• Annotation
• Notes
• Relations:
• Dependencies
• Associations
• Generalisation
• Diagrams
• Extention Mechanisms

unified modelling language, business process modelling

Related Post

• UML Diagram List
• Class Diagram ( UML )
• Class Diagram ( UML ) 2
• Component Diagram ( UML )
• Deployment Diagram ( UML )
• Object Diagram ( UML )
• Use Case Diagram ( UML )
• Use Case Diagram ( UML ) 2
• Use Case Diagram Notation 1 ( UML )
• Activity Diagram ( UML )
• State Diagram ( UML )
• State Diagram ( UML ) 2
• Sequence Diagram ( UML )
• Collaboration Diagram ( UML )
• Post about UML
• DDL, DQL, DML, DCL and TCL Commands
• ER-Model Of A Database
• Post about ERM

Sequence Diagram ( UML )

Notations used in Sequence Diagram are as follows:

Class Role: It describe the way an object should behave in context. The uml object symbol to show class roles, but don’t list object attributes.

Activation: By this box the time taken by the object to complete a task is represented.

Messages: It is used to represent communication between objects.

Lifelines: Lifelines are vertical dashed lines that indicate the object's presence over time.

Destroying Objects: Objects can be terminated early using an arrow labeled "<< destroy >>" that points to an X.

Loops: A repetition or loop within a sequence diagram is depicted as a rectangle. Place the condition for exiting the loop at the bottom left corner in square brackets [ ].

Next Sequence Diagram ( UML ) 2 >

Unified Modelling Language ( UML ), program design, software design, application design

Related Post:

• UML Diagram List
• State Diagram ( UML )
• Component Diagram ( UML )
• Object Diagram ( UML )
• Activity Diagram ( UML )
• Deployment Diagram ( UML )
• Class Diagram ( UML )
• Collaboration Diagram ( UML )
• Use Case Diagram ( uml )
• Use Case Diagram Notation 1
• Sequence Diagram ( UML )
• Post about UML Diagram
• DDL, DQL, DML, DCL and TCL Commands
• Top Database Comment Syntax 1
• Some Useful Running Application Using Windows Run
• Launching Windows Special Folders
• Environment variable 1
• Common Windows Run Commands 1
• How To Check Your Java Version
• How To Check Your Python Version
• How To Check PHP Version
• Check MikTex ( Latex ) Package Version

Use Case Diagram ( uml )

System: Draw your system's boundaries using a Rectangle that contains use cases. Place actors outside the System's Boundaries.

Use Case: Draw use cases using Ovals. Label with ovals with verbs that represent the system's Functions.

Actors: Actors are the Users of a system. When one system is the actor of Another System, label the actor system with the actor Stereotype.

Next  Use Case Diagram ( UML ) 2 >

Unified Modelling Language ( UML ), chart, diagram, hierarchy, program design, software design, application design, program analyst

Related Post:

• Sequence Diagram ( UML )
• State Diagram ( UML )
• Object Diagram ( UML )
• Component Diagram ( UML )
• Object Diagram ( UML )
• Activity Diagram ( UML )
• Deployment Diagram ( UML )
• Class Diagram ( UML )
• Collaboration Diagram ( UML )
• Use Case Diagram Notation 1
• Post about Use Case
• UML Diagram List
• Post about UML
• DDL, DQL, DML, DCL and TCL Commands
• Top Database Comment Syntax 1
• Two Dimensional Shape

Activity Diagram ( UML )

Diagram Notation

Action: It is represented as rounded rectangles.

Decision or Condition: It is represented as Diamond shape.

Initial state: A black circle which represent the start of the workflow.

Final State: A black circle inside a white circle which represent the final point of the workflow.

A flow: Line with arrow.

Swimlanes: Two parallel lines, either horizontal or vertical, and a name labeling the partition in a box at one end represent an activity partition or activity group.

Unified Modelling Language ( UML ), UML symbol, program design, software design, application design

Related Post:

• UML Diagram List
• State Diagram ( UML )
• Object Diagram ( UML )
• Component Diagram ( UML )
• Object Diagram ( UML )
• Activity Diagram ( UML )
• Deployment Diagram ( UML )
• Class Diagram ( UML )
• Collaboration Diagram ( UML )
• Use Case Diagram ( uml )
• Use Case Diagram Notation 1
• Sequence Diagram ( UML )
• DDL, DQL, DML, DCL and TCL Commands
• Top Database Comment Syntax 1
• Flowchart Symbol List
• Some Useful Running Application Using Windows Run
• Launching Windows Special Folders
• Environment variable 1
• Common Windows Run Commands 1
• How To Check Your Java Version
• How To Check Your Python Version
• How To Check PHP Version
• Check MikTex ( Latex ) Package Version

Component Diagram ( UML )

Components

Relationships

Assembly Connector

Ports

Unified Modelling Language ( UML ), UML Symbol, program design, software design, application design

Related Post:

• UML Diagram List
• State Diagram ( UML )
• Object Diagram ( UML )
• Component Diagram ( UML )
• Object Diagram ( UML )
• Activity Diagram ( UML )
• Deployment Diagram ( UML )
• Class Diagram ( UML )
• Collaboration Diagram ( UML )
• Use Case Diagram ( uml )
• Use Case Diagram Notation 1
• Sequence Diagram ( UML )
• DDL, DQL, DML, DCL and TCL Commands
• Top Database Comment Syntax 1
• Some Useful Running Application Using Windows Run
• Launching Windows Special Folders
• Environment variable 1
• Common Windows Run Commands 1
• How To Check Your Java Version
• How To Check Your Python Version
• How To Check PHP Version
• Check MikTex ( Latex ) Package Version

Use Case Diagram 2 ( UML )

Use Case Diagram: shows the interaction between the system and the system users.

Diagram Name: Use Case Diagram

Element Names: Actor, Relationship Link / Relationship Line

Element Names for most common relationship is:  ...

question: Fill in the blank !

the answer is in the comment of this post.

Bibliography:

Java For Dummies by Barry Burd.

Spring Boot 2 by Jens Boje.

Head First Java by Kathy Sierra, et al.

Java for Aliens by Claudio De Sio Cesari, et al.

UML 2 For Dummies by Michael Jesse.

Uml: A Beginner's Guide by Jason Roff, et al.

Database management systems by K. Laxmi Narayanamma.

https://www.ibm.com/

unified modelling language ( uml ), program design, software design, application design

Related Post:

• Use Case Diagram ( uml )
• Use Case Diagram Notation 1
• Sequence Diagram ( UML )
• State Diagram ( UML )
• Object Diagram ( UML )
• Component Diagram ( UML )
• Object Diagram ( UML )
• Activity Diagram ( UML )
• Deployment Diagram ( UML )
• Class Diagram ( UML )
• Collaboration Diagram ( UML )
• DDL, DQL, DML, DCL and TCL Commands
• Top Database Comment Syntax 1
• Two Dimensional Shape

Package Diagram ( UML ) 2

Package

Package Namespaces

Related Post:

• UML Diagram List
• State Diagram ( UML )
• Object Diagram ( UML )
• Component Diagram ( UML )
• Object Diagram ( UML )
• Activity Diagram ( UML )
• Deployment Diagram ( UML )
• Class Diagram ( UML )
• Collaboration Diagram ( UML )
• Use Case Diagram ( uml )
• Use Case Diagram Notation 1
• Sequence Diagram ( UML )
• DDL, DQL, DML, DCL and TCL Commands

Microsoft Visio Diagram And Chart List

Microsoft Office Visio 2007

Open Microsoft Visio then from menu bar:

Template Categories:

File > New > Flowchart > Basic Flowchart ( Algorithm Chart, Process/System Flow Chart )

File > New > Flowchart > Cross Functional Flowchart ( Swimlane Diagram - BPMN Diagram )

File > New > Flowchart > Data Flow Diagram ( DFD - DeMarco and Yourdon )

File > New > Business > Organization Chart

File > New > Business > Brainstorming Diagram ( MindMap )

File > New > Software and Database > Database Model Diagram ( ERD/ERM - Entity Relationship Diagram / Entity Relationship Modelling )

File > New > Software and Database > Data Flow Model Diagram ( DFD - Gane Sarson )

File > New > Software and Database > UML Model Diagram ( Unified Modelling Language )

Shapes ( Stencil )

Visio stencil file format: *.vss

File > Shapes > Flowchart > Basic Flowchart Shapes ( Algorithm Chart, Process/System Flow Chart )

File > Shapes > Flowchart > Cross Functional Flowchart

File > Shapes > Flowchart > Data Flow Diagram Shapes ( DFD - DeMarco and Yourdon )

File > Shapes > Business > Organization Chart > Organization Chart Shapes

File > Shapes > Business > Brainstorming Shapes ( MindMap )

File > Shapes > Software and Database > Database > Entity Relationship ( ERD/ERM - Entity Relationship Diagram / Entity Relationship Modelling )

File > Shapes > Software and Database > Software > Gane Sarson ( DFD - Gane Sarson )

File > Shapes > Software and Database > Software > UML Activity

File > Shapes > Software and Database > Software > UML Collaboration

File > Shapes > Software and Database > Software > UML Component

File > Shapes > Software and Database > Software > UML Deployment

File > Shapes > Software and Database > Software > UML Sequence

File > Shapes > Software and Database > Software > UML Statechart

File > Shapes > Software and Database > Software > UML Static Structure ( Class, Object, Package )

File > Shapes > Software and Database > Software > UML Use Case

Bibliography

https://en.wikipedia.org/

https://medium.com/

https://support.microsoft.com/

Related Post:

• UML Diagram List
• Post Belajar Database Dan SQL Di Website Ini
• Post About Database

View Of State Chart Diagram

Table View State And Transitions Of State Chart Diagram On UML:

Table 1. Table View Of States And Transitions on UML Notation

State/Trigger	Trigger 1	Trigger 2
State name 1	Transition 1	Transition 2
State name 2	Transition 3	Transition 4

Next State Diagram ( UML ) >

program design, software design, low-code application development, software requirement specification document, srs document

Related Post

• UML Diagram List
• UML Vocabulary List
• Most Common UML Notation
• Post about UML
• DDL, DQL, DML, DCL and TCL Commands
• ER-Model Of A Database
• Post about ERM

State Diagram ( UML )

State (Chart/Machine) Diagram

Purpose

It is used to model dynamic nature of the system.

State diagram is used to describe the life time of an object.

By the use of state diagram the state machine is defined to model states of an object.

Next  State Diagram ( UML ) 2 >

Unified Modelling Language

Related Post:

• UML Diagram List
• UML Vocabulary List
• Most Common UML Notation
• Class Diagram ( UML )
• Post about UML
• DDL, DQL, DML, DCL and TCL Commands
• Aktivitas Kebugaran Jasmani
• Datagrid Visual Basic Classic 1
• ListView Properties
• Microsoft Windows Common Control 6
• Microsoft Visual Basic 6 Data Binding Object
• Fungsi File Dalam Visual Basic 6

Class Diagram ( UML ) 2

Relations between classes are consist of:

• Aggregation
• Composition
• Extension
• Dependencies
• Realizations

Class Relation Label

Cardinality/Multiplicity: one, many or more

Class Field

Class Method

Class Field Visibility: private, protected, package private, public.

Class Method Visibility: private, protected, package private, public.

Class Field Modifier: abstract, static.

Class Method Modifier: abstract, static.

Class Stereotypes.

Class Modifier: abstract, interface, enum.

Class Relations

Class Relations: aggregation, composition, extension

Class Relations: dependencies, realization

Class Field Visibility / Class Method Visibility

+ public, - private, # protected, / derived, ~ package private

to learn the name of Class Field Visibility / Class Method Visibility symbol notation and the unicode character of  Class Field Visibility / Class Method Visibility symbol notation, click:

• Symbol And Syntax >
• Symbol And Syntax 2 >

< Previous  Class Diagram ( UML )

class member notation

Bibliography

http://www.sjsu.edu/ ( university )

http://www.uni-muenchen.de/ ( university )

https://www.visual-paradigm.com/

Related Post:

• Collaboration Diagram ( UML )
• Use Case Diagram ( uml )
• Use Case Diagram Notation 1
• Sequence Diagram ( UML )
• UML Diagram List

State Diagram ( UML ) 2

State Diagram consist of:

State drawn as rounded rectangle.

Starting Point drawn as a filled circle.

Ending Point drawn as two concentric circles with a filled inner circle.

Transition drawn as arrow.

Event / Trigger is text that written along the Transition arrow.

Internal Behavior is any behavior that happens while the object is in a state. Internal behavior is written as label / behavior. The label indicates when the behavior executes in other words, events or circumstances causing the behavior. There are three special labels: entry, exit, and do.

Internal transition is a transition that causes a reaction within a state, but doesn't cause the object to change states. Internal transitions are written as trigger [guard] / behavior, and they are listed inside a state.

Composite States

Concurent States

< Previous State Diagram ( UML )

Related Post

• UML Diagram List
• UML Vocabulary List
• Most Common UML Notation
• Post about UML
• DDL, DQL, DML, DCL and TCL Commands
• ER-Model Of A Database
• Post about ERM
• Post about Database

Activity Diagram ( UML ) 2

Activity Diagram

Starting point / Initial Node is shown as A Black Circle shape.

Ending point / Final Node is shown as A Black Circle Inside A White Circle shape.

The Flow Of The Activity / Flow Transition is shown as Single Headed Arrow shape.

• Control Flow is shown as a Solid Line Arrow shape from a source action state to a target action state.
• Object Flow is shown as a Dashed Arrow between an action state and an object.

Activity or Action is shown as Rounded Rectangles shape.

Guard Label / Label Arrow is shown as a Text Inside Angle Bracket.

Control Flow in Activity Diagram consist of:

• Decision / Branches Node is shown as Diamond shape with an incoming edge and presents them to multiple outgoing edges..
• Merge Node is shown as Diamond shape with multiple incoming edges and a single outgoing edge.

Object Node is shown as Rectangle shape.

Parallel Processing: Fork ( the flow of the activity ), Join ( the flow of the activity ), Synchronization Bars.

Parallel Processing consist of:

• Forks are represented by a horizontal or vertical bar ( Synchronization Bars ) with multiple outgoing edges, with each edge leading to a different activity node.
• Join are represented with the concurrent flows merge back as a a single flow of control into a horizontal or vertical bar ( Synchronization Bars ) .
• Synchronization Bars are represented by the heavy horizontal or vertical Solid Line shape.
• Paralel Activity / Concurrent Threads Of Control is represented by Rounded Rectangles shape.

Parallel Processing functions consist of:

• Modeling Parallel Processes.
• Resource Allocation.
• Workflow Management.
• Load Balancing.

Partitions / Swimlane Heading is shown as Labeled Text Inside A Rectangle shape at the top / left with the element responsible / role responsibilities.

Swimlanes has the visual similarity between the horizontal rows / vertical columns of the diagram to that of the swimlanes found within a swiming pool. Swimlanes is shown as a visual region separated from neighboring swimlanes by vertical / horizontal solid lines on both sides and labeled at the top / left with the element responsible for action states within the swimlane.

activities diagram, activity chart, activity modeling, Unified Modelling Language ( UML ), UML symbol

Bibliography

https://binus.ac.id/ ( university )

https://sparxsystems.com/

https://support.microsoft.com/

https://www.visual-paradigm.com/

https://www.softwareideas.net/

John W. Satzinger, Robert B.Jackson, Stephen D.Burd. Systems Analysis And Design In A Changing World. Boston: Cengage Learning.

Larman, Craig. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development. Boston: Addison Wesley Professional.

Mall, Rajib. Fundamentals Of Software Engineering. Delhi: Prentice Hall.

Pressman, Roger S. Software engineering : A Practitioner’s Approach. New York: McGraw-Hill.

Whitten, Jeffrey L, Lonnie D.Bentley. Systems Analysis And Design Methods. New York: McGraw-Hill.

Related Post

• Activity Diagram ( UML )
• UML Diagram List

Sequence Diagram ( UML ) 2

An arrow is a message between two participants.

message in sequence diagram

 

Participants consist of:

actor / participant in sequence diagram

---

boundary

boundary participant in sequence diagram

---

control

control participant in sequence diagram

---

communication

communication entity participant in sequence diagram

---

database

database participant in sequence diagram

Notes: database participant can be change to (rectangle/square) entity participant.

< Previous Sequence Diagram ( UML )

Bibliography:

https://sparxsystems.com/

https://www.ibm.com/

https://www.lucidchart.com/pages/flowchart-symbols-meaning-explained

https://www.plantuml.com/

Unified Modelling Language ( UML ), program design, software design, application design

Related Post:

• Sequence Diagram ( UML )
• UML Diagram List
• UML Vocabulary List

PlantUML Local Installation

Local Installation Procedure

PlantUML Installation requirements:

Java

• Requires Java (certain version) to be installed on your machine.
• Check if Java is already installed, click How To Check Your Java Version.
• If not installed, download and install it from the official Java website or through package managers e.g. apt for Ubuntu, brew for macOS, etc.

GraphViz

• Needed only for some diagrams:
• Usecase diagrams
• Class diagrams
• Object diagrams
• Component diagrams
• Deployment diagram
• State diagrams
• Legacy activity diagrams

PlantUML

• Once ready, download the plantuml.jar file.
• No further unpacking or installation procedures are needed.

Notes

If you want to Check PlantUML Installation.

If you want to initial explore to PlantUML, use the PlantUML online editor, search in the search engine (e.g. Google) or use PlantUML official online editor.

plant uml, unified modelling language, system analyst and design, textual diagram, text to diagram, textual modelling

Bibliography:

https://graphviz.org/

https://plantuml.com/ ( manual ebook )

https://www.oracle.com/

Related Post

• UML Diagram List
• UML Vocabulary List
• Most Common UML Notation
• Post about UML
• DDL, DQL, DML, DCL and TCL Commands
• ER-Model Of A Database
• Post about ERM

ERD In PlantUML

Entity Relationship Diagram ( ERD ) Notation In PlantUML 

Entity : entity Entity_Name

for example: 

entity Entity01

Attribute / Column / Field:
* identifying attribute: field_type(size_number or length_number)

*  mandatory_attribute: field_type(size_number or length_number)
optional_attribute: field_type(size_number or length_number)

Stereotype:
<<PK>>, <<FK>>, <<generated>>

field type: text, number

ERD Relations Name and ERD Relation Symbol

ERD Relations Name : ERD Relation Symbol on the left and ERD Relation Symbol on the right.

Zero or One: |o-- and   --o|

Exactly One:  ||--  and  --||

Zero or Many:  }o--  and  --o{

One or Many:  }|--  and  --|{

< Previous PlantUML Local Installation

Next >

Bibliography:

https://github.com/

https://medium.com/

https://plantuml.com/

https://stackoverflow.com/

https://windowsreport.com/

https://www.conceptdraw.com/

https://www.lucidchart.com/

https://www.smartdraw.com/

https://www.visual-paradigm.com/

erm, entity relationship modeling, erd, entity relationship diagram, er-m, information engineering relations, plant uml

Related Post

• Check PlantUML Installation
• UML Diagram List
• UML Vocabulary List
• Most Common UML Notation
• Post about UML
• DDL, DQL, DML, DCL and TCL Commands
• ER-Model Of A Database
• Post about ERM
• Post Belajar Database Dan SQL Di Website Ini
• Post About Database